Storage Admin HubConfiguration · Protection · Recovery
All guides/Data Protection
Data Protection · ONTAP 9

Design long-term backup with SnapMirror vault

Retention labels, off-cluster copy, restore testing, and monitoring.

Scenario

Example: preserve daily snapshots for 30 days and monthly snapshots for 12 months on a secondary cluster. Match labels and retention to actual compliance and recovery requirements.

Before you change production

Commands and screens can differ by release and platform. Replace example names and documentation IP addresses. Check prerequisites, impact, current health and rollback with your change owner.

1. Define backup policy

  1. Document which applications and volumes are in scope, the retention periods, legal hold needs, RPO and acceptable restore time. Decide whether a vault or unified mirror-vault policy is appropriate.
  2. Check the default policies for the actual ONTAP release. Ensure local snapshot labels match the destination policy rules; unlabeled snapshots may not transfer as expected. Budget destination capacity for change rate and retention.
Read-only planning 
volume snapshot show
snapmirror policy show
snapmirror show

2. Configure and verify

  1. Peer clusters/SVMs and create a destination volume on separate storage. In System Manager, protect the source with the selected policy and schedule, then initialize.
  2. Confirm the expected daily and monthly recovery points appear on the destination after at least one cycle. Monitor transfer errors, lag, destination free space, and retention.
Verify

Multiple recovery dates are present on the destination and capacity is adequate for the retention period.

3. Perform a restore drill

  1. Choose an older point in time and restore a test file or isolated volume. Compare checksums or application data, permissions, and elapsed restore time.
  2. Document how to locate a snapshot, choose destination, and avoid overwriting live data. A backup is useful only when its restore has been exercised.
Verify

Restored data passes owner validation, and the production source is unchanged.

If validation fails

  1. If the monthly copy does not appear, verify source snapshot label, policy rule, schedule and a successful transfer after creation.
  2. If retention uses more space than forecast, compare change rate and retained snapshots before shortening any compliance requirement.
  3. If a restore test cannot find the file, verify source volume, snapshot date, path and whether the selected vault copy included that data.
Verify

Re-run the original validation and record the observed result, exact error, time, and corrective action.

NetApp references