Table of ContentsView in Frames

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. You can use SnapMirror to replicate non-qtree data.

Step

  1. To use SnapMirror to replicate non-qtree data from a source to a destination, enter the following command on the destination system:snapmirror initialize -S source_system:/vol/source_volume/- dest_system:/vol/dest_volume/qtree_name
    The dash (-) character indicates all non-qtree data in the specified volume.
    Note: The snapmirror initialize command creates a destination qtree with the name specified, and then transfers the non-qtree data in the volume. The qtree must not exist before using the command, otherwise the command fails.
    Example
    Using the following command, SnapMirror transfers to the destination qtree (non_qtree_data_in_vol3 on vol4 on systemB) a complete copy of all the data in vol3 (of systemA) that is not a part of a qtree.
    systemB> snapmirror initialize -S systemA:/vol/vol3/- systemB:/vol/vol4/non_qtree_data_in_vol3
    Note: The non-qtree data can only be a SnapMirror source, never a destination. Although you can copy data from the non-qtree data to another qtree, you cannot perform a vice versa operation.

Initializing a destination for non-qtree data

If you run the snapmirror quiesce or the snapmirror break command on the destination volume (/vol/vol4/non_qtree_data_in_vol3), you can resynchronize the destination volume to the source volume.
systemB> snapmirror resync -S /vol/vol3/- /vol/vol4/non_qtree_data_in_vol3
Note: You cannot resynchronize the SnapMirror relationship in the opposite direction.