Backing up qtree data

Run a complete SnapVault transfer for the specified qtrees to be backed up.

Step

At the console for the secondary storage system, enter the following command:snapvault start -S prim_system:prim_qtree_path sec_host:sec_qtree_path
The -S option specifies the primary storage system and path. This option must be set the first time the command is run for each primary storage system qtree you want to copy. It is optional when restarting an initial transfer for a previously configured qtree.

prim_system:prim_qtree_path specifies the qtree on the primary storage system to be backed up.

sec_host is the name of the destination (secondary storage system) to which the data from the primary storage system qtree is transferred. If no secondary storage system is specified, the local host’s name is used.

sec_qtree_path is the path to and includes the name of the qtree on the secondary storage system.
Note: The qtree specified for sec_qtree_name must not exist on the secondary storage system before you run the snapvault start command.

For information about snapvault start command options, see the na_snapvault(1) man page.

Example

systemB> snapvault start -S systemA:/vol/vol2/qtree3 /vol/vol1/qtree3

SnapVault creates a Snapshot copy of qtree3 in vol2 of the primary storage system (systemA), copies the data in it to the secondary storage system (systemB) at vol/vol1/qtree3, and configures the qtree for future updates.

Note: The time required for this baseline transfer is limited by the total amount of primary storage system data to be backed up and by the inode count. SnapVault can carry out initial backup at an approximate rate of 7 million inodes per hour (110,000 inodes per minute). In the first phase of a large transfer, SnapVault creates inodes, and it might appear that no activity is taking place.

Parent topic: How to start a SnapVault backup relationship