Elastic Compute Service:CreateSnapshot

Local snapshots have been replaced by the snapshot instant access feature. The metric description is as follows:

• If you used local snapshots before December 14, 2020, Normal use of the Category parameter is allowed.

• If you did not use local snapshots before December 14, 2020, no additional configuration is required. Snapshots created for enterprise SSD series disks (enterprise SSD, ESSD AutoPL, ESSD Entry, and regional enterprise SSD) are active by default after creation, and both the manual snapshot and automatic snapshot features are supported. The InstantAccess, InstantAccessRetentionDays, and DisableInstantAccess parameters related to the instant access feature no longer take effect in API operations. The DescribeSnapshots and DescribeSnapshotGroups API operations add the Available response parameter to describe the active status of snapshots.

Before you begin:

• The snapshot feature is activated. For more information, see Activate the snapshot feature.

• The cloud disk must be in the In Use or Available state. Take note of the following items based on the disk state:

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

  • If the cloud disk is in the Available state, make sure that the cloud disk was previously attached to an ECS instance. You cannot create snapshots for cloud disks that have never been attached to an ECS instance.

  • When a cloud disk is used to create a dynamic extended volume or a RAID array, we recommend that you use a snapshot-consistent group and enable application-consistent snapshots to back up data. A snapshot-consistent group ensures the chronological consistency of data written to cloud disks and guarantees crash consistency in scenarios where a business system spans multiple cloud disks. 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 less than 10%, and the read and write performance may experience brief instantaneous slowdowns.

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

• During snapshot creation, no backup of incremental data generated by operations on the disk is saved 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, it results in a failed snapshot creation.

• You cannot perform scale-out on a disk while a snapshot is being created for it. Wait until the snapshot is created before you execute scale-out operations.

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

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

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

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

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

  • If the response to a query for ECS instance information contains {"OperationLocks": {"LockReason" : "security"}}, all operations are prohibited.