Tag Management Service (TMS) enables you to add preset tags to CBR vaults to facilitate vault management.
diff --git a/docs/cbr/umn/cbr_01_0009.html b/docs/cbr/umn/cbr_01_0009.html
index 633c6dcf..d0b6ad69 100644
--- a/docs/cbr/umn/cbr_01_0009.html
+++ b/docs/cbr/umn/cbr_01_0009.html
@@ -1,11 +1,11 @@
Constraints
-General- A vault can be associated with only one backup policy.
- A vault can be associated with a maximum of 256 resources.
- A maximum of 32 backup policies can be created.
- Only backups in the Available or Locked vaults can be used to restore data.
- Backups in a Deleting vault cannot be deleted.
- When Storage Disaster Recovery Service (SDRS) is used to set up disaster recovery for cloud servers, restorations can be performed at the disaster recovery site only after protection is disabled.
- Backups cannot be downloaded to a local PC or uploaded to OBS.
- A vault and its associated servers or disks must be in the same region.
+ General- A vault can be associated with only one backup policy.
- A vault can be associated with a maximum of 256 resources.
- A maximum of 32 backup policies can be created.
- Only backups in the Available or Locked vaults can be used to restore data.
- Backups in a Deleting vault cannot be deleted.
- When Storage Disaster Recovery Service (SDRS) is used to set up disaster recovery for cloud servers, restorations can be performed at the disaster recovery site only after protection is disabled.
- Backups cannot be downloaded to a local PC or uploaded to OBS.
- A vault and its associated servers or disks must be in the same region.
- Concurrent data restoration is not supported.
- Auto capacity expansion does not take effect if it is enabled after the vault is full.
- Cloud Disk Backup- Only disks in the Available or In-use state can be backed up.
- A new disk must be at least as large as the backup's source disk.
+ Cloud Disk Backup- Only disks in the Available or In-use state can be backed up.
- Frozen disks in the retention period cannot be backed up.
- A new disk must be at least as large as the backup's source disk.
- Cloud Server Backup- A maximum of 10 shared disks can be backed up with a cloud server.
- Only backups in the Available or Locked vaults can be used to create images.
- You can back up specific disks on a server, but such a backup must be restored as a whole. File- or directory-level restoration is not supported.
- When SDRS is used to set up disaster recovery for cloud servers, restorations can be performed at the disaster recovery site only after protection is disabled.
- You are advised not to back up a server whose disk size exceeds 4 TB.
+ Cloud Server Backup- A maximum of 10 shared disks can be backed up with a cloud server.
- Only backups in the Available or Locked vaults can be used to create images.
- Frozen servers in the retention period cannot be backed up.
- You can back up specific disks on a server, but such a backup must be restored as a whole. File- or directory-level restoration is not supported.
- When SDRS is used to set up disaster recovery for cloud servers, restorations can be performed at the disaster recovery site only after protection is disabled.
- You are advised not to back up a server whose disk size exceeds 4 TB.
SFS Turbo Backup- Only file systems in the Available state can be backed up.
- An SFS Turbo file system backup cannot be used to restore data to the original file system.
diff --git a/docs/cbr/umn/cbr_01_0011.html b/docs/cbr/umn/cbr_01_0011.html
index 4535cb82..256e1dbc 100644
--- a/docs/cbr/umn/cbr_01_0011.html
+++ b/docs/cbr/umn/cbr_01_0011.html
@@ -1,16 +1,16 @@
- Permissions Management
- If you need to assign different permissions to employees in your enterprise to control their access to your CBR resources on the cloud, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your cloud resources.
- With IAM, you can use your cloud account to create IAM users for your employees, and assign permissions to them to control their access to specific types of resources. For example, you can create IAM users for software developers and grant them only the permissions required for using CBR resources to allow them to use CBR resources but prevent them from performing any other operations.
- If your cloud account does not require individual IAM users for permissions management, skip this section.
- IAM is free of charge. For more information about IAM, see IAM Service Overview.
- CBR PermissionsBy default, new IAM users do not have permissions assigned. You need to add an IAM user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.
- CBR is a project-level service deployed and accessed in specific physical regions. To assign CBR permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing CBR, the users need to switch to a region where they have been authorized to use this service.
- You can grant users permissions by using roles and policies.
- - Roles: A type of coarse-grained authorization mechanism that defines permissions related to users responsibilities. Only a limited number of service-level roles for authorization are available. When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
- Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant ECS users only the permissions for managing a certain type of ECSs. Most policies define permissions based on APIs. For the API actions supported by CBR, see Permissions Policies and Supported Actions.
- Table 1 lists all the system-defined roles and policies supported by CBR.
- Table 1 System-defined policies supported by CBRPolicy Name
+Permissions
+If you need to assign different permissions to personnel in your enterprise to access your CBR resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you to securely access your cloud resources.
+ With IAM, you can create IAM users and assign permissions to control their access to specific resources. For example, if you want some software developers in your enterprise to use CBR resources but do not want them to delete CBR resource or perform any other high-risk operations, you can create IAM users and grant permission to use CBR resources but not permission to delete them.
+ If your cloud account does not require individual IAM users for permissions management, you can skip this section.
+ IAM is a free service. You only pay for the resources in your account. For more information about IAM, see IAM Service Overview.
+ CBR PermissionsNew IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned.
+ CBR is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select the specified projects in the specified regions, the users only have permissions for CBR resources in the selected projects. If you set Scope to All resources, the users have permissions for CBR resources in all region-specific projects. When accessing CBR resources, the users need to switch to the authorized region.
+ You can grant permissions by using roles and policies.
+ - Roles: A coarse-grained authorization strategy provided by IAM to assign permissions based on users' job responsibilities. Only a limited number of service-level roles are available for authorization. Cloud services depend on each other. When you grant permissions using roles, you also need to attach any existing role dependencies. Roles are not ideal for fine-grained authorization and least privilege access.
- Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access. For example, you can grant users only permission to manage ECSs of a certain type. A majority of fine-grained policies contain permissions for specific APIs, and permissions are defined using API actions. For the API actions supported by CBR, see Permissions Policies and Supported Actions.
+ Table 1 lists all the system-defined permissions for CBR.
+ Table 1 System-defined permissions for CBRPolicy Name
|
Description
|
@@ -20,21 +20,21 @@
CBR FullAccess
|
-Administrator permissions for CBR. Users granted these permissions can operate and use all vaults, backups, and policies.
+ | Administrator permissions for CBR. Users with these permissions can operate and use all vaults, backups, and policies.
|
System-defined policy
|
CBR BackupsAndVaultsFullAccess
|
-Common user permissions for CBR. Users granted these permissions can create, view, and delete vaults and backups, but cannot create, update, or delete policies.
+ | Common user permissions for CBR. Users with these permissions can create, view, and delete vaults and backups, but cannot create, update, or delete policies.
|
System-defined policy
|
CBR ReadOnlyAccess
|
-Read-only permissions for CBR. Users granted these permissions can only view CBR data.
+ | Read-only permissions for CBR. Users with these permissions can only view CBR data.
|
System-defined policy
|
@@ -43,9 +43,9 @@
- Table 2 lists the common operations supported by each system-defined policy or role of CBR. Select the policies or roles as required.
+ Table 2 lists the common operations supported by system-defined permissions of CBR.
- Table 2 Common operations supported by each system-defined policy or role of CBROperation
+Table 2 Common operations supported by system-defined permissions of CBROperation
|
CBR FullAccess
|
@@ -57,170 +57,192 @@
Querying vaults
|
-√
+ | Supported
|
-√
+ | Supported
|
-√
+ | Supported
|
Creating vaults
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
Listing vaults
|
-√
+ | Supported
|
-√
+ | Supported
|
-√
+ | Supported
|
Updating vaults
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
Deleting vaults
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
Associating resources
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
Dissociating resources
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
Creating policies
|
-√
+ | Supported
+ |
+Not supported
+ |
+Not supported
|
- |
- |
Updating policies
|
-√
+ | Supported
+ |
+Not supported
+ |
+Not supported
|
- |
- |
Applying policies to a vault
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
Removing policies from a vault
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
Deleting policies
|
-√
+ | Supported
+ |
+Not supported
+ |
+Not supported
|
- |
- |
Performing backups
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
Updating subscriptions
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
Querying the Agent status
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
Deleting backups
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
Restoring data using backups
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
Associating vaults
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
Batch adding or deleting vault tags
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
Adding vault tags
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
Editing tags
|
-√
+ | Supported
|
-√
+ | Supported
+ |
+Not supported
|
- |
diff --git a/docs/cbr/umn/cbr_01_0012.html b/docs/cbr/umn/cbr_01_0012.html
index ea5d702d..7b3fcfbc 100644
--- a/docs/cbr/umn/cbr_01_0012.html
+++ b/docs/cbr/umn/cbr_01_0012.html
@@ -2,7 +2,7 @@
CBR Concepts
VaultCBR stores backups of a variety of resources in vaults, which are classified into the following types:
- - Server backup vaults: store only backups of non-database servers. You can associate servers with a server backup vault and apply a backup policy to schedule automatic backups.
- Disk backup vaults: store only disk backups. You can associate disks with a disk backup vault and apply a backup policy to schedule automatic backups.
- SFS Turbo backup vaults: store only backups of SFS Turbo file systems. You can associate file systems with an SFS Turbo backup vault and apply a backup policy to schedule automatic backups.
+ - Server backup vaults: store only backups of non-database servers. You can associate servers with a server backup vault and apply a backup policy to schedule automatic backups.
- Disk backup vaults: store only disk backups. You can associate disks with a disk backup vault and apply a backup policy to schedule automatic backups.
- SFS Turbo backup vaults: store only backups of SFS Turbo file systems. You can associate file systems with an SFS Turbo backup vault and apply a backup policy to schedule automatic backups.
BackupA 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. It can be generated either manually by a one-off backup task or automatically by a periodic backup task.
A one-off backup task is manually created and is executed only once. Periodic backup tasks are automatically executed based on a user-defined backup policy.
diff --git a/docs/cbr/umn/cbr_01_0013.html b/docs/cbr/umn/cbr_01_0013.html
new file mode 100644
index 00000000..f2b3dc90
--- /dev/null
+++ b/docs/cbr/umn/cbr_01_0013.html
@@ -0,0 +1,21 @@
+
+
+ Advantages
+ ReliableCBR offers crash-consistent backup for multiple disks on a server. The backups protect against human errors, virus attacks, and natural disasters, and ensure your data security and reliability.
+
+ EfficientIncremental forever backups shorten the time required for backup by 95%. With Instant Restore, CBR offers an RPO of as low as 1 hour and an RTO of only several minutes.
+ Recovery Point Objective (RPO) specifies the maximum acceptable period in which data might be lost.
+ Recovery Time Objective (RTO) specifies the maximum acceptable amount of time for restoring the entire system after a disaster occurs.
+
+
+ Easy to UseCBR is easier to use than conventional backup systems. You can complete backup in just three steps, and no professional backup skills are required.
+
+ SecureIf the disks are encrypted, their backups are also encrypted to ensure data security.
+
+
+
+
diff --git a/docs/cbr/umn/cbr_01_0014.html b/docs/cbr/umn/cbr_01_0014.html
deleted file mode 100644
index 3cd2bc89..00000000
--- a/docs/cbr/umn/cbr_01_0014.html
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
- User Permissions
- If you need to assign different permissions to employees in your enterprise to access your CBR resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your cloud resources.
- The system provides two types of user permissions by default: user management and resource management.
- - User management refers to management of users, user groups, and user group permissions.
- Resource management refers to control of operations on cloud service resources.
- For details, see Permission Description.
-
-
-
diff --git a/docs/cbr/umn/cbr_02_0003.html b/docs/cbr/umn/cbr_02_0003.html
index e5028c20..634f5161 100644
--- a/docs/cbr/umn/cbr_02_0003.html
+++ b/docs/cbr/umn/cbr_02_0003.html
@@ -2,7 +2,7 @@
Creating a Server Backup Vault
This section describes how to create a server backup vault.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
- In the upper right corner of the page, click Create Server Backup Vault.
- Select a protection type.
- Backup: A server backup vault stores server backups.
- (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 the data on the backed up disks does not depend on the disks that are not backed up. Or, data inconsistency may occur.
@@ -25,7 +25,7 @@
- (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.
You can filter unprotected resources by tag. If a tag is selected, only unprotected resources with the specified tag will be associated with the vault. Or, all unprotected resources will be associated.
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.
- - (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. See Figure 4.
+ - (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 20 tags for a vault, and vault tags are only used for vault search and management. See Figure 4.

Table 1 describes the parameters of a tag.
diff --git a/docs/cbr/umn/cbr_02_0004.html b/docs/cbr/umn/cbr_02_0004.html
index 27f4a8bb..7d62235c 100644
--- a/docs/cbr/umn/cbr_02_0004.html
+++ b/docs/cbr/umn/cbr_02_0004.html
@@ -2,7 +2,7 @@
Creating a Disk Backup Vault
This section describes how to create a disk backup vault.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
- In the upper right corner of the page, click Create Disk Backup Vault.
- (Optional) In the disk list, select the disks you want to back up. After disks are selected, they are added to the list of selected disks. See Figure 1.

@@ -19,7 +19,7 @@
- (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.
You can filter unprotected resources by tag. If a tag is selected, only unprotected resources with the specified tag will be associated with the vault. Or, all unprotected resources will be associated.
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.
- - (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. See Figure 4.
+ - (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 20 tags for a vault, and vault tags are only used for vault search and management. See Figure 4.
Figure 4 Adding a tag
Table 1 describes the parameters of a tag.
diff --git a/docs/cbr/umn/cbr_02_0006.html b/docs/cbr/umn/cbr_02_0006.html
index 1d3389d1..f40206f9 100644
--- a/docs/cbr/umn/cbr_02_0006.html
+++ b/docs/cbr/umn/cbr_02_0006.html
@@ -6,13 +6,21 @@
Backing up a server does not impact the server performance. To ensure data integrity, you are advised to back up the server during off-peak hours when no data is written to the disks.
Prerequisites- Only servers in the Running or Stopped state can be backed up.
- At least one server backup vault is available.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- - On the Cloud Server Backups page, click the Vaults tab and find the vault to which the server is associated.
- Choose More > Perform Backup in the Operation column. In the server list, select the server you want to back up. After a server is selected, it is added to the list of selected servers. See Figure 1.
Figure 1 Selecting the server to be backed up
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
+ - On the Cloud Server Backups page, click the Vaults tab and find the vault to which the server is associated.
- Perform backup in either of the following ways:
- Choose More > Perform Backup in the Operation column. In the server list, select the server you want to back up. After a server is selected, it is added to the list of selected servers. See Figure 1.
Figure 1 Selecting the server to be backed up
+

+- Click the vault name to go to the vault details page. On the Associated Servers tab page, locate the target server and click Perform Backup in the Operation column. See Figure 2.
+
+

+
+
+
+
- Set Name and Description for the backup. Table 1 describes the parameters.
Table 1 Parameter descriptionParameter
|
@@ -44,15 +52,10 @@
---|
- - Choose whether to enable full backup. If full backup is enabled, CBR performs a full backup on every associated server, which requires a larger capacity compared to an incremental backup. See Figure 2.
Figure 2 Selecting full backup
+ - Choose whether to enable full backup. If full backup is enabled, CBR performs a full backup on every associated server, which requires a larger capacity compared to an incremental backup. See Figure 3.

- - (Optional) Click the vault name to go to the vault details page. On the Associated Servers tab page, locate the target server. Click Perform Backup in the Operation column of the server. See Figure 3.
-
-

-
-
- - Click Yes. CBR automatically creates a backup for the server.
On the Backups tab page, if the status of the backup is Available, the backup task is successful.
- You can restart a server if necessary after the backup progress exceeds 10%. However, to ensure data integrity, you are advised to restart it after the backup is complete.
+ - Click OK. CBR automatically creates a backup for the server.
On the Backups tab page, if the status of the backup is Available, the backup task is successful.
+ A server can be restarted if the backup progress exceeds 10%. However, to ensure data integrity, restart it after the backup is complete.
After the backup is complete, you can use the backup to restore server data or create an image. For details, see Restoring from a Cloud Server Backup and Using a Backup to Create an Image.
diff --git a/docs/cbr/umn/cbr_02_0007.html b/docs/cbr/umn/cbr_02_0007.html
index 8fa6d339..0c5b5438 100644
--- a/docs/cbr/umn/cbr_02_0007.html
+++ b/docs/cbr/umn/cbr_02_0007.html
@@ -5,13 +5,21 @@
Backing up a disk does not impact the disk performance. To ensure data integrity, you are advised to back up the disk during off-peak hours when no data is written to the disk.
PrerequisitesA disk can be backed up only when its status is Available or In-use. If you have performed operations such as expanding, attaching, detaching, or deleting a disk, refresh the page first to ensure that the operation is complete and then determine whether to back up the disk.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- - On the Cloud Disk Backups page, click the Vaults tab and find the vault to which the disk is associated.
- Choose More > Perform Backup in the Operation column. In the disk list, select the disk you want to back up. After a disk is selected, it is added to the list of selected disks. See Figure 1.
Figure 1 Selecting the disk to be backed up
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
+ - On the Cloud Disk Backups page, click the Vaults tab and find the vault to which the disk is associated.
- Perform backup in either of the following ways:
- Click Perform Backup in the Operation column. In the disk list, select the disk you want to back up. After a disk is selected, it is added to the list of selected disks. See Figure 1.
Figure 1 Selecting the disk to be backed up
+

+- Click the vault name to go to the vault details page. On the Associated Disks tab page, locate the target disk and click Perform Backup in the Operation column. See Figure 2.
+
+

+
+
+
+
CBR will identify whether the selected disk is encrypted. If it is encrypted, the backups will be automatically encrypted.
- Set Name and Description for the backup. Table 1 describes the parameters.
@@ -45,15 +53,10 @@
|
---|
- Choose whether to enable full backup. If full backup is enabled, CBR performs a full backup on every associated disk, which requires a larger capacity compared to an incremental backup. See Figure 2.Figure 2 Selecting full backup
+Choose whether to enable full backup. If full backup is enabled, CBR performs a full backup on every associated disk, which requires a larger capacity compared to an incremental backup. See Figure 3.

-(Optional) Click the vault name to go to the vault details page. On the Associated Disks tab page, locate the target disk. Click Perform Backup in the Operation column of the disk. See Figure 3.
-
-
-
-
-Click Yes. CBR automatically creates a backup for the disk.On the Backups tab page, if the status of the backup is Available, the backup task is successful.
- If you delete data from the disk during the backup, the deleted data may fail to be backed up. To ensure data integrity, you are advised to wait until the backup task is complete and then make the change and perform a backup again.
+ Click OK. CBR automatically creates a backup for the disk.On the Backups tab page, if the status of the backup is Available, the backup task is successful.
+ If you delete data from the disk during the backup, the deleted data may fail to be backed up. Therefore, to ensure data integrity, delete the target data after the backup is complete, and then perform the backup.
After the backup is complete, you can use the backup to restore disk data. For details, see Restoring from a Cloud Disk Backup.
diff --git a/docs/cbr/umn/cbr_02_0009.html b/docs/cbr/umn/cbr_02_0009.html
index 47f7b15d..1dab7aae 100644
--- a/docs/cbr/umn/cbr_02_0009.html
+++ b/docs/cbr/umn/cbr_02_0009.html
@@ -5,21 +5,21 @@
After a server backup vault or disk backup vault is created, you can associate servers, file systems, or disks with the vault to back up these resources.
Prerequisites- The servers you plan to associate with a vault must be in the Running or Stopped state.
- The disks you plan to associate with a vault must be in the Available or In-use state.
- The SFS Turbo file systems you plan to associate with a vault must be in the Available state.
- The servers you plan to associate with a vault must have at least one disk attached.
- The vault and the resources you plan to associate with it must be in the same region.
- The total size of the resources to be associated cannot be greater than the vault capacity.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- - On a backup page, locate the target vault and click Associate Server, Associate File System, or Associate Disk.
- In the resource list, select the resources you want to associate with the vault. After resources are selected, they are added to the list of selected resources. See Figure 1.
Figure 1 Associate Server
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
+ - On a backup page, locate the target vault and click Associate Server, Associate File System, or Associate Disk.
- In the resource list, select the resources you want to associate with the vault. After resources are selected, they are added to the list of selected resources. See Figure 1.
Figure 1 Associate Server

- - Click OK. Then in the Associated Servers column in the vault list, you can view the number of resources that have been successfully associated.
If a new disk is attached to an associated server, CBR automatically identifies the new disk and includes the new disk in subsequent backup tasks.
+ - Click OK. Then on the Associated Servers tab page, you can view the number of resources that have been associated.
If a new disk is attached to an associated server, CBR automatically identifies the new disk and includes the new disk in subsequent backup tasks.
Automatic AssociationIf you enable automatic association for a backup vault, the vault will automatically associate the unprotected resources and back them up according to the backup policy applied to the vault.
- - You can enable automatic association only when the vault's remaining capacity (Vault's total capacity – Vault's associated capacity) is greater than 40 GB. You can obtain the vault's total capacity and associated capacity in the Basic Information area on the details page of the vault. For example, if you have an 800-GB server backup vault and it has been associated with two 100 GB servers, its remaining capacity is 600 GB (800 GB – 200 GB). In this case, you can enable automatic association.
- If multiple vaults are enabled with automatic association, CBR scans their backup policies and associates resources with the vault whose next scheduled backup time is the earliest.
- If the capacity of the first selected vault is used up, resources will be associated with the vault whose next scheduled backup time is the second earliest.
- If a backup policy with the earliest scheduled backup time is applied to more than one vault, CBR randomly associates the resources with one of these vaults.
- If a vault has automatic association enabled but has no backup policy applied, no resources will be automatically associated with this vault. You can manually associate unprotected resources.
- After automatic association is disabled for a vault, the vault stops automatically scanning for unprotected resources. Associated resources are not affected.
- - Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery.
+- You can enable automatic association only when the vault's remaining capacity (Vault's total capacity – Vault's associated capacity) is greater than both 40 GB and the associated capacity. You can obtain the vault's total capacity and associated capacity in the Basic Information area on the details page of the vault. For example, if you have an 800-GB server backup vault and it has been associated with two 100 GB servers, its remaining capacity is 600 GB (800 GB – 200 GB). In this case, you can enable automatic association.
- If multiple vaults are enabled with automatic association, CBR scans their backup policies and associates resources with the vault whose next scheduled backup time is the earliest.
- If the capacity of the first selected vault is used up, resources will be associated with the vault whose next scheduled backup time is the second earliest.
- If a backup policy with the earliest scheduled backup time is applied to more than one vault, CBR randomly associates the resources with one of these vaults.
- If a vault has automatic association enabled but has no backup policy applied, no resources will be automatically associated with this vault. You can manually associate unprotected resources.
- After automatic association is disabled for a vault, the vault stops automatically scanning for unprotected resources. Associated resources are not affected.
+- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Choose Storage > Cloud Backup and Recovery.
- On any backup page, locate the target vault.
- Choose More > Enable Automatic Association in the Operation column of the vault. See Figure 2.
You can filter unprotected resources by tag. If a tag is selected, only unprotected resources with the specified tag will be associated with the vault. Or, all unprotected resources will be associated.
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. Figure 2 Enabling automatic association
diff --git a/docs/cbr/umn/cbr_02_0010.html b/docs/cbr/umn/cbr_02_0010.html
index acbd1934..ac25cd7e 100644
--- a/docs/cbr/umn/cbr_02_0010.html
+++ b/docs/cbr/umn/cbr_02_0010.html
@@ -2,7 +2,7 @@
Creating an SFS Turbo Backup Vault
This section describes how to create an SFS Turbo backup vault.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery > SFS Turbo Backups.
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery > SFS Turbo Backups.
- In the upper right corner of the page, click Create SFS Turbo Backup Vault.
- Select a protection type.
- Backup: An SFS Turbo backup vault stores SFS Turbo backups.
- (Optional) In the file system list, select the file systems to be backed up. After file systems are selected, they are added to the list of selected file systems. See Figure 1.
Figure 1 Selecting file systems
@@ -12,7 +12,7 @@
- The selected file systems must have not been associated with any vault and must be in the Available state.
- You can also associate file systems with the vault you are creating later if you skip this step.
- 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 file systems you want to back up.
- 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 file systems associated with this vault will be automatically backed up based on this policy.
- If you select Skip, file systems associated with this vault will not be automatically backed up until you apply a backup policy to the vault.
- - (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.
+ - (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 20 tags for a vault, and vault tags are only used for vault search and management.
Table 1 describes the parameters of a tag.
Table 1 Tag parameter descriptionParameter
|
diff --git a/docs/cbr/umn/cbr_02_0012.html b/docs/cbr/umn/cbr_02_0012.html
index 23a815ac..b1f05ae3 100644
--- a/docs/cbr/umn/cbr_02_0012.html
+++ b/docs/cbr/umn/cbr_02_0012.html
@@ -5,13 +5,19 @@
Backing up an SFS Turbo file system does not impact the file system performance. To ensure data integrity, you are advised to back up the file system during off-peak hours when no data is written to the file system.
PrerequisitesA file system can be backed up only when its status is Available or In-use. If you have performed operations such as expanding, mounting, unmounting, or deleting a file system, refresh the page first to ensure that the operation is complete and then determine whether to back up the file system.
-Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery > SFS Turbo Backups.
- - On the SFS Turbo Backups page, click the Vaults tab and find the vault to which the file system is associated.
- Choose More > Perform Backup in the Operation column. In the file system list, select the file system to be backed up. After a file system is selected, it is added to the list of selected file systems. See Figure 1.
Figure 1 Selecting the file system to be backed up
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery > SFS Turbo Backups.
+ - On the SFS Turbo Backups page, click the Vaults tab and find the vault to which the file system is associated.
- Perform backup in either of the following ways:
- Choose More > Perform Backup in the Operation column. In the file system list, select the file system to be backed up. After a file system is selected, it is added to the list of selected file systems. See Figure 1.
Figure 1 Selecting the file system to be backed up
+

-
+- Click the vault name to go to the vault details page. On the Associated File Systems tab page, locate the target file system and click Perform Backup in the Operation column. See Figure 2.
+
+

+
+
+
- Set Name and Description for the backup. Table 1 describes the parameters.
Table 1 Parameter descriptionParameter
|
@@ -43,13 +49,8 @@
---|
- - (Optional) Click the vault name to go to the vault details page. On the Associated File Systems tab page, locate the target file system. Click Perform Backup in the Operation column of the file system. See Figure 2.
-
-

-
-
- - Click Yes. CBR automatically creates a backup for the file system.
On the Backups tab page, if the status of the backup is Available, the backup task is successful.
- If you delete data from the file system during the backup, the deleted data may fail to be backed up. To ensure data integrity, you are advised to wait until the backup task is complete and then make the change and perform a backup again.
+ - Click OK. CBR automatically creates a backup for the file system.
On the Backups tab page, if the status of the backup is Available, the backup task is successful.
+ If you delete data from the file system during the backup, the deleted data may fail to be backed up. Therefore, to ensure data integrity, delete the target data after the backup is complete, and then perform the backup.
After the backup is complete, you can create a new SFS Turbo file system using the backup. For details, see Using a Backup to Create a File System.
diff --git a/docs/cbr/umn/cbr_03_0002.html b/docs/cbr/umn/cbr_03_0002.html
index dfd8c5a4..03229a82 100644
--- a/docs/cbr/umn/cbr_03_0002.html
+++ b/docs/cbr/umn/cbr_03_0002.html
@@ -4,7 +4,7 @@
You can set search criteria for querying desired vaults in the vault list.
PrerequisitesA vault has been created.
- Viewing Vault Details- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
+Viewing Vault Details- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
- On the Vaults tab, view basic information about all vaults. Related parameters are described in the following table. See Figure 1.
Figure 1 Vault list
Table 1 Basic information parametersParameter
@@ -79,7 +79,7 @@
| An intermediate state
|
An intermediate state displayed when a capacity expansion is in progress.
-If a vault is in this state, you can perform operations, such as applying a policy and associating servers, file systems, or disks. However, the following operations are not allowed on such a vault: expanding the vault capacity and changing the vault specifications. Once those operations are complete, the vault status will become Available.
+If a vault is in this state, you can perform operations, such as applying a policy and associating servers or disks. However, the following operations are not allowed on such a vault: expanding the vault capacity and changing the vault specifications. Once those operations are complete, the vault status will become Available.
|
Deleting
@@ -101,10 +101,10 @@
|
- - Search a vault by its name or ID.
- Click Search by Tag in the upper right corner to search for vaults by tag.
- On the displayed Search by Tag page, enter an existing tag key and value and click
. The added tag search criteria are displayed under the text boxes. Click Search in the lower right corner. - You can add a maximum of 10 tags by clicking
. They will be applied together for a combination search. - You can click Reset in the lower right corner to reset the search criteria.
+ - Search a vault by its name or ID.
- Click Search by Tag in the upper right corner to search for vaults by tag.
- On the displayed Search by Tag page, enter an existing tag key and value and click
. The added tag search criteria are displayed under the text boxes. Click Search in the lower right corner. - You can add a maximum of 20 tags by clicking
. They will be applied together for a combination search. - You can click Reset in the lower right corner to reset the search criteria.
- - Click the name of a specific vault to view vault details.
The values of used capacity and backup space are rounded off to integers. For example, the used backup space is displayed as 0 GB, but the backup space that has actually been used might be 0.2 GB.
+ - Click the name of a specific vault to view vault details.
The values of used capacity and backup space are rounded off to integers. CBR will display 0 GB for any backup space less than 1 GB. For example, there may be 200 MB backup space used, but it will be displayed as 0 GB on the console.
diff --git a/docs/cbr/umn/cbr_03_0003.html b/docs/cbr/umn/cbr_03_0003.html
index 6246341a..b22e08e1 100644
--- a/docs/cbr/umn/cbr_03_0003.html
+++ b/docs/cbr/umn/cbr_03_0003.html
@@ -5,7 +5,7 @@
Once you delete a vault, all backups stored in the vault will be deleted.
Prerequisites- There is at least one vault.
- The vault is in the Available or Error state.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
- Find the target vault and choose More > Delete in the Operation column. See Figure 1. All backups stored in the vault will be deleted once you delete a vault.
Figure 1 Deleting a vault

diff --git a/docs/cbr/umn/cbr_03_0005.html b/docs/cbr/umn/cbr_03_0005.html
index 5b627893..04200907 100644
--- a/docs/cbr/umn/cbr_03_0005.html
+++ b/docs/cbr/umn/cbr_03_0005.html
@@ -2,11 +2,10 @@
Dissociating a Resource
If you no longer need to back up an associated resource, dissociate it from your vault.
- After a resource is dissociated, the vault's backup policy no longer applies to the resource. In addition, all manual and automatic backups of this resource will be deleted. Deleted backups cannot be used for data restoration.
+ After a resource is dissociated, the vault's backup policy no longer applies to the resource. In addition, all manual and automatic backups of this resource will be deleted. Deleted backups cannot be used to restore data.
Dissociating a resource from a vault does not affect the performance of services on the resource.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- - Find the target vault and click its name.
- In this example, we will be using the Cloud Server Backups page to illustrate the process. Click the Associated Servers tab. Find the target server and click Dissociate in the Operation column. See Figure 1.
After a resource is dissociated, the vault's backup policy no longer applies to the resource. In addition, all manual and automatic backups of this resource will be deleted. Deleted backups cannot be used for data restoration. Figure 1 Dissociating a server
-
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
+ - Find the target vault and click its name.
- In this example, we will be using the Cloud Server Backups page to illustrate the process. Click the Associated Servers tab. Find the target server and click Dissociate in the Operation column. See Figure 1.
Figure 1 Dissociating a server

diff --git a/docs/cbr/umn/cbr_03_0006.html b/docs/cbr/umn/cbr_03_0006.html
index 3d60d71f..668da3cb 100644
--- a/docs/cbr/umn/cbr_03_0006.html
+++ b/docs/cbr/umn/cbr_03_0006.html
@@ -2,7 +2,7 @@
Expanding Vault Capacity
You can expand the size of a vault if its total capacity is insufficient.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
- Find the target vault and choose More > Expand Capacity in the Operation column. See Figure 1.
Figure 1 Expanding vault capacity

@@ -10,6 +10,7 @@
+
- Enter the capacity to be added. The minimum value is 1.
- Click Next. Confirm the settings and click Submit.
- Return to the vault list and check that the capacity of the vault has been expanded.
diff --git a/docs/cbr/umn/cbr_03_0010.html b/docs/cbr/umn/cbr_03_0010.html
index 0ef0c84b..4ebde43f 100644
--- a/docs/cbr/umn/cbr_03_0010.html
+++ b/docs/cbr/umn/cbr_03_0010.html
@@ -2,8 +2,8 @@
Managing Vault Tags
You can add, edit, or delete tags of a vault. Vault tags are used to filter and manage vaults only.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- - On the Vaults tab, click the name of the target vault and then select the Tags tab.
- Adding a tag
- Click Add Tag in the upper left corner.
- In the displayed dialog box, enter the key and value of the new tag.
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. See Figure 1.
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
+ - On the Vaults tab, click the name of the target vault and then select the Tags tab.
- Adding a tag
- Click Add Tag in the upper left corner.
- In the displayed dialog box, enter the key and value of the new tag.
Tags are key-value pairs, which are used to identify, classify, and search for vaults. You can add a maximum of 20 tags for a vault, and vault tags are only used for vault search and management. See Figure 1.
Figure 1 Adding a tag
Table 1 describes the parameters of a tag.
Table 1 Tag parameter descriptionParameter
@@ -38,7 +38,7 @@
- Click OK.
- Editing a tag
- In the Operation column of the tag that you want to edit, click Edit.
- In the displayed Edit Tag dialog box, enter a new tag value. Table 1 describes the parameters.
- Click OK.
- - Deleting a tag
- In the Operation column of the tag that you want to delete, click Delete.
- In the displayed dialog box, confirm the deletion information.
- Click OK.
+ - Deleting a tag
- In the Operation column of the tag that you want to delete, click Delete.
- In the displayed dialog box, confirm the deletion information.
- Click Yes.
diff --git a/docs/cbr/umn/cbr_03_0013.html b/docs/cbr/umn/cbr_03_0013.html
index d165f34b..8b588ab4 100644
--- a/docs/cbr/umn/cbr_03_0013.html
+++ b/docs/cbr/umn/cbr_03_0013.html
@@ -1,10 +1,10 @@
Viewing a Backup
-On the backup list, you can set search criteria to filter backups and view backup details. The results contain backup tasks that are running or have completed.
+ In the backup list, you can set search criteria to filter backups and view their details. The results contain backup tasks that are running or have completed.
PrerequisitesAt least one backup task has been created.
- Viewing Backup Details- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
+Viewing Backup Details- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
- Click the Backups tab and set filter criteria to view the backups. See Figure 1.
Figure 1 Viewing a backup
- You can search for backups by selecting a status from the All statuses drop-down list in the upper right corner of the backup list. Table 1 describes the backup statuses.
Table 1 Backup statusesStatus
diff --git a/docs/cbr/umn/cbr_03_0014.html b/docs/cbr/umn/cbr_03_0014.html
index a8220601..d470a91d 100644
--- a/docs/cbr/umn/cbr_03_0014.html
+++ b/docs/cbr/umn/cbr_03_0014.html
@@ -5,10 +5,10 @@
ContextSharer
- Backups can only be shared among domains in the same region. They cannot be shared across regions.
- Encrypted backups cannot be shared.
- When a sharer deletes a shared backup, the backup will also be deleted from the recipient's account, but the disks or servers previously created using the backup will be retained.
Recipient
- - A recipient must have at least one backup vault to store the accepted shared backup, and the vault remaining space must be greater than the size of the backup to be accepted.
- A recipient can choose to accept ore reject a backup. After accepting a backup, the recipient can use the backup to create new servers or disks.
- When a sharer deletes a shared backup, the backup will also be deleted from the recipient's account, but the disks or servers previously created using the backup will be retained.
+ - A recipient must have at least one backup vault to store the accepted shared backup, and the vault's remaining space must be greater than the size of the backup to be accepted.
- A recipient can choose to accept or reject a backup. After accepting a backup, the recipient can use the backup to create new servers or disks.
- When a sharer deletes a shared backup, the backup will also be deleted from the recipient's account, but the disks or servers previously created using the backup will be retained.
-Procedure for the Sharer- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- - Click the Backups tab and set filter criteria to view the backups.
- Locate the target backup and choose More > Share Backup in the Operation column.
The backup name, server name, backup ID, and backup type are displayed.
+Procedure for the Sharer- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
+ - Click the Backups tab and set filter criteria to view the backups.
- Locate the target backup and choose More > Share Backup in the Operation column.
The backup name, server or disk name, backup ID, and backup type are displayed.
- Sharing a backup
Figure 1 Share Backup
@@ -16,26 +16,27 @@
-
+
- Click the Share Backup tab.
- Enter the project ID of the recipient.
- Click Add. The project ID to be added will be displayed in the list. You can add multiple project IDs. A backup can be shared to a maximum of ten projects.
- Click OK.
-- Locate the target backup and choose More > Share Backup in the Operation column.
- On the displayed page, click the Cancel Sharing tab and select the backup that no longer needs to be shared. Then, click OK.
-
-
+- Click the Cancel Sharing tab, select the projects you want to cancel sharing, and click OK.
-
-
-
+
+
+
-
-Procedure for the Recipient- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- - On the selected backup page, click the Backups tab and then click Backups Shared with Me.
- Ensure that the recipient has at least one backup vault before accepting the shared backup. For how to purchase a backup vault, see Step 1: Create a Vault.
- Click Accept. On the displayed page, select the vault used to store the shared backup. Ensure that the vault remaining capacity is greater than the backup size.
Automatic Association: Determine whether to enable automatic association for the vault. If you select Configure, the vault automatically scans and associates in the next backup period servers that have not been backed up and performs backup.
+Procedure for the Recipient- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
+ - Click the Backups tab and then click Backups Shared with Me.
- Ensure that the recipient has at least one backup vault before accepting the shared backup. For how to purchase a backup vault, see Step 1: Create a Vault.
- Click Accept. On the displayed page, select the vault used to store the shared backup. Ensure that the vault's remaining capacity is greater than the backup size.
Automatic Association: Determine whether to enable automatic association for the vault. If you select Configure, the vault automatically scans and associates in the next backup period servers that have not been backed up and performs backup.
+
+
- View the shared backup you accepted in the backup list.
+
+
diff --git a/docs/cbr/umn/cbr_03_0015.html b/docs/cbr/umn/cbr_03_0015.html
index 663baa5e..8034ef47 100644
--- a/docs/cbr/umn/cbr_03_0015.html
+++ b/docs/cbr/umn/cbr_03_0015.html
@@ -2,12 +2,11 @@
Deleting a Backup
You can delete unwanted backups to reduce space usage and costs.
- ContextCBR supports manual deletion of backups and automatic deletion of expired backups. The latter is executed based on the backup retention rule in the backup policy. For details, see Creating a Backup Policy.
-
+ CBR supports manual deletion of backups and automatic deletion of expired backups. The latter is executed based on the backup retention rule in the backup policy. For details, see Creating a Backup Policy.
Prerequisites- There is at least one backup.
- The backup to be deleted is in the Available or Error state.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- - Click the Backups tab and locate the desired backup. For details, see Viewing a Backup.
- In the row of the backup, choose More > Delete from the Operation column. See Figure 1. Alternatively, select the backups you want to delete in a batch and click Delete in the upper left corner to delete them.
Figure 1 Deleting a backup
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
+ - Click the Backups tab and locate the desired backup. For details, see Viewing a Backup.
- Choose More > Delete from the Operation column. See Figure 1. Alternatively, select the backups you want to delete in a batch and click Delete in the upper left corner to delete them.
Figure 1 Deleting a backup

diff --git a/docs/cbr/umn/cbr_03_0016.html b/docs/cbr/umn/cbr_03_0016.html
index 8058dafd..c9448fc4 100644
--- a/docs/cbr/umn/cbr_03_0016.html
+++ b/docs/cbr/umn/cbr_03_0016.html
@@ -3,16 +3,17 @@
Using a Backup to Create an Image
CBR allows you to create images using ECS backups. You can use the images to provision ECSs to rapidly restore service running environments.
Prerequisites- The following operations have been performed:
-
- The backup is in the Available state or in the Creating state which is marked with Image can be created.
Once a backup creation starts, the backup enters the Creating state. After a period of time, a message stating "Image can be created" is displayed under Creating. In this case, the backup can be used for creating an image, even though it is still being created and cannot be used for restoration.
+ - The backup is in the Available state or in the Creating state which is marked with "Image can be created."
Once a backup creation starts, the backup enters the Creating state. After a period of time, a message stating "Image can be created" is displayed under Creating. In this case, the backup can be used for creating an image, even though it is still being created and cannot be used for restoration.
- The backup contains the system disk data.
Notes- Images created using 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 system disk and data disks of an ECS, 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 directly. 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, so the size of the generated image may be smaller than the backup size.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
- Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- In the row of the backup, choose More > Create Image. See Figure 1.
Figure 1 Creating an image
- - Create an image by referring to section "Creating a Full-ECS Image from a CBR Backup" in the Image Management Service User Guide.
- Use the image to provision ECSs when needed. For details, see section "Creating an ECS from an Image" in the Image Management Service User Guide.
+
+ - Create an image by referring to section "Creating a Full-ECS Image Using a Cloud Server Backup" in the Image Management Service User Guide.
- Use the image to provision ECSs when needed. For details, see section "Creating an ECS from an Image" in the Image Management Service User Guide.
diff --git a/docs/cbr/umn/cbr_03_0017.html b/docs/cbr/umn/cbr_03_0017.html
index 6ef7a94d..68f359ac 100644
--- a/docs/cbr/umn/cbr_03_0017.html
+++ b/docs/cbr/umn/cbr_03_0017.html
@@ -3,11 +3,11 @@
Using a Backup to Create a Disk
You can create new disks from backups. Once created, the new disks will contain the backup data.
The new disks created using system disk backups can only be used as data disks on servers. They cannot be used as system disks.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- - Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- If the status of the target backup is Available, click Create Disk in the Operation column of the backup.
- Configure the disk parameters.
See the parameter description table in section "Create an EVS Disk" of the Elastic Volume Service User Guide for more information.
+ Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
+ - Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- Click Create Disk in the Operation column of the backup. The button is available only when the backup status is Available.
- Configure the disk parameters.
See the parameter description table in section "Create an EVS Disk" of the Elastic Volume Service User Guide for more information.
Pay attention to the following:
+ - You can create a disk of any type regardless of the backup's source disk type.
- Click Next.
- Go back to the disk list. Check whether the disk is successfully created.
You will see the disk status change as follows: Creating, Available, Restoring, Available. You may not notice the Restoring status because Instant Restore is supported and the restoration speed is very fast. After the disk status has changed from Creating to Available, the disk is successfully created. After the status has changed from Restoring to Available, backup data has been successfully restored to the created disk.
diff --git a/docs/cbr/umn/cbr_03_0025.html b/docs/cbr/umn/cbr_03_0025.html
index 65d4523f..68a44a33 100644
--- a/docs/cbr/umn/cbr_03_0025.html
+++ b/docs/cbr/umn/cbr_03_0025.html
@@ -3,85 +3,84 @@
Creating a Backup Policy
A backup policy allows CBR to automatically back up vaults at specified times or intervals. Periodic backups can be used to restore data quickly against data corruption or loss.
To implement periodic backups, you need a backup policy first. You can use the default backup policy or create one as needed.
- You can apply backup policies to server backup vaults and disk backup vaults. CBR will then periodically perform backup at the time given in the backup policy and delete expired backups.
- Constraints- A backup policy must be enabled before it can be used for periodic backups.
- A maximum of 32 backup policies can be created in each account.
- When expired backups are deleted, automatic backups will be deleted, but manual backups will not.
- Only servers in the Running or Stopped state and disks in the Available or In-use state can be backed up.
+ Constraints- Backup policies can be applied to the following types of vaults: server backup vaults, disk backup vaults
- A backup policy must be enabled before it can be used for periodic backups.
- A maximum of 32 backup policies can be created in each account.
- When expired backups are deleted, automatic backups will be deleted, but manual backups will not.
- Only servers in the Running or Stopped state and disks in the Available or In-use state can be backed up.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- - Choose Policies and click the Backup Policies tab. In the upper right corner, click Create Policy. See Figure 1.
Figure 1 Creating a backup policy
-
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery.
+ - Choose Policies in the navigation pane and click the Backup Policies tab. In the upper right corner, click Create Policy. See Figure 1.
Figure 1 Creating a backup policy
+

- Set the backup policy parameters. Table 1 describes the parameters.
- Table 1 Backup policy parametersParameter
+Table 1 Backup policy parametersParameter
|
-Description
+ | Description
|
-Example Value
+ | Example Value
|
-Type
+ | Type
|
-Select a policy type. In this section, we select the backup policy.
+ | Select a policy type. In this section, we select the backup policy.
|
-Backup policy
+ | Backup policy
|
-Name
+ | Name
|
-Backup policy name
+ | Backup policy name
A name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-).
|
-backup_policy
+ | backup_policy
|
-Status
+ | Status
|
-Whether to enable the backup policy.
+ | Whether to enable the backup policy.
|
-Only after a backup policy is enabled and applied will CBR automatically backs up the vault resources and deletes expired backups.
+ | Only after a backup policy is enabled and applied will CBR automatically backs up the vault resources and deletes expired backups.
|
-Execution Time
+ | Execution Time
|
-Execution time
+ | Execution time
Backups can be scheduled at the beginning of each hour, and you can select multiple hours.
NOTICE: - There may be a time difference between the scheduled backup time and the actual backup time.
- If a large amount of data needs to be backed up, you are advised to make backup less frequent to prevent the system from skipping any execution time.
For example, a disk is scheduled to be backed up at 00:00, 01:00, and 02:00. A backup task starts at 00:00. Because a large amount of incremental data needs to be backed up or a heap of backup tasks are executed at the same time, this backup task takes 90 minutes and completes at 01:30. The system performs the next backup at 02:00. In this case, only two backups are generated in total, one at 00:00, and the other at 02:00.
-
+ - The execution times refer to the local times of clients, not the time zone and times of the region.
|
-00:00, 02:00
+ | 00:00, 02:00
It is recommended that backups be performed during off-peak hours or when no services are running.
|
-Backup Cycle
+ | Backup Cycle
|
-Select a backup frequency.
+ | Select a backup frequency.
- Week-based cycle
Specifies on which days of each week the backup task will be executed. You can select multiple days.
- - Custom cycle
Specifies the interval (every 1 to 30 days) for executing the backup task.
+ - Custom cycle
Specifies the interval (every 1 to 30 days) for executing the backup task.
|
-Every day
+ | Every day
If you select day-based backup, the first backup is supposed to be executed on the day when the backup policy is created. If the execution time on the day you create the backup policy has passed, the first backup will be executed in the next backup cycle.
It is recommended that backups be performed during off-peak hours or when no services are running.
|
-Retention Rule
+ | Retention Rule
|
-Rule that specifies how backups will be retained
+ | Rule that specifies how backups will be retained
- Time period
You can choose to retain backups for one month, three months, six months, one year, or for any desired number (2 to 99999) of days.
- Backup quantity
You can set the maximum number of backups to retain for each resource. The value ranges from 2 to 99999.
- Advanced Options
You can also set long-term retention rules with advanced options. Long-term retention rules and quantity-based retention rules will be both applied.
- Day-based: 0–100
- Weekly: 0–100
- Monthly: 0–100
- Yearly: 0–100
A resource may be backed up multiple times in a day. If day-based backup is configured, only the most recent backup of that day is retained. If you set Day-based to 5, the most recent backup of each of the last five days that have backups generated will be retained and the earliest backups will be deleted automatically. If day-based, weekly, monthly, and yearly retention rules are all configured, all the rules will apply and the union set of backups will be retained. For example, if Day-based is set to 5 and Weekly to 1, five backups will be retained. The long-term retention rule and the quantity-based retention rule both apply.
- - Permanent
NOTE: - The system automatically deletes the earliest and expired backups every other day to avoid exceeding the maximum number of backups to retain or retaining any backup longer than the maximum retention period.
- Expired backups are not deleted right after they are expired. They will be deleted from 12:00 to 00:00 in batches.
- The retention rules apply only to auto-generated backups, but not manual backups. Manual backups need to be deleted manually.
- After a backup is used to create an image, the backup will not be deleted by the retention rule.
- A maximum of 10 backups are retained for failed periodic backup tasks. They are retained for one month and can be deleted manually.
+ - Permanent
NOTE: - The system automatically deletes the earliest and expired backups every other day to avoid exceeding the maximum number of backups to retain or retaining any backup longer than the maximum retention period.
- Expired backups are not deleted right after they are expired. They will be deleted from 12:00 to 00:00 in batches.
- The retention rules apply only to auto-generated backups, but not manual backups. Manual backups need to be deleted manually.
- If a backup is used to create an image, the backup will not be deleted by the retention rule.
- A maximum of 10 backups are retained for failed periodic backup tasks. They are retained for one month and can be deleted manually.
|
-6 months
+ | 6 months
|
@@ -89,10 +88,11 @@
More frequent backups create more backups or retain backups for a longer time, protecting data to a greater extent but occupying more storage space. Set an appropriate backup frequency as needed.
-- Click OK.
- Locate the desired vault and choose More > Apply Backup Policy to apply the policy to the vault. You can view the applied policy on the vault details page.
After the policy is applied, data will be periodically backed up to the vault based on the policy.
+ - Click OK.
You can locate the desired vault and choose More > Apply Backup Policy to apply the policy to the vault. Then you can view the applied policy on the vault details page. After the policy is applied, data will be periodically backed up to the vault based on the policy.
+
-ExampleAt 10:00 a.m. on Monday, a user sets a backup policy for their vault to instruct CBR to execute a backup task at 02:00 a.m. every day and retain a maximum of three backups. As of 11:00 a.m. on Saturday, three backups will be retained, which are generated on Wednesday, Thursday, and Friday. The backup generated at 02:00 a.m. on Tuesday has been automatically deleted.
+ ExampleAt 10:00 a.m. on Monday, a user sets a backup policy for their vault to instruct CBR to execute a backup task at 02:00 a.m. every day and retain a maximum of three backups. As of 11:00 a.m. on Saturday, three backups will be retained, which are generated on Thursday, Friday, and Saturday. The backups generated at 02:00 a.m. on Tuesday and Wednesday have been automatically deleted.
diff --git a/docs/cbr/umn/cbr_03_0027.html b/docs/cbr/umn/cbr_03_0027.html
index bd5da585..e820f933 100644
--- a/docs/cbr/umn/cbr_03_0027.html
+++ b/docs/cbr/umn/cbr_03_0027.html
@@ -1,10 +1,10 @@
Modifying a Policy
- This section describes how to modify a policy.
+ You can modify a policy to better suit your services.
PrerequisitesAt least one policy has been created.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
- Find the target vault and click the vault name to view its details.
- In the Policies area, click Edit in the row of the policy to be edited. See Figure 1.
Figure 1 Editing a backup policy

@@ -12,8 +12,8 @@
Related parameters are described in Table 1.
- - Click OK.
If the retention rule is modified, the new rule does not necessarily apply to existing backups. For details, see Why Does the Retention Rule Not Take Effect After Being Changed?
- - Alternatively, select Policies from the navigation tree on the left and edit the desired policy.
+ - Click OK.
If the retention rule is modified, the new rule does not necessarily apply to existing backups. For details, see Why the New Retention Rule I Changed Is Not Applied?
+ - Alternatively, select Policies from the navigation pane on the left and edit the desired policy.
diff --git a/docs/cbr/umn/cbr_03_0028.html b/docs/cbr/umn/cbr_03_0028.html
index b38a61c7..07c24a76 100644
--- a/docs/cbr/umn/cbr_03_0028.html
+++ b/docs/cbr/umn/cbr_03_0028.html
@@ -1,10 +1,10 @@
Deleting a Policy
- You can delete backup and replication policies if they are no longer needed.
+ You can delete policies if they are no longer needed.
PrerequisitesAt least one policy has been created.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery.
- Click the Backup Policies tab, locate the row that contains the policy you want to delete, and click Delete.
Deleting a policy will not delete the backups generated based on the policy. You can manually delete unwanted backups.
- Confirm the information and click Yes.
diff --git a/docs/cbr/umn/cbr_03_0029.html b/docs/cbr/umn/cbr_03_0029.html
index 872682a4..d4912779 100644
--- a/docs/cbr/umn/cbr_03_0029.html
+++ b/docs/cbr/umn/cbr_03_0029.html
@@ -1,15 +1,16 @@
Applying a Policy to a Vault
- You can apply a backup policy to a vault to execute backup tasks at specified times or intervals.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
+You can apply a backup policy to a vault to execute backup tasks at specified times or intervals.
+ Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
- Find the target vault and choose More > Apply Backup Policy. See Figure 1.
Figure 1 Setting a backup policy
+

- - Select an existing backup policy from the drop-down list or create a new one. For how to create a policy, see Creating a Backup Policy.
- After the policy is successfully applied, you can view the details in the Policies area on the vault details page.
+ - Select an existing backup policy from the drop-down list or create a new one. For how to create a policy, see Creating a Backup Policy.
- After the policy is successfully applied, view details in the Policies area of the vault details page.
diff --git a/docs/cbr/umn/cbr_03_0030.html b/docs/cbr/umn/cbr_03_0030.html
index 5b6786d1..400bffcc 100644
--- a/docs/cbr/umn/cbr_03_0030.html
+++ b/docs/cbr/umn/cbr_03_0030.html
@@ -4,15 +4,17 @@
If you no longer need automatic backup for a vault, remove the policy from the vault.
PrerequisitesA policy has been applied to the vault.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
- Find the target vault and click the vault name to view its details.
- In the Policies area, click Remove Policy. See Figure 1.
Figure 1 Removing a policy
+

-
- - If a backup task is being executed for a resource in the vault, the policy can be removed. However, the backup task will continue and backups will be generated.
- After a policy is removed, backups retained by Time period will expire based on the retention rule, but backups retained by Backup quantity will not. You need manually delete unwanted backups.
+
+ - If a policy is removed when a backup task is being executed for a resource in the vault, the backup task will continue and backups will be generated.
- After a policy is removed, backups retained by Time period will expire based on the retention rule, but backups retained by Backup quantity will not. You need manually delete unwanted backups.
- - Click Yes. Backup or replication tasks will no longer be executed for the vault.
+ - Click Yes.
Tasks will no longer be executed based on this policy for the vault.
+
diff --git a/docs/cbr/umn/cbr_03_0032.html b/docs/cbr/umn/cbr_03_0032.html
index df33a9de..91d5fabd 100644
--- a/docs/cbr/umn/cbr_03_0032.html
+++ b/docs/cbr/umn/cbr_03_0032.html
@@ -2,15 +2,15 @@
Restoring from a Cloud Server Backup
When disks on a server are faulty or their data is lost, you can use a backup to restore the server to its state when the backup was created.
- Constraints- When restoring from a cloud server backup, a data disk backup cannot be restored to the system disk.
- Data cannot be restored to servers in the Faulty state.
+ Constraints- When restoring from a cloud server backup, backup of a data disk cannot be restored to the system disk.
- Data cannot be restored to servers in the Faulty state.
Prerequisites- Disks are running properly on the server whose data needs to be restored.
- The server has at least one Available backup.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
- Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- In the row of the backup, click Restore Server. See Figure 1.
The current server data will be overwritten by the data captured at the time of backup. The restoration cannot be undone.
Figure 1 Restoring a server
-
+

@@ -18,16 +18,15 @@
- (Optional) Deselect Start the server immediately after restoration.
If you do so, manually start the server after the restoration is complete. Servers will be shut down during restoration, so you are advised to perform a restoration during off-peak hours.
- - In the Specified Disk drop-down list, select the target disk to which the backup will be restored.
- If the server has only one disk, the backup is restored to that disk by default.
- If the server has multiple disks, the backup is restored to the original disks by default. You can also restore the backup to another disk of at least the same size as the original disk.
- When restoring from a cloud server backup, a data disk backup cannot be restored to the system disk.
+ - In the Destination Disk drop-down list, select the target disk to which the backup will be restored.
- If the server has only one disk, the backup is restored to that disk by default.
- If the server has multiple disks, the backup is restored to the original disks by default. You can also restore the backup to a different disk of at least the same size as the original disk.
- When restoring from a cloud server backup, backup of a data disk cannot be restored to the system disk.
If the number of disks to be restored is greater than the number of disks that were backed up, restoration may cause data inconsistency.
For example, if the Oracle data is scattered across multiple disks and only some of them are restored, data inconsistency may occur and the application may fail to start.
- Click Yes and confirm that the restoration is successful.
You can view the restoration status in the backup list. When the backup enters the Available state and no new restoration tasks failed, the restoration is successful. The resource is restored to the state when that backup was created.
For details about how to view failed restoration tasks, see Managing Tasks.
- Due to Window limitations, data disks may fail to be displayed after a Windows server is restored.
- After you use a cloud server backup to restore a logical volume group, you need to attach the logical volume group again.
- You need to manually bring these data disks online. For details, see Data Disks Are Not Displayed After a Windows Server Is Restored.
+ If you use a cloud server backup to restore a logical volume group, you need to attach the logical volume group again.
+ Due to Window limitations, data disks may fail to be displayed after a Windows server is restored. If this happens, manually bring these data disks online. For details, see Data Disks Are Not Displayed After a Windows Server Is Restored.
diff --git a/docs/cbr/umn/cbr_03_0033.html b/docs/cbr/umn/cbr_03_0033.html
index 64bfe0e5..31e63ee4 100644
--- a/docs/cbr/umn/cbr_03_0033.html
+++ b/docs/cbr/umn/cbr_03_0033.html
@@ -6,8 +6,8 @@
Constraints- Backups can only be restored to original disks. If you want to restore a backup to a different disk, use the backup to create a new disk.
-Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- - Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- In the row of the backup, click Restore Disk. The Restore Disk page is displayed. See Figure 1.
+
Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
+ - Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- In the row of the backup, click Restore Disk. The Restore Disk dialog box is displayed. See Figure 1.
- The backup data will overwrite the current disk data, and the restoration cannot be undone.
- If the restore button is grayed out, stop the server, detach the disk, and then try again. After the disk data is restored, attach the disk to the server and start the server.
@@ -16,8 +16,9 @@

- - Click Yes. You can check whether data is successfully restored on the Backups tab page of Disk Backups or on the EVS console.
When the status of the backup changes to Available, the restoration is successful. The resource is restored to the state when that backup was created.
- - After the restoration is complete, re-attach the disk to the server. For details, see section "Attaching an Existing Non-Shared Disk" in the Elastic Volume Service User Guide.
+
+ - Click Yes. You can check whether data is successfully restored on the Backups tab page of Cloud Disk Backups or on the EVS console.
When the status of the backup changes to Available, the restoration is successful. The resource is restored to the state when that backup was created.
+ - After the restoration is complete, re-attach the disk to the server. For details, see section "Attaching an Existing Non-Shared Disk" in the Elastic Volume Service User Guide.
diff --git a/docs/cbr/umn/cbr_03_0035.html b/docs/cbr/umn/cbr_03_0035.html
index 991bbcfd..be8260d6 100644
--- a/docs/cbr/umn/cbr_03_0035.html
+++ b/docs/cbr/umn/cbr_03_0035.html
@@ -1,14 +1,14 @@
Managing Tasks
- This section describes how to view tasks. The tasks list shows policy-driven backup tasks that have been executed over the past 30 days.
- PrerequisitesAt least one failed task exists.
+ You can view tasks in the task list, which shows policy-driven tasks that have been executed over the past 30 days.
+ PrerequisitesAt least one task exists.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery > Tasks.
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Choose Storage > Cloud Backup and Recovery > Tasks.
See Figure 1.
Figure 1 Viewing tasks
- - You can filter tasks by task type, task status, task ID, resource ID, resource name, vault ID, vault name, and time.
- Click
in front of the task to view the task details.If a task fails, you can view the failure cause in the task details.
+ - Filter tasks by task type, task status, task ID, resource ID, resource name, vault ID, vault name, and time.
- Click
in front of the task to view the task details.If a task fails, you can view the failure cause in the task details.
diff --git a/docs/cbr/umn/cbr_03_0036.html b/docs/cbr/umn/cbr_03_0036.html
index f6bc2319..451723a1 100644
--- a/docs/cbr/umn/cbr_03_0036.html
+++ b/docs/cbr/umn/cbr_03_0036.html
@@ -220,10 +220,10 @@
-Viewing Audit LogsFor how to view audit logs, see section "Querying Real-Time Traces" in the Cloud Trace Service User Guide.
+ Viewing Audit LogsFor how to view audit logs, see section "Querying Real-Time Traces" in the Cloud Trace Service User Guide.
Disabling or Enabling a TrackerThe following procedure illustrates how to disable an existing tracker on the CTS console. After the tracker is disabled, the system will stop recording operations, but you can still view existing operation records.
- - Log in to the management console.
- In the upper left corner of the page, click
and select your desired region and project. - Click Service List and choose Management & Deployment > Cloud Trace Service.
- Click Trackers in the left navigation pane. See Figure 1.
Figure 1 Viewing trackers
+- Log in to the management console.
- In the upper left corner of the page, click
and select a region. - Click Service List and choose Management & Deployment > Cloud Trace Service.
- Choose Tracker List in the left navigation pane. See Figure 1.
Figure 1 Viewing trackers
- In the tracker list, click Disable in the Operation column.
- Click Yes.
- After the tracker is disabled, the available operation changes from Disable to Enable. To enable the tracker again, click Enable and then click Yes. The system will start recording operations again.
diff --git a/docs/cbr/umn/cbr_03_0046.html b/docs/cbr/umn/cbr_03_0046.html
index 94000ecf..6707eb34 100644
--- a/docs/cbr/umn/cbr_03_0046.html
+++ b/docs/cbr/umn/cbr_03_0046.html
@@ -8,7 +8,13 @@
|
-2023-04-18
+ | 2023-07-02
+ |
+This issue is the twenty-second official release, which incorporates the following change:
+Modified the maximum number of tags that can be added to a vault.
+ |
+
+2023-04-18
|
This issue is the twentieth official release, which incorporates the following change:
Added some CBR operations that can be recorded by CTS in section "Auditing."
diff --git a/docs/cbr/umn/cbr_03_0047.html b/docs/cbr/umn/cbr_03_0047.html
index 800e239c..e83b494b 100644
--- a/docs/cbr/umn/cbr_03_0047.html
+++ b/docs/cbr/umn/cbr_03_0047.html
@@ -1,8 +1,7 @@
Permissions Management
-
+
- Creating a User and Granting CBR Permissions
diff --git a/docs/cbr/umn/cbr_03_0048.html b/docs/cbr/umn/cbr_03_0048.html
index ed6c9fe6..728608cf 100644
--- a/docs/cbr/umn/cbr_03_0048.html
+++ b/docs/cbr/umn/cbr_03_0048.html
@@ -5,10 +5,10 @@
- Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing CBR resources.
- Grant only the permissions required for users to perform a specific task.
- Entrust a cloud account or cloud service to perform efficient O&M on your CBR resources.
If your cloud account does not require individual IAM users, skip this section. If your account cannot meet your requirements, create IAM users by referring to Identity and Access Management User Guide.
Figure Figure 1 illustrates the procedure for granting permissions.
-PrerequisitesYou have learnt about Permissions Management and chosen the policies or roles according to your requirements. For the system policies of other services, see "System Permissions".
+ PrerequisitesLearn about the permissions (see Permissions) supported by CBR and choose policies or roles according to your requirements. For the system policies of other services, see section "Permissions".
- Process FlowFigure 1 Process for granting CBR permissions
- - Create a user group and assign permissions to it.
Create a user group on the IAM console, and assign the CBR ReadOnlyAccess policy to the group.
+Process FlowFigure 1 Process for granting CBR permissions
+ - Create a user group and assign permissions.
Create a user group on the IAM console, and assign the CBR ReadOnlyAccess policy to the group.
- Create an IAM user and add it to the user group.
Create a user on the IAM console and add the user to the group created in 1.
- Log in and verify permissions.
Log in to CBR Console as the created user and verify that the user has read-only permissions for CBR.
- Choose Service List > Cloud Backup and Recovery. Then click Create Server Backup Vault on CBR Console. If a message appears indicating that you do not have the permissions to perform the operation, the CBR ReadOnlyAccess policy has already taken effect.
- Choose any other service in Service List. If a message appears indicating that you do not have the permissions to access the service, the CBR ReadOnlyAccess policy has already taken effect.
@@ -21,3 +21,10 @@
+
+
\ No newline at end of file
diff --git a/docs/cbr/umn/cbr_03_0050.html b/docs/cbr/umn/cbr_03_0050.html
index d6bbf31d..143e75fd 100644
--- a/docs/cbr/umn/cbr_03_0050.html
+++ b/docs/cbr/umn/cbr_03_0050.html
@@ -1,10 +1,11 @@
Creating a Custom Policy
- You can create custom policies to supplement the system-defined policies of CBR. For the actions supported for custom policies, see section "Permissions Policies and Supported Actions" in Cloud Backup and Recovery API Reference.
+ You can create custom policies to supplement the system-defined policies of CBR. For the actions supported for custom policies, see section "Permissions Policies and Supported Actions" in Cloud Backup and Recovery API Reference.
You can create custom policies in either of the following ways:
- Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
- JSON: Edit JSON policies from scratch or based on an existing policy.
- This section provides examples of common custom CBR policies.
+ For details about how to create custom policies, see Creating a Custom Policy.
+ This section provides examples of common CBR custom policies.
Example Custom Policies- Example 1: Allowing users to create, modify, and delete vaults
{
"Version": "1.1",
"Statement": [
diff --git a/docs/cbr/umn/cbr_03_0104.html b/docs/cbr/umn/cbr_03_0104.html
index 99b801be..354da92c 100644
--- a/docs/cbr/umn/cbr_03_0104.html
+++ b/docs/cbr/umn/cbr_03_0104.html
@@ -52,7 +52,7 @@
Constraints- The vaults you have cannot be used for migration. The system will automatically migrate resources to the vaults created by the system.
- Backup resources of one account need to be migrated only once.
- After resources are migrated, disk backups and server backups will be automatically stored in CBR vaults. No further operations are required.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
+Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
- 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 resources to CBR

diff --git a/docs/cbr/umn/cbr_03_0107.html b/docs/cbr/umn/cbr_03_0107.html
index c7db1de3..ca798259 100644
--- a/docs/cbr/umn/cbr_03_0107.html
+++ b/docs/cbr/umn/cbr_03_0107.html
@@ -2,11 +2,12 @@
Using a Backup to Create a File System
In case of a virus attack, accidental deletion, or software or hardware fault, you can use an SFS Turbo file system backup to create a new file system. Once created, data on the new file system is the same as that in the backup.
- Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- - Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- If the status of the target backup is Available, click Create File System in the Operation column of the backup.
- Configure the file system parameters. See Figure 1.
Figure 1 Creating a file system
- - You can learn about the parameter descriptions in table "Parameter description" under "Creating an SFS Turbo File System" in the Scalable File Service User Guide.
+ Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
+ - Click the Backups tab and locate the desired backup. For details, see Viewing a Backup.
- Click Create File System in the Operation column of the backup. The button is available only when the backup status is Available.
- Configure the file system parameters. See Figure 1.
Figure 1 Creating a file system
+
+ - You can learn about the parameter descriptions in table "Parameter description" under "Creating an SFS Turbo File System" in "Create a File System" of the Scalable File Service User Guide.
- - Click Next.
- Go back to the file system list and check whether the file system is successfully created.
You will see the file system status change as follows: Creating, Available, Restoring, Available. You may not notice the Restoring status because Instant Restore is supported and the restoration speed is very fast. After the file system status has changed from Creating to Available, the file system is successfully created. After the status has changed from Restoring to Available, backup data has been successfully restored to the created file system.
+ - Click Create Now.
- Go back to the file system list and check whether the file system is successfully created.
You will see the file system status change as follows: Creating, Available, Restoring, Available. You may not notice the Restoring status because Instant Restore is supported and the restoration speed is very fast. After the file system status has changed from Creating to Available, the file system is successfully created. After the status has changed from Restoring to Available, backup data has been successfully restored to the created file system.
diff --git a/docs/cbr/umn/cbr_03_0114.html b/docs/cbr/umn/cbr_03_0114.html
index fea5aa98..ee100b9f 100644
--- a/docs/cbr/umn/cbr_03_0114.html
+++ b/docs/cbr/umn/cbr_03_0114.html
@@ -67,9 +67,8 @@
|
-Viewing Monitoring Statistics- Log in to the management console.
- View the monitoring graphs using either of the following methods.
- Method 1: Choose Storage > Cloud Backup and Recovery. In the vault list, locate the vault whose monitoring data you want to view and choose More > View Monitoring Data in the Operation column.
- Method 2: Choose Management & Deployment > Cloud Eye > Cloud Service Monitoring > Cloud Backup and Recovery. In the vault list, click View Metric in the Operation column of the vault whose monitoring data you want to view.
- - You can view the vault monitoring data by metric or monitored duration.
For more information, see the Cloud Eye User Guide.
-
+Viewing Monitoring Statistics- Log in to the management console.
- View the monitoring graphs using either of the following methods.
- Method 1: Choose Storage > Cloud Backup and Recovery. In the vault list, locate the vault whose monitoring data you want to view and choose More > View Monitoring Data in the Operation column.
- Method 2: Choose Management & Deployment > Cloud Eye > Cloud Service Monitoring > Cloud Backup and Recovery. In the vault list, click View Metric in the Operation column of the vault whose monitoring data you want to view.
+ - View the vault monitoring data by metric or monitored duration.
For more information, see the Cloud Eye User Guide.
diff --git a/docs/cbr/umn/cbr_03_0115.html b/docs/cbr/umn/cbr_03_0115.html
index 3f6890d1..343e678c 100644
--- a/docs/cbr/umn/cbr_03_0115.html
+++ b/docs/cbr/umn/cbr_03_0115.html
@@ -2,36 +2,36 @@
Creating an Alarm Rule
Cloud Eye allows you to use alarm templates to create alarm rules, making it easy and convenient to add or modify alarm rules for resources or cloud services, especially for a large number of resources and cloud services.
- This section describes how to create an alarm rule for CBR.
- Procedure- Log in to the management console.
- In the upper left corner of the page, click
and select your desired region and project. - Under Management & Deployment, select Cloud Eye. In the navigation pane on the left, choose Alarm Management > Alarm Rules.
- On the displayed page, click Create Alarm Rule in the upper right corner.
- In the Create Alarm Rule dialog box, set the parameters.
- Set Name and Description.
- Table 1 Parameters for configuring the rule name and descriptionParameter
+You can create alarm rules for CBR.
+Procedure- Log in to the management console.
- In the upper left corner of the page, click
and select a region. - Under Management & Deployment, select Cloud Eye. In the navigation pane on the left, choose Alarm Management > Alarm Rules.
- On the displayed page, click Create Alarm Rule in the upper right corner.
- On the displayed Create Alarm Rule page, configure the parameters.
- Set Name and Description.
Parameters for configuring the rule name and description
+ Parameter
|
-Description
+ | Description
|
-Example Value
+ | Example Value
|
-Name
+ | Name
|
-Name of the alarm rule. The system generates a random name, which you can modify.
+ | Name of the alarm rule. The system generates a random name, which you can modify.
|
-alarm-cgnw
+ | alarm-cgnw
|
-Description
+ | Description
|
-Alarm rule description. This parameter is optional.
+ | Alarm rule description. This parameter is optional.
|
--
+ | -
|
- - Set alarm content parameters.
- If you select Cloud Backup and Recovery for Resource Type, vaults are monitored with two metrics. Table 2 describes the parameters.
-
Table 2 ParametersParameter
+- Configure alarm content parameters.
- If you select Cloud Backup and Recovery for Resource Type, vaults are monitored with two metrics. Table 1 describes the parameters.
+
Table 1 ParametersParameter
|
Description
|
@@ -96,190 +96,9 @@
---|
- - If you set Resource Type to Event Monitoring, CBR resources are monitored based on specific events. Table 2 describes the parameters.
-
Table 3 ParametersParameter
- |
-Description
- |
-Example Value
- |
-
-
-Resource Type
- |
-Event Monitoring is selected in this example.
- |
-Event Monitoring
- |
-
-Dimension
- |
-Metric dimension of the selected resource type.
- |
-System event
- |
-
-Monitoring Scope
- |
-Monitoring scope for event monitoring.
-Default value: All resources
- |
--
- |
-
-Method
- |
-Select Create manually.
- |
-Create manually
- |
-
-Alarm Policy
- |
-Policy for triggering an alarm.
-Table 4 lists the supported CBR events that trigger alarms.
- |
--
- |
-
-
-
-
-
-Table 4 CBR events that trigger alarmsEvent Source
- |
-Event Name
- |
-Alarm Severity
- |
-Description
- |
-Solution
- |
-Impact
- |
-
-
-CBR
- |
-Failed to create the backup.
- |
-Major
- |
-Backup creation failed.
- |
-Manually create a backup or contact the administrator.
- |
-Data may be lost.
- |
-
-Failed to restore the resource using a backup.
- |
-Major
- |
-Resource restoration using a backup failed.
- |
-Restore the resource using another backup or contact the administrator.
- |
-Data may be lost.
- |
-
-Failed to delete the backup.
- |
-Major
- |
-Backup deletion failed.
- |
-Try again later or contact the administrator.
- |
-Charging may be abnormal.
- |
-
-Failed to delete the vault.
- |
-Major
- |
-Vault deletion failed.
- |
-Try again later or contact the administrator.
- |
-Charging may be abnormal.
- |
-
-Replication failure
- |
-Major
- |
-Backup replication failed.
- |
-Try again later or contact the administrator.
- |
-Data may be lost.
- |
-
-The backup is created successfully.
- |
-Major
- |
-Backup created.
- |
-None
- |
-None
- |
-
-Resource restoration using a backup succeeded.
- |
-Major
- |
-Resource restoration using a backup succeeded.
- |
-Check that data is successfully restored.
- |
-None
- |
-
-The backup is deleted successfully.
- |
-Major
- |
-Backup deleted.
- |
-None
- |
-None
- |
-
-The vault is deleted successfully.
- |
-Major
- |
-Vault deleted.
- |
-None
- |
-None
- |
-
-Replication success
- |
-Major
- |
-Backup replicated.
- |
-None
- |
-None
- |
-
-
-
-
- You can change the alarm severity as needed.
-
- - Configure the alarm notification.
-
Table 5 Parameters for configuring alarm notificationParameter
+- Configure alarm notifications.
+
Table 2 Parameters for configuring alarm notificationsParameter
|
Description
|
@@ -289,23 +108,23 @@
Alarm Notification
|
-Specifies whether to notify users when alarms are triggered. Notifications can be sent by email or text message, or through HTTP/HTTPS request to servers.
+ | Whether to notify users when alarms are triggered. Notifications can be sent by email or text message, or through HTTP/HTTPS request to servers.
You can enable (recommended) or disable Alarm Notification.
|
-
|
-Validity Period
+ | Notification Window
|
-Cloud Eye sends notifications only within the validity period specified in the alarm rule.
-For example, if Validity Period is set to 00:00-8:00, Cloud Eye sends notifications only within 00:00-8:00.
+ | Cloud Eye sends notifications only within the notification window specified in the alarm rule.
+If Notification Window is set to 00:00-8:00, Cloud Eye sends alarm notifications only within 00:00-8:00.
|
-
|
Notification Object
|
-Specifies the name of the topic the alarm notification is to be sent to.
+ | The name of the topic the alarm notification is to be sent to.
If you enable alarm notification, you need to select a topic. If no desirable topics are available, you need to create one first, whereupon the SMN service is invoked. For details about how to create a topic, see the Simple Message Notification User Guide.
|
-
@@ -313,7 +132,7 @@
|
Trigger Condition
|
-Specifies the condition for triggering the alarm notification. You can select Generated alarm, Cleared alarm, or both.
+ | The condition for triggering the alarm notification. You can select Generated alarm, Cleared alarm, or both.
|
-
|
diff --git a/docs/cbr/umn/cbr_05_0003.html b/docs/cbr/umn/cbr_05_0003.html
index 25840ad1..dbaff285 100644
--- a/docs/cbr/umn/cbr_05_0003.html
+++ b/docs/cbr/umn/cbr_05_0003.html
@@ -12,7 +12,7 @@
- Run the reboot command to restart the system.
Figure 4 Normal bootup page
- After entering the system, attach the data disks manually.
Figure 5 Attaching the data disks manually
- Run the blkid command to obtain the UUID information of the data disks.
Figure 6 Obtaining UUIDs of data disks
- - Run the vi /etc/fstab command to open the file, press i to enter the editing mode, and add the attachment information of all data disks. Then, press Esc to exit the editing mode and run :wq! to save the change and exit.
Figure 7 Adding attachment information of data disks
+ - Run the vi /etc/fstab command to open the file, press i to enter the editing mode, and add the attachment information of all data disks. Then, press Esc to exit the editing mode and run :wq! to save the change and exit.
Figure 7 Adding attachment information of data disks
After the information is added, the system will automatically attach the data disks on restart.
diff --git a/docs/cbr/umn/cbr_06_0003.html b/docs/cbr/umn/cbr_06_0003.html
index 48b753ab..91513078 100644
--- a/docs/cbr/umn/cbr_06_0003.html
+++ b/docs/cbr/umn/cbr_06_0003.html
@@ -4,7 +4,7 @@
CBR by default performs a full backup for a resource in the initial backup and incremental backups in all subsequent backups. If a resource has been backed up for many times, and then all of its generated backups are deleted, and the resource is backed up again, the system will also perform a full backup for the resource.
- The initial full backup covers only the used capacity of a disk. If a 100 GB disk contains 40 GB data, the initial backup consumes 40 GB backup space.
- Subsequent incremental backup backs up data changed since the last backup. If 5 GB data changed since the last backup, only the 5 GB changed data will be backed up.
CBR allows you to use any backup, no matter it is a full or incremental one, to restore the full data of a resource. By virtue of this, manual or automatic deletion of a backup will not affect the restoration function.
- Suppose server X has backups A, B, and C (in time sequence) and every backup involves data changes. If backup B is deleted, you can still use backup A or C to restore data.
+ Suppose server X has backups A, B, and C (in time sequence) and every backup involves data changes. If backup B is deleted, you can use backup A or C to restore data. If backup A and backup B are both deleted, you can still use backup C to restore data.
In extreme cases, the size of a backup is the same as the disk size. The used capacity in a full backup and the changed capacity in an incremental backup are calculated based on the data block change in a disk, not by calculating the file change in the operating system. The size of a full backup cannot be evaluated based on the file capacity in the operating system, and the size of an incremental backup cannot be evaluated based on the file size change.
diff --git a/docs/cbr/umn/cbr_06_0005.html b/docs/cbr/umn/cbr_06_0005.html
index a8dcda0e..deccaf53 100644
--- a/docs/cbr/umn/cbr_06_0005.html
+++ b/docs/cbr/umn/cbr_06_0005.html
@@ -3,40 +3,34 @@
What Are the Differences Between Backups and Snapshots?
Both backups and snapshots provide data redundancy for disks to improve data reliability. Table 1 lists the differences between them.
- Table 1 Differences between backups and snapshotsItem
+Table 1 Differences between backups and snapshotsItem
|
-Storage Solution
+ | Storage Solution
|
-Data Synchronization
+ | Data Synchronization
|
-DR Range
- |
-Service Recovery
+ | Service Recovery
|
-Backup
+ | Backup
|
-Backup data is stored in OBS, instead of disks. This ensures data restoration upon disk data loss or corruption.
+ | Backup data is stored in OBS, instead of disks. This ensures data restoration upon disk data loss or corruption.
|
-A backup is the data copy of a disk at a given point in time. CBR supports automatic backup by configuring backup policies. Deleting a disk will not clear its backups.
+ | A backup is the data copy of a disk at a given point in time. CBR supports automatic backup by configuring backup policies. Deleting a disk will not clear its backups.
|
-A backup and its source disk reside in the same AZ.
- |
-Data can be recovered and services can be restored by restoring the backup data to original disks or creating new disks from backups, ensuring excellent data reliability.
+ | You can restore backups to their original disks or create new disks from the backups.
|
-Snapshot
+ | Snapshot
|
-Snapshot data is stored with disk data.
+ | Snapshot data is stored with disk data.
NOTE: Creating a backup requires a certain amount of time because data needs to be transferred. Therefore, creating or rolling back a snapshot consumes less time than creating a backup.
|
-A snapshot is the state of a disk at a specific point in time. If a disk is deleted, all the snapshots created for this disk will also be deleted. If you have reinstalled or changed the server OS, snapshots of the system disk are automatically deleted. Snapshots of the data disks can be used as usual.
+ | A snapshot is the state of a disk at a specific point in time. If a disk is deleted, all the snapshots created for this disk will also be deleted. If you have reinstalled or changed the server OS, snapshots of the system disk are automatically deleted. Snapshots of the data disks can be used as usual.
|
-A snapshot and its source disk reside in the same AZ.
- |
-You can use a snapshot to roll back its original disk or create a disk for data restoration and service recovery.
+ | You can use a snapshot to roll back its original disk or create a disk for data restoration and service recovery.
|
diff --git a/docs/cbr/umn/cbr_06_0016.html b/docs/cbr/umn/cbr_06_0016.html
index bde80fb3..e5902214 100644
--- a/docs/cbr/umn/cbr_06_0016.html
+++ b/docs/cbr/umn/cbr_06_0016.html
@@ -1,9 +1,9 @@
Can a Server Be Restored Using Its Backups After It Is Changed?
-Yes. If a server has been backed up and then changed such as adding, deleting, or expanding disks, its backups can still be used to restore data. You are advised to back up data again after the change.
- If you have added a disk after backup and then use backups to restore data, data on the newly added disk will not change.
- If you have deleted a disk after backup and then use backups to restore data, data on the deleted disk will not be restored.
+ Yes. If a server has been backed up and then changed (adding, deleting, or expanding disks), its backups can still be used to restore data. You are advised to back up data again after the change.
+ If you have added a disk after a backup and then use the backup to restore data, data on the new disk will not change.
+ If you have deleted a disk after a backup and then use the backup to restore data, data on the deleted disk cannot be restored.
diff --git a/docs/cbr/umn/cbr_06_0018.html b/docs/cbr/umn/cbr_06_0018.html
index 5a64c31a..60607e3f 100644
--- a/docs/cbr/umn/cbr_06_0018.html
+++ b/docs/cbr/umn/cbr_06_0018.html
@@ -1,7 +1,7 @@
What Can I Do if the Password Becomes a Random One After I Use a Backup to Restore a Server or Use an Image to Create a Server?
- For details about how to reset the password, see section Passwords in the Elastic Cloud Server User Guide.
+ For details about how to reset the password, see Passwords in the Elastic Cloud Server User Guide.
diff --git a/docs/cbr/umn/cbr_06_0020.html b/docs/cbr/umn/cbr_06_0020.html
index c4037625..b774c82f 100644
--- a/docs/cbr/umn/cbr_06_0020.html
+++ b/docs/cbr/umn/cbr_06_0020.html
@@ -1,7 +1,7 @@
Is There a Quota for CBR Vaults?
- No. You can create as many vaults as needed.
+ There are no quotas on CBR vaults. You can create as many vaults as needed.
diff --git a/docs/cbr/umn/cbr_06_0042.html b/docs/cbr/umn/cbr_06_0042.html
index f8068176..658cf935 100644
--- a/docs/cbr/umn/cbr_06_0042.html
+++ b/docs/cbr/umn/cbr_06_0042.html
@@ -7,7 +7,7 @@
|
---|
|
---|
|
---|
|
---|
|
---|
|
---|
---|
|
---|
|