Table of ContentsView in Frames

Creating the SnapVault relationship of a mirror-SnapVault cascade

The SnapVault relationship of a mirror-SnapVault cascade requires a different configuration from a SnapVault relationship that is not a part of a mirror-SnapVault cascade.

Before you begin

About this task

The Snapshot copies that are exported to the mirror destination are ones that are created by Data ONTAP. These Snapshot copies are called "sm_created" Snapshot copies. Only these Snapshot copies are replicated from the mirror to the SnapVault backup. If the default SnapVault policy is used, the SnapVault secondary accumulates up to 251 "sm_created" Snapshot copies. The next Snapshot copy transferred after this limit is reached will be added and the oldest "sm_created" Snapshot copy will be rotated out. You can manage this retention and rotation behavior by adding a rule specifying the "sm_created" SnapMirror label to the default SnapVault policy.


  1. On the destination SVM, create a SnapVault secondary volume with a volume type DP.
    For information about creating a FlexVol volume, see the Clustered Data ONTAP System Administration Guide for Cluster Administrators.
  2. Create a SnapVault policy by using the snapmirror policy create command, or use the default SnapVault policy called XDPDefault.
    This procedure uses the XDPDefault policy in the examples.
  3. Add the sm_created snapmirror-label to the SnapVault policy by using the snapmirror policy add-rule command.
    Only the sm_created rule is observed. Any other rules associated with the SnapVault policy, such as the daily or weekly rule, are disregarded.
    The following command adds a rule to the XDPDefault policy to retain 40 sm_created Snapshot copies on the SnapVault secondary:
    vserverB::> snapmirror policy add-rule -vserver vserverC -policy 
    XDPDefault -snapmirror-label sm_created -keep 40
  4. On the destination SVM, create a SnapVault relationship and assign a SnapVault policy by using the snapmirror create command with the type XDP parameter and the policy parameter.
    The following command creates a SnapVault relationship between the primary volume srcvolB on SVM vserverB and the empty secondary volume dstvolC on SVM vserverC. It assigns the SnapVault policy named XDPDefault:
    vserverC::> snapmirror create -source-path vserverB:srcvolB
    -destination-path vserverC:dstvolC -type XDP -policy XDPDefault
  5. On the destination SVM, initialize the SnapVault relationship by using the snapmirror initialize command to start a baseline transfer.
    Note: Creating a baseline for a large amount of data can take many hours.
    The following command begins the relationship initialization by creating and transferring a baseline Snapshot copy to the secondary volume dstvolC on SVM vserverC:
    vserverC::> snapmirror initialize -destination-path