Table of ContentsLibraryView in Frames

Configuring SnapVault for NetBackup with NetApp volume SnapMirror

To set up a disaster recovery solution for SnapVault for NetBackup using volume SnapMirror, you need to configure volume SnapMirror relationships for the DSUs to be protected on the NearStore storage systems.

Considerations

For each DSU that needs protection, the DSU's volume on the NearStore system needs to be configured as the source of a volume SnapMirror relationship. For details on how to configure volume SnapMirror relationships, refer to the volume SnapMirror section of this document. The destination of each volume SnapMirror relationship needs to reside on a different NearStore system than the source and have a name identical to that of the source volume.
Note: Identical names for the source and the destination volumes is not a generic requirement for volume SnapMirror when used outside the context of SnapVault for NetBackup. It is not in any way enforced when configuring volume SnapMirror relationships. However, for failovers to work in the context of SnapVault for NetBackup, the volume names must be identical on the SnapMirror source and destination.

Steps

  1. Configure both NearStore storage systems (SystemA and SystemB) with the required licenses and option settings to allow SnapVault for NetBackup as well as volume SnapMirror. For licenses and options required for volume SnapMirror, refer to the volume SnapMirror section of this document.
  2. For NetBackup, the initial configuration remains the same. Create NetBackup policies for DSUs that specify SystemA as the NearStore server. In addition to the usual configuration for backing up data to volumes on SystemA, make sure to add SystemB to the list of NDMP Hosts in NetBackup.

    For more information on how to add a NearStore storage system as an NDMP Host in NetBackup, see the NetBackup documentation.

  3. Configure catalog backups if protecting the catalog is part of your disaster recovery plan.

    For configuring catalog backups, see the NetBackup Administrator's Guide for the given platform.

  4. On SystemB, create volumes with names identical to those volumes to be protected on SystemA.
  5. On SystemB, configure one SnapMirror relationship for each volume to be protected. Each volume will have a volume on SystemA as the source and a volume with the exact same name on SystemB as the destination.

    Note: Configure a SnapMirror schedule with relatively frequent updates to minimize any data mismatches between the source and destination in the case of a disaster. For more details, see how to configure SnapMirror relationships and schedules in this guide.