edit-icon download-icon

Snapshot 2.0 service FAQs

Last Updated: Dec 15, 2017

1. What are the new features in Snapshot 2.0?

Snapshot 2.0 has the following features:

  • Improving I/O performance of block storage when you creates a snapshot: Influence on I/O is reduced to less than 10%.
  • Providing more flexible automatic snapshot policies: Supporting customizing time for creating a snapshot, weekdays for repetition, and retention period for the automatically created snapshots, and querying the amount of disks that the automatic snapshot policy is applied to and other detailed information of the disks.
  • Allowing you to apply automatic snapshot policies to all types of block storage.
  • Providing you with a snapshot chain of each disk, representing the total size of the snapshots of a disk.

2. What can I do with snapshots?

Snapshots are copies of block storage of an ECS instance at a specific time point. They provide the following functions:

  • Backing up data: Data on your ECS instance can be automatically backed up using the automatic snapshot function.
  • Recovering data: When your ECS instance is attacked or incorrectly operated, you can use the snapshots of the disks to recover data at a specific time point.
  • Cloning an ECS instance: By creating the disks based on the snapshots of an existing ECS instance, you can create an ECS instance with the exactly same environment configurations for applications with that of the existing one.

3. What types of cloud disks do the Snapshot 2.0 support?

Now, Snapshot 2.0 supports Basic Cloud Disks, SSD Cloud Disks, and Ultra Cloud Disks. After you create an automatic snapshot policy and apply it to a disk, snapshots of the specified disk are created at the specified time point.

4. What is the snapshot quota?

Snapshot 2.0 allows a quota of 64 snapshots for each disk.

5. How long can I retain a snapshot?

It depends on how the snapshot is created:

  • If a snapshot is manually created in the ECS console or using API CreateSnapshot, it will be retained until you delete it manually.
  • If a snapshot is automatically created according to an automatic snapshot policy, it will be deleted when the specified retention period ends.

6. What is the impact on the I/O performance of block storage when I am creating a snapshot?

Generally, the loss of I/O performance caused by snapshot is less than 10%.

7. Do I have to pay for a snapshot?

Snapshot 2.0 is free of charge for a period after release, and you can get its beta features free currently.

8. When are the old automatic snapshot policies become unavailable?

The old automatic snapshot policies are the policies that are created based on the last version of snapshot service.

  • After release of Snapshot 2.0, you can view and manage the automatic snapshot policies created according to Snapshot 2.0 in the ECS console. The old automatic snapshot policies are invisible for good.
  • If an old automatic snapshot policy is applied to a disk, it keeps working until March 31, 2016.

9. How long can I retain the snapshots created based on old automatic snapshot policies?

Before Snapshot 2.0, the old retention policy for the snapshots automatically created based on the old automatic snapshot policies are that only the snapshots within the last three days and the snapshot in the last weekend are retained.

  • After Snapshot 2.0 goes online, the old retention policy still works.
  • After the old snapshot policies go offline on March 31, 2016, the old retention policy still works until April 1, 2016.
  • From April 1 to April 4, all snapshots created based on the old automatic snapshot policies will be deleted.
  • All manually created snapshots can be retained if you like.
Thank you! We've received your feedback.