Automatic snapshot policies allow snapshots to be created regularly. These policies can be applied to both system disks and data disks. Automatic snapshot policies improve data security and operation error tolerance.
Automatic snapshot policies allow snapshots to be created regularly at the scheduled time. These policies can protect disk data and improve system security and operation error tolerance. When your applications such as personal website or databases deployed on an ECS instance encounter security attacks or system vulnerabilities, you may not be able to manually create snapshots. In these cases, you can then use the most recent automatic snapshot to roll back affected cloud disks and reduce losses.
You can also specify an automatic snapshot policy to create snapshots before regular system maintenance tasks. This eliminates the need to manually create snapshots and ensure that snapshots are not forgotten to be created.
Note the following points when you use automatic snapshot policies:
- An account can have up to 100 automatic snapshot policies in a single region.
- When the maximum number of snapshots is reached, the earliest automatic snapshot will be deleted automatically. This does not apply to manual snapshots.
- Modifying the snapshot retention period of an automatic snapshot policy will only affect new snapshots created after the modification. The retention period of existing snapshots will not be modified.
- You cannot create manual snapshots while an automatic snapshot is being created. You must wait until after the automatic snapshot has been created.
- You can only apply automatic snapshot policies to cloud disks that are in the In Use state.
- Automatic snapshot policies cannot be applied to local disks.