The SnapMirror relationship between two FlexClone volumes that have the common base snapshot helps you to achieve a SnapMirror relationship without transferring the common snapshot data again to the destination system. Both the FlexClone volumes should be created from the SnapMirror source and the corresponding SnapMirror destination volumes with a common base snapshot.
Setting up a SnapMirror relationship between the two FlexClone volumes does not consume any extra space on the parent aggregate for shared Snapshot copies. In this way, you save disk space and network resources. If you delete any of the inherited Snapshot copies from the parent system or transfer new data from the SnapMirror source clone to the SnapMirror destination clone, additional disk space is consumed.
You have two systems SystemA and SystemB. The SystemA system has a volume volA and the SystemB system has a volume volB. The volA and volB volumes are in the SnapMirror relationship where volA is the source volume and volB is the destination volume. A FlexClone volume cloneA is created from volA and a FlexClone volume cloneB is created from volB with a common base snapshot.
Establish the SnapMirror relationship between two FlexClone volumes by entering the following command on SystemB:snapmirror resync -S SystemA:cloneA cloneB
If you are updating the /etc/snapmirror.conf file on SystemB, add the following entry to the file:SystemA:cloneA SystemB:cloneB - - - - -
After updating the /etc/snapmirror.conf file, the following command establishes the SnapMirror relationship between the two FlexClone volumes:snapmirror resync cloneB