Initialization of a SnapMirror destination

You must use the snapmirror initialize command to perform a complete (baseline) transfer of information whenever you start a SnapMirror source-destination relationship for the first time. This process is known as initializing a destination.

• Quotas for SnapMirror destination qtrees
  Qtree quotas apply to qtrees in a SnapMirror relationship.
• Guidelines for creating a qtree SnapMirror relationship
  When creating a qtree SnapMirror relationship, you should follow these guidelines.
• Initialization of a SnapMirror destination from tape
  You can also initialize a destination volume from tape using the snapmirror store command on the source volume and the snapmirror retrieve command on the destination volume.
• Initializing a SnapMirror destination
  To initialize a SnapMirror destination, complete the following steps.
• Space guarantee for a volume SnapMirror destination
  You can reserve space for a volume in an aggregate. You can use this feature to ensure a space guarantee for a volume SnapMirror destination.
• Initializing a destination for non-qtree data
  Non-qtree data is any data on a system that is not contained in its qtrees. Non-qtree data can include configuration and logging directories on the system (for example, /etc or /logs) that are not normally visible to system clients. It can also include directories and files on a storage system volume that has no qtree configured.
• How the snapmirror initialize command copies volumes
  When the snapmirror initalize command copies a volume, it creates a Snapshot copy of all the data on the source and transfers it to the destination. The destination is a volume that you have already created and marked restricted. After SnapMirror finishes transferring the data, it brings the destination online, but in a read-only state. This version of the destination is the baseline for the first incremental update.
• How the snapmirror initialize command copies qtrees
  To use SnapMirror to copy a qtree, you do not create a destination qtree because the snapmirror initialize command creates it. The volume where you want the destination qtree to be, must be online. After the destination qtree is initialized, it is no longer writable. However, the rest of the volume where that qtree resides is still writable.
• What happens after SnapMirror makes the initial copy to the destination
  After you initialize a SnapMirror volume replication, the files and Snapshot copies in the source volume are available on the destination.
• How to check the initialization of a volume
  To check that a destination volume has been initialized, you can use the snapmirror status command.
• Checking the initialization of a qtree
  You can check the creation and initialization of a destination qtree, by completing the following step.
• How the snapmirror initialize command matches source and destination volume size
  When you use the snapmirror initialize command to initialize a volume replication, SnapMirror sets the vol options fs_size_fixed option to on. This option forces the file system on the destination volume to remain the same size as the file system on the source volume.
• What you can do if initialization fails or is interrupted
  When an initial SnapMirror transfer fails, you can resume the transfer by re-entering the snapmirror initialize command if all the following conditions are satisfied.