To avoid data inconsistency after restoration, you are advised to back up the entire server.
If you want to back up only some of the disks to reduce costs, ensure that the data on the backed up disks does not depend on the disks that are not backed up. Or, data inconsistency may occur.
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.
diff --git a/docs/cbr/umn/cbr_03_0001.html b/docs/cbr/umn/cbr_03_0001.html
index 777791e37..8548b9269 100644
--- a/docs/cbr/umn/cbr_03_0001.html
+++ b/docs/cbr/umn/cbr_03_0001.html
@@ -14,6 +14,8 @@
Expanding Vault Capacity
+
Replicating a Vault
+
Managing Vault Tags
diff --git a/docs/cbr/umn/cbr_03_0009.html b/docs/cbr/umn/cbr_03_0009.html
new file mode 100644
index 000000000..ff7919285
--- /dev/null
+++ b/docs/cbr/umn/cbr_03_0009.html
@@ -0,0 +1,59 @@
+
+
+
Replicating a Vault
+
CBR allows you to replicate server backup vaults entirely to replication vaults in a different region. Replicas of server backups in the destination region can be used to create images and provision servers.
+
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.
+ - Only backup vaults 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. The replication rule varies with the replication method:
- Manual replication: A backup can be manually replicated to the destination region as long as it has no replica in that region. A backup can be manually replicated again if its replica in the destination region has been deleted.
- Policy-based replication: A backup can only be automatically replicated to a destination region once. It cannot be automatically replicated to that region again, even if its replica has been deleted.
+ - Only replication-supported regions can be selected as destination regions.
+
+
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
+ - On the Vaults tab, 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.
+
Table 1 Parameter descriptionParameter
+ |
+Description
+ |
+
|---|
+
+Destination Region
+ |
+Region to which the vault is replicated
+Only the regions that support replication will be displayed.
+- If the selected region contains only one project, you can directly select the region name.
- If the selected region has multiple projects, the default project of the region is selected. You can select another project if needed.
+ |
+
+Destination Vault
+ |
+A replication vault in the destination region
+ |
+
+Enable Acceleration
+ |
+Whether to accelerate replication
+The acceleration function is billed by traffic.
+ |
+
+
+
+
- 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.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/cbr/umn/cbr_03_0012.html b/docs/cbr/umn/cbr_03_0012.html
index 3b5014e71..8fc6e06f5 100644
--- a/docs/cbr/umn/cbr_03_0012.html
+++ b/docs/cbr/umn/cbr_03_0012.html
@@ -16,6 +16,8 @@
Using a Backup to Create a File System
+
Replicating a Backup Across Regions
+
diff --git a/docs/cbr/umn/cbr_03_0016.html b/docs/cbr/umn/cbr_03_0016.html
index 9c5823be3..a447022bb 100644
--- a/docs/cbr/umn/cbr_03_0016.html
+++ b/docs/cbr/umn/cbr_03_0016.html
@@ -2,6 +2,7 @@
CBR allows you to create images using ECS backups. You can use the images to provision ECSs to rapidly restore service running environments.
+
You can also use server backups to create images and then provision servers to restore data if your servers were accidentally deleted.
Prerequisites
- The following operations have been performed:
- The backup is in the Available state or in the Creating state which is marked with "Image can be created."
Once a backup creation starts, the backup enters the Creating state. After a period of time, a message stating "Image can be created" is displayed under Creating. In this case, the backup can be used for creating an image, even though it is still being created and cannot be used for restoration.
- Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- In the row of the backup, choose More > Create Image. See Figure 1.
Figure 1 Creating an image
- - Create an image by referring to section "Creating a Full-ECS Image 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_0018.html b/docs/cbr/umn/cbr_03_0018.html
new file mode 100644
index 000000000..6d6f5d255
--- /dev/null
+++ b/docs/cbr/umn/cbr_03_0018.html
@@ -0,0 +1,79 @@
+
+
+
Replicating a Backup Across Regions
+
CBR enables you to replicate backups of server backup vaults from one region to another.
+
Replicas of server backups can be used to create images and provision servers.
+
With cross-region replication, you can quickly deploy services in a different region. Data on the new resource in the destination region is the same as that on the original resource when you took the backup.
+
You can replicate backups in either of the following methods on 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.
+
This section uses the first method to describe how to replicate a backup. For details about the second method, see Replicating a Vault.
+
The replication constraints apply to both replication methods.
+
+
Constraints
- A server backup can be replicated only when it meets all the following conditions:
- It is an ECS backup.
- It contains system disk data.
- It is in the Available state.
+ - Only backups or backup vaults can be replicated. Replicated backups and vaults cannot be replicated again but their replicas can be used to create images.
- A backup can be replicated to multiple regions but can have only one replica in each destination region. The replication rule varies with the replication method:
- Manual replication: A backup can be manually replicated to the destination region as long as it has no replica in that region. A backup can be manually replicated again if its replica in the destination region has been deleted.
- Policy-based replication: A backup can only be automatically replicated to a destination region once. It cannot be automatically replicated to that region again, even if its replica has been deleted.
+ - Only replication-supported regions can be selected as destination regions.
+
+
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select a region.
- Click and choose Storage > Cloud Backup and Recovery. Select a backup type from the left navigation pane.
+ - Click the Backups tab and locate the desired backup. For details, see Viewing a Backup.
- Choose More > Create Replica in the Operation column of the backup. See Figure 1.
Figure 1 Creating a replica
+
+
+
+ - In the displayed dialog box, configure the parameters as described in Table 1.
+
Table 1 Parameter descriptionParameter
+ |
+Description
+ |
+
|---|
+
+Name
+ |
+Replica name
+A name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-).
+ |
+
+Description
+ |
+Replica description
+It cannot exceed 255 characters.
+ |
+
+Destination Region
+ |
+Region to which the backup is replicated
+Only the regions that support replication will be displayed.
+- If the selected region contains only one project, you can directly select the region name.
- If the selected region has multiple projects, the default project of the region is selected. You can select another project if needed.
+ |
+
+Destination Vault
+ |
+A replication vault in the destination region
+You can replicate backups to vaults in multiple destination regions. Creating replica will replicate all backups in the source vault to the destination vault.
+ |
+
+Enable Acceleration
+ |
+Whether to accelerate replication
+The acceleration function is billed by traffic.
+ |
+
+
+
+
The traffic for cross-region replication is the size of the replicated backup.
+
+ - Click OK.
- After the replication is complete, you can switch to the destination region to view generated replicas. For details, see Viewing a Backup. You can then use replicas to create images.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/cbr/umn/cbr_03_0024.html b/docs/cbr/umn/cbr_03_0024.html
index b96c5be00..8b034eec4 100644
--- a/docs/cbr/umn/cbr_03_0024.html
+++ b/docs/cbr/umn/cbr_03_0024.html
@@ -6,6 +6,8 @@
- Creating a Backup Policy
+- Creating a Replication Policy
+
- Modifying a Policy
- Deleting a Policy
diff --git a/docs/cbr/umn/cbr_03_0025.html b/docs/cbr/umn/cbr_03_0025.html
index b85a282f8..e73eb81e8 100644
--- a/docs/cbr/umn/cbr_03_0025.html
+++ b/docs/cbr/umn/cbr_03_0025.html
@@ -3,7 +3,7 @@
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.
-
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.
+
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.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select a region. - Click
and choose Storage > Cloud Backup and Recovery.
- Choose Policies in the 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
@@ -58,9 +58,9 @@
Backup Cycle
|
-Select a backup frequency.
+ | Select a backup cycle.
- Week-based cycle
Specifies on which days of each week the backup task will be executed. You can select multiple days.
- - Custom cycle
Specifies the interval (every 1 to 30 days) for executing the backup task.
+ - Custom cycle
Specifies the interval (every 1 to 30 days) for executing the backup task.
|
Every day
diff --git a/docs/cbr/umn/cbr_03_0026.html b/docs/cbr/umn/cbr_03_0026.html
new file mode 100644
index 000000000..9978f8ba2
--- /dev/null
+++ b/docs/cbr/umn/cbr_03_0026.html
@@ -0,0 +1,116 @@
+
+
+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.
+
+ Procedure- Log in to CBR Console.
- Log in to the management console.
- Click
 in the upper left corner and select a region. - Click
 and choose Storage > Cloud Backup and Recovery.
+ - Choose Policies in the left navigation pane and click the Backup Policies tab. In the upper right corner, click Create Policy. See Figure 1.
Figure 1 Creating a replication policy
+
+
+
+ - Set the replication policy parameters. Table 1 describes the parameters.
+ Table 1 Replication policy parametersParameter
+ |
+Description
+ |
+Remarks
+ |
+
|---|
+
+Type
+ |
+Select a policy type. In this section, we select the replication policy.
+ |
+Replication policy
+ |
+
+Name
+ |
+Replication policy name
+A name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-).
+ |
+replication_policy
+ |
+
+Status
+ |
+Whether to enable the replication policy
+ |
+Only after a replication policy is enabled and applied will CBR automatically replicates the backups in the vaults and deletes expired backup replicas.
+ |
+
+Execution Time
+ |
+Execution times of the replication policy in a day
+Replication tasks can be scheduled at the beginning of each hour, and you can select multiple hours.
+ |
+00:00, 02:00
+It is recommended that replication be performed during off-peak hours or when no services are running.
+ |
+
+Replication Cycle
+ |
+Select a replication cycle.
+
+ |
+Every day
+If you select day-based replication, the first replication is supposed to be executed on the day when the replication policy is created. If the execution time on the day you create the replication policy has passed, the first replication will be performed in the next replication cycle.
+ |
+
+Retention Rule
+ |
+Rule that specifies how backup replicas will be retained in the destination region
+- Replica quantity
You can set the maximum number of backup replicas to retain for each resource. The value ranges from 2 to 99999.
+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 replicated multiple times in a day. If day-based replication is configured, only the most recent backup replica of that day is retained. If you set Day-based to 5, the most recent backup replica of each of the last five days that have backup replicas generated will be retained and the earliest backup replicas will be deleted automatically. If day-based, weekly, monthly, and yearly retention rules are all configured, all the rules will apply and the union set of backup replicas will be retained. For example, if Day-based is set to 5 and Weekly to 1, five backup replicas will be retained. The long-term retention rule and the quantity-based retention rule both apply.
+ - Time period
You can choose to retain backup replicas for one month, three months, six months, one year, or for any desired number (2 to 99999) of days.
+ - Permanent
NOTE: - The system automatically deletes the earliest and expired backup replicas every other day to avoid exceeding the maximum number of backup replicas to retain or retaining any backup replica longer than the maximum retention period.
- There is a delay in deleting expired backup replicas, but normally this delay will not be over 24 hours.
- The retention rules apply only to auto-generated backup replicas, but not manual ones. Manual backup replicas need to be deleted manually.
- After a backup replica is used to create an image, the replica will not be deleted by the retention rule.
+
+
+ |
+6 months
+ |
+
+Destination Region
+ |
+Region to which the backup is replicated
+Only the regions that support replication will be displayed.
+- If the selected region contains only one project, you can directly select the region name.
- If the selected region has multiple projects, the default project of the region is selected. You can select another project if needed.
+ |
+ |
+
+Enable Acceleration
+ |
+Whether to accelerate replication
+The acceleration function is billed by traffic.
+ |
+-
+ |
+
+
+
+ - Click OK.
- Locate the desired vault and choose More > Apply Replication Policy to apply the replication policy to the vault. You can view the applied policy on the vault details page.
After the policy is applied, backups will be periodically replicated to the destination vault based on the policy.
+
+
+ ExampleA user applies a replication policy to a vault in a given region at 11:00 a.m. on Thursday. According to this policy, backups will be replicated to the destination region on 02:00 a.m. everyday, and only two backup replicas will be retained. According to this vault's backup policy, two backups are automatically generated at 00:00 everyday. At 12:00 p.m. on Saturday, the replication vault will contain two backup replicas, which are replicated on Saturday. Backup replicas generated at 02:00 a.m. on Friday have been automatically deleted according to the replication policy.
+
+ |
-2023-09-13
+ |
2023-10-30
+ |
+This issue is the twenty-fourth official release, which incorporates the following change:
+Added support for cross-region replication.
+ |
+
+2023-09-13
|
This issue is the twenty-third official release, which incorporates the following change:
Added support for resource migration.
diff --git a/docs/cbr/umn/cbr_06_0001.html b/docs/cbr/umn/cbr_06_0001.html
index 9d3b5a36c..e38bcbd9d 100644
--- a/docs/cbr/umn/cbr_06_0001.html
+++ b/docs/cbr/umn/cbr_06_0001.html
@@ -8,6 +8,8 @@
- Backup
+- Why Is My Backup Size Larger Than My Disk Size?
+
- Restoration
- Policies
diff --git a/docs/cbr/umn/cbr_06_0002.html b/docs/cbr/umn/cbr_06_0002.html
index 6707acc37..086438766 100644
--- a/docs/cbr/umn/cbr_06_0002.html
+++ b/docs/cbr/umn/cbr_06_0002.html
@@ -10,8 +10,6 @@
- What Are the Differences Between Backups and Snapshots?
-- Why Is My Backup Size Larger Than My Disk Size?
-
- What Are the Differences Between Cloud Server Backup and Cloud Disk Backup?
diff --git a/docs/cbr/umn/cbr_06_0026.html b/docs/cbr/umn/cbr_06_0026.html
index d0cb23e49..395e60cea 100644
--- a/docs/cbr/umn/cbr_06_0026.html
+++ b/docs/cbr/umn/cbr_06_0026.html
@@ -9,7 +9,7 @@
diff --git a/docs/cbr/umn/en-us_image_0000001583331410.jpg b/docs/cbr/umn/en-us_image_0000001583331410.jpg
new file mode 100644
index 000000000..ad5684271
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001583331410.jpg differ
diff --git a/docs/cbr/umn/en-us_image_0000001628917242.png b/docs/cbr/umn/en-us_image_0000001628917242.png
index dd753a41c..ab1b43c6e 100644
Binary files a/docs/cbr/umn/en-us_image_0000001628917242.png and b/docs/cbr/umn/en-us_image_0000001628917242.png differ
diff --git a/docs/cbr/umn/en-us_image_0000001633251313.png b/docs/cbr/umn/en-us_image_0000001633251313.png
new file mode 100644
index 000000000..1909444d2
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001633251313.png differ
diff --git a/docs/cbr/umn/en-us_image_0000001706852702.png b/docs/cbr/umn/en-us_image_0000001706852702.png
new file mode 100644
index 000000000..7f3b8600a
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001706852702.png differ
diff --git a/docs/cbr/umn/en-us_image_0000001754617465.png b/docs/cbr/umn/en-us_image_0000001754617465.png
new file mode 100644
index 000000000..5d186fee2
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001754617465.png differ
diff --git a/docs/cbr/umn/en-us_image_0000001754810509.png b/docs/cbr/umn/en-us_image_0000001754810509.png
new file mode 100644
index 000000000..d90c103ca
Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001754810509.png differ
|
