Elastic Compute Service:CreateSnapshot

The local snapshot feature has been replaced by the snapshot instant access feature. Metric description is as follows:

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

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

Before you begin:

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

• The disk must be in the In Use or Unattached state. Note the following items for different states:

  • 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.

  • When a disk is used to create a dynamic extended volume or a RAID array, use a snapshot-consistent group and enable application-consistent snapshots to back up data. Snapshot-consistent groups ensure write order consistency and crash consistency for data written to multiple disks in a business system. For more information, see Create a snapshot-consistent group and Create an application-consistent snapshot.

When you create a snapshot, take note of the following items:

• Avoid creating snapshots during peak business hours. When a snapshot is being created, the I/O performance of the disk decreases by up to 10%, and read and write performance may be briefly affected.

• If the snapshot has not been created, it cannot be used to create a custom image (CreateImage).

• Incremental data generated by disk operations during snapshot creation is not backup to the snapshot.

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

• A disk for which a snapshot is being created does not support scale-out. Wait until the snapshot is created before you execute the scale-out operation.

• You can create snapshots for disks in the Expired (Expired) state. If the disk reaches its expiration release time during snapshot creation, the disk is released and the snapshot in the Creating (Creating) state is also deleted.

• After a snapshot is created, the system calculates fees based on the snapshot size in each region separately. For more information, see Snapshot billing.

• In the following scenarios, you cannot create a snapshot for the specified disk:

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

  • Snapshot creation has concurrency limits. Exceeding the limits causes creation failures. For more information, see Snapshot limits.

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