Table of ContentsView in Frames

Transfer of LUN clones using qtree SnapMirror

In versions earlier than Data ONTAP 7.3, SnapMirror considers each LUN clone as a new LUN. Therefore, during the initial transfer of the LUN clone, all data from the LUN clone and the original Data ONTAP LUN is transferred to the secondary system.

For descriptions of data backup and restore on volumes containing Data ONTAP LUNs, see the Data ONTAP SAN Administration Guide for 7-Mode.

The transfer of LUN clones using SnapMirror works the same way as the transfer of LUN clones using SnapVault in the non-optimized mode.
Note: Qtree SnapMirror transfers LUN clones in the non-optimized mode only. Qtree SnapMirror does not have the option of optimized transfers.
The use of snapmirror resync for restoring data to a source qtree with LUN clones is not supported. When you replicate qtrees with LUN clones, each LUN clone within the qtree is stored as a LUN within the destination qtree. Therefore, when you recover data from such a destination qtree, the original LUN clones are restored as complete LUNs.
Attention: If you attempt to recover data from the destination to a source qtree with LUN clones, using a snapmirror resync operation, the system displays the following error message:
cannot resync as qtree has one or more lun clones
Aborting resync.
To recover data for a qtree with LUN clones, you can replicate the destination qtree to a new qtree.
Attention: For a qtree with LUN clones, ensure that the volume has enough free space to store the LUN clones as complete LUNs before you initiate data recovery using qtree SnapMirror.