How to start a SnapVault backup relationship

After you have enabled SnapVault on both the primary and secondary storage systems and have given primary and secondary storage systems access to each other, you must specify the qtrees or volumes whose data you want transferred from the primary storage system to the SnapVault secondary storage system. You must then perform a complete (baseline) transfer of data from the primary storage system to secondary storage system.

The snapvault start command configures the SnapVault relationship between primary qtrees or volumes and secondary qtrees by specifying the following:

The primary storage system qtrees or volumes to be backed up on the storage system qtrees
The parameters for the updates from the primary storage system qtrees to the secondary storage system qtrees
These parameters include transfer speed and try count. Try count is the number of times SnapVault will attempt to start a transfer before stopping the operation.
The snapvault start command also initiates the baseline transfer of the primary storage system qtree data to the secondary storage system qtree

Guidelines for creating a SnapVault relationship
When creating a SnapVault relationship, remember the following guidelines for volumes and qtrees.
Backing up qtree data
Run a complete SnapVault transfer for the specified qtrees to be backed up.
What non-qtree data is
Non-qtree data is any data on a storage system that is not contained in its qtrees.
Backing up non-qtree data
When you back up a source volume using SnapVault, the volume is backed up to a qtree on the secondary storage system; therefore, any qtrees in the source volume become directories in the destination qtree.
What volume data backup involves
When you back up a source volume using SnapVault, the volume is backed up to a qtree on the secondary storage system; therefore, any qtrees in the source volume become directories in the destination qtree.

Parent topic: Data protection using SnapVault