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 provides file backup which allows you to back up files and directories on your cloud servers and on-premises hosts, so you do not have to back up your entire servers or disks. Cloud servers can be Huawei Cloud servers or their counterparts from a third-party cloud. If an accidental deletion or a software/hardware fault occurs on your files, you can restore data to any time in the past when a backup was created.

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.

Backup vaults support automatic association with resources that are not backed up. After successful association, resources will be backed up according to the backup policy applied to the vault.

Migrating a resource means that you dissociate a resource from a vault and then associate it to another vault. All backups of the resource will be migrated to the destination vault.

You can expand the size of a vault if its total capacity is insufficient.

If you want a vault to be automatically expanded when its capacity is used up, enable auto capacity expansion.

If this function is enabled, the vault capacity will be automatically expanded to 1.25 times its current capacity when its capacity is used up.

Server backup vaults and server replication vaults both have two specifications: those for server backups/replicas and those for application-consistent backups/replicas.

• Server backups are backups of non-database servers.
• Application-consistent backups are backups of database servers.

If you need to back up database servers, change the specifications of the target vault from server backup to application-consistent backup.

You can only change the specifications of a vault from server backup to application-consistent backup, but not the other way around.

You can add, edit, or delete tags of a vault. Vault tags are used to filter and manage vaults only.

If you need to modify the enterprise project of a vault, go to the Enterprise Management page to move the vault from the original enterprise project to a new one.

CBR enables you to replicate server backups and SFS Turbo backups from one region to another. In the destination region:

• Replicas of server backups can be used to create images and provision servers.
• Replicas of SFS Turbo backups can be used to create file systems.

With cross-region replication, you can quickly deploy services in a different region. Data on the new resource in the destination region is the same as that on the original resource when you took the backup.

You can replicate backups in either of the following methods on CBR Console:

• Select a backup from the backup list and manually perform a replication.
• Select a backup vault and manually replicate it. Alternatively, you can configure a replication policy to periodically replicate backups that have not been replicated or failed to be replicated to the destination region.

To prevent the backup data from being deleted by mistake or maliciously, you can enable backup locking for vaults to improve data security.

Once enabled, all backups in the vault enter the WORM (write once, read many) status. No one can delete the backups that are in their retention periods.

You can use the console or APIs provided by Cloud Eye to query the metrics generated for CBR.

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

Yearly/monthly is a prepaid billing mode. You are billed based on the subscription duration you specify. This mode provides lower prices and is ideal when the resource use duration is predictable.

Pay-per-use is a postpaid billing mode. You are billed based on your resource usage. With this mode, you can increase or delete resources at any time. Fees are deducted from your account balance.