Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments

Configuring the SnapVault secondary storage system

SnapVault secondary storage system requirement  Top

The SnapVault secondary storage system must be running Data ONTAP 6.4 or later to support backup of systems installed with Open Systems SnapVault.

Configuring the SnapVault secondary storage system  Top

To configure the SnapVault secondary storage system to support Open Systems platform SnapVault backup, complete the following steps

Step

Description

1

License the SnapVault secondary storage system. In the filer console of the SnapVault secondary system, enter the following command:

license add sv_secondary_license

For more information see Entering license codes.

2

License the SnapVault primary storage system. In the filer console of the SnapVault secondary system, enter the following command:

license add ossv_primary_license
3

Enable SnapVault. In the secondary storage system filer console, enter the following command:

options snapvault.enable on

For more information see Setting the enable option.

4

Specify the names of the primary storage systems to back up to. Enter the following command:

options snapvault.access host=snapvault_primary1, 
snapvault_primary2 ...

Example

options snapvault.access host=melzhost,samzhost,budzhost

For more information see Setting the access option.

5

For each Open Systems platform directory to be backed up to the SnapVault secondary storage system, execute an initial baseline copy from the primary to secondary storage system.

  • Specify the fully qualified path to the Open Systems host directory that you want to back up. Use the -S prefix to indicate the source path.
  • Even though the Open Systems platform directory to be backed up has no qtree, you still need to specify a host and path to the qtree where you will back up this data on the SnapVault secondary storage system.

Enter the following command:

snapvault start -S prim_host:dirpath 
sec_host:/vol/sec_vol/sec_tree

Example 1 (Windows)


snapvault start -S melzhost:c:\melzdir 
sv_secondary:/vol/sv_vol/tree_melz
snapvault start -S samzhost:c:\samzdir 
sv_secondary:/vol/sv_vol/tree_samz
snapvault start -S budzhost:c:\budzdir 
sv_secondary:/vol/sv_vol/tree_budz

Example 2 (UNIX)


snapvault start -S melzhost:/usr/melzdir 
sv_secondary:/vol/sv_vol/tree_melz
snapvault start -S samzhost:/usr/samzdir 
sv_secondary:/vol/sv_vol/tree_samz
snapvault start -S budzhost:/usr/budzdir 
sv_secondary:/vol/sv_vol/tree_budz

Note
Enter the entire command as a single line.

6

Use the snapvault snap sched command to schedule update copying of new or modified data on all Open Systems platform directories that are backed up to qtrees in SnapVault secondary storage.

Specify the name of the secondary storage volume containing the secondary qtrees, a snapshot basename (for example: "sv_hourly" or "sv_nightly"), the number of SnapVault snapshots to store on the secondary storage system, and the days and hours to execute. For example:

snapvault snap sched -x vol1 sv_weekly 1@sat@19
snapvault snap sched -x vol1 sv_nightly 2@mon-fri@19
snapvault snap sched -x vol1 sv_hourly 11@mon-fri@7-18

The -x parameter causes SnapVault to copy new or modified files from the Open Systems platform directories to their associated qtrees on the secondary storage system. After all the secondary qtrees on the specified volume have been updated, SnapVault then creates a snapshot of this volume for archiving.

Note
If files on an Open Systems platform directory are open when a scheduled SnapVault copy takes place, those files are skipped for the current transfer. Changes to those files will be backed up during the next scheduled transfer.

.

Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments