Deleting an EVS Snapshot

Scenarios

SMS creates snapshots for EVS disks on each target server during the full replication, incremental synchronization, and target cloning. For EVS disks in DSS storage pools, snapshots take up the same amount of space in the pool as the disks. You can delete these snapshots as needed.

If a migration task is deleted, the disk snapshots are also deleted.

Although snapshots themselves do not differ in a technical sense, SMS distinguishes between three types of snapshots, based on the events that trigger them:

Cutover snapshots: After a migration is complete, SMS creates a snapshot for each target server disk. These snapshots are used for rollback if any service faults happen.

You are advised to delete these snapshots after the service cutover is complete and your services run stably on the target server.
Synchronization snapshots: For a Windows migration or Linux block-level migration, after the source data is migrated and synchronized and before the target server is launched, SMS creates a snapshot for each target server disk to ensure data consistency between the source and target.

After the snapshots are deleted, no further synchronization can be performed.
Clone snapshots: When you clone a target server, SMS creates a snapshot for each target server disk. These snapshots are used to clone the target server and put the migration status back to continuous synchronization after the clone is complete.

Procedure

Sign in to the SMS console.
In the navigation pane on the left, choose Servers.
In the server list, locate the server and choose More > Manage Target Delete EVS Snapshot in the Operation column.
In the displayed Delete EVS Snapshot dialog box, select the snapshots to be deleted and click OK.

Figure 1 Confirming the deletion