Setting up SnapVault backup on Open Systems platforms

About configuring SnapVault backup of Open Systems storage platforms

Setting up SnapVault for Open Systems platform backup (backup of Windows NT, Windows 2000, Solaris, or HP-UX systems) involves installing special agents on those systems and preparing the SnapVault secondary storage system to fulfill its backup tasks.

On an Open Systems platform, install the SnapVault agent appropriate to that system's platform (Windows NT, Windows 2000, Solaris, HP-UX). See Configuring an Open Systems platform system for SnapVault.
On the SnapVault secondary storage system, use the filer console commands to license and enable SnapVault, specify the Open Systems platforms to back up, start the initial baseline copy, and schedule times to download updates from the Open Systems platforms. See Configuring the Snap Vault secondary storage system for Open Systems platform backup.
In event of data loss or corruption on an Open Systems platform directory or file, use the svrestore command to restore the affected directory or file to its state at the time of its last SnapVault snapshot. See In event of data loss or corruption on Open Systems storage.

Configuring an Open Systems platform system for SnapVault

On each Open Systems platform (Windows NT, Windows 2000, Solaris, or HP-UNIX) to be backed up to SnapVault, log in to that system and complete the following steps.

Step	Description
1	If you have the CD-ROM labeled Open Systems SnapVault Agent, insert it into the target primary storage system's CD-ROM drive, and invoke the `svinstall` program from your system's command line. `svinstall` When the `svinstall` prompts appear, go to Step 3.
2	If you do not have the Open Systems SnapVault Agent CD-ROM, download the software module for your platform. Go to the software downloads section of the Network Appliance NOW web site, select Open Systems SnapVault, and follow the directions to download and expand the Open Systems SnapVault package appropriate to your system (Windows 2000, Windows NT, Solaris, or HP-UX). At the primary storage system command line, enter the following command. svinstall
3	When the `svinstall` program prompts for the Installation directory, press Enter to accept the default, or enter your own path and press Enter. On a Windows system the default is c:\program files\snapvault On a UNIX system, the default is /usr/snapvault
4	When the `svinstall` program prompts for the user name, password, and NDMP listening port, enter nothing and simply press Enter if you plan to manage SnapVault backup through your Data ONTAP or Open Systems platform command lines only. Note If you plan to manage SnapVault backup through a commercial NDMP application, specify a user and password authorized through that application.

Configuring the Snap Vault secondary storage system for Open Systems platform backup

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
At an actual console, the command for each entry in the examples is entered 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 -x parameter, the name of the secondary storage volume containing the secondary qtrees, a snapshot basename (for example: "sv_hourly," or "sv_nightly," and so on), 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.

.

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 At an actual console, the command for each entry in the examples is entered 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 `-x` parameter, the name of the secondary storage volume containing the secondary qtrees, a snapshot basename (for example: "sv_hourly," or "sv_nightly," and so on), 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.

In event of data loss or corruption on Open Systems storage

In the event of data loss or corruption on the Open Systems platform, the administrator can use the svrestore command to restore a directory or file on the Open Systems platform to its state at the time of one of its SnapVault snapshots.

Step

Description

1
In the command line interface of the Open Systems platform whose data you want to restore, use the svrestore command to specify

the secondary storage system host and the path to the secondary qtree, directory, and file that you want to restore from
the name of the snapshot that you want to restore from (for example, sv_weekly.0, sv_weekly.1, or sv_weekly.2)
the path on the primary storage system to the directory, or file that you want to restore to
For example:

svrestore -f sv_secondary -q /vol/sv_vol/tree_b -s sv_weekly -d c:/melzdir/evidence.doc

Note
In an actual command line, the entire command in this example is entered on a single line.