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

Restore a file, volume, or replicated copy

Choose the smallest safe recovery scope and test the result.

Scenario

Example: a user deleted /projects/budget.xlsx at 10:15. A 10:00 snapshot exists. Restore only the file when possible; a volume rollback would revert unrelated work.

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. Identify the target

  1. Confirm SVM, volume, path, deletion time, latest good recovery point, and whether the file belongs to a running database or VM. Ask the owner to stop writes to the affected object if needed.
  2. List snapshots and check a readable copy exists. If the local snapshot is missing, check the SnapMirror destination or external backup and its retention.
Read-only investigation 
volume snapshot show
snapmirror show
volume show

2. Select recovery scope

  1. For an individual NAS file, use a file-level snapshot restore or copy the older version to an alternate path first; compare content, ownership, and ACLs before replacement.
  2. For a complete volume rollback, document every change since the chosen snapshot and coordinate an application outage. Follow the version-specific restore procedure and confirm no incompatible protection operation is in progress.
  3. For a SnapMirror backup, restore from a selected destination snapshot to a separate recovery volume when a safe test is needed.
Verify

Recovery point, destination path, expected overwrite scope, and approver are recorded.

3. Verify and protect

  1. Have the application owner validate the recovered object and permissions. Check logs for subsequent errors.
  2. Take a fresh recovery point after the service is consistent and ensure replication resumes. Document actual recovery time (RTO) and data age (RPO).
Verify

Recovered data is usable; protection resumed; unintended files are unchanged.

If validation fails

  1. If the expected snapshot is absent locally, inspect the destination or backup catalog and confirm retention before choosing an older point.
  2. If a file restore fails, test to a separate path and check permissions, path spelling and application locks rather than retrying an in-place overwrite.
  3. If a volume rollback would affect other users, create a separate recovery volume or use file-level restore where supported and obtain explicit change approval.
Verify

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

NetApp references