#na_ontap_snapmirror module does not initialize LS mirrors

1 messages · Page 1 of 1 (latest)

deft glen
#

In below example, after playbook run, it creates both mirrors on nodeA (nA) and nodeB (nB), but only nA rootvol mirror is initialized.

I think it's only related to load sharing mirrors.
Is this a bug?

    - name: Create LS mirror of rootvol
      na_ontap_snapmirror:
        state: present
        source_volume: "{{ svm }}_rootvol"
        destination_volume: "{{ svm }}_rootvol_{{ item }}"
        source_vserver: "{{ svm }}"
        destination_vserver: "{{ svm }}"
        initialize: yes
        relationship_type: load_sharing
        schedule: hourly
        <<: *login
      loop:
        - "{{ nAmirrorvol }}"
        - "{{ nBmirrorvol }}"
glossy halo
#

I'd try setting the initialize parameter to true or True instead of yes.

deft glen
#

it's same. intialize: true

mellow crow
#

to initialise an ls mirror you use the "initialize-ls-set". this is different to normal initialize and the ansible module (and REST API) doesnt support this function last time i checked. I am using a single LS mirror now as that is latest best practice (no need for one on each node anymore). https://docs.netapp.com/us-en/ontap/data-protection/manage-snapmirror-root-volume-replication-concept.html