Updated on 2024-02-17 GMT+08:00

Purchasing a Server Backup Vault

This section describes how to purchase a server backup vault.

New resources cannot be associated with vaults in AZ2 of the CN North-Beijing1 region to perform backups. Resources already associated are not affected, and backups can still be performed.

Procedure

  1. Log in to the CBR console.

    1. Log in to the management console.
    2. Click in the upper left corner and select a region.
    3. Click and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.

  2. In the upper right corner of the page, click Buy Server Backup Vault.
  3. Select a billing mode.

    • Yearly/monthly is a prepaid billing mode. You are billed based on the subscription duration you specify. This mode is ideal when the resource use duration is predictable. A longer subscription often means a lower cost.
    • Pay-per-use is a postpaid billing mode. You are billed based on your resource usage and you can increase or delete resources any time.

  4. Select a protection type.

    • Backup: A server backup vault stores server backups.
    • Replication: A server replication vault stores replicas of server backups. If you select Replication, you do not need to select a server.

    For example, if you want to back up a server, select Backup for the vault protection type. If you want to replicate backups of a server from one region to another, select Replication for the vault in this other region.

  5. Determine whether to enable application-consistent backup.

    • If enabled, the vault can be used to store database server backups. For example, you can back up ECSs running MySQL or SAP HANA databases, because application-consistent backup ensures that the backed-up data is transactionally consistent. If an application-consistent backup task fails, CBR automatically performs a non-database server backup task instead. This non-database server backup will be stored in the database server backup vault.
    • If disabled, only non-database server backup is performed on associated servers, which is usually used for ECSs not running databases.

  6. Select a backup data redundancy policy.

    • Single-AZ: Backup data is stored in a single AZ, with lower costs.
    • Multi-AZ: Backup data is stored in multiple AZs to achieve higher reliability.

    The backup data redundancy policy cannot be changed after a vault is purchased. Plan and select a policy that best suits your service needs.

  7. (Optional) In the server list, select the servers or disks you want to back up. After the servers or disks are selected, they are added to the list of selected servers. See Figure 1. You can also select specific disks on a server and associate them with the vault.

    To avoid data inconsistency after restoration, you are advised to back up the entire server.

    If you want to back up only some of the disks to reduce costs, ensure that data on the backed up disks does not depend on the disks that are not backed up. Or, data inconsistency may occur.

    For example, the data of an Oracle database is scattered across different disks. If only some of the disks are backed up, restoration restores only the data of the disks that have been backed up, with data on the rest of the disks unchanged. As a result, the data may be inconsistent and the Oracle database may fail to start.

    Figure 1 Selecting servers

    • The selected servers must have not been associated with any vault and must be in the Running or Stopped state.
    • You can also associate servers with the vault you are creating later if you skip this step.

  8. Specify a vault capacity ranging from 10 GB to 10,485,760 GB. Properly plan the vault capacity, which must be at least the same as the size of the servers you want to back up. Also, if automatic association is enabled and a backup policy is applied to the vault, more capacity is required.

    As the vault's used space grows, you can expand the vault capacity if it becomes insufficient.

  9. Configure auto backup.

    • If you select Configure, you must then select an existing backup policy or create a new policy. After the vault is created, CBR will apply the policy to this vault, and all servers associated with this vault will be automatically backed up based on this policy.
    • If you select Skip, servers associated with this vault will not be automatically backed up until you apply a backup policy to the vault.

  10. If you have subscribed to the Enterprise Project Management Service (EPS), add the vault to an existing enterprise project.

    EPS provides a unified method to manage cloud resources by project, allowing you to manage resources, users, and user groups in your projects. The default enterprise project is default.

    If the CBR FullAccess permissions have been assigned to IAM users, enterprise projects will not be displayed for you to choose from when you create a vault. Go to the Enterprise Project Management console and assign the CBR FullAccess permissions to the target user group.

  11. (Optional) Configure automatic resource association.

    • If you select Configure, in the next backup period, CBR will automatically scan all unprotected resources, associate them with the vault, and then perform backups.
    • If you select Skip, CBR will not scan and associate unprotected resources with the vault you are creating.

    If no tag is available, you can create tags on the corresponding resource page. You can search for vaults by specifying a maximum of 5 tags at a time. If you select more than one tag, the vaults with any of the specified tags will be returned.

  12. (Optional) Add tags to the vault.

    Tags are key-value pairs, which are used to identify, classify, and search for vaults. You can add a maximum of 10 tags for a vault, and vault tags are only used for vault search and management.

    If you have applied for the OBT of the Organizations service, and then your organization has enabled the tag policy type for CBR and has a tag policy attached, you must comply with the tag policy rules when creating vaults, otherwise vaults may fail to be created. Contact the organization administrator to learn more about tag policies.

    Table 1 describes the parameters of a tag.
    Table 1 Tag parameter description

    Parameter

    Description

    Example Value

    Key

    Each tag has a unique key. You can customize a key or select the key of an existing tag created in TMS.

    A tag key:

    • Can contain 1 to 36 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).

    Key_0001

    Value

    A tag value can be repetitive or left blank.

    A tag value:

    • Can contain 0 to 43 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).

    Value_0001

  13. Specify a name for the vault.

    The name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-), for example, vault-f61e.

    You can also use the default name vault_xxxx.

  14. Specify the required duration if you select yearly/monthly billing. The validity period ranges from 1 month to 5 years.

    Determine whether to enable auto renewal. If you select Auto Renewal:

    • Your subscription will be renewed each month for monthly billing.
    • Your subscription will be renewed each year for yearly billing.

  15. Complete the payment as prompted.
  16. Go back to the Cloud Server Backups page. You can see the created vault in the vault list.

    You can associate servers with the vault and perform backup for the servers. For details, see Vault Management.