Rolling Back to a Scheduled Snapshot

Prerequisites

• A snapshot has been created.
• Host services have been stopped before the rollback to ensure data consistency.
• For a source namespace or source dtree that has multiple scheduled snapshots, only one rollback operation can be performed at a time.
• If compliance WORM has been configured for a source namespace, a source dtree, or the namespace where a source dtree resides, rollback is not supported.
• If cross-site DR has been configured for a source namespace or the namespace where a source dtree resides, rollback is not supported.
• If a dtree is created in a source namespace and a share is configured for the dtree, you need to delete the share from the dtree before performing a rollback.
• If a source namespace serves as the primary end of a remote replication pair, a rollback can be performed only after the remote replication pair is split. During the rollback, you cannot synchronize data for the remote replication pair.
• If a source namespace serves as the secondary end of a remote replication pair, a rollback can be performed only after the remote replication pair is split and write protection is disabled for the secondary end.

Procedure

1. Choose Data Protection > Plans > Snapshot Schedule > Scheduled Snapshot.
2. Select a desired account from the Account drop-down list in the upper left corner.
3. Select a desired source namespace or source dtree and scheduled snapshot, and click Rollback.

   The Roll Back to Snapshot page is displayed on the right.

   

   You can also click More on the right of a desired scheduled snapshot and select Rollback.

4. In Rollback Speed, select Low, Medium, High, or Highest.
   • Low: 0 MB/s to 2 MB/s, applicable when the service load is heavy.
   • Medium: 2 MB/s to 10 MB/s, applicable when the service load is relatively heavy.
   • High: 10 MB/s to 40 MB/s, applicable when the service load is relatively light.
   • Highest: above 40 MB/s, applicable when the service load is light.

5. Click OK.
6. Confirm the operation as prompted. You are advised to clear the client cache by mounting the client again