Overview
Cloud Backup and Recovery (CBR) enables you to easily back up Elastic Cloud Servers (ECSs), Elastic Volume Service (EVS) disks, and SFS Turbo file systems. In case of a virus attack, accidental deletion, or software or hardware fault, you can use the backup to restore data to any point when the data was backed up.
-CBR protects your services by ensuring the security and consistency of your data.
CBR Architecture
CBR involves backups, vaults, and policies.
Backup
@@ -70,7 +69,7 @@When creating a backup of a disk, CBR also creates a snapshot for it. CBR keeps only the latest snapshot. Every time it creates a new snapshot during backup, it deletes the old snapshot.
CBR stores backups in OBS to ensure data security.
Backup Options
CBR supports one-off backup and periodic backup. A one-off backup is manually created and is executed only once. Periodic backup tasks are automatically executed based on a user-defined backup policy.
+Backup Options
CBR supports one-off backup and periodic backup. A one-off backup task is manually created and is executed only once. Periodic backup tasks are automatically executed based on a user-defined backup policy.
Table 2 compares the two backup options.
Item @@ -124,7 +123,7 @@Access to CBRYou can access the CBR service through the console or by calling HTTPS-based APIs.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SFS Turbo backup |
-+ | You can back up SFS Turbo file systems and use the backups create new SFS Turbo file system. |
diff --git a/docs/cbr/umn/cbr_01_0005.html b/docs/cbr/umn/cbr_01_0005.html
index 953c3847..83df764f 100644
--- a/docs/cbr/umn/cbr_01_0005.html
+++ b/docs/cbr/umn/cbr_01_0005.html
@@ -5,6 +5,7 @@
Policy Name |
@@ -70,7 +70,8 @@
√ |
-+ | × + |
||
|---|---|---|---|---|---|
Listing vaults |
@@ -87,7 +88,8 @@
√ |
-+ | × + |
||
Deleting vaults |
@@ -95,7 +97,8 @@
√ |
-+ | × + |
||
Associating resources |
@@ -103,7 +106,8 @@
√ |
-+ | × + |
||
Dissociating resources |
@@ -111,21 +115,26 @@
√ |
-+ | × + |
||
Creating policies |
√ |
-- | + | × + |
+× + |
Updating policies |
√ |
-- | + | × + |
+× + |
Applying policies to a vault |
@@ -133,7 +142,8 @@
√ |
-+ | × + |
||
Removing policies from a vault |
@@ -141,14 +151,17 @@
√ |
-+ | × + |
||
Deleting policies |
√ |
-- | + | × + |
+× + |
Performing backups |
@@ -156,7 +169,8 @@
√ |
-+ | × + |
||
Updating subscriptions |
@@ -164,7 +178,8 @@
√ |
-+ | × + |
||
Querying the Agent status |
@@ -172,7 +187,8 @@
√ |
-+ | × + |
||
Deleting backups |
@@ -180,7 +196,8 @@
√ |
-+ | × + |
||
Restoring data using backups |
@@ -188,7 +205,8 @@
√ |
-+ | × + |
||
Associating vaults |
@@ -196,7 +214,8 @@
√ |
-+ | × + |
||
Batch adding or deleting vault tags |
@@ -204,7 +223,8 @@
√ |
-+ | × + |
||
Adding vault tags |
@@ -212,7 +232,8 @@
√ |
-+ | × + |
||
Editing tags |
@@ -220,7 +241,8 @@
√ |
-+ | × + |
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 Backup
Enhanced 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 generates enhanced backups. CBR only generates enhanced backups currently.
-The only difference between common backups and enhanced backups is that enhanced backup 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.
+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.
Creating a Server Backup Vault
This section describes how to create a server backup vault.
-Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- In the upper right corner of the page, click Create Server Backup Vault.
- Select a protection type.
- Backup: A server backup vault stores server backups.
- (Optional) In the server list, select the servers or disks you want to back up. After the servers or disks are selected, they are added to the list of selected servers. See Figure 1. You can also select specific disks on a server and associate them with the vault.
To avoid data inconsistency after restoration, you are advised to back up the entire server.
If you want to back up only some of the disks to reduce costs, ensure that the data on the backed up disks does not depend on the disks that are not backed up. Or, data inconsistency may occur.
diff --git a/docs/cbr/umn/cbr_02_0004.html b/docs/cbr/umn/cbr_02_0004.html index 3cb5b9c0..27f4a8bb 100644 --- a/docs/cbr/umn/cbr_02_0004.html +++ b/docs/cbr/umn/cbr_02_0004.html @@ -2,7 +2,7 @@Creating a Disk Backup Vault
This section describes how to create a disk backup vault.
-Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup 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.
diff --git a/docs/cbr/umn/cbr_02_0006.html b/docs/cbr/umn/cbr_02_0006.html index 80db241e..1d3389d1 100644 --- a/docs/cbr/umn/cbr_02_0006.html +++ b/docs/cbr/umn/cbr_02_0006.html @@ -6,7 +6,7 @@
Backing up a server does not impact the server performance. To ensure data integrity, you are advised to back up the server during off-peak hours when no data is written to the disks.
-Prerequisites
- Only servers in the Running or Stopped state can be backed up.
- At least one server backup vault is available.
diff --git a/docs/cbr/umn/cbr_02_0007.html b/docs/cbr/umn/cbr_02_0007.html index bcfd68eb..8fa6d339 100644 --- a/docs/cbr/umn/cbr_02_0007.html +++ b/docs/cbr/umn/cbr_02_0007.html @@ -5,7 +5,7 @@Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- On the Cloud Server Backups page, click the Vaults tab and find the vault to which the server is associated.
- Choose More > Perform Backup in the Operation column. In the server list, select the server you want to back up. After a server is selected, it is added to the list of selected servers. See Figure 1.
@@ -54,7 +54,7 @@
- Click Yes. CBR automatically creates a backup for the server.
On the Backups tab page, if the status of the backup is Available, the backup task is successful.
-
You can restart a server if necessary after the backup progress exceeds 10%. However, to ensure data integrity, you are advised to restart it after the backup is complete.
After the backup is complete, you can use the backup to restore server data or create an image. For details, see Restoring Data Using a Cloud Server Backup and Using a Backup to Create an Image.
+After the backup is complete, you can use the backup to restore server data or create an image. For details, see Restoring from a Cloud Server Backup and Using a Backup to Create an Image.
Backing up a disk does not impact the disk performance. To ensure data integrity, you are advised to back up the disk during off-peak hours when no data is written to the disk.
-Prerequisites
A disk can be backed up only when its status is Available or In-use. If you have performed operations such as expanding, attaching, detaching, or deleting a disk, refresh the page first to ensure that the operation is complete and then determine whether to back up the disk.
diff --git a/docs/cbr/umn/cbr_02_0009.html b/docs/cbr/umn/cbr_02_0009.html index a525d212..47f7b15d 100644 --- a/docs/cbr/umn/cbr_02_0009.html +++ b/docs/cbr/umn/cbr_02_0009.html @@ -5,7 +5,7 @@Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- On the Cloud Disk Backups page, click the Vaults tab and find the vault to which the disk is associated.
- Choose More > Perform Backup in the Operation column. In the disk list, select the disk you want to back up. After a disk is selected, it is added to the list of selected disks. See Figure 1.
@@ -55,7 +55,7 @@
- Click Yes. CBR automatically creates a backup for the disk.
On the Backups tab page, if the status of the backup is Available, the backup task is successful.
- If you delete data from the disk during the backup, the deleted data may fail to be backed up. To ensure data integrity, you are advised to wait until the backup task is complete and then make the change and perform a backup again.
After the backup is complete, you can use the backup to restore disk data. For details, see Restoring Data Using a Cloud Disk Backup.
+After the backup is complete, you can use the backup to restore disk data. For details, see Restoring from a Cloud Disk Backup.
After a server backup vault or disk backup vault is created, you can associate servers, file systems, or disks with the vault to back up these resources.
-Prerequisites
- The servers you plan to associate with a vault must be in the Running or Stopped state.
- The disks you plan to associate with a vault must be in the Available or In-use state.
- The SFS Turbo file systems you plan to associate with a vault must be in the Available state.
- The servers you plan to associate with a vault must have at least one disk attached.
- The vault and the resources you plan to associate with it must be in the same region.
- The total size of the resources to be associated cannot be greater than the vault capacity.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- On a backup page, locate the target vault and click Associate Server, Associate File System, or Associate Disk.
- In the resource list, select the resources you want to associate with the vault. After resources are selected, they are added to the list of selected resources. See Figure 1. diff --git a/docs/cbr/umn/cbr_03_0001.html b/docs/cbr/umn/cbr_03_0001.html index a66695c5..a84ba3c8 100644 --- a/docs/cbr/umn/cbr_03_0001.html +++ b/docs/cbr/umn/cbr_03_0001.html @@ -12,6 +12,8 @@
- Expanding Vault Capacity
+ - Replicating a Vault
+ - Managing Vault Tags
diff --git a/docs/cbr/umn/cbr_03_0002.html b/docs/cbr/umn/cbr_03_0002.html
index 888fd480..dfd8c5a4 100644
--- a/docs/cbr/umn/cbr_03_0002.html
+++ b/docs/cbr/umn/cbr_03_0002.html
@@ -4,8 +4,8 @@
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
- View the basic information about vaults. Related parameters are described in the following table. See Figure 1.
+
Viewing Vault Details
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- 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 parameters Parameter
Specifications
Vault specifications
-- A server backup vault stores backups of common servers.
- A server backup vault stores backups of non-database servers.
Vault Capacity (GB)
Capacity used by backups in the vault. It shows the space used by backups and the 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.
- On any backup page, click the Vaults tab and set filter criteria to view the vaults. See Figure 2. +
- On the Vaults tab page, set filter criteria to view specific vaults. See Figure 2.
-
- Select a value from the status drop-down list to query vaults by status. Table 2 describes the vault statuses.
-
Table 2 Vault statuses Status
Status Attribute
+Attribute
Description
An intermediate state
An intermediate state when a capacity expansion is in progress.
-In this state, you cannot expand the vault capacity. However, you can perform other operations, such as applying a policy and associating servers, file systems, or disks. After the capacity expansion is complete, the vault status becomes Available.
+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
An intermediate state
An intermediate state 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.
- Search the vault by its name or ID.
- Click Search by Tag in the upper right corner to search for vaults by tag.
- On the Search by Tag tab page that is displayed, 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 use more than one tag for a combination search. Each time after a key and a value are entered, click . The added tag search criteria are displayed under the text boxes. When more than one tag is added, the tags will be applied together for a combination search. A maximum of 10 tags can be added at a time.
- You can click Reset in the lower right corner to reset the search criteria.
- On the Search by Tag tab page that is displayed, enter an existing tag key and value and click
- Search a vault by its name or ID.
- Click Search by Tag in the upper right corner to search for vaults by tag.
- On the displayed Search by Tag page, enter an existing tag key and value and click . The added tag search criteria are displayed under the text boxes. Click Search in the lower right corner.
- You can add a maximum of 10 tags by clicking . They will be applied together for a combination search.
- You can click Reset in the lower right corner to reset the search criteria.
- On the displayed Search by Tag page, enter an existing tag key and value and click
- Select a value from the status drop-down list to query vaults by status. Table 2 describes the vault statuses.
- Click the vault name to view details about the vault. diff --git a/docs/cbr/umn/cbr_03_0003.html b/docs/cbr/umn/cbr_03_0003.html index 2bc01d22..6246341a 100644 --- a/docs/cbr/umn/cbr_03_0003.html +++ b/docs/cbr/umn/cbr_03_0003.html @@ -2,11 +2,11 @@
For the values of used capacity and backup space, only the integer part is maintained, and the decimal part is rounded off. For example, the used backup space is displayed as 0 GB, but the backup space that has actually been used might be 0.2 GB.
+- Click the name of a specific vault to view vault details.
The values of used capacity and backup space are rounded off to integers. For example, the used backup space is displayed as 0 GB, but the backup space that has actually been used might be 0.2 GB.
Deleting a Vault
You can delete unwanted vaults to reduce storage space usage and costs.
-All backups stored in the vault will be deleted once you delete a vault.
-Prerequisites
- At least one vault exists.
- The vault is in the Available or Error state.
Once you delete a vault, all backups stored in the vault will be deleted.
+-Prerequisites
- There is at least one vault.
- The vault is in the Available or Error state.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
- On any backup page, locate the vault to be deleted 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. Exercise caution when performing this operation.
+
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Find the target vault and choose More > Delete in the Operation column. See Figure 1. All backups stored in the vault will be deleted once you delete a vault.
diff --git a/docs/cbr/umn/cbr_03_0005.html b/docs/cbr/umn/cbr_03_0005.html index 2a5846f1..5b627893 100644 --- a/docs/cbr/umn/cbr_03_0005.html +++ b/docs/cbr/umn/cbr_03_0005.html @@ -1,11 +1,11 @@
Dissociating a Resource
-If you no longer need to back up an associated resource, dissociate it from the vault.
-After a resource is dissociated, the backup policy of the vault no longer has any effect on the resource. In addition, all manual and automatic backups of this resource will be deleted. Deleted backups cannot be used for data restoration. Exercise caution when performing this operation.
+If you no longer need to back up an associated resource, dissociate it from your vault.
+After a resource is dissociated, the vault's backup policy no longer applies to the resource. In addition, all manual and automatic backups of this resource will be deleted. Deleted backups cannot be used for data restoration.
Dissociating a resource from a vault does not affect the performance of services on the resource.
-Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
- On any backup page, locate the target vault and click the vault name.
- In this example, we will be using the Cloud Server Backups page to illustrate the process. Click the Associated Servers tab. Find the target server and click Dissociate in the Operation column. See Figure 1.After a resource is dissociated, the backup policy of the vault no longer has any effect on the resource. In addition, all manual and automatic backups of this resource will be deleted. Deleted backups cannot be used for data restoration. Exercise caution when performing this operation. +
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Find the target vault and click its name.
- In this example, we will be using the Cloud Server Backups page to illustrate the process. Click the Associated Servers tab. Find the target server and click Dissociate in the Operation column. See Figure 1.After a resource is dissociated, the vault's backup policy no longer applies to the resource. In addition, all manual and automatic backups of this resource will be deleted. Deleted backups cannot be used for data restoration.
diff --git a/docs/cbr/umn/cbr_03_0006.html b/docs/cbr/umn/cbr_03_0006.html index 1a083f15..3d60d71f 100644 --- a/docs/cbr/umn/cbr_03_0006.html +++ b/docs/cbr/umn/cbr_03_0006.html @@ -2,8 +2,8 @@
Expanding Vault Capacity
You can expand the size of a vault if its total capacity is insufficient.
-Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
- On any backup page, locate the target vault and choose More > Expand Capacity in the Operation column. See Figure 1.
+
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Find the target vault and choose More > Expand Capacity in the Operation column. See Figure 1.
diff --git a/docs/cbr/umn/cbr_03_0009.html b/docs/cbr/umn/cbr_03_0009.html new file mode 100644 index 00000000..da8c2555 --- /dev/null +++ b/docs/cbr/umn/cbr_03_0009.html @@ -0,0 +1,44 @@ + + +
Replicating a Vault
++CBR allows you to replicate any of the following vaults entirely to a replication vault in a different region: a server backup vault or an SFS Turbo backup vault. Replicas of server backups in the destination region can be used to create images and provision servers. Replicas of SFS Turbo backups in the destination region can be used to create file systems.
+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.
- The replication speed of a single backup is about 80 MB/s. A maximum of eight backups can be replicated at a time.
- 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 or SFS Turbo file systems.
- 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 your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- On the Vaults tab, find the target backup vault.
- Choose More > Create Replica in the Operation column of the vault. + +
- In the displayed dialog box, configure the parameters as described in Table 1.
+
+
+Table 1 Parameter description Parameter
+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
+ - 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.
++ diff --git a/docs/cbr/umn/cbr_03_0010.html b/docs/cbr/umn/cbr_03_0010.html index 6210c9dd..0ef0c84b 100644 --- a/docs/cbr/umn/cbr_03_0010.html +++ b/docs/cbr/umn/cbr_03_0010.html @@ -1,9 +1,9 @@++Parent topic: Vault Management+Managing Vault Tags
-You can add tags to a vault as well as edit and delete these tags. Vault tags are used to filter and manage vaults only.
-Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
- Click the name of a vault and select the Tag tab in the displayed vault information page.
- Adding a tag
- Click Add Tag in the upper left corner.
- In the dialog box that is displayed, set the key and value of the new tag.
A tag is represented in the form of a key-value pair. Tags are used to identify, classify, and search for cloud resources. Vault tags are used to filter and manage vaults only. A vault can have a maximum of 10 tags. See Figure 1.
+You can add, edit, or delete tags of a vault. Vault tags are used to filter and manage vaults only.
+Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- On the Vaults tab, click the name of the target vault and then select the Tags tab.
- Adding a tag
- Click Add Tag in the upper left corner.
- In the displayed dialog box, enter the key and value of the new tag.
Tags are key-value pairs, which are used to identify, classify, and search for vaults. You can add a maximum of 10 tags for a vault, and vault tags are only used for vault search and management. See Figure 1.
Table 1 describes the parameters of a tag.Table 1 Tag parameter description Parameter
@@ -16,7 +16,7 @@Key
Tag key. Each tag of a vault has a unique key. You can customize the key or select the key of an existing tag created in TMS.
+Tag key. Each tag of a vault 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 (_).
- Click OK.
-- Editing a tag
- In the Operation column of the tag that you want to edit, click Edit.
- In the Edit Tag dialog box that is displayed, modify the tag value. Table 1 describes the parameters.
- Click OK.
- Deleting a tag
- In the Operation column of the tag that you want to delete, click Delete.
- In the dialog box that is displayed, confirm the deletion information.
- Click OK.
- Editing a tag
- In the Operation column of the tag that you want to edit, click Edit.
- In the displayed Edit Tag dialog box, enter a new tag value. Table 1 describes the parameters.
- Click OK.
- Deleting a tag
diff --git a/docs/cbr/umn/cbr_03_0012.html b/docs/cbr/umn/cbr_03_0012.html index 3b5014e7..8fc6e06f 100644 --- a/docs/cbr/umn/cbr_03_0012.html +++ b/docs/cbr/umn/cbr_03_0012.html @@ -16,6 +16,8 @@- In the Operation column of the tag that you want to delete, click Delete.
- In the displayed dialog box, confirm the deletion information.
- Click OK.
- Using a Backup to Create a File System
+
- Replicating a Backup Across Regions
diff --git a/docs/cbr/umn/cbr_03_0013.html b/docs/cbr/umn/cbr_03_0013.html index 61837f8c..d165f34b 100644 --- a/docs/cbr/umn/cbr_03_0013.html +++ b/docs/cbr/umn/cbr_03_0013.html @@ -2,10 +2,10 @@
+Viewing a Backup
On the backup list, you can set search criteria to filter backups and view backup details. The results contain backup tasks that are running or have completed.
-Prerequisites
A backup task has been created.
+-Prerequisites
At least one backup task has been created.
Viewing Backup Details
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
- On any backup page, click the Backups tab and set filter criteria to view the backups. See Figure 1.
+
Viewing Backup Details
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Click the Backups tab and set filter criteria to view the backups. See Figure 1.
- You can search for backups by selecting a status from the All statuses drop-down list in the upper right corner of the backup list. Table 1 describes the backup statuses.
Table 1 Backup statuses Status
A stable state
A stable state of a backup after the backup is created, indicating that the backup is available and 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.
Recipient
- A recipient must have at least one backup vault to store the accepted shared backup, and the vault remaining space must be greater than the size of the backup to be accepted.
- A recipient can choose to accept ore reject a backup. After accepting a backup, the recipient can use the backup to create new servers or disks.
- When a sharer deletes a shared backup, the backup will also be deleted from the recipient's account, but the disks or servers previously created using the backup will be retained.
-Procedure for the Sharer
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
-Procedure for the Sharer
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Click the Backups tab and set filter criteria to view the backups.
- Locate the target backup and choose More > Share Backup in the Operation column.
The backup name, server name, backup ID, and backup type are displayed.
-- Sharing a backupFigure 1 Sharing a backup+
- Sharing a backupFigure 1 Share Backup+
+
- Click the Share Backup tab.
- Enter the project ID of the recipient.
- Click Add. The project ID to be added will be displayed in the list. You can add multiple project IDs. A backup can be shared to a maximum of ten projects.
- Click OK.
- Canceling sharing
- Locate the target backup and choose More > Share Backup in the Operation column.
- On the displayed page, click the Cancel Sharing tab and select the backup that no longer needs to be shared. Then, click OK. - -
- Sharing a backup
- Sharing a backup
Procedure for the Recipient
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
Procedure for the Recipient
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- On the selected backup page, click the Backups tab and then click Backups Shared with Me.
- Ensure that the recipient has at least one backup vault before accepting the shared backup. For how to purchase a backup vault, see Step 1: Create a Vault.
- Click Accept. On the displayed page, select the vault used to store the shared backup. Ensure that the vault remaining capacity is greater than the backup size.
Automatic Association: Determine whether to enable automatic association for the vault. If you select Configure, the vault automatically scans and associates in the next backup period servers that have not been backed up and performs backup.
- - View the shared backup you accepted in the backup list.
- View the shared backup you accepted in the backup list. + +
diff --git a/docs/cbr/umn/cbr_03_0015.html b/docs/cbr/umn/cbr_03_0015.html index 3847e778..663baa5e 100644 --- a/docs/cbr/umn/cbr_03_0015.html +++ b/docs/cbr/umn/cbr_03_0015.html @@ -2,12 +2,12 @@Deleting a Backup
You can delete unwanted backups to reduce space usage and costs.
-Context
CBR supports manual deletion of backups and automatic deletion of expired backups. The latter is implemented based on the backup retention rule in the backup policy. For details, see Creating a Backup Policy.
+-Context
CBR supports manual deletion of backups and automatic deletion of expired backups. The latter is executed based on the backup retention rule in the backup policy. For details, see Creating a Backup Policy.
Prerequisites
- At least one backup exists.
- The backup to be deleted is in the Available or Error state.
-Prerequisites
- There is at least one backup.
- The backup to be deleted is in the Available or Error state.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
- On any backup page, click the Backups tab and locate the desired backup. For details, see Viewing a Backup.
- In the row of the backup, choose More > Delete. See Figure 1. Alternatively, select the backups you want to delete and click Delete in the upper left corner to delete them in a batch.
+
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Click the Backups tab and locate the desired backup. For details, see Viewing a Backup.
- In the row of the backup, choose More > Delete from the Operation column. See Figure 1. Alternatively, select the backups you want to delete in a batch and click Delete in the upper left corner to delete them.
diff --git a/docs/cbr/umn/cbr_03_0016.html b/docs/cbr/umn/cbr_03_0016.html index 3597d80d..8058dafd 100644 --- a/docs/cbr/umn/cbr_03_0016.html +++ b/docs/cbr/umn/cbr_03_0016.html @@ -2,17 +2,17 @@
Using a Backup to Create an Image
CBR allows you to create images using ECS backups. You can use the images to provision ECSs to rapidly restore service running environments.
-Prerequisites
- Confirm that the following operations have been performed before you use an ECS backup to create an image:
- You have optimized the Linux ECS (referring to Optimizing a Linux Private Image) and installed Cloud-Init (referring to Installing Cloud-Init).
- You have optimized the Windows ECS (referring to Optimizing a Windows Private Image) and installed Cloudbase-Init (referring to Installing and Configuring Cloudbase-Init).
- A backup can be used to create an image in either of the following scenarios: 1. The backup is in the Available state. 2. The backup is 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.
+-Prerequisites
- The following operations have been performed:
- You have optimized the Linux ECS (referring to Optimizing a Linux Private Image) and installed Cloud-Init (referring to Installing Cloud-Init).
- You have optimized the Windows ECS (referring to Optimizing a Windows Private Image) and installed Cloudbase-Init (referring to Installing and Configuring Cloudbase-Init).
- The backup is in the Available state or in the Creating state which is marked with Image can be created.-
Once a backup creation starts, the backup enters the Creating state. After a period of time, a message stating "Image can be created" is displayed under Creating. In this case, the backup can be used for creating an image, even though it is still being created and cannot be used for restoration.
- The backup you want to use to create an image contains the system disk data.
- The backup contains the system disk data.
Function Description
- Images created using a backup are the same, so CBR allows you to use a backup to create only one full-ECS image that contains the whole data of the system disk and data disks of an ECS, in order to save the image quota. After an image is created, you can use the image to provision multiple ECSs in a batch.
- A backup with an image created cannot be directly deleted. If you want to delete such a backup, delete its image first. If a backup is automatically generated based on a backup policy and the backup has been used to create an image, the backup will not be counted as a retained backup and will not be deleted automatically.
- A backup is compressed when it is used to create an image. Therefore, the size of the generated image is smaller than that of the backup.
-Notes
- Images created using a backup are the same, so CBR allows you to use a backup to create only one full-ECS image that contains the whole data of the system disk and data disks of an ECS, in order to save the image quota. After an image is created, you can use the image to provision multiple ECSs in a batch.
- A backup with an image created cannot be deleted directly. To delete such a backup, delete its image first. If a backup is automatically generated based on a backup policy and the backup has been used to create an image, the backup will not be counted as a retained backup and will not be deleted automatically.
- A backup is compressed when it is used to create an image, so the size of the generated image may be smaller than the backup size.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- In the row of the backup, choose More > Create Image. See Figure 1. -
- Create an image by referring to section "Creating a Full-ECS Image from a CBR Backup" in the Image Management Service User Guide.
- If you want to use an image to provision ECSs, 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 from a CBR Backup" in the Image Management Service User Guide.
- Use the image to provision ECSs when needed. For details, see section "Creating an ECS from an Image" in the Image Management Service User Guide.
diff --git a/docs/cbr/umn/cbr_03_0017.html b/docs/cbr/umn/cbr_03_0017.html index 30a587e2..6ef7a94d 100644 --- a/docs/cbr/umn/cbr_03_0017.html +++ b/docs/cbr/umn/cbr_03_0017.html @@ -1,12 +1,12 @@Using a Backup to Create a Disk
-You can use a disk backup to create a disk. After the disk is created, data on the new disk is the same as that in the disk backup.
-After a new disk is created using the backup data of a system disk, the new disk can only be mounted to the cloud server as a data disk and cannot be mounted as a system disk.
-Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
- Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- If the status of the target backup is Available, click Create Disk in the Operation column of the backup.
- Set the disk parameters.
For details about these parameters, see the parameter description table in section "Create an EVS Disk" of the Elastic Volume Service User Guide.
-Note the following items when setting disk parameters:
-- You can choose the AZ to which the backup source disk belongs, or you can choose a different AZ.
- The new disk must be at least as large as the backup's source disk.
If the capacity of the new disk is greater than that of the backup source disk, initialize the disk by following the steps provided in section "Extending Disk Partitions and File Systems" of the Elastic Volume Service User Guide.
+You can create new disks from backups. Once created, the new disks will contain the backup data.
+The new disks created using system disk backups can only be used as data disks on servers. They cannot be used as system disks.
+Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- If the status of the target backup is Available, click Create Disk in the Operation column of the backup.
- Configure the disk parameters.
See the parameter description table in section "Create an EVS Disk" of the Elastic Volume Service User Guide for more information.
+Pay attention to the following:
+- You can choose the AZ to which the backup source disk belongs, or a different AZ.
- The new disk must be at least as large as the backup's source disk.
If the capacity of the new disk is greater than that of the backup's source disk, format the additional space by following the steps provided in section "Extending Disk Partitions and File Systems" of the Elastic Volume Service User Guide.
- You can create a disk of any type regardless of the backup's disk type.
- Click Next.
- Go back to the disk list. Check whether the disk is successfully created.
You will see the disk status change as follows: Creating, Available, Restoring, Available. You may not notice the Restoring status because Instant Restore is supported and the restoration speed is very fast. After the disk status has changed from Creating to Available, the disk is successfully created. After the status has changed from Restoring to Available, backup data has been successfully restored to the created disk.
diff --git a/docs/cbr/umn/cbr_03_0018.html b/docs/cbr/umn/cbr_03_0018.html new file mode 100644 index 00000000..8b314b92 --- /dev/null +++ b/docs/cbr/umn/cbr_03_0018.html @@ -0,0 +1,64 @@ + + +Replicating a Backup Across Regions
++CBR enables you to replicate server backups and SFS Turbo backups from one region to another. In the destination region:
+- Replicas of server backups can be used to create images and provision servers.
- Replicas of SFS Turbo backups can be used to create file systems.
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
- Cloud disk backups cannot be replicated to other regions.
- 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 or SFS Turbo file systems.
- 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 your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Click the Backups tab and locate the desired backup. For details, see Viewing a Backup.
- Choose More > Create Replica in the Operation column of the backup. + +
- In the displayed dialog box, configure the parameters as described in Table 1.
+
+
+Table 1 Parameter description Parameter
+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.
++ 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.
++ diff --git a/docs/cbr/umn/cbr_03_0024.html b/docs/cbr/umn/cbr_03_0024.html index b96c5be0..8b034eec 100644 --- a/docs/cbr/umn/cbr_03_0024.html +++ b/docs/cbr/umn/cbr_03_0024.html @@ -6,6 +6,8 @@++Parent topic: Backup Management+- 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 b6387b5c..828dd44b 100644 --- a/docs/cbr/umn/cbr_03_0025.html +++ b/docs/cbr/umn/cbr_03_0025.html @@ -1,21 +1,21 @@Creating a Backup Policy
-A backup policy allows a vault to automatically execute backup tasks at specified times or intervals. Periodic backups can be used to restore data quickly against data corruption or loss.
-To implement periodic backup, you need to create a backup policy first. CBR will then periodically perform backups according to the execution time specified in the backup policy. You can choose to use the default backup policy provided by CBR or create one as needed.
-You can apply backup policies to server backup vaults and disk backup vaults.
-Context
- After a backup policy is enabled, CBR automatically backs up resources associated with the vaults that have been associated with the policy and periodically deletes expired backups.
- Each account can create a maximum of 32 backup policies.
- When expired backups are cleared based on a policy's retention rules, only automatic backups will be deleted. Manual backup will not be deleted.
- Only servers in the Running or Stopped state can be backed up.
- Only disks in the Available or In-use state can be backed up.
diff --git a/docs/cbr/umn/cbr_03_0046.html b/docs/cbr/umn/cbr_03_0046.html index 975bd54f..f6ec80b3 100644 --- a/docs/cbr/umn/cbr_03_0046.html +++ b/docs/cbr/umn/cbr_03_0046.html @@ -8,7 +8,19 @@A backup policy allows CBR to automatically back up vaults at specified times or intervals. Periodic backups can be used to restore data quickly against data corruption or loss.
+To implement periodic backups, you need a backup policy first. You can use the default backup policy or create one as needed.
+You can apply backup policies to server backup vaults and disk backup vaults. CBR will then periodically perform backup at the time given in the backup policy and delete expired backups.
+-Constraints
- A backup policy must be enabled before it can be used for periodic backups.
- A maximum of 32 backup policies can be created in each account.
- When expired backups are deleted, automatic backups will be deleted, but manual backups will not.
- Only servers in the Running or Stopped state and disks in the Available or In-use state can be backed up.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
-Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Choose Policies and click the Backup Policies tab. In the upper right corner, click Create Policy. See Figure 1.
-
+
- Set the backup policy parameters. Table 1 describes the parameters.
-
Table 1 Backup policy parameter description Parameter
+- -More frequent backup intervals 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 cycle as needed.
+- More frequent backups create more backups or retain backups for a longer time, protecting data to a greater extent but occupying more storage space. Set an appropriate backup frequency as needed.
- Click OK.
- Locate the desired vault and choose More > Apply Backup Policy to apply the created policy to the vault. You can view the applied policy on the vault details page.
After the policy is applied, data will be periodically backed up to the vault based on the policy.
+- Click OK.
- Locate the desired vault and choose More > Apply Backup Policy to apply the policy to the vault. You can view the applied policy on the vault details page.
After the policy is applied, data will be periodically backed up to the vault based on the policy.
Example
A user has a vault associated with one disk. At 10:00 a.m. on Monday, the user sets a backup policy for the vault, that is, executing a backup task at 02:00 a.m. every day and retaining a maximum of three backups. At 11:00 a.m. on Saturday, three backups are retained, which are generated on Wednesday, Thursday, and Friday. The backup generated at 2:00 a.m. on Tuesday has been automatically deleted.
+Example
At 10:00 a.m. on Monday, a user sets a backup policy for their vault to instruct CBR to execute a backup task at 02:00 a.m. every day and retain a maximum of three backups. As of 11:00 a.m. on Saturday, three backups will be retained, which are generated on Wednesday, Thursday, and Friday. The backup generated at 02:00 a.m. on Tuesday has been automatically deleted.
diff --git a/docs/cbr/umn/cbr_03_0026.html b/docs/cbr/umn/cbr_03_0026.html new file mode 100644 index 00000000..136a0f20 --- /dev/null +++ b/docs/cbr/umn/cbr_03_0026.html @@ -0,0 +1,107 @@ + + +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.
+You can apply replication policies to server backup vaults and SFS Turbo backup vaults.
++Constraints
When a backup time and a replication time are both configured, ensure that replication starts after backup is complete. Or, replication may fail.
++Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Choose Policies and click the Replication Policies tab. In the upper right corner, click Create Policy. + +
- Set the replication policy parameters. Table 1 describes the parameters.
+
+
+Table 1 Replication policy parameters Parameter
+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 Frequency
+Select a replication frequency.
+- Weekly
Specifies on which days of each week the replication task will be executed. You can select multiple days.
+ - Day based
Specifies the interval (every 1 to 30 days) for executing the replication task.
+
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.
+ - PermanentNOTE:+
- 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.
+-
+ - Weekly
- Click Create Now.
- 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.
+
+Example
A 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.
+++ diff --git a/docs/cbr/umn/cbr_03_0027.html b/docs/cbr/umn/cbr_03_0027.html index 8c2f651c..bd5da585 100644 --- a/docs/cbr/umn/cbr_03_0027.html +++ b/docs/cbr/umn/cbr_03_0027.html @@ -2,18 +2,18 @@++Parent topic: Policy Management+Modifying a Policy
This section describes how to modify a policy.
-Prerequisites
You have created at least one policy.
+-Prerequisites
At least one policy has been created.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
- On any backup page, find the target vault and click the vault name to view the vault details.
- In the Policies area, click Edit in the row of a policy to open the policy editing page. See Figure 1.
+
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Find the target vault and click 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.
Related parameters are described in Table 1.
- - Click OK.
If the policy retention rule is modified, the new rule takes effect depending on how you have changed it. For details, see Why Does the Retention Rule Not Take Effect After Being Changed?
- - Alternatively, you can select Policies from the navigation tree on the left and edit the desired policy.
- Click OK.
If the retention rule is modified, the new rule does not necessarily apply to existing backups. For details, see Why Does the Retention Rule Not Take Effect After Being Changed?
+- Alternatively, select Policies from the navigation tree on the left and edit the desired policy.
- Log in to CBR Console.
diff --git a/docs/cbr/umn/cbr_03_0028.html b/docs/cbr/umn/cbr_03_0028.html index bfa32ea1..b38a61c7 100644 --- a/docs/cbr/umn/cbr_03_0028.html +++ b/docs/cbr/umn/cbr_03_0028.html @@ -1,10 +1,10 @@Deleting a Policy
-You can delete backup and replication policies if needed.
-Prerequisites
You have created at least one policy.
+You can delete backup and replication policies if they are no longer needed.
+-Prerequisites
At least one policy has been created.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Click the Backup Policies tab, locate the row that contains the policy you want to delete, and click Delete.
Deleting a policy will not delete the backups generated based on the policy. You can manually delete unwanted backups.
- Confirm the information and click Yes.
Applying a Policy to a Vault
-A backup policy allows a vault to automatically execute backup tasks at specified times or intervals. Periodic backups can be used to restore data quickly against data corruption or loss.
-Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
- On any backup page, find the target vault and choose More > Apply Backup Policy. See Figure 1.
+
You can apply a backup policy to a vault to execute backup tasks at specified times or intervals.
+Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Find the target vault and choose More > Apply Backup Policy. See Figure 1.
-
- You can select an existing backup policy from the drop-down list or create a new one. For how to create a policy, see Creating a Backup Policy.
- After the policy is successfully applied, you can view the details in the Policies area on the vault details page.
- Select an existing backup policy from the drop-down list or create a new one. For how to create a policy, see Creating a Backup Policy.
- After the policy is successfully applied, you can view the details in the Policies area on the vault details page.
diff --git a/docs/cbr/umn/cbr_03_0030.html b/docs/cbr/umn/cbr_03_0030.html index f7a0e6ee..5b6786d1 100644 --- a/docs/cbr/umn/cbr_03_0030.html +++ b/docs/cbr/umn/cbr_03_0030.html @@ -4,14 +4,15 @@If you no longer need automatic backup for a vault, remove the policy from the vault.
-Prerequisites
A policy has been applied to the vault.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
- On any backup page, find the target vault and click the vault name to view the vault details.
- In the Policies area, click Remove Policy. See Figure 1.
+
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Find the target vault and click the vault name to view its details.
- In the Policies area, click Remove Policy. See Figure 1.
-
- If a backup task is being executed for a resource in the vault, the policy can be removed normally. However, the backup task will continue and backups will be generated.
- After a policy is removed, backups retained by time will expire based on the retention rule, but backups retained by quantity will not be automatically deleted. You can manually delete unwanted backups.
- - If a backup task is being executed for a resource in the vault, the policy can be removed. However, the backup task will continue and backups will be generated.
- After a policy is removed, backups retained by Time period will expire based on the retention rule, but backups retained by Backup quantity will not. You need manually delete unwanted backups.
- Click Yes. The vault will no longer execute tasks as specified in this policy.
+- Click Yes. Backup or replication tasks will no longer be executed for the vault.
diff --git a/docs/cbr/umn/cbr_03_0031.html b/docs/cbr/umn/cbr_03_0031.html index cdb1152f..ffd4247b 100644 --- a/docs/cbr/umn/cbr_03_0031.html +++ b/docs/cbr/umn/cbr_03_0031.html @@ -4,9 +4,9 @@diff --git a/docs/cbr/umn/cbr_03_0032.html b/docs/cbr/umn/cbr_03_0032.html index 74536f08..df33a9de 100644 --- a/docs/cbr/umn/cbr_03_0032.html +++ b/docs/cbr/umn/cbr_03_0032.html @@ -1,13 +1,13 @@ -Restoring Data Using a Cloud Server Backup
-When disks on a server are faulty, or server data is lost due to misoperations, you can use a backup to restore the server.
-Context
- Data on data disks cannot be restored to system disks.
- Data cannot be restored to servers in the Faulty state.
Restoring from a Cloud Server Backup
+When disks on a server are faulty or their data is lost, you can use a backup to restore the server to its state when the backup was created.
+-Constraints
- When restoring from a cloud server backup, a data disk backup cannot be restored to the system disk.
- Data cannot be restored to servers in the Faulty state.
Prerequisites
- Disks on the server whose data needs to be restored are running properly.
- The server whose data needs to be restored has at least one Available backup.
-Prerequisites
- Disks are running properly on the server whose data needs to be restored.
- The server has at least one Available backup.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
- Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- In the row of the backup, click Restore Server. See Figure 1.
The historical data at the backup point in time will overwrite the current server data. The restoration cannot be undone.
+Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- In the row of the backup, click Restore Server. See Figure 1.@@ -15,19 +15,19 @@ -
The current server data will be overwritten by the data captured at the time of backup. The restoration cannot be undone.
- (Optional) Deselect Start the server immediately after restoration.If you deselect Start the server immediately after restoration, manually start the server after the restoration is complete.
Servers are shut down during restoration. It is therefore recommended that you perform restoration operations during off-peak hours.
+- (Optional) Deselect Start the server immediately after restoration.
If you do so, manually start the server after the restoration is complete.- Servers will be shut down during restoration, so you are advised to perform a restoration during off-peak hours.
- In the Specified Disk drop-down list, select the target disk to which the backup will be restored.
- If the server has only one disk, the backup is restored to the disk by default.
- If the server has multiple disks, the backup is respectively restored to the original disks by default. You can also restore the backup to another disk on the backup server by selecting the disk from the drop-down list. However, the specified destination disk must be at least as large as the backup source disk.
- Backup data of data disks cannot be restored to system disks.
- In the Specified Disk drop-down list, select the target disk to which the backup will be restored.
- - If the server has only one disk, the backup is restored to that disk by default.
- If the server has multiple disks, the backup is restored to the original disks by default. You can also restore the backup to another disk of at least the same size as the original disk.
- When restoring from a cloud server backup, a data disk backup cannot be restored to the system disk.
If the number of disks to be restored is greater than the number of disks that are backed up, restoration may cause data inconsistency.
-For example, if the data of Oracle is scattered across multiple disks and only some of them are restored, data inconsistency occurs after the restoration and the application may unable to start.
+- If the number of disks to be restored is greater than the number of disks that were backed up, restoration may cause data inconsistency.
+For example, if the Oracle data is scattered across multiple disks and only some of them are restored, data inconsistency may occur and the application may fail to start.
- Click Yes and confirm the restoration is successful.
In the backup list, view the restoration status. When the backup enters the Available state and no new failed restoration tasks exist in Tasks, the restoration is successful. The resource is restored to the state at the time you took that backup.
+- Click Yes and confirm that the restoration is successful.
You can view the restoration status in the backup list. When the backup enters the Available state and no new restoration tasks failed, the restoration is successful. The resource is restored to the state when that backup was created.
For details about how to view failed restoration tasks, see Managing Tasks.
- diff --git a/docs/cbr/umn/cbr_03_0033.html b/docs/cbr/umn/cbr_03_0033.html index 765b6b02..64bfe0e5 100644 --- a/docs/cbr/umn/cbr_03_0033.html +++ b/docs/cbr/umn/cbr_03_0033.html @@ -1,21 +1,23 @@ -If a Windows server is restored, data disks may fail to be displayed due to Windows limitations.
-After you use a cloud server backup to restore a logical volume group, the logical volume group needs to be attached again.
-You need to manually online these data disks. For details, see Data Disks Are Not Displayed After a Windows Server Is Restored.
+ Due to Window limitations, data disks may fail to be displayed after a Windows server is restored.
+After you use a cloud server backup to restore a logical volume group, you need to attach the logical volume group again.
+You need to manually bring these data disks online. For details, see Data Disks Are Not Displayed After a Windows Server Is Restored.
Restoring Data Using a Cloud Disk Backup
-You can use a disk backup to restore a disk to the time when the backup was created.
-Prerequisites
- The status of the disk to be restored must be Available.
- 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.
Restoring from a Cloud Disk Backup
+You can use a disk backup to restore the disk to its state when the backup was created.
+-Prerequisites
- The disk to be restored is Available.
- 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.
Constraints
- Backups can only be restored to original disks. If you want to restore a backup to a disk other than the original one, directly use the backup to create a new disk.
-Constraints
- Backups can only be restored to original disks. If you want to restore a backup to a different disk, use the backup to create a new disk.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
- Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- In the row of the backup, click Restore Disk. The Restore Disk page is displayed. See Figure 1.
- The backup data will overwrite the current disk data, and the restoration cannot be undone.
- If the restore button is grayed out, stop the server, detach the disk to be restored, and then restore data. After the disk data is restored, attach the disk to the server and start the server.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- In the row of the backup, click Restore Disk. The Restore Disk page is displayed. See Figure 1.
+
+
- The backup data will overwrite the current disk data, and the restoration cannot be undone.
- If the restore button is grayed out, stop the server, detach the disk, and then try again. After the disk data is restored, attach the disk to the server and start the server.
-
- Click Yes. You can check whether the data is successfully restored on the Backups tab page of Disk Backups or on the EVS console.
When the status of the backup changes to Available, the restoration is successful. The resource is restored to the state at the time you took that backup.
- - After the restoration is complete, re-attach the disk to the server. For details, see section "Attaching an Existing Non-Shared Disk" in the Elastic Volume Service User Guide.
- Click Yes. You can check whether data is successfully restored on the Backups tab page of Disk Backups or on the EVS console.
When the status of the backup changes to Available, the restoration is successful. The resource is restored to the state when that backup was created.
+- After the restoration is complete, re-attach the disk to the server. For details, see section "Attaching an Existing Non-Shared Disk" in the Elastic Volume Service User Guide.
diff --git a/docs/cbr/umn/cbr_03_0036.html b/docs/cbr/umn/cbr_03_0036.html index 272a02cd..f6bc2319 100644 --- a/docs/cbr/umn/cbr_03_0036.html +++ b/docs/cbr/umn/cbr_03_0036.html @@ -83,6 +83,13 @@addResources
- (Optional) Deselect Start the server immediately after restoration.
- Log in to CBR Console.
- Log in to CBR Console.
- Log in to CBR Console.
Performing a replication
+vault
+replicateVaultBackup
+Performing a backup
vault
@@ -104,6 +111,13 @@deleteBackup
Synchronizing a backup
+backup
+syncBackup
+Restoring a backup
backup
@@ -111,14 +125,105 @@restoreBackup
Replicating a backup
+backup
+replicateBackup
+Setting resources
+vault
+setResources
+Migrating resources
+vault
+migrateResources
+Disabling protection
+vault
+disableProtect
+Deleting backups from a vault
+vault
+deleteVaultBackup
+Synchronizing vault backups
+vault
+syncVaultBackup
+Batch creating or deleting vault tags
+vault
+bulkCreateDeleteVaultTag
+Creating a vault tag
+vault
+createVaultTag
+Deleting a vault tag
+vault
+deleteVaultTag
+Creating a share member
+backup
+createBackupMember
+Updating a share member
+backup
+updateBackupMember
+Deleting a share member
+backup
+deleteBackupMember
+Updating a backup
+backup
+updateBackup
+
diff --git a/docs/cbr/umn/cbr_03_0037.html b/docs/cbr/umn/cbr_03_0037.html index 201046a7..877f76d3 100644 --- a/docs/cbr/umn/cbr_03_0037.html +++ b/docs/cbr/umn/cbr_03_0037.html @@ -13,6 +13,7 @@Viewing Audit Logs
For how to view audit logs, see section "Querying Real-Time Traces" in the Cloud Trace Service User Guide.
+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 your desired region and project.
- Click Service List and choose Management & Deployment > Cloud Trace Service.
- Click Trackers in the left navigation pane. See Figure 1.
+
- Log in to the management console.
- In the upper left corner of the page, click and select your desired region and project.
- Click Service List and choose Management & Deployment > Cloud Trace Service.
- Click Trackers in the left navigation pane. See Figure 1.
- 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.
- Domain name, project name, and project ID, which can be obtained by performing the following operations:
Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.
- Quota information, which includes:
- Service name
- Quota type
- Required quota
- Log in to CBR Console.
- The following operations have been performed:
- Confirm that the following operations have been performed before you use an ECS backup to create an image:
- Log in to CBR Console.
2023-03-02
+2023-04-19
+This issue is the twenty-first official release, which incorporates the following changes:
+- Added section "Replicating a Backup Across Regions."
- Added section "Replicating a Vault."
- Added section "Creating a Replication Policy."
2023-04-18
+This issue is the twentieth official release, which incorporates the following change:
+Added some CBR operations that can be recorded by CTS in section "Auditing."
+2023-03-02
This issue is the nineteenth official release, which incorporates the following changes:
- Updated the screenshots in section "A Server Created Using an Image Enters Maintenance Mode After Login."
- Modified section "Sharing a Backup."
Permissions Management
--+- Creating a User and Granting CBR Permissions
diff --git a/docs/cbr/umn/cbr_03_0048.html b/docs/cbr/umn/cbr_03_0048.html index 9c1cdce2..a375b6a1 100644 --- a/docs/cbr/umn/cbr_03_0048.html +++ b/docs/cbr/umn/cbr_03_0048.html @@ -4,14 +4,14 @@+ + \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0050.html b/docs/cbr/umn/cbr_03_0050.html index 8f788e08..3ab0fa07 100644 --- a/docs/cbr/umn/cbr_03_0050.html +++ b/docs/cbr/umn/cbr_03_0050.html @@ -1,10 +1,10 @@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 employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing CBR resources.
- Grant only the permissions required for users to perform a specific task.
- Entrust a cloud account or cloud service to perform efficient O&M on your CBR resources.
If your cloud account does not require individual IAM users, skip this section. If your account cannot meet your requirements, create IAM users by referring to Identity and Access Management User Guide.
-This section describes the procedure for granting permissions (see Figure 1).
-Prerequisites
You have learnt about the permissions (see Permissions Management) supported by CBR and chosen the policies or roles according to your requirements. For the system policies of other services, see "System Permissions".
+Figure Figure 1 illustrates the procedure for granting permissions.
+-Prerequisites
Learn 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 "Permissions".
@@ -21,3 +21,10 @@Process Flow
-- Create a user group and assign permissions to it.
Create a user group on the IAM console, and assign the CBR ReadOnlyAccess policy to the group.
+Process Flow
+- Create a user group and assign permissions.
Create a user group on the IAM console, and assign the CBR ReadOnlyAccess policy to the group.
- Create an IAM user and add it to the user group.
Create a user on the IAM console and add the user to the group created in 1.
- - Log in and verify permissions.
Log in to CBR Console using the created user, and verify that the user has read-only permissions for CBR.
-- Choose Service List > Cloud Backup and Recovery. Then click Create Server Backup Vault on CBR Console. If a message appears indicating that you have insufficient permissions to perform the operation, the CBR ReadOnlyAccess policy has already taken effect.
- Choose any other service in Service List. If a message appears indicating that you have insufficient permissions to access the service, the CBR ReadOnlyAccess policy has already taken effect.
- Log in and verify permissions.
Log in to CBR Console as the created user and verify that the user has read-only permissions for CBR.
+- Choose Service List > Cloud Backup and Recovery. Then click Create Server Backup Vault on CBR Console. If a message appears indicating that you do not have the permissions to perform the operation, the CBR ReadOnlyAccess policy has already taken effect.
- Choose any other service in Service List. If a message appears indicating that you do not have the permissions to access the service, the CBR ReadOnlyAccess policy has already taken effect.
- Create a user group and assign permissions.
Creating a Custom Policy
-Custom policies can be created to supplement the system-defined policies of CBR. For the actions supported for custom policies, see section "Permissions Policies and Supported Actions" in Cloud Backup and Recovery API Reference.
+You can create custom policies to supplement the system-defined policies of CBR. For the actions supported for custom policies, see section "Permissions Policies and Supported Actions" in Cloud Backup and Recovery API Reference.
You can create custom policies in either of the following ways:
- Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
- JSON: Edit JSON policies from scratch or based on an existing policy.
This section provides examples of common user-defined CBR policies.
+For details about how to create custom policies, see Creating a Custom Policy. This section provides examples of common CBR custom policies.
Example Custom Policies
- Example 1: Allowing users to create, modify, and delete vaults
{ "Version": "1.1", "Statement": [ @@ -21,7 +21,7 @@ ] } - Example 2: Denying users to delete vaults and backups
A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.
-The following method can be used if you need to assign permissions of the CBR FullAccess policy to a user but you want to prevent the user from deleting vaults and backups. Create a custom policy for denying vault and backup deletion, and attach both policies to the group to which the user belongs. Then, the user can perform all operations on CBR except deleting vaults or backups. The following is an example of a deny policy:
+If you need to assign permissions of the CBR FullAccess policy to a user but want to prevent the user from deleting vaults and backups, create a custom policy for denying vault and backup deletion, and attach both policies to the group to which the user belongs. In this way, the user can perform all operations on CBR except deleting vaults or backups. The following is an example deny policy:
{ "Version": "1.1", "Statement": [ diff --git a/docs/cbr/umn/cbr_03_0104.html b/docs/cbr/umn/cbr_03_0104.html index 3c87b21e..99b801be 100644 --- a/docs/cbr/umn/cbr_03_0104.html +++ b/docs/cbr/umn/cbr_03_0104.html @@ -1,19 +1,58 @@(Optional) Migrating Resources from CSBS/VBS
-Context
The cloud platform has launched the next-generation backup service, CBR. If you have backup resources in CSBS or VBS but want to switch to CBR for the management of these historical backup resources, you can migrate them to CBR in a few clicks.
+-Context
The cloud platform has launched the next-generation backup service, CBR. If you have backups in CSBS or VBS but want to switch to CBR to manage these historical backups, you can migrate them to CBR in a few clicks.
If you have never used CSBS or VBS, or do not need the historical backups anymore, skip this section.
Migration Rules
During migration, the system will automatically create vaults based on your historical resources.
-- If servers or disks have been associated with a backup policy and have been backed up, during the migration, the system will create a vault with the same name (up to 64 characters) as the policy name, regardless of whether the policy is enabled. After the vault is created, the policy will be applied to the vault.
- If servers or disks have been associated with a backup policy but no backup has been generated, during the migration, the system will create a vault only when the policy is enabled. After the vault is created, the policy will be applied to the vault. The rule for naming the vault is the same as that in the preceding rule.
- If servers or disks have been applied with a backup or replication policy but no backup or replica has been generated, and the policy is not enabled, then only the policy will be migrated.
- The system will migrate backup and replication policies regardless of whether they are associated with servers or disks.
- Generated backup replicas will be stored in a replication vault named default.
- Other backups, such as manual backups, will be stored in a server backup vault named default. Different vaults will be automatically created based on different types of resources. For example, the system will create a disk backup vault during the migration of disk backups.
- After resources are migrated, backups created using CBR will also be displayed in VBS Console, but you will be billed only once.
To delete backups from VBS Console, find these backups in CBR and delete them. Then, the backups will also be automatically deleted from VBS Console.
+Migration Rules
During migration, CBR will automatically create vaults based on the types of your historical resources.
+ ++
+Table 1 Migration rules Before Migration
+After Migration
+Servers or disks are associated with a backup policy.
+If backups have been generated, CBR will create a vault with the same name (up to 64 characters) as the policy name (regardless of whether the policy is enabled) and apply the policy to the vault after the vault is created.
+If no backup is generated, CBR will create a vault only when the policy is enabled. The policy applying rule and vault naming rule are the same as above.
+Servers or disks are associated with a backup or replication policy.
+If no backup is generated and the policy is disabled, only the policy will be migrated.
+Backup or replication policies are not associated with any resource.
+The policies will be migrated.
+Backup replicas are generated.
+CBR will create a replication vault named default to store generated backup replicas.
+An image is created using a backup and a tag is added to the image.
+The backup will fail to be migrated. Go to the IMS console, delete the tag and then migrate the backup again. After the backup is migrated, add the tag if needed.
+Other backups, including manual backups, will be stored in a server backup vault named default. Different vaults will be created based on different types of resources. For example, CBR will create a disk backup vault to store the migrated disk backups.
+After the migration, backups created using CBR will also be displayed on the VBS console, but you will be billed only once.- To delete backups from the VBS console, find these backups in CBR and delete them. Then, the backups will also be deleted from the VBS console.
- If an image has been created using a backup before the migration and a tag has been added to the image, the backup migration may fail. In this case, go to IMS Console, delete the tag of the image, and then perform the migration again. After the migration is complete, re-add the tag if needed.
+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. The system will automatically migrate resources to the vaults created by the system.
- Backup resources of one account need to be migrated only once.
- After resources are migrated, disk backups and server backups will be automatically stored in CBR vaults. No further operations are required.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup 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.
diff --git a/docs/cbr/umn/cbr_03_0107.html b/docs/cbr/umn/cbr_03_0107.html index 212327e1..c7db1de3 100644 --- a/docs/cbr/umn/cbr_03_0107.html +++ b/docs/cbr/umn/cbr_03_0107.html @@ -1,10 +1,10 @@
Using a Backup to Create a File System
-In case of a virus attack, accidental deletion, or software or hardware fault, you can use an SFS Turbo file system backup to create a new file system. After it is created, data on the new file system is the same as that in the backup.
-Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
- Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- If the status of the target backup is Available, click Create File System in the Operation column of the backup.
- Set the file system parameters. See Figure 1.
-
- For detailed parameter descriptions, see table "Parameter description" under "Creating an SFS Turbo File System" in the Scalable File Service User Guide.
diff --git a/docs/cbr/umn/cbr_03_0115.html b/docs/cbr/umn/cbr_03_0115.html index 034ee7eb..3f6890d1 100644 --- a/docs/cbr/umn/cbr_03_0115.html +++ b/docs/cbr/umn/cbr_03_0115.html @@ -3,7 +3,7 @@In case of a virus attack, accidental deletion, or software or hardware fault, you can use an SFS Turbo file system backup to create a new file system. Once created, data on the new file system is the same as that in the backup.
+Procedure
- Log in to CBR Console.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Choose Storage > Cloud Backup and Recovery. Choose your desired type of backup from the left navigation pane.
- Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
- If the status of the target backup is Available, click Create File System in the Operation column of the backup.
- Configure the file system parameters. See Figure 1.
+
- You can learn about the parameter descriptions in table "Parameter description" under "Creating an SFS Turbo File System" in the Scalable File Service User Guide.
- Click Next.
- Go back to the file system list and check whether the file system is successfully created.
You will see the file system status change as follows: Creating, Available, Restoring, Available. You may not notice the Restoring status because Instant Restore is supported and the restoration speed is very fast. After the file system status has changed from Creating to Available, the file system is successfully created. After the status has changed from Restoring to Available, backup data has been successfully restored to the created file system.
Viewing Monitoring Statistics
- Log in to the management console.
- View the monitoring graphs using either of the following methods.
- Method 1: Choose Storage > Cloud Backup and Recovery. In the vault list, locate the vault whose monitoring data you want to view and choose More > View Monitoring Data in the Operation column.
- Method 2: Choose Management & Deployment > Cloud Eye > Cloud Service Monitoring > Cloud Backup and Recovery. In the vault list, click View Metric in the Operation column of the vault whose monitoring data you want to view.
- You can view the vault monitoring data by metric or monitored duration.
For more information, see the Cloud Eye User Guide.
+
Creating an Alarm Rule
Cloud Eye allows you to use alarm templates to create alarm rules, making it easy and convenient to add or modify alarm rules for resources or cloud services, especially for a large number of resources and cloud services.
This section describes how to create an alarm rule for CBR.
-Procedure
- Log in to the management console.
- In the upper left corner of the page, click
and select your desired region and project. - Under Management & Deployment, select Cloud Eye. In the navigation pane on the left, choose Alarm Management > Alarm Rules.
- On the displayed page, click Create Alarm Rule in the upper right corner.
- In the Create Alarm Rule dialog box, set the parameters.
- Set Name and Description.+
Procedure
- Log in to the management console.
- In the upper left corner of the page, click and select your desired region and project.
- Under Management & Deployment, select Cloud Eye. In the navigation pane on the left, choose Alarm Management > Alarm Rules.
- On the displayed page, click Create Alarm Rule in the upper right corner.
- In the Create Alarm Rule dialog box, set the parameters.
- Set Name and Description.
- Set Name and Description.
- Set Name and Description.
- Log in to CBR Console.
- You can search for backups by selecting a status from the All statuses drop-down list in the upper right corner of the backup list. Table 1 describes the backup statuses.
- Log in to CBR Console.
- Adding a tag
- Log in to CBR Console.
- Adding a tag
- Log in to CBR Console.
- Log in to CBR Console.
- Log in to CBR Console.
- Log in to CBR Console.
- Log in to CBR Console.
- Click the name of a specific vault to view vault details.
- Log in to CBR Console.
You can set search criteria for querying desired vaults in the vault list.
-Prerequisites
A vault has been created.
Viewing Vault Details
- Log in to CBR Console.
