Elastic Compute Service:CreateSnapshot

The local snapshot feature has been replaced by the snapshot instant access feature. The metric descriptions are as follows:

• If you used local snapshots before December 14, 2020, you can continue to use the Category parameter as Normal.

• If you did not use local snapshots before December 14, 2020, no additional configuration is required. Snapshots created for ESSD-series disks (ESSD, ESSD AutoPL, ESSD Entry, and regional ESSD) are instantly active by default and support both manual snapshots and automatic snapshots. The InstantAccess, InstantAccessRetentionDays, and DisableInstantAccess parameters related to the snapshot instant access feature are no longer effective. The DescribeSnapshots and DescribeSnapshotGroups API operations will include a new response element Available to indicate the active status of a snapshot.

Before you begin:

• Activate the snapshot feature. For more information, see Activate the snapshot feature.

• The disk must be in the In Use or Unattached state. The following precautions apply to each state:

  • If the disk is in the In Use state, the instance must be in the Running or Stopped state.

  • If the disk is in the Unattached state, the disk must have been previously attached to an ECS instance. Snapshots cannot be created for disks that have never been attached to an ECS instance.

  • If the disk is used to create a dynamic volume or a RAID array, use a snapshot-consistent group and enable application-consistent snapshots to back up data. A snapshot-consistent group ensures write-order consistency across multiple disks in a business system and guarantees crash consistency. For more information, see Create a snapshot-consistent group and Create an application-consistent snapshot.

When creating a snapshot, note the following:

• Avoid creating snapshots during peak business hours. Creating a snapshot reduces disk I/O performance by less than 10% and may cause a brief slowdown in read and write performance.

• If a snapshot is not yet complete, it cannot be used to create a custom image (CreateImage).

• Incremental data generated by disk operations during snapshot creation is not included in the backup of the snapshot.

• If the disk is attached to an ECS instance, do not change the instance status (such as stopping or restarting the ECS instance) during snapshot creation. Otherwise, the snapshot creation will be failed.

• A disk for which a snapshot is being created cannot be scaled out. Wait until the snapshot is complete before you execute the scale-out operation.

• You can create a snapshot for a disk in the Expired (Expired) state. If the disk reaches its expiration time while a snapshot is being created, the disk is released and the snapshot in the Creating (Creating) state is deleted at the same time.

• After a snapshot is created, fees are charged separately for each region based on the snapshot size. For more information, see Snapshot billing.

• You cannot create a snapshot for a specified disk in the following scenarios:

  • The number of manual snapshots retained for the disk has reached the upper limit. For more information, see Snapshot limits.

  • Snapshot creation is subject to concurrency limits. Exceeding the limit causes the creation to fail. For more information, see Snapshot limits.

  • When querying ECS instance information, if the returned data contains {"OperationLocks": {"LockReason" : "security"}}, all operations are prohibited.