EVS Snapshot Overview

Updated on 2025-02-27 GMT+08:00

View PDF

Overview

An EVS snapshot is a complete copy or image of the disk data taken at a specific time. Snapshot is a major disaster recovery (DR) approach, and you can use a snapshot to restore disk data to the time when the snapshot was created.

**Table 1** Snapshot-related operations
Operation	Description	Reference
Creating snapshots	You can create a snapshot to save the disk data at a specified time. NOTE: Snapshots are read-only. After snapshots are created, data in the snapshots cannot be modified.	Creating an EVS Snapshot
Rolling back data	If data on a disk is incorrect or damaged, you can roll back data from a snapshot to the source disk.	Rolling Back Disk Data from a Snapshot
Creating disks from a snapshot	You can create disks from a snapshot to quickly copy the snapshot data to disks.	Creating a Disk from a Snapshot
Checking snapshot information	You can check the snapshot details, including the region and AZ, source disk information, and tags.	Checking EVS Snapshot Details
Deleting snapshots	If you no longer require certain snapshots or the snapshot quantity reaches the maximum allowed, you can delete the snapshots.	Deleting an EVS Snapshot

Snapshot Usage Scenarios

The snapshot function helps address your following needs:

Routine data backup
You can create snapshots for disks on a timely basis and use snapshots to recover your data in case that data loss or data inconsistency occurred due to unintended operations, viruses, or attacks.
Rapid data restoration
You can create a snapshot or multiple snapshots before an application software upgrade or a service data migration. If an exception occurs during the upgrade or migration, service data can be rapidly restored to the time when the snapshot was created.

For example, a fault occurred on system disk A of server A, and therefore server A cannot be started. As system disk A is already faulty, data on system disk A cannot be restored by rolling back data from snapshots. However, you can create disk B using an existing snapshot of system disk A and attach disk B to a properly running server, for example server B. In this case, server B obtains the data of system disk A from disk B.

NOTE:

When rolling back data from snapshots, data can only be rolled back to the source disk, and a rollback to a different disk is not possible.
Multi-service quick deployment
You can use a snapshot to create multiple disks containing the same initial data. These disks can be used as data resources for various services, for example data mining, report query, and development and testing. This method protects the initial data and creates disks rapidly, meeting diverse service requirements.

Snapshot Principles

Snapshots and backups are different in that a backup saves the data as another copy in the storage system other than on the disk, whereas a snapshot establishes a relationship between the snapshot and disk data. For details, see Differences Between Disk Backups and Disk Snapshots.

The following example describes the snapshot principles with two snapshots s1 and s2 created for disk v1 at different points in time:

Disk v1 was created, which contains no data.
Data d1 and d2 were written to disk v1. Data d1 and d2 were written to new spaces.
Snapshot s1 was created for disk v1 modified in step 2. Data d1 and d2 were not saved as another copy elsewhere. Instead, a relationship between snapshot s1 and data d1 and d2 was established.
Data d3 was written to disk v1, and data d2 was changed to d4. Data d3 and d4 were written to new spaces, and data d2 was not overwritten. The relationship between snapshot s1 and data d1 and d2 was still valid. Snapshot s1 can be used to restore data if needed.
Snapshot s2 was created for disk v1 modified in step 4, and a relationship between snapshot s2 and data d1, d3, and d4 was established.
Figure 1 Snapshot principles

Differences Between Disk Backups and Disk Snapshots

Both disk backups and disk snapshots provide redundancies for improved disk data reliability. Table 2 lists the differences between them.

**Table 2** Differences between backups and snapshots
Item	Storage Solution	Data Synchronization	DR Range	Service Recovery
Backup	Backups are stored in OBS, instead of disks. This ensures data restoration upon disk damage or corruption.	A backup is a copy of a disk taken at a given time and is stored in a different location. Automatic backup can be performed based on backup policies. Deleting a disk will not delete its backups.	A backup and its source disk reside in different AZs.	You can use a backup to roll back data to its source disk or create a new disk. The data durability is high.
Snapshot	Snapshots are stored on the same disk as the source data. NOTE: Creating a backup requires a certain amount of time because data needs to be transferred to OBS. Creating a snapshot or rolling back data from a snapshot consumes less time than creating a backup.	A snapshot is the state of a disk at a specific point in time and is stored on the same disk. If the disk is deleted, all its snapshots will also be deleted. For example, if you reinstalled or changed the server OS, snapshots of the system disk were also automatically deleted. Snapshots of the data disks can be used as usual.	A snapshot and its source disk reside in the same AZ.	You can use a snapshot to roll back data to its source disk or create a new disk.

Parent topic: Managing EVS Snapshots

Previous topic: Managing EVS Snapshots

Next topic: Using EVS Snapshots

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot