If data in a namespace is damaged, you can perform rollback to copy the data of a specified snapshot to the source namespace to restore the namespace data.
Prerequisites
- A snapshot has been created.
- Host services have been stopped before the rollback to ensure data consistency.
- For a source namespace that has multiple snapshots, you can use only one snapshot for the namespace rollback at a time.
- If compliance WORM has been configured for a source namespace, rollback is not supported.
- If cross-site DR has been configured for a source namespace, 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
- Choose Data Protection > Protection Entity > Namespace > Snapshot.
- Select a desired account from the Account drop-down list in the upper left corner.
- Select a desired namespace and 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 snapshot and select Rollback.
- 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.
- Click OK.
- Confirm the operation as prompted. You are advised to clear the client cache by mounting the client again