This section describes how to perform operations, such as browsing, modifying, starting rolling back, stopping rolling back, reactivating, mapping, deleting, and creating clone for a snapshot after being created.
Creating a Consistency Snapshot
When an application or a type of services requires multiple volumes for snapshot creation to maintain consistent snapshot time, you are advised to create a consistency snapshot.
Rolling Back to a Snapshot
This operation enables you to quickly recover data of the source volume to the state when the snapshot was generated, reducing the amount of lost data.
Stopping Rolling Back to a Snapshot
This operation enables you to stop rolling back the source volume to a snapshot. After the rollback is stopped, Running Status of the snapshot changes to Online. However, the source volume data of the snapshot is incomplete and the source volume data is no longer the original data on the snapshot.
Reactivating a Snapshot
This operation enables you to delete the original snapshot data and protect the data at the current time point of the source volume. When multiple snapshots are reactivated, the default activation points in time are different.
Mapping a Snapshot
This operation enables you to map a snapshot to hosts, host groups, or VBSs.
Unmapping a Snapshot
This operation enables you to unmap a snapshot from hosts, host groups, or VBSs.
Deleting a Snapshot
This operation enables you to delete a snapshot. After a snapshot is deleted, resources it occupies will be released.
Creating a Snapshot Clone
After creating a snapshot clone, you can use the clone to concurrently generate multiple physical copies of the source snapshot. The copied data can be independently operated for multiple times without affecting the data in the source snapshot.