ONTAP Hardware

identity preserve set to true on volume snapmirror

madhudiwakar
4,887 Views

Hello.. I know that setting "identity-preserve" to true replicates all configuration info and permissions to the destination SVM. But what happens if I use the same flag on volume snapmirror? Does it copy any meta data ? If yes, what is it and what is the benefit of setting this flag on a volume replication? Thank you very much in advance.

1 ACCEPTED SOLUTION

Sergey_Osipov
4,816 Views

https://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-cmpr-991/snapmirror__create.html?cp=5_1_21_2

 

[-identity-preserve {true|false}] - Identity Preserve Vserver DRSpecifies whether or not the identity of the source Vserver is replicated to the destination Vserver of the Vserver SnapMirror relationship that will be created. If this parameter is set to true, the source Vserver's configuration will additionally be replicated to the destination. If the parameter is set to false, then only the source Vserver's volumes and RBAC configuration are replicated to the destination. This parameter is applicable only for SnapMirror relationships with Vserver endpoints. The default value is false.

 

Even though you can use an option with true parameter while creating regular volume level relationship it doesn't do anything and after initializing the value of the option is "-"

 

Here is an output from the lab:

::> snapmirror create -source-path svm1_cluster1:vol1 -destination-path svm1_cluster1:test -identity-preserve true

 

::> snapmirror initialize -destination-path svm1_cluster1:test

 

::> snapmirror show -destination-path svm1_cluster1:test -fields status,state,identity-preserve
source-path destination-path state status identity-preserve
------------------ ------------------ ------------ ------ -----------------
svm1_cluster1:vol1 svm1_cluster1:test Snapmirrored Idle -

 

View solution in original post

2 REPLIES 2

pedro_rocha
4,856 Views

Hi

 

This lists what gets copied with each flag:

 

https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.pow-dap%2FGUID-B9E36563-1C7A-48F5-A9FF-1578B99AADA9.html&anchor=GUID-B9E36563-1C7A-4...

 

The behavior of the flags are the same wether it is an SVM DR or Snapmirror.

 

Using SVM DR you have DR at the SVM granularity. So all the volumes are replicated and you can recover all of them on the DR site. Using the flag (identity preserve) with a snapmirror relationship enables DR at the volume level, according to the snapmirror relationships you created. I think this is why...

 

Regards,

Pedro

Sergey_Osipov
4,817 Views

https://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-cmpr-991/snapmirror__create.html?cp=5_1_21_2

 

[-identity-preserve {true|false}] - Identity Preserve Vserver DRSpecifies whether or not the identity of the source Vserver is replicated to the destination Vserver of the Vserver SnapMirror relationship that will be created. If this parameter is set to true, the source Vserver's configuration will additionally be replicated to the destination. If the parameter is set to false, then only the source Vserver's volumes and RBAC configuration are replicated to the destination. This parameter is applicable only for SnapMirror relationships with Vserver endpoints. The default value is false.

 

Even though you can use an option with true parameter while creating regular volume level relationship it doesn't do anything and after initializing the value of the option is "-"

 

Here is an output from the lab:

::> snapmirror create -source-path svm1_cluster1:vol1 -destination-path svm1_cluster1:test -identity-preserve true

 

::> snapmirror initialize -destination-path svm1_cluster1:test

 

::> snapmirror show -destination-path svm1_cluster1:test -fields status,state,identity-preserve
source-path destination-path state status identity-preserve
------------------ ------------------ ------------ ------ -----------------
svm1_cluster1:vol1 svm1_cluster1:test Snapmirrored Idle -

 

Public