CBR Overview
What Is CBR?
Cloud Backup and Recovery (CBR) enables you to easily back up cloud servers and cloud disks. In case of a virus attack, accidental deletion, or software or hardware fault, you can restore data to any point when the data was backed up.
CBR protects your workloads by ensuring the security and consistency of your data.
CBR Architecture
CBR involves backups, vaults, and policies.
- Backup
A backup is a copy of a particular chunk of data and is usually stored elsewhere so that it may be used to restore the original data in the event of data loss. There are the following types of backups:
- Cloud server backup: uses the consistency snapshot technology to protect data for ECSs and BMSs. Backups of non-database servers are non-database server backups, and those of database servers are application-consistent backups.
- Cloud disk backup: provides snapshot-based backups for EVS disks.
- Vault
CBR stores backups in vaults. Before creating a backup, you need to create at least one vault and associate the resources you want to back up with the vaults. Then the resources can be backed up to the associated vaults.
Vaults can be either backup vaults or replication vaults. Backup vaults store resource backups, and replication vaults store backup replicas.
Different types of resources must be backed up to different types of vaults. For example, cloud servers must be backed up to server backup vaults, not disk backup vaults or any other types of vaults.
- Policy
There are backup policies and replication policies.
- A backup policy defines when you want to take a backup and for how long you would retain each backup.
- A replication policy defines when you want to replicate from backup vaults and for how long you would retain each replica. Backup replicas are stored in replication vaults.
Backup Mechanism
The first backup is a full backup and backs up all used data blocks.
For example, if a disk size is 100 GB and 40 GB has been used, only the 40 GB of data is backed up.
Subsequent backups are incremental backups. An incremental backup backs up only the data changed since the last backup to save the storage space and backup time.
When a backup is deleted, data blocks will not be deleted if they are depended on by other backups, ensuring that other backups can still be used for restoration. Both a full backup and an incremental backup can be used to restore data to a given backup point in time.
When creating a backup of a disk, CBR also creates a snapshot for it. CBR keeps only the latest snapshot. Every time it creates a new snapshot during backup, it deletes the old snapshot.
CBR stores backups in OBS to ensure data security.
Backup Options
CBR supports one-off backup and periodic backup. A one-off backup task is manually created by users and is executed only once. Periodic backup tasks are automatically executed based on a user-defined backup policy.
Item |
One-Off Backup |
Periodic Backup |
---|---|---|
Backup policy |
Not required |
Required |
Number of backup tasks |
One manual backup task |
Periodic tasks driven by a backup policy |
Backup name |
User-defined backup name, which is manualbk_xxxx by default |
System-assigned backup name, which is autobk_xxxx by default |
Backup mode |
Full backup for the first time and incremental backup subsequently, by default |
Full backup for the first time and incremental backup subsequently, by default |
Application scenario |
Executed before patching or upgrading the OS or upgrading an application on a resource. A one-off backup can be used to restore the resource to the original state if the patching or upgrading fails. |
Executed for routine maintenance of a resource. The latest backup can be used for restoration if an unexpected failure or data loss occurs. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.