Application scenario
diff --git a/docs/cbr/umn/cbr_01_0011.html b/docs/cbr/umn/cbr_01_0011.html index 8bcc23b80..ca452c07d 100644 --- a/docs/cbr/umn/cbr_01_0011.html +++ b/docs/cbr/umn/cbr_01_0011.html @@ -4,7 +4,7 @@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.
+IAM is a free service. You only pay for the resources in your account. For more information about IAM, see What Is IAM?.
CBR Permissions
New 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.
diff --git a/docs/cbr/umn/cbr_01_0035.html b/docs/cbr/umn/cbr_01_0035.html index 04f94817e..9f3a946ab 100644 --- a/docs/cbr/umn/cbr_01_0035.html +++ b/docs/cbr/umn/cbr_01_0035.html @@ -1,7 +1,7 @@Enabling Backup Locking
-Scenarios
To prevent the backup data from being deleted by mistake or maliciously, you can enable backup locking for vaults to improve data security.
+Scenarios
To prevent the backup data from being deleted by mistake or maliciously, you can enable backup locking for vaults to improve data security(eu-nl).
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.
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.
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.
+ - Determine whether to enable backup locking(eu-nl).
If enabled, backups in the vault will not be deleted maliciously or by mistake, improving data reliability.
diff --git a/docs/cbr/umn/cbr_02_0004.html b/docs/cbr/umn/cbr_02_0004.html index 8f6179c7a..bfd4c4fe1 100644 --- a/docs/cbr/umn/cbr_02_0004.html +++ b/docs/cbr/umn/cbr_02_0004.html @@ -3,7 +3,7 @@
Backup locking cannot be disabled after it is enabled.
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.
- 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.
+ - In the upper right corner of the page, click Create Disk Backup Vault.
- Determine whether to enable backup locking(eu-nl).
If backup locking is enabled, backups in the vault will not be deleted maliciously or by mistake. This improves data reliability.
diff --git a/docs/cbr/umn/cbr_02_0009.html b/docs/cbr/umn/cbr_02_0009.html index 9387d89e5..bcc1b5781 100644 --- a/docs/cbr/umn/cbr_02_0009.html +++ b/docs/cbr/umn/cbr_02_0009.html @@ -39,7 +39,7 @@ Backup locking cannot be disabled after it is enabled.
-
- Click OK. Then on the Associated Servers tab page, you can view the number of resources that have been associated. diff --git a/docs/cbr/umn/cbr_02_0010.html b/docs/cbr/umn/cbr_02_0010.html index e8213de5f..22bbed4cb 100644 --- a/docs/cbr/umn/cbr_02_0010.html +++ b/docs/cbr/umn/cbr_02_0010.html @@ -4,7 +4,7 @@
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.
After a new disk is added to the associated server, the system automatically identifies the new disk and backs up the new disk.
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.
- 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.
+ - Determine whether to enable backup locking(eu-nl).
If backup locking is enabled, backups in the vault will not be deleted maliciously or by mistake. This improves data reliability.
diff --git a/docs/cbr/umn/cbr_03_0002.html b/docs/cbr/umn/cbr_03_0002.html index 3340b78fc..bc32a260c 100644 --- a/docs/cbr/umn/cbr_03_0002.html +++ b/docs/cbr/umn/cbr_03_0002.html @@ -115,8 +115,7 @@ Backup locking cannot be disabled after it is enabled.
- 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.
- Search a vault by its name or ID.
- Click the name of a specific vault to view vault details.
diff --git a/docs/cbr/umn/cbr_03_0006.html b/docs/cbr/umn/cbr_03_0006.html index 1ebe11f25..274a1079d 100644 --- a/docs/cbr/umn/cbr_03_0006.html +++ b/docs/cbr/umn/cbr_03_0006.html @@ -5,7 +5,6 @@ - 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.
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 > Expand Capacity in the Operation column. See Figure 1.
-
diff --git a/docs/cbr/umn/cbr_03_0014.html b/docs/cbr/umn/cbr_03_0014.html index 8f6a1985f..9bf9d2ce9 100644 --- a/docs/cbr/umn/cbr_03_0014.html +++ b/docs/cbr/umn/cbr_03_0014.html @@ -4,7 +4,9 @@
Scenarios
You can share server or disk backups with domains. Shared backups can be used to create servers or disks.
@@ -22,15 +24,18 @@Context
Sharer
-- Backups can only be shared among domains in the same region. They cannot be shared across regions.
- Encrypted backups cannot be shared. Backups cannot be shared across regions. Account to which a backup is shared must be in the same region as the backup.
- 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.
- Backups can only be shared among domains in the same region. They cannot be shared across regions.
- Backups cannot be shared across regions. Account to which a backup is shared must be in the same region as the backup.
- 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.
- When an encrypted backup is shared, the encryption key must be shared with the recipient so that the recipient can use the shared backup.+
- For details about how to share a key, see Creating a Grant. To obtain the recipient Account ID, hover over the username and choose My Credentials > API Credentials to check the Account ID.
- Cloud disk backup encryption depends on an agency created that grants KMS access permissions to EVS. If the disk to be backed up is encrypted, the disk backup generated will be an encrypted backup. The encryption attribute of backups cannot be changed.
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.
- Click the Share Backup tab.
- Enter the project ID of the recipient.
-
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.
- Canceling sharing
- Click the Cancel Sharing tab, select the projects you want to cancel sharing, and click OK. +
- Click OK.
Return to the backup list, click the backup name to go to the backup details page, and click the Share List tab to view the shared 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.
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.
- 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.
- 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. If a disk already has a backup, after another backup, the old snapshot will be deleted and the latest one will be retained.
diff --git a/docs/cbr/umn/cbr_03_0016.html b/docs/cbr/umn/cbr_03_0016.html index bfcb4d206..9737eab79 100644 --- a/docs/cbr/umn/cbr_03_0016.html +++ b/docs/cbr/umn/cbr_03_0016.html @@ -15,7 +15,7 @@Prerequisites
- There is at least one backup.
- The backup to be deleted is in the Available or Error state.
-
- 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_0025.html b/docs/cbr/umn/cbr_03_0025.html index 982500fc8..4687f14d7 100644 --- a/docs/cbr/umn/cbr_03_0025.html +++ b/docs/cbr/umn/cbr_03_0025.html @@ -3,8 +3,8 @@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.
-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 subsequent backups.
- The minimum interval between two full backups is 1 day.
Peak hours for 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 during off-peak hours.
+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 one 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.
@@ -27,12 +27,12 @@
Type
Select a policy type. In this section, we select the backup policy.
+Select a policy type. In this example, select the backup policy.
Backup policy
Name
+Policy Name
Backup policy name
A name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-).
@@ -50,8 +50,8 @@Backup Frequency
Select a backup frequency.
-- Weekly
Specifies on which days of each week the backup task will be executed. You can select multiple days.
- - Day based
Specifies the interval (every 1 to 30 days) for executing the backup task.
+- Weekly
Specifies on which days of each week the backup will be executed. You can select multiple days.
+ - Day based
Specifies the interval (every 1 to 30 days) for executing the backup.
- Weekly
Every day
@@ -61,14 +61,14 @@Execution Time
Execution time
+Time when the backup is executed.
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. CBR 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
-- It is recommended that backups be performed during off-peak hours or when no services are running.
- Peak hours of the backup service are from 00:00 to 06:00, during which there may be scheduling delays. So you are advised to evaluate your service types and schedule backups outside of the backup peak hours.
- It is recommended that backups be performed during off-peak hours or when no services are running.
- Peak hours for the backup service are from 00:00 to 06:00, during which there may be scheduling delays. So you are advised to evaluate your service types and schedule backups outside of the backup peak hours.
Retention Rule
@@ -77,9 +77,9 @@- 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. 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.
- - PermanentNOTE:
- 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.
- 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 will be retained. 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 failed periodic backups are retained. They are retained for one month and can be deleted manually.
- If a backup has been generated and the next backup task is in progress, CBR will not allow you to delete the most recent backup generated. You can delete the backup only after the ongoing backup task is complete.
- 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.
diff --git a/docs/cbr/umn/cbr_03_0026.html b/docs/cbr/umn/cbr_03_0026.html index 0d285b9e1..a1934cfbb 100644 --- a/docs/cbr/umn/cbr_03_0026.html +++ b/docs/cbr/umn/cbr_03_0026.html @@ -3,11 +3,12 @@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.
+- Click Create Now.
You can locate the desired vault and choose More > Apply Backup Policy in the Operation column 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.
Creating a Replication Policy
A replication policy allows CBR to periodically replicate backups that have not been replicated or failed to be replicated to the destination region.
When a backup time and a replication time are both configured, ensure that replication starts after backup is complete. Or, replication may fail.
-Constraints
- You can only apply replication policies to server backup vaults.
Constraints
- You can only apply replication policies to server backup vaults.
- A maximum of 32 replication policies can be created in each account.
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. Select Replication Policy for Type. See Figure 1.
+
- Set the replication policy parameters. Table 1 describes the parameters.
diff --git a/docs/cbr/umn/cbr_03_0027.html b/docs/cbr/umn/cbr_03_0027.html index fcc4b43e7..a7289f7ae 100644 --- a/docs/cbr/umn/cbr_03_0027.html +++ b/docs/cbr/umn/cbr_03_0027.html @@ -9,6 +9,7 @@
+
diff --git a/docs/cbr/umn/cbr_03_0032.html b/docs/cbr/umn/cbr_03_0032.html index 9133e626c..f35872be1 100644 --- a/docs/cbr/umn/cbr_03_0032.html +++ b/docs/cbr/umn/cbr_03_0032.html @@ -4,7 +4,7 @@
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.
- 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.
Notes and 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.
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.
@@ -24,9 +24,9 @@Prerequisites
- Disks are running properly on the server whose data needs to be restored.
- The server has at least one Available backup.
- 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.
+For example, if the Oracle data is scattered across multiple disks and only some of them are restored, data may become inconsistent 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.
+- 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 data is restored to the state when that backup was created.
For details about how to view failed restoration tasks, see Managing Tasks.
diff --git a/docs/cbr/umn/cbr_03_0048.html b/docs/cbr/umn/cbr_03_0048.html index 5cc02b8af..cb96f8cc3 100644 --- a/docs/cbr/umn/cbr_03_0048.html +++ b/docs/cbr/umn/cbr_03_0048.html @@ -2,7 +2,7 @@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_0036.html b/docs/cbr/umn/cbr_03_0036.html index c35b7af43..7e206b392 100644 --- a/docs/cbr/umn/cbr_03_0036.html +++ b/docs/cbr/umn/cbr_03_0036.html @@ -223,7 +223,7 @@Viewing Audit Logs
For how to view audit logs, see section "Querying Real-Time Traces" in the Cloud Trace Service User Guide.
Disabling or Enabling a Tracker
The 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 a region.
- Click Service List and choose Management & Deployment > Cloud Trace Service.
- Choose Tracker List in the left navigation pane. See Figure 1.
+
- 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.
- 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.
Creating a User and Granting CBR Permissions
This section describes how to use IAM to implement fine-grained permissions control for your CBR resources. With IAM, you can:
-- 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.
- Create IAM users 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.
Prerequisites
Learn 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".
diff --git a/docs/cbr/umn/cbr_03_0050.html b/docs/cbr/umn/cbr_03_0050.html index 4229b76d1..324e0dce5 100644 --- a/docs/cbr/umn/cbr_03_0050.html +++ b/docs/cbr/umn/cbr_03_0050.html @@ -4,7 +4,7 @@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.
For details about how to create custom policies, see Creating a Custom Policy.
+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", diff --git a/docs/cbr/umn/cbr_03_0107.html b/docs/cbr/umn/cbr_03_0107.html index cf4b7c9ae..0b24f1654 100644 --- a/docs/cbr/umn/cbr_03_0107.html +++ b/docs/cbr/umn/cbr_03_0107.html @@ -6,7 +6,7 @@ - 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.
-
- 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.
- 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.
diff --git a/docs/cbr/umn/cbr_03_0114.html b/docs/cbr/umn/cbr_03_0114.html index d120b7f2d..dd384f4a1 100644 --- a/docs/cbr/umn/cbr_03_0114.html +++ b/docs/cbr/umn/cbr_03_0114.html @@ -6,45 +6,56 @@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.
Namespace
SYS.CBR
Metrics
-Table 1 CBR metrics Metric ID
+Table 1 CBR metrics Metric ID
Metric Name
+Metric Name
Description
+Description
Value Range
+Value Range
Monitored Object
+Unit
Monitoring Period (Raw Data)
+Conversion Rule
+Monitored Object (Dimension)
+Monitoring Period (Raw Data)
used_vault_size
+used_vault_size
Used Vault Size
+Used Vault Size
Used capacity of the vault
-Unit: GB
+Used capacity of the vault
≥ 0
+≥ 0
Vault
+GB
15 min
+1024 (IEC)
+Vault
+15 min
vault_util
+vault_util
Vault Usage
+Vault Usage
Capacity usage of the vault
+Capacity usage of the vault
0~100%
+0~100
Vault
+%
15 min
+N/A
+Vault
+15 min
diff --git a/docs/cbr/umn/cbr_03_0156.html b/docs/cbr/umn/cbr_03_0156.html index 73e1b3005..6f7c86143 100644 --- a/docs/cbr/umn/cbr_03_0156.html +++ b/docs/cbr/umn/cbr_03_0156.html @@ -5,7 +5,7 @@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.
- 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.
- 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. +
- After creating a policy and applying it to a vault, you can view the policy on the vault details page. On any backup page, locate the desired vault and click its name to go to the details page.
- View the policy applied to the vault.
2024-12-18
+2025-04-11
+This is the twenty-eighth official release.
+Updated the following content:
+- Updated the screenshots in section "Viewing the Policy of a Vault."
- Modified the descriptions in section "Does CBR Support Cross-Region Backup?"
2025-03-29
+This issue is the twenty-seventh official release.
+Updated the following content:
+Added the description of sharing encrypted backups in section "Sharing Backups."
+2024-12-18
This issue is the twenty-sixth 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 d209d961e..946b7bf9b 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.
diff --git a/docs/cbr/umn/cbr_06_0003.html b/docs/cbr/umn/cbr_06_0003.html index 5e9293608..2a81ce258 100644 --- a/docs/cbr/umn/cbr_06_0003.html +++ b/docs/cbr/umn/cbr_06_0003.html @@ -1,14 +1,14 @@Figure 7 Adding attachment information of data disksAfter the information is added, the system will automatically attach the data disks on restart.
What Are Full Backup and Incremental Backup?
-Description
A full backup backs up all data at a certain time point.
+-Definitions
A 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 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.
+If backup A is deleted, only data blocks that are exclusive to backup A are deleted, and data blocks in backup A referenced by subsequent backups will not be deleted. Similarly, 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
Differences
- Backup duration: A full backup backs up the entire resource data which is usually larger than an incremental backup, so full backup take a longer time.
- Restoration duration: Both full backups and incremental backups can be restored. There is no obvious difference between their restoration speeds.
- Reliability: The latest incremental backup depends on the last full backup and intermediate incremental backups. If any backup data block is damaged, subsequent backups may be affected, which will reduce the backup reliability. All full backup data is independent and does not depend on previous backups. So full backups are more reliable.
You are advised to configure periodic full backup (for example, once every 30 days) and daily incremental backup to reduce the interval of full backup on which incremental backup depends and improve the reliability of backups.
+Differences
- Backup duration: A full backup backs up the entire resource data which is usually larger than an incremental backup, so full backup take a longer time.
- Restoration duration: Both full backups and incremental backups can be restored. There is no obvious difference between their restoration speeds.
- Reliability: The latest incremental backup depends on the last full backup and intermediate incremental backups. If any backup data block is damaged, subsequent backups may be affected, which will reduce the backup reliability. All full backup data is independent and does not depend on previous backups. So full backups are more reliable.
You are advised to configure periodic full backup (for example, once every 30 days) and daily incremental backup. This approach shortens the backup interval that incremental backups rely on, enhancing backup reliability.
- 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.
Does CBR Support Cross-Region Backup?
-No. CBR supports only backup and restoration within a region but not across regions.
+You can replicate backups to a destination region and create images in the destination region using the generated replicas.
+You can replicate backups in either of the following methods on the CBR console:
+- Select a backup from the backup list and manually perform a replication.
- Select a backup vault and manually replicate it. Alternatively, you can configure a replication policy to periodically replicate backups that have not been replicated or failed to be replicated to the destination region.
For details, see Replicating a Backup Across Regions.
diff --git a/docs/cbr/umn/cbr_06_0018.html b/docs/cbr/umn/cbr_06_0018.html index 60607e3f4..d71093a73 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 Passwords in the Elastic Cloud Server User Guide.
+For details about how to reset the password, see Password Reset 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 6703050d9..07f243682 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?
-There are no quota limits.
+diff --git a/docs/cbr/umn/en-us_image_0000002155501529.png b/docs/cbr/umn/en-us_image_0000002155501529.png index e787384b2..102eba55f 100644 Binary files a/docs/cbr/umn/en-us_image_0000002155501529.png and b/docs/cbr/umn/en-us_image_0000002155501529.png differ diff --git a/docs/cbr/umn/en-us_image_0000002155560465.png b/docs/cbr/umn/en-us_image_0000002155560465.png index 4f9aaa79a..3019dc38a 100644 Binary files a/docs/cbr/umn/en-us_image_0000002155560465.png and b/docs/cbr/umn/en-us_image_0000002155560465.png differ diff --git a/docs/cbr/umn/en-us_image_0160751578.png b/docs/cbr/umn/en-us_image_0160751578.png deleted file mode 100644 index 541894181..000000000 Binary files a/docs/cbr/umn/en-us_image_0160751578.png and /dev/null differThere are no quota limits for other vaults.
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.
- Weekly
- Click OK. Then on the Associated Servers tab page, you can view the number of resources that have been associated.
- Log in to the CBR console.
