Using SnapVault

What SnapVault does

SnapVault protects data resident in individual qtrees on SnapVault clients by transferring data from SnapVault client snapshots to a separate SnapVault server.

Using SnapVault with LUNs

To use SnapVault to back up LUNs, complete the following steps.

Caution
You must save contents of host file system buffers to disk before running snapvault commands on the filer.

Step	Action
1	Make sure that you followed the procedures in the Data ONTAP 6.4 Data Protection Guide for Preparing to run SnapVault Specifying the host names of SnapVault clients that are allowed to restore data from the server or creating application-consistent snapshots from the host Specifying the host name of the server on each SnapVault client, using the `snapvault.access` option Using the `snapvault snap sched` command to configure the SnapVault client snapshot schedule, if not using application-consistent snapshots created by the host Using the `snapvault snap sched -v` command to configure the SnapVault server snapshot schedule Starting SnapVault
2	From the SnapVault server, enter the following command: snapvault start [-S [source_filer:]src_qtree_path] [dest_filer:]/vol/dest_volume/dest_qtree_with_luns `-S` [source_filer:]src_qtree_path specifies the source (SnapVault client) qtree to be backed up. This option must be set the first time the command is run for each SnapVault client qtree you want to copy. dest_filer is the name of the SnapVault server to which the snapshots from the SnapVault client are transferred. If no SnapVault server is specified, the local host's name is used. dest_volume is the name of the volume on the SnapVault server to which the data from the SnapVault client is transferred. dest_qtree_path is the path to and the name of the qtree on the SnapVault server. The qtree on the SnapVault server must have the same name as the qtree on the SnapVault client server. Note If the server qtree name exists before the command runs, the command fails. Example: filerA> snapvault start -S filerB:/vol/vol2/payroll_qtree /vol/vol1/payroll_qtree Result: SnapVault creates a snapshot of payroll_qtree (which contains LUNs) in vol2 of the SnapVault client (filerB), copies the data in it to the SnapVault server (filerA) at /vol/vol1/payroll_qtree, and configures the qtree for future updates.

Step

Action

Make sure that you followed the procedures in the Data ONTAP 6.4 Data Protection Guide for

Preparing to run SnapVault
Specifying the host names of SnapVault clients that are allowed to restore data from the server or creating application-consistent snapshots from the host
Specifying the host name of the server on each SnapVault client, using the snapvault.access option
Using the snapvault snap sched command to configure the SnapVault client snapshot schedule, if not using application-consistent snapshots created by the host
Using the snapvault snap sched -v command to configure the SnapVault server snapshot schedule
Starting SnapVault

From the SnapVault server, enter the following command:

snapvault start [-S [source_filer:]src_qtree_path] 
[dest_filer:]/vol/dest_volume/dest_qtree_with_luns

-S [source_filer:]src_qtree_path specifies the source (SnapVault client) qtree to be backed up. This option must be set the first time the command is run for each SnapVault client qtree you want to copy.

dest_filer is the name of the SnapVault server to which the snapshots from the SnapVault client are transferred. If no SnapVault server is specified, the local host's name is used.

dest_volume is the name of the volume on the SnapVault server to which the data from the SnapVault client is transferred.

dest_qtree_path is the path to and the name of the qtree on the SnapVault server. The qtree on the SnapVault server must have the same name as the qtree on the SnapVault client server.

Note
If the server qtree name exists before the command runs, the command fails.

Example:

filerA> snapvault start -S 
filerB:/vol/vol2/payroll_qtree /vol/vol1/payroll_qtree

Result:

SnapVault creates a snapshot of payroll_qtree (which contains LUNs) in vol2 of the SnapVault client (filerB), copies the data in it to the SnapVault server (filerA) at /vol/vol1/payroll_qtree, and configures the qtree for future updates.

Note
If you need to update the snapshot at a time not specified in the SnapVault schedule, use the snapvault update command. See complete information in the SnapMirror chapter of the Data ONTAP 6.3 Data Protection Guide.

Reason to the SnapVault client

You might need to restore data from the SnapVault server to the SnapVault client if the data on the SnapVault client is damaged or corrupted or to migrate data from one filer to another.

After you restore data to the SnapVault client you must do one of the following:

Restart the backup process from the restored data (because you want to continue SnapVault protection of the data).
Cancel any further backups and release the resources on the SnapVault server that were used in the SnapVault relationship (because you no longer want to back up that data).

Restoring data to the SnapVault client

To restore data from the SnapVault server to the SnapVault client, complete the following step.

Step	Action
1	Enter the following command from the SnapVault client: snapvault restore [-s] [-k]] -S [source_filer:]source_qtree_path [dest_filer:]dest_qtree_path `-S` [source_filer:]source_qtree_path specifies the name of the SnapVault server from which you want to restore the data. dest_filer is the name of the SnapVault client that you want to restore to. If specified, this name must match the name of the SnapVault client. dest_qtree_path is the name of the SnapVault client qtree that you want to restore to. For more information about SnapVault options, see the Data ONTAP 6.3 Data Protection Guide.
2	If you ...	Then...
	Want to resume SnapVault backups to the newly restored qtree on the SnapVault client	Cancel backup of the newly restored qtree on the SnapVault client Go to Step 3.
	Don't want to resume SnapVault backups to the newly restored qtree on the SnapVault client	Go to Step 6.
3	From the SnapVault server, enter the following command on a single line: snapvault start -r [-s] [-k] [-S][dest_filer:]dest_qtree_path `-r` is required to restart backups from a restored SnapVault client. `-S` [source_filer:]src_qtree_path sets the new SnapVault client for the qtree. For more information about SnapVault options, see the Data ONTAP 6.4 Data Protection Guide.
4	Export the LUN to the administrative host by entering the following command: lun map lun-path igroup LUN_ID Result You are done. Example This example shows the SnapVault client (filerB) requesting data to be restored from the SnapVault server (filerA) and then the server restarting the SnapVault backup relationship: filerB> snapvault restore -S filerA:/vol/sv_vol/payroll_qtree /vol/vol1/payroll_qtree_with_luns filerA> snapvault start -r -S filerB:/vol/vol1/payroll_qtree_with_luns lun map /vol/vol_name/qtree_1/payroll_backup_lun server 3
5	Enter the following command on the server: snapvault release source_qtree_path [dest_filer:]dest_qtree_path source_qtree_path is the name of the SnapVault client snapshot that you want to release. [dest_filer:]dest_qtree_path is the name of the SnapVault server snapshot that you want to release.
6	Export the LUN to the administrative host. lun map lun-path igroup LUN_ID Result You are done. Example 2 This example shows the SnapVault client (filerB) requesting data to be restored from the SnapVault server (filerA) and then the server canceling the SnapVault backup relationship on both filers to release the resources used: filerB> snapvault restore -S filerA:/vol/sv_vol/payroll_qtree_with_luns /vol/vol1/payroll_qtree filerA> snapvault release filerB:/vol/vol1/payroll_qtree_with_luns filerA:/vol/sv_vol/payroll_qtree_with_luns lun map /vol/vol_name/qtree_1/payroll_backup_lun server 1

Note
In Data ONTAP 6.3 and later, WAFL volumes can be space reserved, which means that if free space within the WAFL volume is below a certain threshold, snapshots cannot be taken and SnapVault might fail.