Table of ContentsView in Frames

Preparing your environment to archive backups (clustered Data ONTAP)

SnapManager can archive backups to a SnapVault secondary, which contains a set of read-only backup copies that are located on a destination volume. If you want to archive backups to a backup vault, you need to create a SnapMirror policy and configure a vault relationship between volumes.

About this task

Clustered Data ONTAP SnapVault support is integrated using SnapDrive. The NetApp Management Console is not used with SnapManager for clustered Data ONTAP SnapVault support.

The following steps provide a high-level overview of how to create a backup vault. For more detailed information, see the Data Protection Guide for your version of Data ONTAP or the online help for OnCommand System Manager.

You do not need to schedule SnapMirror transfers or create Snapshot copy policies through Data ONTAP. SnapManager for Microsoft SQL does that for you when you create a backup schedule and select the option to archive backups to secondary storage.

Steps

  1. Identify the secondary storage to which you want to archive the backups.
  2. Create a destination volume with the volume type DP.
  3. Create a SnapMirror policy.
  4. Add a rule to the SnapMirror policy that includes the following five labels:

    • Daily
    • Weekly
    • Monthly
    • Hourly
    • Unlimited

    These are fixed labels that SnapManager uses. You select one of these options when you archive a backup.

  5. Create a relationship between the source and destination volumes, assigning the XDP relationship type and applying the SnapMirror policy to that relationship.

    The XDP relationship type defines the relationship as a vault relationship.

  6. Initialize the relationship to start a baseline transfer.

After you finish

Use SnapManager to back up your databases and select the option to archive backups to secondary storage.