A cloud disk has adopted a three-copy redundancy mechanism for data security. Why do we still need to use snapshots?
In situations where a logic-level data error occurs, for example, suppose a user deletes data by mistake, or if the data is damaged by a virus or file system exceptions, all three copies of the data stored will be affected and historical data cannot be restored. If you have created a snapshot previously, you can use the snapshot to restore data to the point in time the snapshot was created.
Suppose an administrator created snapshot A for a cloud disk at 11:00, and the cloud disk was infected with a virus at 12:00, which caused that data to be unusable. In this case, the three copies of the data would have been updated to status 2, and the data cannot be restored. To restore data to the uninfected status 1, you have to use the snapshot A created at 11:00.
Why does the used disk storage displayed in the file system differ from the snapshot size?
A cloud disk snapshot is a block-level clone or backup. In general, the snapshot size will be larger than the data size displayed in the file system because:
The underlying data block stores the metadata of the file system.
Some data are deleted. Deleting data modifies the written-in data block, which will be backed up to snapshots.
What are the differences between snapshots and images?
If no data disk is attached to an instance and all data are written on the system disk, the data on the system disk cannot be protected by creating an image. Images cannot be scheduled for continuous backup. Once the system disk data are damaged, you can only recover the data to the state when the image was initially created. Therefore, images are not suitable for data protection. Specific differences are as follows:
Backup data of a cloud disk at a certain point in time
CVM software configuration template, which contains information about the operating system and pre-installed programs
Application Scenarios
Regularly back up important business data
Back up data before major operations
Produce multiple copies of data
Back up systems that will remain unchanged in the short term
Deploy applications in batches
Migrate the system
Why can't some of the snapshot be used to create images?
You can create snapshots for both system disks and data disks. However, only the snapshot of a system disk can be used to create a custom image.
Why can't I delete the snapshot?
To delete a snapshot, make sure that the snapshot you want to delete is not associated with any image. To query associated snapshots of an image, go to the image page and click the ID/Name of the image.
How are snapshots created from an image billed?
Images use the CBS snapshot service for data storage. The associated snapshots of a custom image will be billed by the storage size. To view the size of your snapshots, go to Snapshot Overview.
How are shared images billed?
The owner of shared images is charged the snapshot fee, while the recipient account will not be charged. For more information about the snapshot billing, see Billing Overview.
What is a scheduled snapshot?
A scheduled snapshot is automatically created for the cloud disk according to the associated scheduled snapshot policy. To use this feature, you must first create a scheduled snapshot policy and associate it with the cloud disk. For more information, see Scheduling Snapshots.
What limits do scheduled snapshots have?
A maximum of 30 scheduled snapshot policies can be created in one region. Each scheduled snapshot policy can be associated with up to 200 cloud disks. In addition, snapshots created according to the scheduled snapshot policies must comply with snapshot quota. For more information, see Use Limits.
How are snapshots created?
You can create a snapshot using the following methods:
Custom snapshot: You can manually create a snapshot to quickly save data of the cloud disk at a specified point in time. For more information, see Creating Snapshots.
Scheduled snapshot: You can associate a scheduled snapshot policy with the cloud disk to periodically create and delete snapshots. For more information, see Scheduled Snapshots.
Is snapshot available in all availability zones?
Yes.
How are snapshots billed?
Snapshots are billed according to your total snapshot storage size in each region in a pay-as-you-go manner; and the fee is calculated and deducted on the dot of every hour. For more information about billing, see Billing Overview and Price Overview.
Do I need to detach a disk or interrupt all reads and writes before creating a snapshot?
No. You can create a real-time snapshot while the disk is connected and in use, without affecting the normal operation of your business. However, the snapshot can only capture the written data but not cached data of the cloud disk. To ensure all application data is captured, we recommend that you suspend all disk I/O operations before creating a snapshot. For a cloud disk that is used as a system disk, we recommend that you shut down the CVM to create a more complete snapshot.
Will creating a snapshot affect the disk performance?
Creating a snapshot will occupy a small amount of the cloud disk I/O. We recommend creating snapshots during off-peak hours of your business.
How long does it take to create a snapshot?
The time it takes to create a snapshot is influenced by factors such as the number of disk writes and the underlying read-write operations. Creating a snapshot will not affect your disk use.
Do I need to shut down the CVM to roll back to a snapshot?
For a cloud disk that has been attached to a CVM, you have to shut down the CVM to roll it back to a snapshot.
For a cloud disk that has not been attached to a CVM, you can directly roll it back to a snapshot.
Can I read a previous snapshot to restore a cloud disk?
Yes. You can use an existing snapshot created at any point in time to restore data, regardless of the snapshot's point in time.
Can I delete the source snapshot when it is being replicated?
No. It can only be deleted after the replication is complete.
Is the new snapshot created by replication still associated with the source snapshot's source disk?
The snapshot created via cross-region replication is no longer associated with the source disk of the source snapshot. The rollback feature is unavailable for replicated snapshot.
Will associated snapshots be deleted when the CVM is terminated?
No, the associated snapshots will not be deleted automatically. You can delete them via the console or an API. For more information, see Deleting Snapshots.
How do I delete a snapshot?
For cloud disk snapshots, you can delete them directly via the console or an API. For more information, see Deleting Snapshots.
For snapshots associated with custom images, you must first delete the custom images and then delete the snapshots.
Can I use a snapshot created from the system disk to create a cloud disk?
No. You can only use the snapshot of the system disk to create a custom image.
Does the snapshot support the cross-region replication feature?
Yes. You can use this feature to easily migrate data and services to other regions, or construct your cross-region disaster recovery system. For more information, see Cross-region Snapshot Replicating.
Yes
No
Was this page helpful?