2016-03-03 04:59 AM
In cDOT 8.3.x, Snapmirror relationships are established within the SVM itself. Going between 8.1.x, 8.2.x and 8.3.x it seems like there are some "cosmetic" differences between how snapmirrors are established and managed, but the SVM still owns the protection policy. This is the link to the 8.3 Snapmirror best practices guide:
If you're running a previous version just make sure you grab the document for your particular cDOT in that some of the commands and/or SystemManager screens will look different.
2016-03-09 01:59 AM
Thanks for the reply, when i run the Snapmirror show command on cluster. it shows the below output and its a bit difficult to understand or if the snapmirror configuration is on SVM or volumes.
SourceLocation DestinationLocation Status MirrorState LagTime RelationshipType
-------------- ------------------- ------ ----------- ------- ----------------
PEPNS00044-PI: PEPNS00044-DR: idle snapmirrored 00:04:47 data_protection
PEPNS00044-PI:vl_VMdata PEPNS00044-DR:vc_VMdata idle snapmirrored 00:04:45 data_protection
PEPNS00044-PI:vl_home PEPNS00044-DR:vc_home idle snapmirrored 00:04:45 data_protection
PEPNS00044-PI:vl_rdshome PEPNS00044-DR:vc_rdshome idle snapmirrored 00:04:45 data_protection
PEPNS00044-PI:vl_rdsprofiles PEPNS00044-DR:vc_rdsprofiles idle snapmirrored 00:04:45 data_protection
the above output shows the SVM as well as the SVM:Volname, whereas as for as i understand it should be only SVM: but not with the volumes, if configured for SVM DR. a bit confusing for me to understand the Snapmirror configuration.
2016-03-09 05:12 AM
OK, so it means if we configure the Snapmirror DR configuration, The Snapmirror Show command will show the status of Snapmirror SVM DR along with volumes associated on the concerned SVM.
2016-03-09 11:44 AM