Help Center > > Service Overview> What Is CBR?

What Is CBR?

Updated at: Feb 09, 2021 GMT+08:00


Cloud Backup and Recovery (CBR) enables you to back up Elastic Cloud Servers (ECSs), Bare Metal Servers (BMSs), Elastic Volume Service (EVS) disks, SFS Turbo file systems, and on-premises VMware virtual environments with ease. In case of a virus attack, accidental deletion, or software or hardware fault, you can restore data to any point in the past when the data was backed up.

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

Product Architecture

CBR consists of backups, vaults, and policies.


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. The following are the types of CBR backups:

  • Cloud disk backup. This type of backup provides snapshot-based data protection for EVS disks.
  • Cloud server backup. This type of backup uses the consistency snapshot technology for disks to protect data of ECSs. The backups of servers without deployed databases are common server backups, and those of servers with deployed databases are application-consistent backups.
  • File system backup. This type of backup protects data of SFS Turbo file systems.
  • Hybrid cloud backup. This type of backup protects data of on-premises OceanStor Dorado storage systems and VMware VMs by storing their backups on the cloud. You can manage the backups on CBR Console.


CBR uses vaults to store backups. Before creating a backup, you need to create at least one vault and associate the resource you want to back up with the vault. Then the backup of the resource is stored in the associated vault.

The backups of different types of resources must be stored in different types of vaults.


  • Backup policies: To perform automatic backups, configure a backup policy by setting the execution times of backup tasks, the backup cycle, and retention rules, and then apply the policy to a vault.
Figure 1 Architecture of CBR

Differences Between the Backup Types

Table 1 Differences between the backup types


Cloud Server Backup

Cloud Disk Backup

File System Backup

Hybrid Cloud Backup

Resources to be backed up or restored

All disks (system and data disks) on a server

One or more specified disks (system or data disks)

SFS Turbo file systems

Backups synchronized from on-premises backup software and VMs

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 users' application data.

Data in the SFS Turbo file systems needs to be protected.

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.

Backup data and original file systems are stored separately. You can use the backup data to create a new file system.

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

Backup Mechanism

A full backup is performed only for the first backup and backs up all used data blocks. For example, if the size of a disk is 100 GB and the used space is 40 GB, the 40 GB of data is backed up. 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, so that other backups can still be used for restoration. Both a full backup and an incremental backup can restore data to the state at a given backup point in time.

When creating a backup of a disk, CBR also creates a snapshot for it. Every time a new disk backup is created, CBR deletes the old snapshot and keeps only the latest snapshot.

CBR stores backup data in OBS, 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 is executed only once. Periodic backup tasks are automatically executed based on 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 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.

You can also use the two backup options together if needed. For example, you can associate all servers or file systems with a vault and then apply a backup policy to the vault to execute periodic backup for them, and manually perform one-off backups for the most important servers or file systems to further ensure 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 by calling HTTPS-based APIs.

  • Management Console

    The console is a web-based UI where you can perform operations on CBR resources easily. Log in to the management console and select Cloud Backup and Recovery.

  • Calling 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.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?

Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel