Context

HUAWEI CLOUD has launched the next-generation backup service, CBR. If you have backup resources in CSBS or VBS but want to switch to CBR for the management of these historical backups, you can migrate the backup resources to CBR in a few clicks.

If you have never used CSBS or VBS or do not need the historical backup resources anymore, skip this section.

After the migration, unsubscribe resource packages referring to instructions in How Do I Unsubscribe from CSBS or VBS Resource Packages?

Migration Rule Description

During migration, the system automatically creates vaults based on your historical resources.

1. If a server or disk has been associated with a backup policy and has been backed up, during the migration, the system creates a vault with the same name as the backup policy (containing a maximum of 64 characters), regardless of whether the policy is enabled. After the vault is created, it is applied with the policy.
2. If a server or disk has been associated with a backup policy but no backup has been generated, during the migration, the system creates a vault only when the policy is enabled. After the vault is created, it is applied with the policy. The rule for naming the vault is the same as that in the preceding item.
3. If a server or disk has been applied with a backup or replication policy but no backup or replica has been generated, and the policy is not enabled, then only the policy is migrated.
4. The system migrates the backup and replication policies regardless of whether they are associated with servers or disks.
5. If application-consistent backup is enabled in a backup policy, the system creates a vault named default for storing generated application-consistent backups.
6. The generated backup replicas are stored in a replication vault named default.
7. Other backups, such as manual backups, are stored in a server backup vault named default. Different vaults are automatically created based on different types of resources. For example, the system creates a disk backup vault during the migration of disk backups.
8. After the migration, backups created using CBR will also be displayed on the VBS console, but you will be billed only once.
9. If an image has been created using a backup before the migration and a tag has been added to the image, the backup migration may fail. In this case, go to the IMS console page, delete the tag of the image, and then perform the migration again. After the migration is complete, re-add the tag if needed.
10. If backups are migrated from any of the following regions, all backups in these regions will be migrated: CN East-Shanghai1, CN East-Shanghai 2, CN North-Beijing1, CN North-Beijing4, CN South-Guangzhou, CN-Hong Kong, AP-Singapore, and AP-Bangkok. To migrate backups in other regions, go to the corresponding region and proceed with migration separately.

Base on the preceding rules, the capacity of each vault created by the system is predefined as follows:

• If the total server/disk capacity is greater than the backup size multiplied by 1.2, the vault capacity is equal to the total disk capacity.
• If the total server/disk capacity is smaller than the backup size multiplied by 1.2, the vault capacity is equal to the backup size multiplied by 1.2.
  

  Total server/disk capacity indicates the total capacity of the servers or disks to be associated with the vault.

For example, a user has a 100 GB ECS and a 50 GB ECS. The used storage capacity of the two ECSs is 20 GB and 10 GB, respectively. The user manually has backed up the two entire ECSs using the cloud server backup function. During the migration, the system automatically compares the total server/disk capacity with the backup size multiplied by 1.2. In this example, the total server capacity is 150 GB, and the backup size multiplied by 1.2 is 36 GB. Therefore, the system automatically creates a 150 GB vault.

Constraints

• By default, a vault created by the system is billed on pay-per-use basis. If you want to switch to the yearly/monthly billing mode, refer to instructions in Changing the Billing Mode from Pay-per-Use to Yearly/Monthly.
• After the migration, VBS and CSBS will be unavailable. CBR is billed in the new billing mode. For details, see How Is CBR Billed?
• The vaults you have purchased cannot be used for migration. The system automatically migrates resources to the vaults created by the system.

Procedure

1. Log in to CBR Console.
   1. Log in to the management console.
   2. Click in the upper left corner and select your region and project.
   3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.

2. Click Migrate to CBR in the upper right corner. Read the content in the displayed dialog box and click OK. See Figure 1.
   Figure 1 Migrating backup resources to CBR

   

3. The system automatically migrates resources. After the migration, a vault named default is created and a message is displayed in the upper part of the page indicating that the migration is successful.

FAQ

1. Why Are CBR Backups Displayed on the VBS Console?

   If you have migrated data from CSBS and VBS to CBR, and created a cloud disk backup on CBR Console, the same backup record will be generated in VBS. This is due to an underlying mechanism. VBS Console displays all backups generated by CBR, CSBS, and VBS. These backups will not be billed repeatedly.

2. How Do I Delete Backups from VBS Console?

   Find these backups in CBR and delete them. Then, the backups will be also deleted from VBS Console. After you have migrated data from CSBS and VBS to CBR, backups in VBS Console cannot be deleted alone.

3. What Are the Differences Between CBR, CSBS, and VBS?

   CBR integrates CSBS and VBS. In addition, CBR supports SFS Turbo backup, hybrid cloud backup, and application backup. The usage and billing of CBR are also different from CSBS and VBS.

4. What Can I Do If a Message Is Displayed Indicating that a Resource Has Been Bound with CSBS or VBS?

   Choose Cloud Server Backup Service or Volume Backup Service from the service list. On the corresponding service console, check whether there are resources bound with policies on the Policies tab. If there is, unbind the resources from the policy and go to CBR Console to associate the resource with a vault.