Tencent Cloud CBS snapshots have the scheduled snapshot feature, which makes it easier for developers to flexibly set backup job policies.
The following table describes the scheduled snapshot policies recommended for different businesses.
|Scenario||Snapshot Policy||Snapshot Retention Period|
|Core product/service||Use scheduled snapshots, with the policy set to once per day.||7 to 30 days|
|Non-core and non-data product/service||Use scheduled snapshots, with the policy set to once per week.||7 days|
|Archive||Scheduled snapshot is not required. You can create snapshots manually whenever needed.||One month to several months|
|Test||Scheduled snapshot is not required. You can create snapshots manually whenever needed.||Deleted after being used|
The following table describes the content and features of scheduled snapshot policies, which help you better use snapshots in your businesses.
|Object||All cloud disks, including system disks and data disks.|
|Policy||The point in time for scheduled snapshot creation can be accurate to every hour or every day. A scheduled snapshot policy is valid permanently after being set.If you modify a scheduled snapshot policy, it takes effect immediately.|
|Scheduled termination(Important)||Scheduled snapshots can be terminated periodically. After you set a snapshot lifecycle (1–30 days), scheduled snapshots are automatically deleted upon expiration, which reduces the backup costs.If you do not set a scheduled termination policy, scheduled snapshots will be stored permanently.|
|Batch||You can apply the same scheduled snapshot policy to multiple cloud disks.|
|Naming rules||Scheduled snapshots are named in the format of snap_yyyyMMdd_HH. yyyyMMdd is the creation date, and HH is the creation hour. You can manually modify snapshot names.For example, snap_20180418_11 indicates a snapshot that was automatically created on 11:00 April 18, 2018.|
|Lifecycle(Important)||Snapshot lifecycles vary depending on the snapshot creation method:
|Snapshot conflict||Scheduled snapshots do not conflict with custom snapshots in use. However, they may conflict with each other on the creation time.
|Snapshot quota||Each disk has a certain snapshot quota. If the number of snapshots on a disk has reached the quota limit, the scheduled snapshot task will be suspended or blocked.The snapshot quota is used to prevent continuous increase in the storage costs if developers forget a scheduled snapshot policy.|
|ASP||Indicates the scheduled snapshot policy, that is, Auto Snapshot Policy.|
|ASP quota||A single Tencent Cloud account can set a maximum of 30 ASPs in each region. An ASP can be associated with a maximum of 200 cloud disks.|
|Operations logs||Show the creation process of all scheduled snapshots, same as that of manually created snapshots.|
A single Tencent Cloud account can set a maximum of 30 scheduled snapshot policies in each region.
Log in to the Scheduled Snapshot Policy page.
Select a region.
Click Create, as shown in the following figure:
On the Create a new snapshot policy page, set the following parameters and click OK.
|Name||Required.The name of a scheduled snapshot policy. It can contain up to 60 characters.|
|Region||Required.This parameter cannot be changed on the current page. For more information on how to set this parameter, see Step 2.|
|Backup Date||Required.The date for automatically creating snapshots. Value range: Sunday to Saturday.|
|Backup Time||Required.The time to automatically create snapshots. Value range: 00:00 - 23:00. Due to server performance issues, the actual scheduled snapshot creation time may be slightly different from time set here. In this case, data in a snapshot is based on the actual creation time.|
A scheduled snapshot policy can be associated with a maximum of 200 cloud disks.
If Retention Period is set to Permanent for a scheduled snapshot policy, you do not need to perform the following operations for snapshots automatically created using this policy.