Help Center> > Service Overview >What Is CBR?

What Is CBR?


Cloud Backup and Recovery (CBR) allows users to back up cloud disks, elastic cloud servers and bare metal servers (referred to as servers), as well as on-premises VMware virtual environments with ease. If there is a virus intrusion, accidental deletion, or software or hardware fault, data can be restored to any point in the past when the data was backed up.

CBR protects your services by ensuring the security and accuracy of your data.

Product Architecture

CBR involves backups, vaults, and backup policies.


A backup is generated in a backup operation for an object. A backup can be used to restore data of the source backup object. CBR backups are classified into the following types:

  • Cloud disk backup: provides snapshot-based data protection for disks.
  • Cloud server backup: provides data protection based on multi-disk consistency snapshot for elastic cloud servers and bare metal servers. In addition, the backups of servers without databases deployed are common server backups, and those of servers deployed with databases are database server backups.
  • Hybrid cloud backup: provides in-cloud management and restoration for backups created using on-premises backup software OceanStor BCManager and VMware servers.


CBR uses vaults to store backups. Before creating a backup, you need to create at least one vault and associate the server or disk to be backed up with the vault. Then the backup of the server or disk will be stored in the associated vault.

Vaults can be classified as backup vaults which store backups or replication vaults which store replicas of backups.

Backups of different types of backup objects must be stored in different types of vaults accordingly.

Backup Policy

To perform automatic backups, you can configure a backup policy by setting the execution time of backup tasks, backup period, and retention rules, and then bind a vault to the policy.

Figure 1 Architecture of CBR

Differences Between the Three Backup Types

Table 1 Differences between the three backup types


Cloud Server Backup

Cloud Disk Backup

Hybrid Cloud Backup

Backup or restoration objects

All disks (system and data disks) on a server

One or more specified disks (system or data disks)

Backups synchronized from on-premises backup software

Recommended scenario

An entire cloud server needs to be protected.

Only data disks need to be backed up, because the system disk does not contain personal data.

Backups for on-premises servers need to be managed and restored in the cloud.


All disks on a server are backed up at the same time, ensuring data consistency.

Backup cost is reduced without compromising data security.

On-premises data can be backed up to the cloud and used to build new services in the cloud.

Backup Mechanism

Full backup is performed only for the first backup and all subsequent backups are incremental backups. An incremental backup backs up only the data changed since the last backup, which is storage and time-efficient. When a backup is deleted, only the data blocks that are not depended on by other backups are deleted, without affecting data restoration using other backups. Both full backup and incremental backup can restore data to the state at the backup point in time.

CBR automatically creates snapshots during backup and retains the latest snapshots for each disk. If a disk already has a backup and a new backup is created, the system will automatically delete the old snapshot and save the latest one generated.

CBR coordinates with OBS to back up data to object storage, enhancing backup data security.

Backup Options

CBR supports one-off backup and periodic backup. A one-off backup task is manually created by users and takes effect only once. Periodic backup tasks are automatically driven by a user-defined backup policy.

Table 2 describes the two backup options.

Table 2 One-off backup and periodic backup


One-Off Backup

Periodic Backup

Backup policy

Not required


Number of backup operations

Only one, manual

Periodic operations driven by the backup policy

Backup name

User-defined backup name, which defaults to manualbk_xxxx

System-assigned backup name, which defaults to autobk_xxxx

Backup mode

Full backup at the first time and incremental backup subsequently, by default

Full backup at 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 in case the patching or upgrading fails.

Executed for routine maintenance of a resource. The latest backup can be used for restoration in case an unexpected failure or data loss occurs.

Users can also intermix the two backup options if needed. For example, associate all servers with a vault and then bind the vault to a backup policy to execute periodic backup for them, and manually perform one-off backups for the most important servers to further ensure their data security. Figure 2 shows the intermixed use of the two backup options.

Figure 2 Intermixed use of the two backup options

How to Access CBR

You can access the CBR service through the management console or using HTTPS-based APIs.

  • Through the Management Console

    You can use the console to perform operations on CBR resources directly. Log in to the management console and select Cloud Backup and Recovery.

  • Through APIs

    If you need to integrate the CBR service provided by the cloud system into a third-party system for secondary development, you can use an API to access the CBR service. For details, see the Cloud Backup and Recovery API Reference.