Overview

In some core businesses, the data in the disk feature high importance and fast data change. In order to guarantee the data security, developers should periodically create disk snapshots. Based on such scenarios, cloud platform provides you with the automatic snapshot feature. The system will automatically implement the snapshot operation for you as long as you define the disk and time cycle for creating a disk.

Note:

• The maximum number of snapshots that can be created per CDS disk is 512, including 256 manual snapshots and 256 automatic snapshots. When the number of automatic snapshots reaches the maximum, the system will automatically delete the automatic snapshot with the oldest creation time, please view Snapshot Overview for operation.
• The time for snapshot creation depends on the size of the disk data, and generally ranges from seconds to minutes.

Operation Guide

Create an Automatic Snapshot Policy

1.Log in to cloud platform

Log in to = official website.

• In case you are not registered, you must first register account.
• Registered, direct login.

2.Log in to the BCC console

On the left of the console, select "Product Service > Baidu Cloud Compute (BCC) " to enter the page of BCC instance list. Click "Automatic Snapshot Policy" in the "Snapshot" on the left of the page to enter the setting page of automatic snapshot.

3.Create an automatic snapshot policy

In the pop-up of "Create an Automatic Snapshot Policy", enter the policy name and select the creation time and repetition date. You can also set the snapshot retention time, and the automatic snapshot will be deleted automatically beyond the retention time. After setting, click "Confirm" to complete the policy creation.

As shown in the examples in the Figure below, designate that the policy becomes valid within the period from Monday to Friday, and the snapshots are created automatically at 0:00, 12:00 and 18:00 of each day in the five days above. Meanwhile, set the snapshot retention period of 7 days.

After the creation, you can view the existing snapshot policies in the automatic snapshot policy list, and implement the operations for the existing snapshot policies, such as modification, disk binding/unbinding, closing/opening and deletion.

Note:

• The snapshot policy and the CDS to be bound must be in the same available zone in the same region;
• The same user can create a maximum of 100 snapshot policies in the same available zone.

Modify an Automatic Snapshot Policy

You can also modify the created automatic snapshot policy in the automatic snapshot policy list.

After clicking "Modify a Policy", you can modify the name, creation time and repetition date of the automatic snapshot policy. Meanwhile, you can modify the retention time of the snapshot, or set the snapshot as permanent retention.

Note:

• The modified automatic snapshot policy will override the original policy. After the modification, the disk to which the policy is bound will execute the automatic snapshot according to the modified policy;
• The created automatic snapshots are retained according to the newly set "retention time" only after the policy is modified. The automatic snapshots created under the old policy are still retained according to the originally set "retention time". For example, the automatic snapshot has been bound to one CDS before being modified, and the originally set "retention time" of the policy is 60 days. When the "retention time" of the automatic snapshot policy is modified as 30 days, the automatic snapshots created before the policy is modified are still retained according to the retention time of 60 days not 30 days. To delete the existing snapshots, please enter the "snapshot list" to manually delete them.

Bind the Snapshot Policy to the Disk

The snapshot policy can become valid only when it is bound to the disk. You can bind the selected policy to the existing disk by the button of "Bind Disk" in the automatic snapshot policy list.

Note:

• The snapshot policy can be bound to the Cloud Disk Storage (CDS) mounted on cloud platform and Baidu Cloud Compute (BCC) and Dedicated Cloud Compute (DCC), and cannot be bound to the local disk; to bind the system disk, the status of the system disk must be "Operating";
• One snapshot policy can be bound to multiple CDS, but one CDS only supports the binding of one snapshot policy. As shown in the Figure above, when you bind a new policy to the disk to which other snapshot policies are bound, the policies previously bound to the disk become invalid.

Associate the Disk with the Snapshot Policy

After setting the automatic snapshot policy, you can also associate the automatic snapshot policy to one disk in the CDS list. After entering the "disk list", you can select one disk and bind an existing snapshot policy to the disk.

Note:

• Only the data disk in the status of "Mounted" and the system disk in the status of "Operating" can associate with the snapshot policy and become valid;
• The original automatic snapshot setting features of BCC and DCC of cloud platform will be smoothly migrated to the new snapshot policy features. The original automatic snapshot configuration will not be lost, and the system will help you to automatically migrate all the existing configurations to new snapshot policies.