Function Overview

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.

CBR provides snapshot-based data protection for EVS disks. You can use CBR to back up a single disk on a server to protect data on the disk.
Backup/Restoration objects: one or more specified disks (system or data disks)
Recommended scenario: Only data disks need to be backed up, because the system disk does not contain personal data.
Advantages: Backup cost is reduced without compromising data security.

CBR protects data based on multi-disk consistency snapshots for ECSs and BMSs. You can use CBR to back up an entire server to protect data on the server. You are advised to use cloud server backup in scenarios that require high data consistency, such as RAID clusters.
Backup/Restoration object: all disks (system and data disks) on a server
Recommended scenario: An entire cloud server needs to be protected.
Advantages: All disks on a server are backed up at the same time, ensuring data consistency.

You can use CBR to back up SFS Turbo file systems and then use the backups to create new SFS Turbo file systems, preventing the loss of important data.
Backup/Restoration object: SFS Turbo file systems
Recommended scenario: Data in the SFS Turbo file systems needs to be protected.
Advantages: Backups and original file systems are stored separately. You can use a backup to create a new file system.

You can use CBR to synchronize the backups of VMware VMs to the cloud, and then manage the backups on the cloud and restore data to other cloud servers using the backup data.
Hybrid cloud backup includes:
VMware backup: CBR synchronizes the backups of on-premises VMware VMs.

There are three backup types in terms of backup consistency:

Inconsistent backup: Files and disks are backed up at different points in time. CBR's server backup uses the consistency snapshot technology for disks to protect data of ECSs and BMSs. If you back up multiple EVS disks separately, the backup time points of the EVS disks are different. As a result, the backup data of the EVS disks is inconsistent.

Crash-consistent backup captures data existing on disks upon backup and backs up files or disks at the same point in time, without backing up memory data and quieting application systems. Backup consistency of application systems is not ensured. Though the application consistency is not ensured, disks, such as chkdsk, will be checked upon operating system re-startup to restore damaged data and log rollback will be performed on databases to keep data consistent.

Application-consistent backup: Files and disks are backed up at the same point in time, including memory data, to ensure application system consistency.

CBR supports both crash-consistent backup and application-consistent backup (also called database backup).

If a MySQL or SAP HANA database is deployed on a server, you can use the application-consistent backup function of CBR to back up the server data and application cache. Crash-consistent backup backs up only data and some application caches without interrupting services. When a system fails or data loss occurs, you can use an application-consistent backup to quickly restart services. A crash-consistent backup, however, may fail to restore some application configurations.

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 executed based on a user-defined backup policy.
A backup policy allows a vault to automatically execute backup tasks at a specified interval. Periodic backups can be used to restore data quickly against data corruption or loss.

You can use CBR to quickly restore data in the following scenarios to ensure service security and reliability.
Hacker attacks and virus infection
CBR can instantly restore data to the latest backup point at which the server has not been affected by hacker attacks and viruses.
Accidental deletion
CBR can instantly restore a server or disk to the backup point prior to the accidental deletion.
Application update errors
CBR can instantly restore a server or disk to the backup point prior to the application update.
System breakdown
CBR can instantly restore a server to the backup point prior to the system breakdown.

You can share a server or disk backup with other projects. The shared backups can be used to create servers.
Backups can be shared only among users in the same region.
A backup recipient can choose whether to accept the backup. After accepting the backup, the recipient can use the backup to create a new server.
Encrypted backups cannot be shared. Backups cannot be shared across regions. Projects to which a backup is shared must be in the same region as the backup.

You can use a disk backup to create a disk. After the disk is created, data on the new disk is the same as that in the disk backup.
After a new disk is created using the backup data of a system disk, the new disk can only be mounted to the cloud server as a data disk and cannot be mounted as a system disk.
You can choose the AZ to which the backup source disk belongs, or you can choose a different AZ.
The newly created disk must be at least as large as the backup source disk.
You can create a disk of any type regardless of the backup's disk type.
Batch creation is not supported when you use backup data to create EVS disks. Quantity can only be 1.

CBR allows you to create images using ECS backups. You can use the images to provision ECSs to rapidly restore service operating environments.
Images created from a backup are the same, so CBR allows you to use a backup to create only one full-ECS image that contains the whole data of the ECS's system disk and data disks, in order to save the image quota. After an image is created, you can use the image to provision multiple ECSs in a batch.
A backup with an image created cannot be deleted manually or automatically. If you want to delete such a backup, delete its image first. If a backup is automatically generated based on a backup policy and the backup has been used to create an image, the backup will not be counted as a retained backup and will not be deleted automatically.
A backup is compressed when it is used to create an image. Therefore, the size of the generated image is smaller than that of the backup.

You can use a file system backup to create a new file system. After it is created, data on the new file system is the same as that in the backup.

You can use Cloud Trace Service (CTS) to trace operations in CBR.