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_0011.html b/docs/cbr/umn/cbr_01_0011.html
index 325d20b24..8bcc23b80 100644
--- a/docs/cbr/umn/cbr_01_0011.html
+++ b/docs/cbr/umn/cbr_01_0011.html
@@ -1,6 +1,6 @@
-Permissions
+Permissions Management
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.
diff --git a/docs/cbr/umn/cbr_01_0012.html b/docs/cbr/umn/cbr_01_0012.html
index 7b3fcfbc4..e7d895429 100644
--- a/docs/cbr/umn/cbr_01_0012.html
+++ b/docs/cbr/umn/cbr_01_0012.html
@@ -14,7 +14,7 @@
Instant Restore is an enhanced function of CBR and requires no additional configuration. After Instant Restore is provided, you take less time to restore server data or create images.
Enhanced BackupEnhanced backups are backups generated after Instant Restore is provided. Enhanced backups make it faster to restore server data or create images.
- Before providing Instant Restore, CBR generates common backups. After providing Instant Restore, CBR first performs a full backup for each associated resource and then generates enhanced backups. CBR only generates enhanced backups currently.
+ Before providing Instant Restore, CBR generates common backups. After providing Instant Restore, CBR first performs a full backup for each associated resource and then generates enhanced backups. CBR only generates enhanced backups for new resources currently.
For the same resource, an enhanced backup and a common backup have the same backup content and size. They only differ in the restoration speed.
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.
+ EfficientIncremental 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.
diff --git a/docs/cbr/umn/cbr_01_0035.html b/docs/cbr/umn/cbr_01_0035.html
new file mode 100644
index 000000000..04f94817e
--- /dev/null
+++ b/docs/cbr/umn/cbr_01_0035.html
@@ -0,0 +1,32 @@
+
+
+ Enabling Backup Locking
+ ScenariosTo prevent the backup data from being deleted by mistake or maliciously, you can enable backup locking for vaults to improve data security.
+ Once enabled, all backups in the vault enter the WORM (write once, read many) status. No one can delete the backups that are in their retention periods.
+ This section describes how to enable backup locking for a vault. You can also enable it when creating a vault.
+ - Backup locking does not affect normal backup, restoration, and replication operations.
- Manual backups are not affected by backup locking and can be manually deleted.
+
+
+ Constraints- Backup locking cannot be disabled after it is enabled.
- After backup locking is enabled, associated resources cannot be dissociated and files cannot be migrated.
- After backup locking is enabled, policy-based backups can only be deleted after they expire. You cannot manually delete them.
+
+ Enabling Backup Locking for an Existing Vault- Log in to the 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 any backup page, locate the target vault and choose More > Enable Backup Locking in the Operation column.
- In the displayed dialog box, click OK to enable backup locking.
Figure 1 Backup locking
+
+
+ - Click OK.
The vault list is displayed, and you can see that the value in the Back Locking column is Enabled.
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/cbr/umn/cbr_02_0003.html b/docs/cbr/umn/cbr_02_0003.html
index ff4cb6115..0ee0ad143 100644
--- a/docs/cbr/umn/cbr_02_0003.html
+++ b/docs/cbr/umn/cbr_02_0003.html
@@ -3,23 +3,29 @@
Creating a Server Backup Vault
This section describes how to create a server backup vault.
Procedure- Log in to the 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.
- Replication: A server replication vault stores replicas of server backups. If you select Replication, you do not need to select a server.
+ - 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.
- Replication: A server replication vault stores replicas of server backups. If you select Replication, you do not need to select a server.
For example, if you want to back up a server, select Backup for the vault protection type. If you want to replicate backups of a server from one region to another, select Replication for the vault in this other region.
+ - Determine whether to enable backup locking.
If enabled, backups in the vault will not be deleted maliciously or by mistake, improving data reliability.
+
+ Backup locking cannot be disabled after it is enabled.
+ - (Optional) In the server list, select the servers or disks you want to back up. After the servers or disks are selected, they are added to the list of selected servers. See Figure 1. You can also select specific disks on a server and associate them with the vault.
To avoid data inconsistency after restoration, you are advised to back up the entire server.
If you want to back up only some of the disks to reduce costs, ensure that data on the backed up disks does not depend on the disks that are not backed up. Or, data inconsistency may occur.
For example, the data of an Oracle database is scattered across different disks. If only some of the disks are backed up, restoration restores only the data of the disks that have been backed up, with data on the rest of the disks unchanged. As a result, the data may be inconsistent and the Oracle database may fail to start.
Figure 1 Selecting servers
+
-
+
- The selected servers must have not been associated with any vault and must be in the Running or Stopped state.
- You can also associate servers with the vault you are creating later if you skip this step.
- Specify a vault capacity ranging from 10 GB to 10,485,760 GB. Properly plan the vault capacity, which must be at least the same as the size of the servers you want to back up. Also, if a backup policy is applied to the vault, more capacity is required.
As the vault's used space grows, you can expand the vault capacity if it becomes insufficient. See Figure 2. Figure 2 Setting the vault capacity
+
+
- Configure auto backup. See Figure 3.
- If you select Configure, you must then select an existing backup policy or create a new policy. After the vault is created, CBR will apply the policy to this vault, and all servers associated with this vault will be automatically backed up based on this policy.
- If you select Skip, servers associated with this vault will not be automatically backed up until you apply a backup policy to the vault.
Figure 3 Configuring auto backup
@@ -30,30 +36,30 @@
Table 1 describes the parameters of a tag.
- Table 1 Tag parameter descriptionParameter
+Table 1 Tag parameter descriptionParameter
|
-Description
+ | Description
|
-Example Value
+ | Example Value
|
|---|
-Key
+ | Key
|
-Each tag has a unique key. You can customize a key or select the key of an existing tag created in TMS.
+ | Each tag has a unique key. You can customize a key or select the key of an existing tag created in TMS.
A tag key:
- Can contain 1 to 36 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
|
-Key_0001
+ | Key_0001
|
-Value
+ | Value
|
-A tag value can be repetitive or left blank.
+ | A tag value can be repetitive or left blank.
A tag value:
- Can contain 0 to 43 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
|
-Value_0001
+ | Value_0001
|
@@ -63,7 +69,7 @@
- Specify a name for the vault.
The name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-), for example, vault-f61e.
You can also use the default name vault_xxxx.
- - Complete the creation as prompted.
- Go back to the Cloud Server Backups page. You can see the created vault in the vault list.
You can associate servers with the vault and perform backup for the servers. For details, see Querying a Vault.
+ - Complete the creation as prompted.
- Go back to the Cloud Server Backups page. You can see the created vault in the vault list.
You can associate servers with the vault and perform backup for the servers. For details, see Viewing a Vault.
diff --git a/docs/cbr/umn/cbr_02_0004.html b/docs/cbr/umn/cbr_02_0004.html
index d79ddf981..8f6179c7a 100644
--- a/docs/cbr/umn/cbr_02_0004.html
+++ b/docs/cbr/umn/cbr_02_0004.html
@@ -3,53 +3,58 @@
Creating a Disk Backup Vault
This section describes how to create a disk backup vault.
Procedure- Log in to the 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.
-
-
-
-
-
+ - In the upper right corner of the page, click Create Disk Backup Vault.
- Determine whether to enable backup locking.
If backup locking is enabled, backups in the vault will not be deleted maliciously or by mistake. This improves data reliability.
+
+ Backup locking cannot be disabled after it is enabled.
+
+ - (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.
+
+
+
+
- The selected disks must have not been associated with any vault and must be in the Available or In-use state.
- You can also associate disks 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 disks you want to back up. See Figure 2.
Figure 2 Setting the vault capacity
-
+
+
- Configure auto backup. See Figure 3.
- 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 disks associated with this vault will be automatically backed up based on this policy.
- If you select Skip, disks associated with this vault will not be automatically backed up until you apply a backup policy to the vault.
-Figure 3 Configuring auto backup
+Figure 3 Configuring auto backup
+
- (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 20 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. Vault tags are used to filter and manage vaults only. A vault can have a maximum of 20 tags. See Figure 4.
-
+
Table 1 describes the parameters of a tag.
- Table 1 Tag parameter descriptionParameter
+Table 1 Tag parameter descriptionParameter
|
-Description
+ | Description
|
-Example Value
+ | Example Value
|
|---|
-Key
+ | Key
|
-Each tag has a unique key. You can customize a key or select the key of an existing tag created in TMS.
+ | Each tag has a unique key. You can customize a key or select the key of an existing tag created in TMS.
A tag key:
- Can contain 1 to 36 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
|
-Key_0001
+ | Key_0001
|
-Value
+ | Value
|
-A tag value can be repetitive or left blank.
+ | A tag value can be repetitive or left blank.
A tag value:
- Can contain 0 to 43 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
|
-Value_0001
+ | Value_0001
|
diff --git a/docs/cbr/umn/cbr_02_0006.html b/docs/cbr/umn/cbr_02_0006.html
index 084e270fc..a3baa65e4 100644
--- a/docs/cbr/umn/cbr_02_0006.html
+++ b/docs/cbr/umn/cbr_02_0006.html
@@ -9,20 +9,16 @@
Procedure- Log in to the 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.
diff --git a/docs/cbr/umn/cbr_02_0007.html b/docs/cbr/umn/cbr_02_0007.html
index b506ae9c2..55fa5fc9c 100644
--- a/docs/cbr/umn/cbr_02_0007.html
+++ b/docs/cbr/umn/cbr_02_0007.html
@@ -8,19 +8,17 @@
Procedure- Log in to the 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.
diff --git a/docs/cbr/umn/cbr_02_0009.html b/docs/cbr/umn/cbr_02_0009.html
index 6b39a5af3..9387d89e5 100644
--- a/docs/cbr/umn/cbr_02_0009.html
+++ b/docs/cbr/umn/cbr_02_0009.html
@@ -33,9 +33,9 @@
Procedure- Log in to the 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
-
-
+
+
diff --git a/docs/cbr/umn/cbr_02_0010.html b/docs/cbr/umn/cbr_02_0010.html
index 7e2846fd9..e8213de5f 100644
--- a/docs/cbr/umn/cbr_02_0010.html
+++ b/docs/cbr/umn/cbr_02_0010.html
@@ -3,7 +3,11 @@
Creating an SFS Turbo Backup Vault
This section describes how to create an SFS Turbo backup vault.
Procedure- Log in to the 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.
+ - 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.
+ - Determine whether to enable backup locking.
If backup locking is enabled, backups in the vault will not be deleted maliciously or by mistake. This improves data reliability.
+
+ Backup locking cannot be disabled after it is enabled.
+
- (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
@@ -16,30 +20,30 @@
Table 1 describes the parameters of a tag.
- Table 1 Tag parameter descriptionParameter
+Table 1 Tag parameter descriptionParameter
|
-Description
+ | Description
|
-Example Value
+ | Example Value
|
|---|
-Key
+ | Key
|
-Each tag has a unique key. You can customize a key or select the key of an existing tag created in TMS.
+ | Each tag has a unique key. You can customize a key or select the key of an existing tag created in TMS.
A tag key:
- Can contain 1 to 36 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
|
-Key_0001
+ | Key_0001
|
-Value
+ | Value
|
-A tag value can be repetitive or left blank.
+ | A tag value can be repetitive or left blank.
A tag value:
- Can contain 0 to 43 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
|
-Value_0001
+ | Value_0001
|
diff --git a/docs/cbr/umn/cbr_02_0012.html b/docs/cbr/umn/cbr_02_0012.html
index 0cb9f4aa3..9ecb927c1 100644
--- a/docs/cbr/umn/cbr_02_0012.html
+++ b/docs/cbr/umn/cbr_02_0012.html
@@ -11,14 +11,11 @@
-
-
- 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.
-
diff --git a/docs/cbr/umn/cbr_03_0001.html b/docs/cbr/umn/cbr_03_0001.html
index 3dd86260b..ad2318e95 100644
--- a/docs/cbr/umn/cbr_03_0001.html
+++ b/docs/cbr/umn/cbr_03_0001.html
@@ -4,7 +4,7 @@
diff --git a/docs/cbr/umn/cbr_03_0002.html b/docs/cbr/umn/cbr_03_0002.html
index 245b9e5d3..3340b78fc 100644
--- a/docs/cbr/umn/cbr_03_0002.html
+++ b/docs/cbr/umn/cbr_03_0002.html
@@ -1,49 +1,61 @@
-Querying a Vault
+Viewing a Vault
You can set search criteria for querying desired vaults in the vault list.
PrerequisitesA vault has been created.
Viewing Vault Details- Log in to the 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.
-
-
- Table 1 Basic information parametersParameter
+
+
+ Table 1 Basic information parametersParameter
|
-Description
+ | Description
|
|---|
-Name/ID
+ | Name/ID
|
-Name and ID of the vault. Click the vault name to view details about the vault.
+ | Name and ID of the vault. Click the vault name to view details about the vault.
|
-Type
+ | Type
|
-Vault type
+ | Vault type
|
-Status
+ | Status
|
-Vault status. Table 2 describes the vault statuses.
+ | Vault status. Table 2 describes the vault statuses.
|
-Specifications
+ | Backup Locking
|
-Vault specifications
+ | Whether backup locking is enabled for the vault.
+- Enabled: If backup locking is enabled, it cannot be disabled.
- Disabled: Backup locking is disabled for the vault.
+ |
+
+Specifications
+ |
+Vault specifications
- A server backup vault stores backups of non-database servers.
|
-Vault Capacity (GB)
+ | Vault Capacity (GB)
|
-Capacity used by the backups in the vault. It shows the space used by backups and the total vault capacity.
+ | Capacity used by the backups in the vault. It shows the space used by backups and the total vault capacity.
For example: If 20/100 is displayed, 20 GB has been used out of the 100 GB vault capacity.
|
-Associated Servers/File Systems/Disks
+ | Policy Status
|
-Number of servers, file systems, and disks associated with the vault. You can click the number to view details of associated resources. The associated capacity shown on the details page is the total capacity of all the resources that have been associated with this vault.
+ | Policy status or no policy applied
+- No policy applied: The vault has not been applied with any backup policy yet.
- Enabled: The vault has been applied with a backup policy, and the policy is enabled.
- Disabled: The vault has been applied with a backup policy, but the policy is disabled.
+ |
+
+Associated Servers/File Systems/Disks
+ |
+Number of servers, file systems, and disks associated with the vault. You can click the number to view details of associated resources. The associated capacity shown on the details page is the total capacity of all the resources that have been associated with this vault.
|
@@ -51,52 +63,52 @@
- On the Vaults tab page, set filter criteria to view specific vaults. See Figure 2.
Figure 2 Querying a vault
-
-- Select a value from the status drop-down list to query vaults by status. Table 2 describes the vault statuses.
-
Table 2 Vault statusesStatus
+
+ - Select a value from the status drop-down list to query vaults by status. Table 2 describes the vault statuses.
+
Table 2 Vault statusesStatus
|
-Attribute
+ | Attribute
|
-Description
+ | Description
|
|---|
-All statuses
+ | All statuses
|
---
+ | --
|
-All vaults are displayed if this value is selected.
+ | All vaults are displayed if this value is selected.
|
-Available
+ | Available
|
-A stable state
+ | A stable state
|
-A stable state after a vault task is complete.
+ | A stable state after a vault task is complete.
This state allows most of the operations.
|
-Locked
+ | Locked
|
-An intermediate state
+ | An intermediate state
|
-An intermediate state displayed when a capacity expansion is in progress.
+ | 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.
|
-Deleting
+ | Deleting
|
-An intermediate state
+ | An intermediate state
|
-An intermediate state displayed when a vault is being deleted.
+ | An intermediate state displayed when a vault is being deleted.
In this state, a progress bar is displayed indicating the deletion progress. If the progress bar remains unchanged for an extended time, an exception has occurred. Contact technical support.
|
-Error
+ | Error
|
-A stable state
+ | A stable state
|
-A vault enters the Error state when an exception occurs during task execution.
+ | A vault enters the Error state when an exception occurs during task execution.
You can click Tasks in the navigation pane on the left to view the error cause. If the error persists, contact technical support.
|
@@ -106,8 +118,9 @@
- 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. 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.
+ - 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 ac3f89023..98f43a3c9 100644
--- a/docs/cbr/umn/cbr_03_0003.html
+++ b/docs/cbr/umn/cbr_03_0003.html
@@ -8,14 +8,16 @@
Procedure- Log in to the 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
-
-
+
+
+
- - Click Yes.
+
+ - Click OK.
diff --git a/docs/cbr/umn/cbr_03_0005.html b/docs/cbr/umn/cbr_03_0005.html
index 2683011b3..d007895b8 100644
--- a/docs/cbr/umn/cbr_03_0005.html
+++ b/docs/cbr/umn/cbr_03_0005.html
@@ -8,12 +8,11 @@
- 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
-
+
-
-
+
- Confirm the information and click Yes.
- Find the target vault and choose More > Expand Capacity in the Operation column. See Figure 1.
Figure 1 Expanding vault capacity
-
-
+
+
-
+
- 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_0009.html b/docs/cbr/umn/cbr_03_0009.html
index 3c100b11d..711d1ae46 100644
--- a/docs/cbr/umn/cbr_03_0009.html
+++ b/docs/cbr/umn/cbr_03_0009.html
@@ -1,11 +1,11 @@
Replicating a Vault Across Regions
-ScenariosCBR allows you to replicate server backup vaults entirely to replication vaults in other regions of the same account. Replicas of server backups in the destination region can be used to create images and provision servers. to quickly deploy services across regions.
+ ScenariosCBR allows you to replicate all backups in a server backup vault to replication vaults in other regions of the same account. Replicas of server backups in the destination region can be used to create images and provision servers. to quickly deploy services across regions.
There are two methods available for replicating a vault.
- Manual replication: Select a backup vault and manually replicate it.
- Policy-based replication: Configure a replication policy to periodically replicate backups that have not been replicated or failed to be replicated to the destination region.
- Constraints- Disk backup vaults cannot be replicated to other regions.
- Backup data can be replicated to vaults in different regions, and backup replicas occupy the replication vault space.
- A server backup vault can be replicated only when it contains at least one backup that meets all the following conditions:
- The backup is an ECS backup.
- The backup contains system disk data.
- The backup is in the Available state.
+Constraints- Disk backup vaults cannot be replicated to other regions.
- Backup data can be replicated to vaults in different regions. Any traffic costs associated with this operation will be attributed to the source region. Backup replicas occupy the replication vault space.
- A server backup vault can be replicated only when it contains at least one backup that meets all the following conditions:
- The backup is an ECS backup.
- The backup contains system disk data.
- The backup is in the Available state.
- Only backup vaults of the same type can be replicated. Replicated vaults cannot be replicated again but their replicas can be used to create images.
- A backup vault can be replicated to different destination regions. For manual and policy-based vault replication, a vault can only be replicated to a destination region once. It cannot be replicated to that region again, even if its backups have been deleted.
- Only replication-supported regions can be selected as destination regions.
- On the Vaults tab, find the target backup vault.
- Choose More > Create Replica in the Operation column of the vault. See Figure 1.
Figure 1 Creating a replica
-
- In the displayed dialog box, configure the parameters as described in Table 1.
@@ -38,7 +37,7 @@
- Click OK.
- After the replication is complete, you can switch to the destination region to view generated replicas. For details, see Querying a Vault. You can then use replicas to create images.
+- Click OK.
- After the replication is complete, you can switch to the destination region to view generated replicas. For details, see Viewing a Vault. You can then use replicas to create images.
diff --git a/docs/cbr/umn/cbr_03_0013.html b/docs/cbr/umn/cbr_03_0013.html
index ee03f296b..36038fa6a 100644
--- a/docs/cbr/umn/cbr_03_0013.html
+++ b/docs/cbr/umn/cbr_03_0013.html
@@ -1,74 +1,76 @@
Viewing a Backup
- 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.
+ ScenarioIn 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.
Procedure- Log in to the 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 above the backup list. Table 1 describes the backup statuses.
-
Table 1 Backup statusesStatus
+
+ - You can search for backups by selecting a status from the All statuses drop-down list above the backup list. Table 1 describes the backup statuses.
+
Table 1 Backup statusesStatus
|
-Status Attribute
+ | Status Attribute
|
-Description
+ | Description
|
|---|
-All statuses
+ | All statuses
|
---
+ | --
|
-All backups are displayed if this value is selected.
+ | All backups are displayed if this value is selected.
|
-Available
+ | Available
|
-A stable state
+ | A stable state
|
-A stable state of a backup after the backup is created, indicating that the backup is currently not being used.
+ | A stable state of a backup after the backup is created, indicating that the backup is currently not being used.
This state allows most of the operations.
|
-Creating
+ | Creating
|
-An intermediate state
+ | An intermediate state
|
-An intermediate state of a backup from the start of a backup job to the completion of this job.
+ | An intermediate state of a backup from the start of a backup job to the completion of this job.
In the Tasks list, a progress bar is displayed for a backup task in this state. If the progress bar remains unchanged for an extended time, an exception has occurred. Contact technical support.
|
-Restoring
+ | Restoring
|
-An intermediate state
+ | An intermediate state
|
-An intermediate state when using the backup to restore data.
+ | An intermediate state when using the backup to restore data.
In the Tasks list, a progress bar is displayed for a restoration task in this state. If the progress bar remains unchanged for an extended time, an exception has occurred. Contact technical support.
|
-Deleting
+ | Deleting
|
-An intermediate state
+ | An intermediate state
|
-An intermediate state from the start of deleting the backup to the completion of deleting the backup.
+ | An intermediate state from the start of deleting the backup to the completion of deleting the backup.
In the Tasks list, a progress bar is displayed for a deletion task in this state. If the progress bar remains unchanged for an extended time, an exception has occurred. Contact technical support.
|
-Error
+ | Error
|
-A stable state
+ | A stable state
|
-A backup enters the Error state when an exception occurs.
+ | A backup enters the Error state when an exception occurs.
A backup in this state cannot be used for restoration, and must be deleted manually. If manual deletion fails, contact technical support.
|
- You can search for backups by clicking Advanced Search above the backup list.
You can search by specifying a backup name, backup ID, backup type, backup status, vault ID, server name, server ID, server type, protection type, or the creation date. See Figure 2.
+ - You can search for backups by clicking Advanced Search above the backup list.
You can search by specifying a backup name, backup ID, backup status, vault ID, server name, server type, server ID, or the creation date. See Figure 2.
-
+
+
- Click the backup name to view details about the backup.
diff --git a/docs/cbr/umn/cbr_03_0014.html b/docs/cbr/umn/cbr_03_0014.html
index 2475fbcd1..8f6a1985f 100644
--- a/docs/cbr/umn/cbr_03_0014.html
+++ b/docs/cbr/umn/cbr_03_0014.html
@@ -8,17 +8,15 @@
Recipient
- 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 the 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.
+Procedure- Log in to the 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
+
-
-
-
-
+
@@ -26,18 +24,16 @@
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 10 projects.
- Click OK.
- - Click the Cancel Sharing tab, select the projects you want to cancel sharing, and 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 the 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.
+Procedure- Log in to the 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.
diff --git a/docs/cbr/umn/cbr_03_0015.html b/docs/cbr/umn/cbr_03_0015.html
index 9abed435b..2b350a496 100644
--- a/docs/cbr/umn/cbr_03_0015.html
+++ b/docs/cbr/umn/cbr_03_0015.html
@@ -3,22 +3,21 @@
Deleting a Backup
You can delete unwanted backups to reduce space usage and costs.
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.
- Backups are not stored on a server. Deleting backups has no impact on the server performance.
+ - Backups are not stored on a server. Deleting backups has no impact on the server performance.
- If a backup has been created and the next backup task is in progress, CBR will not allow you to delete the most recent backup created. You can delete the backup only after the backup task is complete.
- CBR automatically creates snapshots during backup and retains the latest snapshot for each disk.
Prerequisites- There is at least one backup.
- The backup to be deleted is in the Available or Error state.
Procedure- Log in to the 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
+
-
-
-
-
+
+
-
- - Click Yes.
+
+ - Click OK.
diff --git a/docs/cbr/umn/cbr_03_0016.html b/docs/cbr/umn/cbr_03_0016.html
index 6fc5bb46e..bfcb4d206 100644
--- a/docs/cbr/umn/cbr_03_0016.html
+++ b/docs/cbr/umn/cbr_03_0016.html
@@ -15,7 +15,7 @@
- - 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.
+ - 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_0024.html b/docs/cbr/umn/cbr_03_0024.html
index 8b034eec4..d8d0ca85f 100644
--- a/docs/cbr/umn/cbr_03_0024.html
+++ b/docs/cbr/umn/cbr_03_0024.html
@@ -4,6 +4,8 @@
+- Viewing the Policy of a Vault
+
- Creating a Backup Policy
- Creating a Replication Policy
diff --git a/docs/cbr/umn/cbr_03_0025.html b/docs/cbr/umn/cbr_03_0025.html
index 1dc6e31db..982500fc8 100644
--- a/docs/cbr/umn/cbr_03_0025.html
+++ b/docs/cbr/umn/cbr_03_0025.html
@@ -4,18 +4,18 @@
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.
Peak hours of the backup service are from 22:00 to 08:00, during which there may be delays. So you are advised to evaluate your service types and schedule backups in discrete time periods.
- 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.
- CBR by default performs a full backup for a resource in the initial backup and incremental backups in all subsequent backups.
- The minimum interval between two full backups is 1 day.
+ 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.
- CBR by default performs a full backup for a resource in the initial backup and incremental backups in subsequent backups.
- The minimum interval between two full backups is 1 day.
Procedure- Log in to the 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 left 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
|
@@ -78,8 +78,8 @@
- 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 If there are more than five backup replicas, the system automatically deletes the earliest backup replicas. 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.
- 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.
+ 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. That is, a total of five backups are retained. If there are more than five backup replicas, the system automatically deletes the earliest backup replicas. 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 during 08:00 to 20:00 in batches. For example, if a backup expired at 20:00 on November 23, 2024, it will be deleted during 08:00 to 20:00 on November 24, 2024. In this way, backup data can be deleted during off-peak hours.
- The retention rules apply only to auto-generated backups, but not manual backups. Manual backups need to be deleted manually.
- A maximum of 10 backups are retained for failed periodic backup tasks. They are retained for one month and can be deleted manually.
- If a backup has been created and the next backup task is in progress, CBR will not allow you to delete the most recent backup created. You can delete the backup only after the backup task is complete.
diff --git a/docs/cbr/umn/cbr_03_0026.html b/docs/cbr/umn/cbr_03_0026.html
index 546666f9a..0d285b9e1 100644
--- a/docs/cbr/umn/cbr_03_0026.html
+++ b/docs/cbr/umn/cbr_03_0026.html
@@ -6,7 +6,7 @@
Constraints- You can only apply replication policies to server backup vaults.
Procedure- Log in to the 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 left navigation pane and click the Replication Policies tab. In the upper right corner, click Create Policy. See Figure 1.
Figure 1 Creating a replication policy
+ - Choose Policies in the left navigation pane and click the Replication Policies tab. In the upper right corner, click Create Policy. Select Replication Policy for Type. See Figure 1.
Figure 1 Creating a replication policy
diff --git a/docs/cbr/umn/cbr_03_0027.html b/docs/cbr/umn/cbr_03_0027.html
index b4379e82f..fcc4b43e7 100644
--- a/docs/cbr/umn/cbr_03_0027.html
+++ b/docs/cbr/umn/cbr_03_0027.html
@@ -7,6 +7,7 @@
Procedure- Log in to the 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
+
diff --git a/docs/cbr/umn/cbr_03_0028.html b/docs/cbr/umn/cbr_03_0028.html
index 580171eef..d2d022d80 100644
--- a/docs/cbr/umn/cbr_03_0028.html
+++ b/docs/cbr/umn/cbr_03_0028.html
@@ -5,9 +5,10 @@
PrerequisitesAt least one policy has been created.
Procedure- Log in to the 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.
+ - Click the Backup Policies tab, locate the row that contains the policy you want to delete, and click Delete.
Figure 1 Deleting a policy
+ 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.
+ - Confirm the information and click OK.
@@ -16,3 +17,10 @@
Figure 1 Restoring a server
-
-
-
-
+
- (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.
-
-
- 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.
diff --git a/docs/cbr/umn/cbr_03_0035.html b/docs/cbr/umn/cbr_03_0035.html
index 3c0dee5d3..22a3d4e11 100644
--- a/docs/cbr/umn/cbr_03_0035.html
+++ b/docs/cbr/umn/cbr_03_0035.html
@@ -4,10 +4,11 @@
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 the 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.
+Procedure for Viewing the Task Execution Status- Log in to the 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.
-
+
+
- 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_0037.html b/docs/cbr/umn/cbr_03_0037.html
index 42deb415a..b72707a5c 100644
--- a/docs/cbr/umn/cbr_03_0037.html
+++ b/docs/cbr/umn/cbr_03_0037.html
@@ -4,7 +4,7 @@
What Is Quota?Quotas can limit the number or amount of resources available to users, such as the maximum number of ECS or EVS disks that can be created.
If the existing resource quota cannot meet your service requirements, you can apply for a higher quota.
- How Do I View My Quotas?- Log in to the management console.
- Click
 in the upper left corner and select the desired region and project. - In the upper right corner of the page, click
 .The Service Quota page is displayed.
+How Do I View My Quotas?- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- In the upper right corner of the page, click .
The Quotas page is displayed.
- View the used and total quota of each type of resources on the displayed page.
If a quota cannot meet service requirements, apply for a higher quota.
Permissions Management
+Management permissions
diff --git a/docs/cbr/umn/cbr_03_0048.html b/docs/cbr/umn/cbr_03_0048.html
index b3c5a9c6a..5cc02b8af 100644
--- a/docs/cbr/umn/cbr_03_0048.html
+++ b/docs/cbr/umn/cbr_03_0048.html
@@ -5,7 +5,7 @@
- Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing CBR resources.
- Grant users only the permissions required to perform a given task based on their job responsibilities.
- 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.
-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".
+ PrerequisitesLearn about the permissions (see Permissions Management) 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.
Create a user group on the IAM console, and assign the CBR ReadOnlyAccess policy to the group.
@@ -17,7 +17,7 @@
diff --git a/docs/cbr/umn/cbr_03_0050.html b/docs/cbr/umn/cbr_03_0050.html
index 143e75fd5..4229b76d1 100644
--- a/docs/cbr/umn/cbr_03_0050.html
+++ b/docs/cbr/umn/cbr_03_0050.html
@@ -60,7 +60,7 @@
Base on the preceding rules, the capacity of each vault created by the system is predefined as 1.2 times of the total backup size.
For example, a user has a 100 GB ECS and a 50 GB ECS. The used storage capacity of the two ECSs is 20 GB and 10 GB, respectively. The user manually has backed up the two entire ECSs using cloud server backup. During migration, the capacity of the vault automatically created will be 1.2 times of the total backup size. In this example, the total backup size multiplied by 1.2 is 36 GB. So the system will automatically create a 36 GB vault.
-Constraints- The vaults you have cannot be used for migration. Resources will automatically migrated to system-created vaults.
- Backup resources of one account only need to be migrated once.
- After resources are migrated, disk backups and server backups will be automatically stored in CBR vaults. No further operations are required.
+ Constraints- The vaults you have cannot be used for migration. Resources will automatically migrated to system-created vaults.
- Backup resources of one account only need to be migrated once.
- During the migration, do not delete the CBR backup vault that is automatically created. Use it after the migration is complete.
- 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 the 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 e5a4ffdfc..cf4b7c9ae 100644
--- a/docs/cbr/umn/cbr_03_0107.html
+++ b/docs/cbr/umn/cbr_03_0107.html
@@ -3,12 +3,12 @@
Creating a File System from an SFS Turbo Backup
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 the 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
+ - 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.
+ - 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 Turbo User Guide.
- - 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.
+ - 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 22e2fb490..d120b7f2d 100644
--- a/docs/cbr/umn/cbr_03_0114.html
+++ b/docs/cbr/umn/cbr_03_0114.html
@@ -70,7 +70,6 @@
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 40a082c06..dacdceb58 100644
--- a/docs/cbr/umn/cbr_03_0115.html
+++ b/docs/cbr/umn/cbr_03_0115.html
@@ -142,7 +142,7 @@
- Click Create.
- After the alarm rule is created, if the metric data reaches the specified threshold or a CBR event happens, Cloud Eye immediately informs you that an exception has occurred. For details, see the Cloud Eye User Guide.
+ After the alarm rule is created, if the metric data reaches the specified threshold or a CBR event happens, Cloud Eye immediately informs you that an exception has occurred. For details, see the Cloud Eye User Guide.
diff --git a/docs/cbr/umn/cbr_03_0116.html b/docs/cbr/umn/cbr_03_0116.html
index f18b21315..ec8742b2f 100644
--- a/docs/cbr/umn/cbr_03_0116.html
+++ b/docs/cbr/umn/cbr_03_0116.html
@@ -2,11 +2,11 @@
Migrating Resources from a Vault
Migrating a resource means that you dissociate a resource from a vault and then associate it to another vault. All backups of the resource will be migrated to the destination vault.
- Notes and Constraints- Resources can be migrated only when the source and destination vaults are in the Available or Locked state.
- The source and destination vaults for resource migration must be of the same types. For example, resources in a server backup vault can be migrated to another server backup vault, but cannot be migrated to another disk backup vault.
- The remaining capacity of the destination vault must be greater than the size of resource backups to be migrated.
- Cross-account resource migration is currently not supported.
- The source and destination vaults must be in the same region.
+ Notes and Constraints- Resources can be migrated only when the source and destination vaults are in the Available or Locked state.
- Resources can be migrated only when no task is being executed in the source and destination vaults.
- The remaining capacity of the destination vault must be greater than the size of resource backups to be migrated.
- Cross-account resource migration is currently not supported.
- The source and destination vaults must be in the same region.
- The source and destination vaults for resource migration must be of the same types. For example, resources in a server backup vault can be migrated to another server backup vault, but cannot be migrated to another disk backup vault.
Procedure- Log in to the 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 Migrate in the Operation column.
-
+
Figure 1 Migrating a resource
diff --git a/docs/cbr/umn/cbr_03_0156.html b/docs/cbr/umn/cbr_03_0156.html
new file mode 100644
index 000000000..73e1b3005
--- /dev/null
+++ b/docs/cbr/umn/cbr_03_0156.html
@@ -0,0 +1,24 @@
+
+
+Viewing the Policy of a Vault
+After a policy is created, you can view the policy in the policy list or on the vault details page.
+ - Log in to the 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 > Policies.
+ - View the created policy in the policy list. In the search box above the list, you can select an attribute or enter a keyword to search for policies.
+
+ - After creating a policy and applying it to a vault, you can view the policy on the vault details page. Select a backup type on the left navigation pane. On the page displayed, locate the desired vault, click the vault name.
- View the policy applied to the vault.
+
+
+
|---|
-2024-6-30
+ | 2024-12-18
+ |
+This issue is the twenty-sixth official release.
+Updated the following content:
+- Added sections "Enabling Backup Locking" and "Viewing the Policy of a Vault".
- Added the description of enabling backup locking in sections "Creating a Server Backup Vault," "Creating a Disk Backup Vault", and "Creating an SFS Turbo Backup Vault".
- Updated screenshots in sections "Viewing a Vault", "Viewing a Backup", "Deleting a Vault", "Deleting a Backup", "Deleting a Policy", and "Managing Tasks."
+ |
+
+2024-6-30
|
This issue is the twenty-fifth official release.
Updated the following content:
diff --git a/docs/cbr/umn/cbr_05_0003.html b/docs/cbr/umn/cbr_05_0003.html
index 4e9c192b4..d209d961e 100644
--- a/docs/cbr/umn/cbr_05_0003.html
+++ b/docs/cbr/umn/cbr_05_0003.html
@@ -6,13 +6,13 @@
Possible CauseAfter the server creation, the configuration parameters contained in the /etc/fstab file in the system disk of the new server are that of the backup source server, causing the UUID information to be inconsistent with the new data disks. As a result, the ECS encounters an error when uploading /etc/fstab during the bootup and enters maintenance mode.
SolutionThe following uses CentOS as an example.
- - After creating an ECS using an image, log in to the ECS console, click Remote Login in the row of the ECS.
- On the maintenance mode page that is displayed, access the system as prompted.
Figure 1 Maintenance mode of the system
+- After creating an ECS using an image, log in to the ECS console, click Remote Login in the row of the ECS.
- On the maintenance mode page that is displayed, access the system as prompted.
Figure 1 Maintenance mode of the system
- Run the cat /etc/fstab command to check the disk attachment information.
Figure 2 Data disk UUIDs
- Run the vi /etc/fstab command to open the file, press i to enter the editing mode, and delete 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 3 /etc/fstab after being updated
- 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.
What Are Full Backup and Incremental Backup?
DescriptionA full backup backs up all data at a certain time point.
An incremental backup backs up the changed data since the last full or incremental backup.
- CBR uses the permanent incremental backup technology. A full backup is performed for a resource in the initial backup and incremental backups in all subsequent backups. If a full backup expires and is deleted, its next incremental backup will be regarded as the resource's full backup.
+ CBR uses the permanent incremental backup technology. A full backup is performed for a resource in the initial backup and incremental backups in subsequent backups. If a full backup expires and is deleted, its next incremental backup will be regarded as the resource's full backup.
Suppose that server X has backups A, B, and C in time sequence. Backup A is a full backup, and backups B and C are incremental backups. Only changed data blocks are backed up in incremental backups and unchanged data blocks are indexed using pointers, so each incremental backup can be regarded as a virtual full backup.
If backup A is deleted, data blocks in backup A indexed by subsequent backups will not be deleted. Only data blocks that are exclusive to backup A are deleted. So, backups B and C can still be used to restore data. Or if backups A and B are deleted, backup C can also be used to restore data independently. There is no obvious difference between their restoration speeds.
Figure 1 Backup mechanism
@@ -11,7 +11,7 @@
- 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 rather than 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.
+ - 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 rather than 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_0010.html b/docs/cbr/umn/cbr_06_0010.html
index 629dfe90b..b5399ac2f 100644
--- a/docs/cbr/umn/cbr_06_0010.html
+++ b/docs/cbr/umn/cbr_06_0010.html
@@ -1,7 +1,9 @@
Can I Choose to Back Up Only Some Partitions of a Disk?
- No. The minimum backup granularity supported by CBR is disks.
+ No.
+ The minimum backup granularity that CBR supports is disk.
+ CBR backs up the status, configuration, and data of a disk at a certain time point for restoration in case of a fault.
diff --git a/docs/cbr/umn/cbr_06_0013.html b/docs/cbr/umn/cbr_06_0013.html
index 15735528c..cfe90f05d 100644
--- a/docs/cbr/umn/cbr_06_0013.html
+++ b/docs/cbr/umn/cbr_06_0013.html
@@ -4,6 +4,7 @@
The system shuts down the server before restoring server data, and automatically starts up the server after the restoration is complete.
If you deselect Start the server immediately after restoration, you need to manually start the server after the restoration is complete.
Before restoring the disk data, stop the server to which the disk is attached and detach the disk from the server. After the disk data is restored, attach the disk to the server and start the server.
+ For more information, see Restoring from a Cloud Server Backup.
diff --git a/docs/cbr/umn/cbr_06_0014.html b/docs/cbr/umn/cbr_06_0014.html
index b12cc6298..fc8358d4a 100644
--- a/docs/cbr/umn/cbr_06_0014.html
+++ b/docs/cbr/umn/cbr_06_0014.html
@@ -1,8 +1,9 @@
Can I Use a System Disk Backup to Recover an ECS?
- Yes. However, before the recovery, you need to detach the system disk to be recovered from the ECS.
- You can also use a backup of the system disk to create new disks. However, newly created disks cannot be used as system disks.
+ Yes. Before the recovery, you need to detach the system disk to be recovered from the ECS.
+ You can also use a system disk backup to create an EVS disk.
+ Disks created using system disk backups can only be used as data disks on servers. They cannot be used as system disks.
diff --git a/docs/cbr/umn/cbr_06_0015.html b/docs/cbr/umn/cbr_06_0015.html
index 3cdc98573..66eb36fd8 100644
--- a/docs/cbr/umn/cbr_06_0015.html
+++ b/docs/cbr/umn/cbr_06_0015.html
@@ -1,7 +1,10 @@
Do I Need to Stop the Server Before Restoring Data Using Disk Backups?
- Yes. Before restoring the disk data using a disk backup, you must stop the server to which the disk is attached, and detach the disk from the server. After the disk data is restored, attach the disk to the server and start the server.
+ Yes. Before restoring the disk data using a disk backup, you must stop the server to which the disk is attached, and detach the disk from the server.
+ After the disk data is restored, attach the disk to the server and start the server.
+ For details, see Restoring from a Cloud Disk Backup.
+
diff --git a/docs/cbr/umn/cbr_06_0017.html b/docs/cbr/umn/cbr_06_0017.html
index aaf5ba8b2..52e2a6860 100644
--- a/docs/cbr/umn/cbr_06_0017.html
+++ b/docs/cbr/umn/cbr_06_0017.html
@@ -3,7 +3,7 @@
Can a Disk Be Restored Using Its Backups After Its Capacity Is Expanded?
Yes. After restoration, the capacity of the expanded disk goes back to the original capacity before expansion.
If you want to use the capacity added to the disk, you need to attach the restored disk to a server, log in to the server, and then manually modify the file system configuration.
- For details, see Disk Capacity Expansion in the Elastic Volume Service User Guide.
+ For details, see section "Disk Capacity Expansion" in the Elastic Volume Service User Guide.
diff --git a/docs/cbr/umn/cbr_06_0020.html b/docs/cbr/umn/cbr_06_0020.html
index b774c82fe..6703050d9 100644
--- a/docs/cbr/umn/cbr_06_0020.html
+++ b/docs/cbr/umn/cbr_06_0020.html
@@ -1,7 +1,9 @@
Is There a Quota for CBR Vaults?
- There are no quotas on CBR vaults. You can create as many vaults as needed.
+ There are no quota limits.
+ You can create as many vaults as needed.
+ There is no limit on the number of backups that can be created for a single resource. You can create multiple backups for a resource.
diff --git a/docs/cbr/umn/cbr_06_0055.html b/docs/cbr/umn/cbr_06_0055.html
index 313e5f6ae..095872a28 100644
--- a/docs/cbr/umn/cbr_06_0055.html
+++ b/docs/cbr/umn/cbr_06_0055.html
@@ -1,7 +1,9 @@
Can I Use Its Backup for Restoration After a Resource Is Deleted?
- Yes. Resources and backups are not stored together. If a resource is deleted, its backup still stays in your CBR vault. You can use the backup to restore the resource to a backup point in time.
+ Yes.
+ Resources and backups are not stored together. If resources are deleted, backups will not be deleted at the same time.
+ So, you can still use the backups to restore resources to a backup point in time.
diff --git a/docs/cbr/umn/cbr_06_0056.html b/docs/cbr/umn/cbr_06_0056.html
index a1359cf4e..03a5002b2 100644
--- a/docs/cbr/umn/cbr_06_0056.html
+++ b/docs/cbr/umn/cbr_06_0056.html
@@ -1,7 +1,9 @@
How Many Backups Can I Create for a Resource?
- You can create as many backups for a resource as needed.
+ This number is not limited.
+ Theoretically, you can create as many backups for a resource as needed.
+ By default, full backup at the first time and incremental backup subsequently.
diff --git a/docs/cbr/umn/cbr_06_0062.html b/docs/cbr/umn/cbr_06_0062.html
index e1539e89c..acf0d4c5d 100644
--- a/docs/cbr/umn/cbr_06_0062.html
+++ b/docs/cbr/umn/cbr_06_0062.html
@@ -1,7 +1,9 @@
Can I Stop an Ongoing Backup Task?
- No. An ongoing backup task cannot be stopped.
+ No.
+ An ongoing backup task cannot be stopped.
+ You need to wait until the backup is complete and then perform operations on the backup.
diff --git a/docs/cbr/umn/cbr_06_0072.html b/docs/cbr/umn/cbr_06_0072.html
index b08754dc3..3f776dd1b 100644
--- a/docs/cbr/umn/cbr_06_0072.html
+++ b/docs/cbr/umn/cbr_06_0072.html
@@ -2,6 +2,8 @@
Can I Stop an Ongoing Restoration Task?
No. An ongoing restoration task cannot be stopped.
+ The backup data will overwrite the current data, and the restoration cannot be undone.
+ For more information, see Restoring Data.
diff --git a/docs/cbr/umn/en-us_image_0000001463274188.png b/docs/cbr/umn/en-us_image_0000001463274188.png
deleted file mode 100644
index 4d9cc8fb8..000000000
Binary files a/docs/cbr/umn/en-us_image_0000001463274188.png and /dev/null differ
diff --git a/docs/cbr/umn/en-us_image_0000001926048954.png b/docs/cbr/umn/en-us_image_0000001926048954.png
deleted file mode 100644
index 2b3b28bb9..000000000
Binary files a/docs/cbr/umn/en-us_image_0000001926048954.png and /dev/null differ
diff --git a/docs/cbr/umn/en-us_image_0000001926225120.png b/docs/cbr/umn/en-us_image_0000001926225120.png
deleted file mode 100644
index 9779e63f1..000000000
Binary files a/docs/cbr/umn/en-us_image_0000001926225120.png and /dev/null differ
diff --git a/docs/cbr/umn/en-us_image_0000001953185673.png b/docs/cbr/umn/en-us_image_0000001953185673.png
deleted file mode 100644
index 07c32567f..000000000
Binary files a/docs/cbr/umn/en-us_image_0000001953185673.png and /dev/null differ
diff --git a/docs/cbr/umn/en-us_image_0000001953568037.png b/docs/cbr/umn/en-us_image_0000001953568037.png
deleted file mode 100644
index 46270d354..000000000
Binary files a/docs/cbr/umn/en-us_image_0000001953568037.png and /dev/null differ
diff --git a/docs/cbr/umn/en-us_image_0000001953594521.png b/docs/cbr/umn/en-us_image_0000001953594521.png
deleted file mode 100644
index 8ba05f5b4..000000000
Binary files a/docs/cbr/umn/en-us_image_0000001953594521.png and /dev/null differ
diff --git a/docs/cbr/umn/en-us_image_0000001992338654.png b/docs/cbr/umn/en-us_image_0000001992338654.png
deleted file mode 100644
index 5416a73c3..000000000
Binary files a/docs/cbr/umn/en-us_image_0000001992338654.png and /dev/null differ
diff --git a/docs/cbr/umn/en-us_image_0000001995695954.png b/docs/cbr/umn/en-us_image_0000001995695954.png
deleted file mode 100644
index e8d7f323d..000000000
Binary files a/docs/cbr/umn/en-us_image_0000001995695954.png and /dev/null differ
diff --git a/docs/cbr/umn/en-us_image_0000001995856846.png b/docs/cbr/umn/en-us_image_0000001995856846.png
deleted file mode 100644
index 27250b293..000000000
Binary files a/docs/cbr/umn/en-us_image_0000001995856846.png and /dev/null differ
diff --git a/docs/cbr/umn/en-us_image_0000001995858070.png b/docs/cbr/umn/en-us_image_0000001995858070.png
deleted file mode 100644
index 60e0fe9dc..000000000
Binary files a/docs/cbr/umn/en-us_image_0000001995858070.png and /dev/null differ
diff --git a/docs/cbr/umn/en-us_image_0000002032295753.png b/docs/cbr/umn/en-us_image_0000002032295753.png
deleted file mode 100644
index 7fc131e87..000000000
Binary files a/docs/cbr/umn/en-us_image_0000002032295753.png and /dev/null differ
diff --git a/docs/cbr/umn/en-us_image_0000002043775410.png b/docs/cbr/umn/en-us_image_0000002043775410.png
new file mode 100644
index 000000000..3df832dfe
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002043775410.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002118788384.png b/docs/cbr/umn/en-us_image_0000002118788384.png
new file mode 100644
index 000000000..f79f38ada
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002118788384.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002118794904.png b/docs/cbr/umn/en-us_image_0000002118794904.png
new file mode 100644
index 000000000..a23d5a9f5
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002118794904.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002118823934.png b/docs/cbr/umn/en-us_image_0000002118823934.png
new file mode 100644
index 000000000..80be35887
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002118823934.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002118824430.png b/docs/cbr/umn/en-us_image_0000002118824430.png
new file mode 100644
index 000000000..e2290fd65
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002118824430.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002120105234.png b/docs/cbr/umn/en-us_image_0000002120105234.png
new file mode 100644
index 000000000..27c5cbc90
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002120105234.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002120162156.png b/docs/cbr/umn/en-us_image_0000002120162156.png
new file mode 100644
index 000000000..1909444d2
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002120162156.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002120263914.png b/docs/cbr/umn/en-us_image_0000002120263914.png
new file mode 100644
index 000000000..f7b2aac82
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002120263914.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002124587690.png b/docs/cbr/umn/en-us_image_0000002124587690.png
new file mode 100644
index 000000000..a23d5a9f5
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002124587690.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002138006136.png b/docs/cbr/umn/en-us_image_0000002138006136.png
new file mode 100644
index 000000000..067462fff
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002138006136.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002154002153.png b/docs/cbr/umn/en-us_image_0000002154002153.png
new file mode 100644
index 000000000..7821b9cef
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002154002153.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002154011457.png b/docs/cbr/umn/en-us_image_0000002154011457.png
new file mode 100644
index 000000000..1e76a9704
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002154011457.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002154180233.png b/docs/cbr/umn/en-us_image_0000002154180233.png
new file mode 100644
index 000000000..3e25c8e03
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002154180233.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002155393081.png b/docs/cbr/umn/en-us_image_0000002155393081.png
new file mode 100644
index 000000000..eb647fe31
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002155393081.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002155501529.png b/docs/cbr/umn/en-us_image_0000002155501529.png
new file mode 100644
index 000000000..e787384b2
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002155501529.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002155522085.jpg b/docs/cbr/umn/en-us_image_0000002155522085.jpg
new file mode 100644
index 000000000..ad5684271
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002155522085.jpg differ
diff --git a/docs/cbr/umn/en-us_image_0000002155560465.png b/docs/cbr/umn/en-us_image_0000002155560465.png
new file mode 100644
index 000000000..4f9aaa79a
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002155560465.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002159985785.png b/docs/cbr/umn/en-us_image_0000002159985785.png
new file mode 100644
index 000000000..a23d5a9f5
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002159985785.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002173190841.png b/docs/cbr/umn/en-us_image_0000002173190841.png
new file mode 100644
index 000000000..261930849
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002173190841.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002173280461.png b/docs/cbr/umn/en-us_image_0000002173280461.png
new file mode 100644
index 000000000..f45c2e5f8
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002173280461.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002173284725.png b/docs/cbr/umn/en-us_image_0000002173284725.png
new file mode 100644
index 000000000..66b0fba8a
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002173284725.png differ
diff --git a/docs/cbr/umn/en-us_image_0000002173405673.png b/docs/cbr/umn/en-us_image_0000002173405673.png
new file mode 100644
index 000000000..7ec47b6c4
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002173405673.png differ
diff --git a/docs/cbr/umn/en-us_image_0251455944.png b/docs/cbr/umn/en-us_image_0251455944.png
deleted file mode 100644
index d98baf530..000000000
Binary files a/docs/cbr/umn/en-us_image_0251455944.png and /dev/null differ
|
|
|---|
|
|---|
|
|---|
|
|---|
|
|---|
|
|---|
|
