Setting up a SnapVault backup

Set up the SnapVault secondary license. In the console of the SnapVault secondary system, enter the following command:

license add sv_secondary_license

Enable SnapVault. In the console, enter the following command:

options snapvault.enable on

Initialize the compliance clock if you have not already done so. In the console, enter the following command:

date -c initialize

Result

The system prompts you to confirm the current local time and that you want to initialize the compliance clock.

Create the LockVault log volume, a SnapLock volume that contains Files Transferred log files. See Creating SnapLock volumes for details.

Enable the LockVault log volume. Enter the following command:

options snapvault.lockvault_log_volume volume_name

volume_name is the lockvault log volume.

See Configuring the LockVault log volume for more information.

Note
You must use the name of a previously created SnapLock volume for this command to succeed.

Use the options snapvault.access command to specify the names of the primary storage systems to back up and restore. Enter the following command:

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

For each qtree on the primary storage systems to be backed up, use the snapvault start command line to execute an initial baseline copy of the qtree from the primary to the secondary storage system.

On each command line, specify the primary storage system, volume, and qtree; and the secondary storage host, SnapLock volume, and qtree. Use the -S prefix to indicate the source qtree path. For example, to start a baseline copy of qtrees tree_a, tree_b, and tree_c to a SnapLock Compliance volume called sv_vol, use the following commands:

snapvault start -S system_a:/vol/vol1/tree_a sv_systemb:/vol/sv_vol/tree_a

snapvault start -S system_a:/vol/vol1/tree_b sv_systemb:/vol/sv_vol/tree_b

snapvault start -S system_a:/vol/vol1/tree_c sv_systemb:/vol/sv_vol/tree_c

Note
Enter each command on a single line.

On the primary storage systems

On each primary storage system that contains qtrees to be backed up to a SnapVault secondary storage system, use the snapvault snap sched command to schedule sets of SnapVault Snapshot copies on each volume containing the backed-up qtrees.

For each set of Snapshot copies, specify volume name, Snapshot copy basename (for example: "sv_hourly," or "sv_nightly," and so on), number of SnapVault Snapshot copies to store locally, and the days and hours to execute the Snapshot copies. For example:

snapvault snap sched vol1 sv_weekly 1@sat@19

snapvault snap sched vol1 sv_nightly 2@mon-fri@19

snapvault snap sched vol1 sv_hourly 11@mon-fri@7-18

Note
When specifying the SnapVault Snapshot copy basename, avoid using "hourly," "nightly," or "weekly." Such naming will conflict with the non-SnapVault snap sched Snapshot copies.

On the SnapVault secondary storage system

For each SnapVault volume Snapshot set that you scheduled on your primary storage systems (see Step 1), enter the following snapvault snap sched -x command to schedule a set of transfers to and subsequent Snapshot copies of the SnapVault secondary storage system:

snapvault snap sched -x sec_vol snap_name 
   count[@day_list] [@hour_list]

Caution
Before scheduling SnapVault Snapshot copies, ensure that the SnapLock default retention period is set correctly or that you explicitly set the retention period when you schedule SnapVault Snapshot copies (see Managing WORM Snapshot copies from SnapVault.)

Snapshot copy basenames on the primary and secondary systems must match, but Snapshot copy times and number of stored Snapshot copies can differ.

The -x parameter causes SnapVault to copy new or modified data from the primary qtrees 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 copy of this volume for archiving.

count is the number of Snapshot copies you want to retain for this set. This value is ignored for SnapLock volumes.

@day_list is a comma-separated list that specifies the days on which a new Snapshot copy is created for this set.

@hour_list specifies the hours at which a new Snapshot copy is created for this set.

Example:

The following commands schedule transfers and Snapshot copies every Saturday at 8 p.m., every Monday through Friday at 8 p.m., and every hour, Monday through Friday from 7 a.m. to 7 p.m., respectively:

snapvault snap sched -x sv_vol sv_weekly 8@sat@20

snapvault snap sched -x sv_vol sv_nightly 7@mon-fri@20

snapvault snap sched -x sv_vol sv_hourly 11@mon-fri@7-19

On the SnapVault primary and secondary storage system

If the SnapVault feature is scheduled to perform Snapshot management at the same time as default snap sched activity, then the Snapshot management operations scheduled using the snap sched command might fail with syslog messages, "Skipping creation of hourly snapshot," and "Snapshot already exists." To avoid this condition, disable the conflicting times using snap sched, and use the snapvault snap sched command to configure equivalent schedules.

To turn off the regular Snapshot schedule, enter the command:

snap sched volume 0 0 0