Parameters to set up SnapVault

Download PDF of this page

Several parameters are required to set up SnapVault.

Parameter Setting Description

NTAP_SNAPVAULT_UPDATE

(Y

N)

Enables you to turn on and off the SnapVault update function.

SNAPVAULT_ VOLUMES

Lists the source storage systems and volumes on which you want to perform a SnapVault update (for example, controller1:vol1,vol2,vol3;controller2:vol1;controller3:vol2,vol3). Note:

  • For SnapVault and SnapMirror updates to work, the relationships must exist.

    Snap Creator does not create the relationships.

  • The host names in the SnapMirror or SnapVault relationship must be the same as specified in the VOLUMES, SNAPMIRROR_VOLUMES, and SNAPVAULT_VOLUMES options. Also, the host where Snap Creator runs must be able to resolve the host names.

  • For vSphere or vCloud, the value should be set to auto:detect.

  • Host names should be the short host name (name that appears on storage controller command prompt), not the FQDN.

SNAPVAULT_QTREE_INCLUDE

Lists the source storage systems and qtree paths that should be included in the SnapVault update. Without this option, all qtrees under a volume are vaulted by SnapVault if a relationship exists. Qtrees listed in the following example are vaulted by SnapVault and the rest are ignored by SnapVault: controller1:/vol/qtree/qtree1,/vol/volume/qtree2;controller2:/vol/volume/qtree1.

NTAP_SNAPVAULT_RETENTIONS

Determines the number of Snapshot copies on the SnapVault secondary that you want to retain for a given policy (for example, daily:21, weekly:12, monthly:3).

NTAP_SNAPVAULT_RETENTION_AGE

Enables you to define a retention age (in days) for SnapVault Snapshot copies. If configured, SnapVault Snapshot copies are deleted only if they exceed the number defined in NTAP_SNAPVAULT_RETENTIONS and if they are older than the retention age (in days).

NTAP_SNAPVAULT_SNAPSHOT

(Y

N)

Enables use of SnapVault Snapshot copies; that is, Snapshot copies that are compatible with the storage controller SnapVault scheduler. When using this option, Snapshot copy delete is handled by the storage controller and not by Snap Creator. Additionally, Snapshot copies are named as follows: sv_<POLICY>.<##>. The policy name comes from the NTAP_SNAPSHOT_RETENTIONS parameter and the retention set is also applied to the storage controller SnapVault schedule.

NTAP_SNAPVAULT_ NODELETE

(Y

N)

Overrides NTAP_SNAPVAULT_RETENTIONS and prevents Snapshot copies from being deleted. Leaving this on can cause your volume to fill up.

NTAP_SNAPVAULT_RESTORE_WAIT

(Y

N)

In the case of SnapVault restore, it forces Snap Creator to wait for the operation to finish. This is recommended because after the SnapVault restore is complete, Snap Creator prompts the user to delete the restore Snapshot copies that get created on primary storage and are no longer needed.

NTAP_SNAPVAULT_WAIT

The wait time (in minutes) for the SnapVault update process to finish before creating a Snapshot copy on the SnapVault secondary.

NTAP_SNAPVAULT_MAX_TRANSFER