Updated on 2025-07-30 GMT+08:00

Creating an EVS Snapshot

Scenarios

You can create EVS snapshots to save disk data at specific time points. Before you perform any critical operation, such as a data rollback, software upgrade, or data migration, you are advised to create snapshots to back up data. This ensures that your data is not affected even if an exception occurred during the operation.

Constraints

Table 1 Constraints

Item

Description

General constraints

  • Snapshots can be created for both system disks and data disks.
  • Snapshots of encrypted disks are stored encrypted, and those of non-encrypted disks are stored non-encrypted.

Legacy snapshots

  • You can manually create a maximum of seven legacy snapshots for a disk.
  • Huawei Cloud reserves the right to restrict user snapshots created during OBT.
  • The enterprise project of a snapshot is the same as that of the snapshot's source disk.

Standard snapshots

  • You can manually create a maximum of 256 standard snapshots for a disk, of which up to seven can have Instant Snapshot Restore enabled.
  • You can create one standard snapshot for a disk at a time. You can only create the next standard snapshot for the same disk after the previous snapshot has been created.
  • Standard snapshots cannot be created for the disks in edge AZs. For details about the differences between edge AZs and general AZs, see CloudPond User Guide.
  • When standard snapshots are created for Common I/O and High I/O disks, Instant Snapshot Restore cannot be enabled.
  • It usually takes several minutes to create a standard snapshot. The time required varies depending on the amounts of data written to the disk. The larger the data volume, the longer the time required. The initial standard snapshot usually takes more time because data of the entire disk is backed up. Subsequent standard snapshots are quicker, but the time required is still determined by the amount of changed data compared with each last snapshot. The more the changed data, the longer the time required.
  • If data on a disk is rolled back from a snapshot, the next standard snapshot created for this disk will be a full snapshot.
  • During the creation of a standard snapshot, any incremental data written to the disk will not be backed up to the snapshot created.
  • During the creation of a snapshot, deleting the snapshot's source disk will affect the snapshot creation. Delete the source disk after the snapshot is created.
  • You can add a maximum of 20 tags to a snapshot.
  • Tag keys of the same snapshot must be unique.

Impacts on Performance

During the snapshot creation, disk I/Os are affected, so you may experience slow reads or writes at some points. It is recommended that you create snapshots at off-peak hours.

Billing

Legacy snapshots are free. You can use them free of charge.

Standard snapshots are billed based on the storage usage of snapshot chains and the usage period. For details, see Billing for EVS Snapshots.

Prerequisites

Snapshots can only be created for Available or In-use disks.

Legacy Snapshots

Legacy snapshots are stored on the physical disks that provide storage resources for EVS disks. They do not use the EVS disk space. If a disk is deleted, all legacy snapshots of this disk will also be deleted.

Standard Snapshots

Standard snapshots are stored in OBS, instead of on disks. They can be used to restore data when the disk is damaged.

Related Links

  • You are advised to delete unnecessary snapshots on a regular basis to reduce snapshot costs. For details, see Deleting an EVS Snapshot.
  • To check more snapshot FAQs, see Snapshot.