tencent cloud

Cloud Virtual Machine

Release Notes and Announcements
Release Notes
Public Image Release Notes
Official End of Support Plan for the Operating System
Announcements
Product Introduction
CVM Overview
Strengths
Basic Concepts
Regions and Zones
Tutorial
Service Regions and Service Providers
Billing
Billing Overview
Billing Modes
Billing Items
Billing Mode Conversion Overview
Purchasing Instances
Configuration Adjustment Billing Guide
Overdue Payments
Getting Started
Purchasing a Customized Linux Instance
Purchasing a Customized Windows Instance
User Guide
Operation Guide Overview
Use Limits
Instances
Spot Instances
Reserved Instances
Images
Storage
Backup and Restoration
Network
Security
Passwords/Keys
Monitoring and Alarms
Ops Management
Convenience Features
Migrating a Server
Online Migration
Migration Consultation
Troubleshooting
CVM Login Failures
Windows Instance Login Failures
Linux Instance Login Failures
Other Login Failures
Instance Running Failures
Linux Instance Memory Failures
Network Failures
Use Cases
Suggestions on CVM Model Selection
Environment Building
Website Building
Application Building
Visual GUI Building
Uploading Local Files to CVM
Network Performance Test
Other Practical Tutorials
API Documentation
History
Introduction
API Category
Making API Requests
Region APIs
Instance APIs
Cloud Hosting Cluster APIs
Image APIs
Instance Launch Template APIs
Placement Group APIs
Key APIs
Security Group APIs
Network APIs
Data Types
Error Codes
Security and Compliance
CAM
Network
FAQs
Regions and Zones
Billing
Instances
Storage
Images
Server Migration
Network
Security
Operating Systems
Ops and Monitoring
CAM
NTP Service
Scenarios
Agreements
CVM Service Level Agreements
Red Hat Enterprise Linux Image Service Agreement
Public IP Service Level Agreement
Glossary

Snapshot

PDF
Focus Mode
Font Size
Last updated: 2025-09-08 16:15:45

Overview

Real-time replica of online data Snapshots are fully usable copies of cloud disks. When a problem occurs to a cloud disk where a snapshot has been created, you can use the snapshot to quickly restore the cloud disk to normal status. We recommend you to create a snapshot for the cloud disk before making any major changes to your businesses, so that data can be quickly restored if the business changes failed.
Persistent backup at critical milestones Snapshots can be used as persistent backups of business data to keep the business data at milestones.
Quick business deployment Snapshots allow you to quickly clone multiple cloud disks for quick server deployment.

Use Cases

Snapshots provide convenient and efficient data protection service, which can be used in the following business scenarios:
Daily data backup You can use snapshots to regularly back up important business data to avoid data loss caused by incorrect operations, attacks, and viruses.
Quick data recovery You can create snapshots before performing major operations, such as changing operating systems, upgrading applications, or migrating business data. If any problem occurs, you can use snapshots to restore the business data.
Application of multiple replicas of production data You can create snapshots for the production data to provide near real-time data for applications such as data mining, report query, and development testing.
Quick environment deployment You can create snapshots for a CVM instance to create a custom image, and use the custom image to create CVM instances for batch deployment with the same environment and less configuration time.

Billing

For more information about snapshot prices, see Billing Overview and Price Overview.

Quota Limits

For more information about snapshot quota limits, see Use Limits.

Snapshot Types

Manual snapshot You can manually create a snapshot for a cloud disk at a certain point in time. This snapshot can be used to create more cloud disks with identical data, or to restore the cloud disk to the point in time when the snapshot was created. For more information, see Creating Snapshots.
Scheduled snapshot For businesses that are updated continuously, you can use scheduled snapshots to provide continuous data backups. To achieve continuous backups of cloud disk data over a certain time period, you only need to configure a backup policy and associate it with cloud disks, which significantly enhances data security. For more information, see Scheduled Snapshot.
Note:
During snapshot creation, application data saved in the memory may not be persistently stored. As such, snapshots may not capture the latest and most complete cloud disk data. For more information, refer to Notes to ensure snapshot data consistency.

Case Review

Case 1: No manual snapshots were created before performing high-risk operations, resulting in data loss

Customer A has never created a snapshot for the cloud disk. In May 2019, an operator performed a fio test on the cloud disk. The file system was corrupted. The data was damaged and could not be recovered. Analysis: If customer A has created a snapshot for the cloud disk before testing, the snapshot can be used to roll back data and resume business immediately after the data damage.

Case 2: No scheduled snapshots were created for important data disks, resulting in data loss

Customer B created snapshots for multiple cloud disks, except those purchased after January 2019 for cost reasons. In June 2019, a cloud disk without snapshot protection had an unrecoverable data loss due to an accidental deletion of system-layer file data. Analysis: If customer B has created scheduled snapshots for this cloud disk, the data can be recovered to the point in time when the last snapshot was created, thereby minimizing loss. After the incident, customer B created a snapshot for that cloud disk to enhance data protection.

Case 3: Using the scheduled snapshot to roll back data and restore business after an incorrect operation

Customer C created snapshots for all cloud disks. In May 2019, a startup exception occurred due to an incorrect operation. Analysis: Customer C promptly restored data using the scheduled snapshot that was created two days ago, and the business remains stable.
These cases all involve data loss due to incorrect operations, but the results are different. By comparison, we can find that:
In situations where a snapshot hasn’t been created, data is rarely recoverable when a server or cloud disk exception occurs, resulting in major loss.
In situations where a snapshot has been created, data can be recovered when a server or cloud disk exception occurs, minimizing loss.
We recommend regularly creating snapshots for businesses based on business types, enhancing data security and achieving low-cost, high-efficiency disaster recovery.

Others

For other questions, refer to Snapshot FAQs.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback