Cloud Backup and Recovery (CBR) is the unified disaster recovery platform for Volcano Engine's cloud products, providing orchestration and management services for cloud backups. With cloud backup, you can centrally manage data backups and recovery for cloud products, enjoy consistent backup management across products, and easily handle data loss caused by malware attacks, accidental deletion, or various failures. ## Product architecture Cloud backup consists of backup sources, backup policies, backup plans, recovery points, and backup storage spaces. ![图片](https://portal.volccdn.com/obj/volcfe/cloud-universal-doc/upload_90a928e5ceffb8ae32f9ffe55dfa702e.png) * **Backup source** The backup source refers to the object to be backed up and is the starting point of cloud backup operations. It can be computing resources, service instances, or a group of coordinated services and resources in the backup source products, such as an entire ECS machine, cloud disk, or object storage bucket. * **Backup policy** The backup policy defines information such as the backup cycle and backup type. Automate backups by linking backup policies and backup storage through backup plans. * **Backup plan** Create a backup plan to enable automatic backups of the backup source. The plan associates the backup source with a backup policy, specifies backup storage, and sets data retention rules. After creating a backup plan, the system performs unified automatic backups on the specified backup source according to the linked backup policy configuration. * **Recovery point** Data generated from executing a single backup task. Recovery points are classified as automatic or manual based on the backup trigger method. * **Backup storage** Used to store recovery points. Cloud backup storage depends on the backup or snapshot storage configuration of the backup source product. For example, ECS full machine backup uses TOS Bucket as backup storage. ## Backup methods Cloud backup offers both automatic and manual backup options. The detailed descriptions and differences between these two methods are as follows: |**Comparison items** |**Automatic backup** |**Manual backup** | |---|---|---| |Trigger method |Automatically triggered based on backup rules set in the backup policy. |Triggered manually. | |Backup policy & backup plan |Required. |Not required. | |Restore point name |The initial name is automatically generated by the system and can be modified later.

Name prefix: `autobackup_`. |Supports customization.

Name prefix: `manualbackup_`. | |Use cases |Suitable for scenarios requiring regular and frequent data protection, such as daily resource backups, to quickly restore data in case of unexpected failures causing data loss. |This applies to scenarios triggered irregularly by specific events, such as manual backups before operations like OS patch installation or upgrades. This ensures quick recovery of the resource to its previous state if the installation or upgrade fails. | ## Activate cloud backup Cloud backup is currently in public beta. You can activate it for free on the [Cloud Backup](https://www.volcengine.com/product/cbr) page. ## Billing * After activating cloud backup, no charges apply if no backup operations are performed. * Cloud backup itself does not incur charges. Its usage depends on the backup and storage configurations of the source product, with fees billed by the source product and storage space providers.