diff --git a/docs/cbr/umn/ALL_META.TXT.json b/docs/cbr/umn/ALL_META.TXT.json index d5ee5c6e9..2cbde6f58 100644 --- a/docs/cbr/umn/ALL_META.TXT.json +++ b/docs/cbr/umn/ALL_META.TXT.json @@ -13,7 +13,7 @@ "uri":"cbr_01_0002.html", "product_code":"cbr", "code":"2", - "des":"Cloud Backup and Recovery (CBR) enables you to back up Elastic Cloud Servers (ECSs), Elastic Volume Service (EVS) disks, and SFS Turbo file systems with ease. In case of ", + "des":"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 v", "doc_type":"usermanual", "kw":"What Is CBR?,Service Overview,User Guide", "title":"What Is CBR?", @@ -23,7 +23,7 @@ "uri":"cbr_01_0005.html", "product_code":"cbr", "code":"3", - "des":"CBR backs up resources to maximize user data security and consistency and ensure service continuity. CBR is suitable for data backup and restoration.CBR can be used to qu", + "des":"CBR is ideal for data backup and restoration. The backups can maximize your data security and consistency.You can use CBR to quickly restore data to the latest backup poi", "doc_type":"usermanual", "kw":"Application Scenarios,Service Overview,User Guide", "title":"Application Scenarios", @@ -33,7 +33,7 @@ "uri":"cbr_01_0003.html", "product_code":"cbr", "code":"4", - "des":"Table 1 lists the basic functions of CBR.Before using this service, it is recommended that you go to basic concepts to learn more about CBR, such as about vault and backu", + "des":"Table 1 lists the functions of CBR.Before using CBR functions, it is recommended that you learn about basic CBR concepts.", "doc_type":"usermanual", "kw":"Functions,Service Overview,User Guide", "title":"Functions", @@ -63,7 +63,7 @@ "uri":"cbr_01_0009.html", "product_code":"cbr", "code":"7", - "des":"A vault can be associated with only one backup policy.A vault can be associated with a maximum of 256 resources.A maximum of 32 backup policies can be created.Only the ba", + "des":"A vault can be associated with only one backup policy.A vault can be associated with a maximum of 256 resources.A maximum of 32 backup policies can be created.Only backup", "doc_type":"usermanual", "kw":"Constraints,Service Overview,User Guide", "title":"Constraints", @@ -93,7 +93,7 @@ "uri":"cbr_01_0012.html", "product_code":"cbr", "code":"10", - "des":"CBR uses vaults to store backups of resources. Backup vaults are classified into the following types:Server backup vaults: store backups of only common servers. You can a", + "des":"CBR stores backups of a variety of resources in vaults, which are classified into the following types:Server backup vaults: store only backups of non-database servers. Yo", "doc_type":"usermanual", "kw":"CBR Concepts,Basic Concepts,User Guide", "title":"CBR Concepts", @@ -183,7 +183,7 @@ "uri":"cbr_02_0006.html", "product_code":"cbr", "code":"19", - "des":"This section describes how to quickly create a cloud server backup.If you do not need an ECS for the moment, you can back up the ECS and then delete it. Then, create an i", + "des":"This section describes how to quickly create a cloud server backup.If you do not need an ECS for the moment, you can back up the ECS and then delete it. When you want an ", "doc_type":"usermanual", "kw":"Creating a Cloud Server Backup,Step 3: Create a Backup,User Guide", "title":"Creating a Cloud Server Backup", @@ -193,7 +193,7 @@ "uri":"cbr_02_0007.html", "product_code":"cbr", "code":"20", - "des":"This section describes how to quickly create a cloud disk backup.During the cloud disk backup, the performance of the disk is not affected. To ensure data integrity, back", + "des":"This section describes how to quickly create a cloud disk backup.Backing up a disk does not impact the disk performance. To ensure data integrity, you are advised to back", "doc_type":"usermanual", "kw":"Creating a Cloud Disk Backup,Step 3: Create a Backup,User Guide", "title":"Creating a Cloud Disk Backup", @@ -203,7 +203,7 @@ "uri":"cbr_02_0012.html", "product_code":"cbr", "code":"21", - "des":"This section describes how to quickly create an SFS Turbo file system backup.During the SFS Turbo file system backup, the performance of the file system is not affected. ", + "des":"This section describes how to quickly create an SFS Turbo file system backup.Backing up an SFS Turbo file system does not impact the file system performance. To ensure da", "doc_type":"usermanual", "kw":"Creating an SFS Turbo Backup,Step 3: Create a Backup,User Guide", "title":"Creating an SFS Turbo Backup", diff --git a/docs/cbr/umn/CLASS.TXT.json b/docs/cbr/umn/CLASS.TXT.json index b5538c4d6..7c9ade89e 100644 --- a/docs/cbr/umn/CLASS.TXT.json +++ b/docs/cbr/umn/CLASS.TXT.json @@ -9,7 +9,7 @@ "code":"1" }, { - "desc":"Cloud Backup and Recovery (CBR) enables you to back up Elastic Cloud Servers (ECSs), Elastic Volume Service (EVS) disks, and SFS Turbo file systems with ease. In case of ", + "desc":"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 v", "product_code":"cbr", "title":"What Is CBR?", "uri":"cbr_01_0002.html", @@ -18,7 +18,7 @@ "code":"2" }, { - "desc":"CBR backs up resources to maximize user data security and consistency and ensure service continuity. CBR is suitable for data backup and restoration.CBR can be used to qu", + "desc":"CBR is ideal for data backup and restoration. The backups can maximize your data security and consistency.You can use CBR to quickly restore data to the latest backup poi", "product_code":"cbr", "title":"Application Scenarios", "uri":"cbr_01_0005.html", @@ -27,7 +27,7 @@ "code":"3" }, { - "desc":"Table 1 lists the basic functions of CBR.Before using this service, it is recommended that you go to basic concepts to learn more about CBR, such as about vault and backu", + "desc":"Table 1 lists the functions of CBR.Before using CBR functions, it is recommended that you learn about basic CBR concepts.", "product_code":"cbr", "title":"Functions", "uri":"cbr_01_0003.html", @@ -54,7 +54,7 @@ "code":"6" }, { - "desc":"A vault can be associated with only one backup policy.A vault can be associated with a maximum of 256 resources.A maximum of 32 backup policies can be created.Only the ba", + "desc":"A vault can be associated with only one backup policy.A vault can be associated with a maximum of 256 resources.A maximum of 32 backup policies can be created.Only backup", "product_code":"cbr", "title":"Constraints", "uri":"cbr_01_0009.html", @@ -81,7 +81,7 @@ "code":"9" }, { - "desc":"CBR uses vaults to store backups of resources. Backup vaults are classified into the following types:Server backup vaults: store backups of only common servers. You can a", + "desc":"CBR stores backups of a variety of resources in vaults, which are classified into the following types:Server backup vaults: store only backups of non-database servers. Yo", "product_code":"cbr", "title":"CBR Concepts", "uri":"cbr_01_0012.html", @@ -162,7 +162,7 @@ "code":"18" }, { - "desc":"This section describes how to quickly create a cloud server backup.If you do not need an ECS for the moment, you can back up the ECS and then delete it. Then, create an i", + "desc":"This section describes how to quickly create a cloud server backup.If you do not need an ECS for the moment, you can back up the ECS and then delete it. When you want an ", "product_code":"cbr", "title":"Creating a Cloud Server Backup", "uri":"cbr_02_0006.html", @@ -171,7 +171,7 @@ "code":"19" }, { - "desc":"This section describes how to quickly create a cloud disk backup.During the cloud disk backup, the performance of the disk is not affected. To ensure data integrity, back", + "desc":"This section describes how to quickly create a cloud disk backup.Backing up a disk does not impact the disk performance. To ensure data integrity, you are advised to back", "product_code":"cbr", "title":"Creating a Cloud Disk Backup", "uri":"cbr_02_0007.html", @@ -180,7 +180,7 @@ "code":"20" }, { - "desc":"This section describes how to quickly create an SFS Turbo file system backup.During the SFS Turbo file system backup, the performance of the file system is not affected. ", + "desc":"This section describes how to quickly create an SFS Turbo file system backup.Backing up an SFS Turbo file system does not impact the file system performance. To ensure da", "product_code":"cbr", "title":"Creating an SFS Turbo Backup", "uri":"cbr_02_0012.html", diff --git a/docs/cbr/umn/cbr_01_0002.html b/docs/cbr/umn/cbr_01_0002.html index 96378c2ca..5af06e3b0 100644 --- a/docs/cbr/umn/cbr_01_0002.html +++ b/docs/cbr/umn/cbr_01_0002.html @@ -1,20 +1,19 @@

What Is CBR?

-

Overview

Cloud Backup and Recovery (CBR) enables you to back up Elastic Cloud Servers (ECSs), Elastic Volume Service (EVS) disks, and SFS Turbo file systems with ease. In case of a virus attack, accidental deletion, or software or hardware fault, you can restore data to any point in the past when the data was backed up.

+

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.

-

Product Architecture

CBR consists of backups, vaults, and policies.

+

CBR Architecture

CBR involves backups, vaults, and policies.

Backup

-

A backup is a copy of a particular chunk of data and is usually stored elsewhere so that it may be used to restore the original data in the event of data loss. The following are the types of CBR backups:

-
  • Cloud disk backup. This type of backup provides snapshot-based data protection for EVS disks.
  • Cloud server backup. This type of backup uses the consistency snapshot technology for disks to protect data of ECSs.
  • SFS Turbo backup. This type of backup protects data of SFS Turbo file systems.
+

A backup is a copy of a particular chunk of data and is usually stored elsewhere so that it may be used to restore the original data in the event of data loss. There are the following types of backups:

+
  • Cloud disk backup: provides snapshot-based backups for EVS disks.
  • Cloud server backup: uses the consistency snapshot technology to protect data for ECSs.
  • SFS Turbo backup: backs up data of SFS Turbo file systems.

Vault

-

CBR uses vaults to store backups. Before creating a backup, you need to create at least one vault and associate the resource you want to back up with the vault. Then the generated resource backups are stored in the associated vault.

-

The backups of different types of resources must be stored in different types of vaults.

+

CBR stores backups in vaults. Before creating a backup, you need to create at least one vault and associate the resources you want to back up with the vaults. Then the resources can be backed up to the associated vaults.

+

Different types of resources must be backed up to different types of vaults. For example, cloud servers must be backed up to server backup vaults, not disk backup vaults or any other types of vaults.

Policy

-
  • Backup policies: To perform automatic backups, configure a backup policy by setting the execution times of backup tasks, the backup frequency, and retention rules, and then apply the policy to a vault.
-
Figure 1 Architecture of CBR
-

+
  • A backup policy defines when you want to take a backup and for how long you would retain each backup.
+
Figure 1 CBR architecture

@@ -25,53 +24,54 @@

Differences Among the Backup Types

-
Table 1 Differences among the backup types

Item

+
- - - - - - - - - - - - - - -
Table 1 Differences among the backup types

Item

Cloud Server Backup

+

Cloud Server Backup

Cloud Disk Backup

+

Cloud Disk Backup

SFS Turbo Backup

+

SFS Turbo Backup

Backup and restore object

+

What to back up

All disks (system and data disks) on a server

+

All disks (system and data disks) on a server

One or more specific disks (system or data disks)

+

One or more specific disks (system or data disks)

SFS Turbo file systems

+

SFS Turbo file systems

Recommended scenario

+

When to use

An entire cloud server needs to be protected.

+

You want to back up entire cloud servers.

Only data disks need to be backed up, because the system disk does not contain users' application data.

+

You want to back up only data disks.

Data in the SFS Turbo file systems needs to be protected.

+

You want to back up entire SFS Turbo file systems.

Advantages

+

Advantages

All disks on a server are backed up at the same time, ensuring data consistency.

+

All disks on a server are backed up at a time.

Backup cost is reduced without compromising data security.

+

Only data of specific disks is backed up, which costs less than backing up an entire server.

Backup data and original file systems are stored separately. You can use the backup data to create a new file system.

+

File system data and their backups are stored separately, and the backups can be used to create new file systems.
-

Backup Mechanism

CBR in-cloud backups offer block-level backup. A full backup is performed only for the first backup and backs up all used data blocks. For example, if the size of a disk is 100 GB and the used space is 40 GB, the 40 GB of data is backed up. An incremental backup backs up only the data changed since the last backup, which is storage- and time-efficient. When a backup is deleted, only the data blocks that are not depended on by other backups are deleted, so that other backups can still be used for restoration. Both a full backup and an incremental backup can restore data to the state at a given backup point in time.

-

When creating a backup of a disk, CBR also creates a snapshot for it. Every time a new disk backup is created, CBR deletes the old snapshot and keeps only the latest snapshot.

-

CBR stores backup data in OBS to enhance backup data security.

+

Backup Mechanism

CBR in-cloud backup offers block-level backup. The first backup is a full backup and backs up all used data blocks. For example, if a disk size is 100 GB and 40 GB has been used, only the 40 GB of data is backed up. An incremental backup backs up only the data changed since the last backup to save the storage space and backup time.

+

A backup will not be deleted if it is depended on by other backups, ensuring that other backups can still be used for restoration. Both a full backup and an incremental backup can be used to restore data to a given backup point in time.

+

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 task is manually created by users and is executed only once. Periodic backup tasks are automatically executed based on a user-defined backup policy.

-

Table 2 describes the two backup options.

+

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.

+

Table 2 compares the two backup options.

@@ -92,7 +92,7 @@ - - - - -
Table 2 One-off backup and periodic backup

Item

One manual backup task

Periodic tasks driven by a backup policy

+

Periodic tasks triggered by a preset backup policy

Backup name

@@ -104,26 +104,26 @@

Backup mode

Full backup for the first time and incremental backup subsequently, by default

+

The first backup is a full backup and the consecutive backups are incremental.

Full backup for the first time and incremental backup subsequently, by default

+

The first backup is a full backup and the consecutive backups are incremental.

Application scenario

Executed before patching or upgrading the OS or upgrading an application on a resource. A one-off backup can be used to restore the resource to the original state if the patching or upgrading fails.

+

Executed before patching or upgrading the OS or upgrading an application. A one-off backup can be used for restoration if the patching or upgrading fails.

Executed for routine maintenance of a resource. The latest backup can be used for restoration if an unexpected failure or data loss occurs.

+

Executed for routine maintenance. The latest backup can be used for restoration if an unexpected failure or data loss occurs.
-

You can also use the two backup options together if needed. For example, you can associate resources with a vault and apply a backup policy to the vault to execute periodic backup for all the resources in the vault. Additionally, you can perform backup for the most important resources on demand to enhance data security. Figure 2 shows the intermixed use of the two backup options.

-
Figure 2 Intermixed use of the two backup options
+

You can also use the two backup options together if needed. For example, you can associate resources with a vault and apply a backup policy to the vault to execute periodic backup for all the resources in the vault. Additionally, you can perform a one-off backup for the most important resources to enhance data security. Figure 2 shows the use of the two backup options.

+
Figure 2 Use of the two backup options
-

Method of Access

You can access the CBR service through the console or by calling HTTPS-based APIs.

-
  • Console

    Use the console if you prefer a web-based UI to perform operations. Log in to the console and choose Cloud Backup and Recovery.

    +

    Access to CBR

    You can access the CBR service through the console or by calling HTTPS-based APIs.

    +
    • Console

      Use the console if you prefer a web-based UI. Log in to the console and choose Cloud Backup and Recovery.

    • APIs

      Use APIs if you need to integrate CBR into a third-party system for secondary development. For details, see the Cloud Backup and Recovery API Reference.

    diff --git a/docs/cbr/umn/cbr_01_0003.html b/docs/cbr/umn/cbr_01_0003.html index d168fc108..242e67e59 100644 --- a/docs/cbr/umn/cbr_01_0003.html +++ b/docs/cbr/umn/cbr_01_0003.html @@ -1,10 +1,10 @@

    Functions

    -

    Table 1 lists the basic functions of CBR.

    -

    Before using this service, it is recommended that you go to basic concepts to learn more about CBR, such as about vault and backup policy.

    +

    Table 1 lists the functions of CBR.

    +

    Before using CBR functions, it is recommended that you learn about basic CBR concepts.

    -
    - @@ -53,9 +53,9 @@
    Table 1 CBR basic functions

    Category

    +
    @@ -14,101 +14,101 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/cbr/umn/cbr_01_0005.html b/docs/cbr/umn/cbr_01_0005.html index b490b40a1..953c3847f 100644 --- a/docs/cbr/umn/cbr_01_0005.html +++ b/docs/cbr/umn/cbr_01_0005.html @@ -1,10 +1,9 @@

    Application Scenarios

    -

    CBR backs up resources to maximize user data security and consistency and ensure service continuity. CBR is suitable for data backup and restoration.

    -

    Data Backup and Restoration

    CBR can be used to quickly restore data in the following scenarios:

    -
    • Hacker or virus attacks
    • Accidental deletion
    • Application update errors
    • System breakdown

      For any of the incidents above, you can use CBR to restore data to the latest backup point prior to the incident.

      -
    +

    CBR is ideal for data backup and restoration. The backups can maximize your data security and consistency.

    +

    Data Backup and Restoration

    You can use CBR to quickly restore data to the latest backup point if any of the following incidents occur:

    +
    • Hacker or virus attacks
    • Accidental deletion
    • Application update errors
    • System breakdown

    diff --git a/docs/cbr/umn/cbr_01_0006.html b/docs/cbr/umn/cbr_01_0006.html index 994274ff1..bedb2f6c7 100644 --- a/docs/cbr/umn/cbr_01_0006.html +++ b/docs/cbr/umn/cbr_01_0006.html @@ -10,7 +10,7 @@ -
    @@ -18,21 +18,21 @@

    Creating a Cloud Disk Backup

    - - - @@ -46,14 +46,14 @@ - - diff --git a/docs/cbr/umn/cbr_01_0008.html b/docs/cbr/umn/cbr_01_0008.html index 7eadc3000..fe093d3e3 100644 --- a/docs/cbr/umn/cbr_01_0008.html +++ b/docs/cbr/umn/cbr_01_0008.html @@ -11,7 +11,7 @@

    Selecting an AZ

    When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.

    • For high DR capability, deploy resources in different AZs within the same region.
    • For lower network latency, deploy resources in the same AZ.
    -

    Regions and Endpoints

    Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.

    +

    Regions and Endpoints

    Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.

    diff --git a/docs/cbr/umn/cbr_01_0009.html b/docs/cbr/umn/cbr_01_0009.html index d1ad0d992..633c6dcfc 100644 --- a/docs/cbr/umn/cbr_01_0009.html +++ b/docs/cbr/umn/cbr_01_0009.html @@ -1,11 +1,11 @@

    Constraints

    -

    General

    • A vault can be associated with only one backup policy.
    • A vault can be associated with a maximum of 256 resources.
    • A maximum of 32 backup policies can be created.
    • Only the backups in a vault whose status is Available or Locked can be used for data restoration.
    • Backups in a vault whose status is Deleting cannot be deleted.
    • When Storage Disaster Recovery Service (SDRS) is used to set up disaster recovery for cloud servers, restorations can be performed at the disaster recovery site only after protection is disabled.
    • Backups cannot be downloaded to a local PC or uploaded to OBS.
    • A vault and its associated servers or disks must be in the same region.
    +

    General

    • A vault can be associated with only one backup policy.
    • A vault can be associated with a maximum of 256 resources.
    • A maximum of 32 backup policies can be created.
    • Only backups in the Available or Locked vaults can be used to restore data.
    • Backups in a Deleting vault cannot be deleted.
    • When Storage Disaster Recovery Service (SDRS) is used to set up disaster recovery for cloud servers, restorations can be performed at the disaster recovery site only after protection is disabled.
    • Backups cannot be downloaded to a local PC or uploaded to OBS.
    • A vault and its associated servers or disks must be in the same region.

    Cloud Disk Backup

    • Only disks in the Available or In-use state can be backed up.
    • A new disk must be at least as large as the backup's source disk.
    -

    Cloud Server Backup

    • Shared disks on a server can be backed up, but there can be no more than 10 shared disks.
    • Only backups in a vault whose status is Available or Locked can be used to create images.
    • You can choose to back up only specified disks on a server, but such a backup of disks must be restored as a whole. File- or directory-level restoration is not supported.
    • When SDRS is used to set up disaster recovery for cloud servers, restorations can be performed at the disaster recovery site only after protection is disabled.
    • You are advised not to back up a server whose disk size exceeds 4 TB.
    +

    Cloud Server Backup

    • A maximum of 10 shared disks can be backed up with a cloud server.
    • Only backups in the Available or Locked vaults can be used to create images.
    • You can back up specific disks on a server, but such a backup must be restored as a whole. File- or directory-level restoration is not supported.
    • When SDRS is used to set up disaster recovery for cloud servers, restorations can be performed at the disaster recovery site only after protection is disabled.
    • You are advised not to back up a server whose disk size exceeds 4 TB.

    SFS Turbo Backup

    • Only file systems in the Available state can be backed up.
    • An SFS Turbo file system backup cannot be used to restore data to the original file system.
    diff --git a/docs/cbr/umn/cbr_01_0012.html b/docs/cbr/umn/cbr_01_0012.html index 968b76b5b..1c3b5989b 100644 --- a/docs/cbr/umn/cbr_01_0012.html +++ b/docs/cbr/umn/cbr_01_0012.html @@ -1,21 +1,21 @@

    CBR Concepts

    -

    Vault

    CBR uses vaults to store backups of resources. Backup vaults are classified into the following types:

    -
    • Server backup vaults: store backups of only common servers. You can associate servers with a server backup vault and apply a backup policy to the vault.
    • Disk backup vaults: store only disk backups. You can associate disks with a disk backup vault and apply a backup policy to the vault.
    • SFS Turbo backup vaults: store only backups of SFS Turbo file systems. You can associate file systems with an SFS Turbo backup vault and apply a backup policy to the vault.
    +

    Vault

    CBR stores backups of a variety of resources in vaults, which are classified into the following types:

    +
    • Server backup vaults: store only backups of non-database servers. You can associate servers with a server backup vault and apply a backup policy to schedule automatic backups.
    • Disk backup vaults: store only disk backups. You can associate disks with a disk backup vault and apply a backup policy to schedule automatic backups.
    • SFS Turbo backup vaults: store only backups of SFS Turbo file systems. You can associate file systems with an SFS Turbo backup vault and apply a backup policy to schedule automatic backups.
    -

    Backup

    A backup is a copy of a particular chunk of data and is usually stored elsewhere so that it may be used to restore the original data in the event of data loss. It can be generated either manually by a one-off backup task or automatically by a periodic task.

    -

    CBR supports one-off backup and periodic backup. A one-off backup task is manually created by users and is executed only once. Periodic backup tasks are automatically executed based on a user-defined backup policy.

    -
    • The name of a one-off backup is manualbk_xxxx. It can be user- or system-defined.
    • The name of a periodic backup is autobk_xxxx, which is assigned automatically by the system.
    +

    Backup

    A backup is a copy of a particular chunk of data and is usually stored elsewhere so that it may be used to restore the original data in the event of data loss. It can be generated either manually by a one-off backup task or automatically by a periodic backup task.

    +

    A one-off backup task is manually created and is executed only once. Periodic backup tasks are automatically executed based on a user-defined backup policy.

    +
    • A one-off backup is named manualbk_xxxx and can be user- or system-defined.
    • A periodic backup is named autobk_xxxx by CBR.
    -

    Backup Policy

    A backup policy is a set of rules for backing up data, including the policy name, policy status, execution time of backup tasks, backup frequency, and retention rule. A retention rule specifies for how long backups are retained or the number of backups that are retained. Automatic backups can be performed by applying a backup policy to a backup vault.

    +

    Backup Policy

    A backup policy is a set of rules that define the schedule and retention of backups. After you apply a backup policy to a vault, CBR automatically backs up data and retains backups based on that backup policy.

    -

    Instant Restore

    Instant Restore is a function for restoring data and creating images from backups. Instant Restore is much faster than a normal restoration process.

    -

    Common backups do not support Instant Restore, whereas enhanced backups do. By default, all CBR backups are enhanced backups. Compared with common backups, enhanced backups use less time to restore server data or create images.

    +

    Instant Restore

    Instant Restore restores data and creates images from backups, much faster than a normal restore.

    +

    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 can be used to quickly restore server data or create images. This type of backups depends on Instant Restore.

    -

    Before Instant Restore is rolled out, all CBR backups generated are common backups. After Instant Restore is rolled out, all CBR backups generated are enhanced backups. This is an overall performance upgrade of CBR, and no additional configuration is required. Currently, all CBR backups generated are enhanced backups.

    -

    It takes a longer time to restore server data or create images using common backups. Enhanced backups can do the same thing with significantly shortened time. The only difference between common backups and enhanced backups is the restoration speed.

    +

    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.

    diff --git a/docs/cbr/umn/cbr_02_0003.html b/docs/cbr/umn/cbr_02_0003.html index 238ca4d3a..d8a76f4c6 100644 --- a/docs/cbr/umn/cbr_02_0003.html +++ b/docs/cbr/umn/cbr_02_0003.html @@ -2,11 +2,11 @@

    Creating a Server Backup Vault

    This section describes how to create a server backup vault.

    -

    Procedure

    1. Log in to CBR Console.

      1. Log in to the management console.
      2. Click in the upper left corner and select your region and project.
      3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
      -

    2. In the upper right corner of the page, click Create Server Backup Vault.
    3. Select a protection type.

      • Backup: The created vault is a server backup vault, which stores cloud server backups.
      -

    4. (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 may also select only some of the disks of a server and associate them with the vault.

      To ensure post-restoration data consistency, you are advised to back up the entire server.

      +

      Procedure

      1. Log in to CBR Console.

        1. Log in to the management console.
        2. Click in the upper left corner and select your region and project.
        3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
        +

      2. In the upper right corner of the page, click Create Server Backup Vault.
      3. Select a protection type.

        • Backup: A server backup vault stores server backups.
        +

      4. (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.

        -

        For example, the data of an Oracle database is scattered across different disks. If only some of the disks are backed up, restoration restores only the data of the disks that have been backed up, with the rest of the data unchanged. As a result, the data may be inconsistent and applications may fail to start.

        +

        For example, the data of an Oracle database is scattered across different disks. If only some of the disks are backed up, restoration restores only the data of the disks that have been backed up, with data on the rest of the disks unchanged. As a result, the data may be inconsistent and the Oracle database may fail to start.

        Figure 1 Selecting servers

        @@ -14,18 +14,18 @@

        -
        • The selected servers must have not been associated with another vault and must be in the Running or Stopped state.
        • You can associate servers with the vault you are creating if you skip this step.
        +
        • The selected servers must have not been associated with any vault and must be in the Running or Stopped state.
        • You can also associate servers with the vault you are creating later if you skip this step.
        -

      5. Specify the vault capacity, which ranges from 10 GB to 10,485,760 GB. You need to properly plan the vault capacity, which must be at least the same as the size of the servers you want to back up. Also, if a backup policy is applied to the vault, more capacity is required.

        As the vault's used space grows, you can expand the vault capacity if it becomes insufficient. See Figure 2.
        Figure 2 Setting the vault capacity
        +

      6. Specify a vault capacity ranging from 10 GB to 10,485,760 GB. Properly plan the vault capacity, which must be at least the same as the size of the servers you want to back up. Also, if a backup policy is applied to the vault, more capacity is required.

        As the vault's used space grows, you can expand the vault capacity if it becomes insufficient. See Figure 2.
        Figure 2 Setting the vault capacity

        -

      7. Determine whether to configure auto backup. See Figure 3.

        • If you select Configure, you must then select an existing backup policy or create a new policy. After the vault is created, the system will apply the policy to this vault, and all servers associated with this vault will be automatically backed up based on this policy.
        • If you select Skip, servers associated with this vault will not be automatically backed up until you apply a backup policy to it.
        -
        Figure 3 Configuring automatic backup
        +

      8. Configure auto backup. See Figure 3.

        • If you select Configure, you must then select an existing backup policy or create a new policy. After the vault is created, CBR will apply the policy to this vault, and all servers associated with this vault will be automatically backed up based on this policy.
        • If you select Skip, servers associated with this vault will not be automatically backed up until you apply a backup policy to the vault.
        +
        Figure 3 Configuring auto backup

        -

      9. (Optional) Configure automatic resource association.

        • If you select Configure, in the next backup period, unprotected resources will be automatically scanned and associated with the vault, and backups will be automatically executed.
        • If you select Skip, resources will not be automatically associated with the vault you are creating.
        -

        You can filter unprotected resources by tag. If a tag is selected, only unprotected resources having the specified tag will be associated with the vault. Or, all unprotected resources will be associated.

        -

        Only existing tags can be selected. If no tag is available, create tags on the corresponding resource page. You can select a maximum of 5 tags to search for vaults. If you select more than one tag, the vaults containing any of the specified tags will be returned.

        -

      10. (Optional) Add tags to the vault.

        A tag is represented in the form of a key-value pair. Tags are used to identify, classify, and search for vaults. Vault tags are used to filter and manage vaults only. A vault can have a maximum of 10 tags. See Figure 4.

        +

      11. (Optional) Configure automatic resource association.

        • If you select Configure, in the next backup period, CBR will automatically scan all unprotected resources, associate them with the vault, and then perform backups.
        • If you select Skip, CBR will not scan and associate unprotected resources with the vault you are creating.
        +

        You can filter unprotected resources by tag. If a tag is selected, only unprotected resources with the specified tag will be associated with the vault. Or, all unprotected resources will be associated.

        +

        If no tag is available, you can create tags on the corresponding resource page. You can search for vaults by specifying a maximum of 5 tags at a time. If you select more than one tag, the vaults with any of the specified tags will be returned.

        +

      12. (Optional) Add tags to the vault.

        Tags are key-value pairs, which are used to identify, classify, and search for vaults. You can add a maximum of 10 tags for a vault, and vault tags are only used for vault search and management. See Figure 4.

        Figure 4 Adding a tag

        Table 1 describes the parameters of a tag. @@ -39,7 +39,7 @@
    - @@ -59,8 +59,8 @@
    Table 1 CBR functions

    Category

    Function

    Cloud disk backup

    Backing up disks

    +

    Manual disk backup

    Cloud disk backup provides snapshot-based data protection for EVS disks. You can use CBR to back up a single disk on a server to protect the data on that disk.

    +

    Cloud disk backup provides snapshot-based backup for EVS disks on servers. You can back up specific disks to protect data on them.
      

    Policy-driven data backup

    +

    Policy-based backup

    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.

    +

    You can create, modify, or delete a backup policy. A backup policy defines the schedule and retention for automatic backups.
      

    Backup management

    When a backup task is running or completed, you can set search criteria to filter backups from the backup list to manage them and view their details.

    +

    You can set search criteria to quickly find the backups you want to manage. Then you can view their details, share, restore, or delete them if needed.
      

    Restoring disk data using backups

    +

    Disk restoration using backups

    When a disk is faulty, or disk data is lost due to misoperations, you can use a backup to restore the disk.

    +

    When a disk is faulty, or their data is lost, you can use a backup to quickly restore the data.
      

    Creating disks using backups

    +

    Disk creation using backups

    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.

    +

    You can use a disk backup to create a disk that contains the same data as the backup.
      

    Sharing a Backup

    You can share a server or disk backup with other accounts. Shared backups can be used to create disks or servers.

    +

    You can share a disk backup with other accounts to allow them to use the backup to create disks.

    Cloud server backup

    Backing up servers

    +

    Manual server backup

    Cloud server backup uses the consistency snapshot technology for disks to protect data of ECSs. You can use CBR to back up an entire server to protect the data on the server.

    +

    Cloud server backup uses the consistency snapshot technology to protect data of ECSs. You can use CBR to back up an entire server to protect their data.
      

    Policy-driven data backup

    +

    Policy-based backup

    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.

    +

    You can create, modify, or delete a backup policy. A backup policy defines the schedule and retention for automatic backups.
      

    Backup management

    When a backup task is running or completed, you can set search criteria to filter backups from the backup list to manage them and view their details.

    +

    You can set search criteria to quickly find the backups you want to manage. Then you can view their details, share, restore, replicate, or delete them if needed.
      

    Restoring server data using backups

    +

    Server restoration using backups

    When a server is faulty, or server data is lost due to misoperations, you can use a backup to restore the server.

    +

    When a server is faulty, or their data is lost, you can use a backup to quickly restore the data.
      

    Sharing a Backup

    You can share a server or disk backup with other accounts. Shared backups can be used to create disks or servers.

    +

    You can share a server backup with other accounts to allow them to use the backup to create servers.
      

    Creating images using backups

    +

    Image creation using server backups

    Cloud server backup allows you to create images using ECS backups. You can use the images to provision ECSs to rapidly restore service running environments.

    +

    You can create images from ECS backups and then use the images to quickly provision ECSs to restore service.

    SFS Turbo backup

    Backing up SFS Turbo file systems

    +

    Manual SFS Turbo file system backup

    SFS Turbo backup allows you to back up SFS Turbo file systems. An SFS Turbo file system backup can be used to create a new SFS Turbo file system, preventing the loss of important data.

    +

    You can back up SFS Turbo file systems and use the backups create new SFS Turbo file system.
      

    Policy-driven data backup

    +

    Policy-based backup

    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.

    +

    You can create, modify, or delete a backup policy. A backup policy defines the schedule and retention for automatic backups.
      

    Backup management

    When a backup task is running or completed, you can set search criteria to filter backups from the backup list to manage them and view their details.

    +

    You can set search criteria to quickly find the backups you want to manage. Then you can view their details, share, restore, replicate, or delete them if needed.
      

    Using a Backup to Create a File System

    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.

    +

    You can use an SFS Turbo file system backup to create a file system that contains the same data as the backup.

    CBR backs up data of disks on an ECS, and restores backup data to disks of an ECS to restore lost or corrupted data. Generated backups can be used to create images to rapidly restore service running environments.

    +

    CBR backs up data of an ECS and uses the backup to restore data for the ECS. You can also create images from ECS backups and use the images to quickly provision ECSs to restore services.

    ECS

    CBR backs up data of SFS Turbo file systems. You can use backup data to create new file systems to restore lost or corrupted data.

    +

    CBR backs up data of SFS Turbo file systems and uses the backup to create new file systems to restore lost or corrupted data.

    SFS

    Creating an SFS Turbo Backup

    CBR stores backup data in OBS to enhance backup data security.

    +

    CBR stores backups securely in OBS.

    OBS

    What Is CBR?

    CBR backs up data on disks. You can use backup data to create new disks.

    +

    CBR backs up data of EVS disks and uses the backup to create new disks.

    EVS

    Auditing

    IAM is a self-service system for enterprises to manage cloud resources. It provides user identity management and access control functions.

    +

    IAM is a self-service system for enterprise administrators to manage cloud resources. It provides user identity management and access control functions.

    IAM

    User Permissions

    Tag Management Service (TMS) enables you to add preset tags to CBR vaults to facilitate filtering and management.

    +

    Tag Management Service (TMS) enables you to add preset tags to CBR vaults to facilitate vault management.

    TMS

    Key

    Each tag has a unique key. You can customize the key or select the key of an existing tag created in TMS.

    +

    Each tag has a unique key. You can customize a key or select the key of an existing tag created in TMS.

    A tag key:

    • Can contain 1 to 36 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    -

  • Specify a name for the vault.

    A name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-), for example, vault-f61e.

    -

    You can use the default name, which is in the format of vault_xxxx.

    +

  • Specify a name for the vault.

    The name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-), for example, vault-f61e.

    +

    You can also use the default name vault_xxxx.

  • Complete the creation as prompted.
  • Go back to the Cloud Server Backups page. You can see the created vault in the vault list.

    You can associate servers with the vault and perform backup for the servers. For details, see Querying a Vault.

    • diff --git a/docs/cbr/umn/cbr_02_0004.html b/docs/cbr/umn/cbr_02_0004.html index 6ea6651cc..3cb5b9c07 100644 --- a/docs/cbr/umn/cbr_02_0004.html +++ b/docs/cbr/umn/cbr_02_0004.html @@ -2,24 +2,24 @@

    Creating a Disk Backup Vault

    This section describes how to create a disk backup vault.

    -

    Procedure

    1. Log in to CBR Console.

      1. Log in to the management console.
      2. Click in the upper left corner and select your region and project.
      3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
      +

      Procedure

      1. Log in to CBR Console.

        1. Log in to the management console.
        2. Click in the upper left corner and select your region and project.
        3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

      2. In the upper right corner of the page, click Create Disk Backup Vault.
      3. (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.

        Figure 1 Selecting disks

        -
        • The selected disks must have not been associated with a vault and must be in the Available or In-use state.
        • You can associate disks with the vault you are creating if you skip this step.
        +
        • The selected disks must have not been associated with any vault and must be in the Available or In-use state.
        • You can also associate disks with the vault you are creating later if you skip this step.
        -

      4. Specify the vault capacity. This capacity indicates the total size of the disks that you want to associate with this vault. You need to properly plan the vault capacity, which must be at least the same as the size of the disks you want to back up. The capacity ranges from 10 GB to 10485760 GB. See Figure 2.

        Figure 2 Setting the vault capacity
        +

      5. Specify a vault capacity ranging from 10 GB to 10,485,760 GB. Properly plan the vault capacity, which must be at least the same as the size of the disks you want to back up. See Figure 2.

        Figure 2 Setting the vault capacity

        -

      6. Determine whether to configure auto backup. See Figure 3.

        • If you select Configure, you must then select an existing backup policy or create a new policy. After the vault is created, the system will apply the policy to this vault, and all disks associated with this vault will be automatically backed up based on this policy.
        • If you select Skip, disks associated with this vault will not be automatically backed up until you apply a backup policy to it.
        -
        Figure 3 Configuring automatic backup
        +

      7. Configure auto backup. See Figure 3.

        • If you select Configure, you must then select an existing backup policy or create a new policy. After the vault is created, CBR will apply the policy to this vault, and all disks associated with this vault will be automatically backed up based on this policy.
        • If you select Skip, disks associated with this vault will not be automatically backed up until you apply a backup policy to the vault.
        +
        Figure 3 Configuring auto backup

        -

      8. (Optional) Configure automatic resource association.

        • If you select Configure, in the next backup period, unprotected resources will be automatically scanned and associated with the vault, and backups will be automatically executed.
        • If you select Skip, resources will not be automatically associated with the vault you are creating.
        -

        You can filter unprotected resources by tag. If a tag is selected, only unprotected resources having the specified tag will be associated with the vault. Or, all unprotected resources will be associated.

        -

        Only existing tags can be selected. If no tag is available, create tags on the corresponding resource page. You can select a maximum of 5 tags to search for vaults. If you select more than one tag, the vaults containing any of the specified tags will be returned.

        -

      9. (Optional) Add tags to the vault.

        A tag is represented in the form of a key-value pair. Tags are used to identify, classify, and search for vaults. Vault tags are used to filter and manage vaults only. A vault can have a maximum of 10 tags. See Figure 4.

        +

      10. (Optional) Configure automatic resource association.

        • If you select Configure, in the next backup period, CBR will automatically scan all unprotected resources, associate them with the vault, and then perform backups.
        • If you select Skip, CBR will not scan and associate unprotected resources with the vault you are creating.
        +

        You can filter unprotected resources by tag. If a tag is selected, only unprotected resources with the specified tag will be associated with the vault. Or, all unprotected resources will be associated.

        +

        If no tag is available, you can create tags on the corresponding resource page. You can search for vaults by specifying a maximum of 5 tags at a time. If you select more than one tag, the vaults with any of the specified tags will be returned.

        +

      11. (Optional) Add tags to the vault.

        Tags are key-value pairs, which are used to identify, classify, and search for vaults. You can add a maximum of 10 tags for a vault, and vault tags are only used for vault search and management. See Figure 4.

        Figure 4 Adding a tag

        Table 1 describes the parameters of a tag. @@ -33,7 +33,7 @@

    Key

    Each tag has a unique key. You can customize the key or select the key of an existing tag created in TMS.

    +

    Each tag has a unique key. You can customize a key or select the key of an existing tag created in TMS.

    A tag key:

    • Can contain 1 to 36 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    -

  • Specify a name for the vault.

    A name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-), for example, vault-612c. See Figure 5.

    +

  • Specify a name for the vault.

    The name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-), for example, vault-612c. See Figure 5.

    Figure 5 Setting the vault name
    -

    You can use the default name, which is in the format of vault_xxxx.

    +

    You can also use the default name vault_xxxx.

  • Complete the creation as prompted.
  • Go back to the Cloud Disk Backups page. You can see the created vault in the vault list.

    You can associate disks to the new vault or perform backup for the disks. For details, see Vault Management.

    • diff --git a/docs/cbr/umn/cbr_02_0006.html b/docs/cbr/umn/cbr_02_0006.html index c5de58342..80db241ee 100644 --- a/docs/cbr/umn/cbr_02_0006.html +++ b/docs/cbr/umn/cbr_02_0006.html @@ -2,18 +2,18 @@

    Creating a Cloud Server Backup

    This section describes how to quickly create a cloud server backup.

    -

    If you do not need an ECS for the moment, you can back up the ECS and then delete it. Then, create an image from the ECS backup and use the image to create an ECS as needed.

    -

    During the cloud server backup, the performance of the server is not affected. To ensure data integrity, back up the server during off-peak hours when no write operation is performed on the disks.

    +

    If you do not need an ECS for the moment, you can back up the ECS and then delete it. When you want an ECS later, you can create an image from the ECS backup and use the image to create ECSs.

    +

    Backing up a server does not impact the server performance. To ensure data integrity, you are advised to back up the server during off-peak hours when no data is written to the disks.

    Prerequisites

    • Only servers in the Running or Stopped state can be backed up.
    • At least one server backup vault is available.
    -

    Procedure

    1. Log in to CBR Console.

      1. Log in to the management console.
      2. Click in the upper left corner and select your region and project.
      3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
      +

      Procedure

      1. Log in to CBR Console.

        1. Log in to the management console.
        2. Click in the upper left corner and select your region and project.
        3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

      2. On the Cloud Server Backups page, click the Vaults tab and find the vault to which the server is associated.
      3. Choose More > Perform Backup in the Operation column. In the server list, select the server you want to back up. After a server is selected, it is added to the list of selected servers. See Figure 1.

        Figure 1 Selecting the server to be backed up

        -

      4. Set the Name and Description for the backup. Table 1 describes the parameters.

        +

      5. Set Name and Description for the backup. Table 1 describes the parameters.

        @@ -44,14 +44,14 @@
        Table 1 Parameter description

        Parameter

        Description

        @@ -26,7 +26,7 @@

        Name of the backup you are creating.

        A name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-).

        -
        NOTE:

        You can use the default name, which is in the format of manualbk_xxxx.

        +
        NOTE:

        You can also use the default name manualbk_xxxx.

        If multiple servers are to be backed up, the system automatically adds suffixes to their backup names, for example, backup-0001 and backup-0002.
        -

      6. Choose whether to enable full backup. If full backup is enabled, the system performs a full backup on every associated server, which requires a larger capacity compared to an incremental backup. See Figure 2.

        Figure 2 Selecting full backup
        +

      7. Choose whether to enable full backup. If full backup is enabled, CBR performs a full backup on every associated server, which requires a larger capacity compared to an incremental backup. See Figure 2.

        Figure 2 Selecting full backup

        -

      8. (Optional) You can also click the vault name to open the detailed page of the vault. On the Associated Servers tab page, locate the target server. Click Perform Backup in the Operation column of the server. See Figure 3.

        Figure 3 Perform Backup
        +

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

        Figure 3 Perform Backup

        -

      10. Click Yes. The system 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.

        +

      11. 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.

        diff --git a/docs/cbr/umn/cbr_02_0007.html b/docs/cbr/umn/cbr_02_0007.html index c985aa3fd..bcfd68ebb 100644 --- a/docs/cbr/umn/cbr_02_0007.html +++ b/docs/cbr/umn/cbr_02_0007.html @@ -2,19 +2,19 @@

        Creating a Cloud Disk Backup

        This section describes how to quickly create a cloud disk backup.

        -

        During the cloud disk backup, the performance of the disk is not affected. To ensure data integrity, back up the disk during off-peak hours when no write operation is performed on the disk.

        +

        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.

        -

        Procedure

        1. Log in to CBR Console.

          1. Log in to the management console.
          2. Click in the upper left corner and select your region and project.
          3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
          +

          Procedure

          1. Log in to CBR Console.

            1. Log in to the management console.
            2. Click in the upper left corner and select your region and project.
            3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

          2. On the Cloud Disk Backups page, click the Vaults tab and find the vault to which the disk is associated.
          3. Choose More > Perform Backup in the Operation column. In the disk list, select the disk you want to back up. After a disk is selected, it is added to the list of selected disks. See Figure 1.

            Figure 1 Selecting the disk to be backed up

            -

            The system will identify whether the selected disk is encrypted. If it is encrypted, its backup data will be stored in encrypted mode.

            +

            CBR will identify whether the selected disk is encrypted. If it is encrypted, the backups will be automatically encrypted.

            -

          4. Set the Name and Description for the backup. Table 1 describes the parameters.

            +

          5. Set Name and Description for the backup. Table 1 describes the parameters.

            @@ -45,15 +45,15 @@
            Table 1 Parameter description

            Parameter

            Description

            @@ -27,7 +27,7 @@

            Name of the backup you are creating.

            A name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-).

            -
            NOTE:

            You can use the default name, which is in the format of manualbk_xxxx.

            +
            NOTE:

            You can also use the default name manualbk_xxxx.

            If multiple disks are to be backed up, the system automatically adds suffixes to their backup names, for example, backup-0001 and backup-0002.
            -

          6. Choose whether to enable full backup. If full backup is enabled, the system performs a full backup on every associated disk, which requires a larger capacity compared to an incremental backup. See Figure 2.

            Figure 2 Selecting full backup
            +

          7. Choose whether to enable full backup. If full backup is enabled, CBR performs a full backup on every associated disk, which requires a larger capacity compared to an incremental backup. See Figure 2.

            Figure 2 Selecting full backup

            -

          8. (Optional) You can also click the vault name to open the detailed page of the vault. On the Associated Disks tab page, locate the target disk. Click Perform Backup in the Operation column of the disk. See Figure 3.

            Figure 3 Perform Backup
            +

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

            Figure 3 Perform Backup

            -

          10. Click Yes. The system 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 files from the disk during the backup, the deleted files may fail to be backed up. To ensure data integrity, you are advised to wait until the backup task is complete and then delete data and perform a backup again.

            +

          11. 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.

          diff --git a/docs/cbr/umn/cbr_02_0009.html b/docs/cbr/umn/cbr_02_0009.html index 5965a1357..a525d2126 100644 --- a/docs/cbr/umn/cbr_02_0009.html +++ b/docs/cbr/umn/cbr_02_0009.html @@ -3,9 +3,9 @@

          Step 2: Associate a Resource with the Vault

          If you have already associated servers, file systems, or disks when creating a vault, skip this step.

          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 to be associated must be in the same region.
          • The total capacity of the resources to be associated cannot be greater than the capacity of the vault.
          +

          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

          1. Log in to CBR Console.

            1. Log in to the management console.
            2. Click in the upper left corner and select your region and project.
            3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
            +

            Procedure

            1. Log in to CBR Console.

              1. Log in to the management console.
              2. Click in the upper left corner and select your region and project.
              3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

            2. On a backup page, locate the target vault and click Associate Server, Associate File System, or Associate Disk.
            3. In the resource list, select the resources you want to associate with the vault. After resources are selected, they are added to the list of selected resources. See Figure 1.

              Figure 1 Associate Server

              @@ -13,19 +13,19 @@

              -

            4. Click OK. Then in the Associated Servers column in the vault list, you can view the number of resources that have been successfully associated.

              If a new disk is attached to an associated server, the system automatically identifies the new disk and includes the new disk in subsequent backup tasks.

              +

            5. Click OK. Then in the Associated Servers column in the vault list, you can view the number of resources that have been successfully associated.

              If a new disk is attached to an associated server, CBR automatically identifies the new disk and includes the new disk in subsequent backup tasks.

            -

            Automatic Association

            Backup vaults support automatic association with resources that are not backed up. After successful association, resources will be backed up according to the backup policy applied to the vault.

            -
            • You can enable automatic association only when the vault's remaining capacity is greater than 40 GB. Remaining capacity of a vault = Total capacity of the vault - Capacity of resources associated with the vault. You can obtain the vault capacity and associated capacity in the Basic Information area on the details page of the vault. Specifically, if the capacity of a server backup vault is 800 GB and it has been associated with two 100 GB servers, the remaining capacity is 600 GB (800 GB – 200 GB). In this case, you can enable automatic association.
            • If multiple vaults are enabled with automatic association, the system scans their backup policies and associates resources with the vault whose next scheduled backup time is the earliest.
            • When the capacity of the vault selected by the system is used up, resources will be associated with the vault whose next scheduled backup time is the second earliest.
            • If a backup policy with the earliest scheduled backup time is applied to more than one vault, the system randomly associates the resources with one of these vaults.
            • If a vault is enabled with automatic association but no backup policy has been applied to it, no resources will be automatically associated with this vault. You can manually associate resources that have not been backed up with the vault.
            • After the automatic association function is disabled for a vault, the vault stops automatically scanning for resources that have not been backed up. The associated resources are not affected.
            +

            Automatic Association

            If you enable automatic association for a backup vault, the vault will automatically associate the unprotected resources and back them up according to the backup policy applied to the vault.

            +
            • You can enable automatic association only when the vault's remaining capacity (Vault's total capacity – Vault's associated capacity) is greater than 40 GB. You can obtain the vault's total capacity and associated capacity in the Basic Information area on the details page of the vault. For example, if you have an 800-GB server backup vault and it has been associated with two 100 GB servers, its remaining capacity is 600 GB (800 GB – 200 GB). In this case, you can enable automatic association.
            • If multiple vaults are enabled with automatic association, CBR scans their backup policies and associates resources with the vault whose next scheduled backup time is the earliest.
            • If the capacity of the first selected vault is used up, resources will be associated with the vault whose next scheduled backup time is the second earliest.
            • If a backup policy with the earliest scheduled backup time is applied to more than one vault, CBR randomly associates the resources with one of these vaults.
            • If a vault has automatic association enabled but has no backup policy applied, no resources will be automatically associated with this vault. You can manually associate unprotected resources.
            • After automatic association is disabled for a vault, the vault stops automatically scanning for unprotected resources. Associated resources are not affected.
            1. Log in to CBR Console.

              1. Log in to the management console.
              2. Click in the upper left corner and select your region and project.
              3. Choose Storage > Cloud Backup and Recovery.
              -

            2. On any backup page, locate the target vault.
            3. Choose More > Enable Automatic Association in the Operation column of the vault. See Figure 2.

              You can filter unprotected resources by tag. If a tag is selected, only unprotected resources having the specified tag will be associated with the vault. Or, all unprotected resources will be associated.

              -
              Only existing tags can be selected. If no tag is available, create tags on the corresponding resource page. You can select a maximum of 5 tags to search for vaults. If you select more than one tag, the vaults containing any of the specified tags will be returned.
              Figure 2 Enabling automatic association
              +

            4. On any backup page, locate the target vault.
            5. Choose More > Enable Automatic Association in the Operation column of the vault. See Figure 2.

              You can filter unprotected resources by tag. If a tag is selected, only unprotected resources with the specified tag will be associated with the vault. Or, all unprotected resources will be associated.

              +
              If no tag is available, you can create tags on the corresponding resource page. You can search for vaults by specifying a maximum of 5 tags at a time. If you select more than one tag, the vaults with any of the specified tags will be returned.
              Figure 2 Enabling automatic association

              -

            6. After the function is enabled, you can see Automatic association in the Associated Servers column of the vault list.
            7. (Optional) If the automatic association function is not required, choose More > Disable Automatic Association in the Operation column of the vault. See Figure 3.

              Figure 3 Disabling automatic association
              +

            8. Check that Automatic association is displayed in the Associated Servers column of the vault list.
            9. (Optional) If automatic association is not required, choose More > Disable Automatic Association in the Operation column of the vault. See Figure 3.

              Figure 3 Disabling automatic association

            diff --git a/docs/cbr/umn/cbr_02_0010.html b/docs/cbr/umn/cbr_02_0010.html index c0f6849f0..acbd19343 100644 --- a/docs/cbr/umn/cbr_02_0010.html +++ b/docs/cbr/umn/cbr_02_0010.html @@ -3,16 +3,16 @@

            Creating an SFS Turbo Backup Vault

            This section describes how to create an SFS Turbo backup vault.

            Procedure

            1. Log in to CBR Console.

              1. Log in to the management console.
              2. Click in the upper left corner and select your region and project.
              3. Choose Storage > Cloud Backup and Recovery > SFS Turbo Backups.
              -

            2. In the upper right corner of the page, click Create SFS Turbo Backup Vault.
            3. Select a protection type.

              • Backup: The created vault is an SFS Turbo backup vault, which stores backups of SFS Turbo file systems.
              +

            4. In the upper right corner of the page, click Create SFS Turbo Backup Vault.
            5. Select a protection type.

              • Backup: An SFS Turbo backup vault stores SFS Turbo backups.

            6. (Optional) In the file system list, select the file systems to be backed up. After file systems are selected, they are added to the list of selected file systems. See Figure 1.

              Figure 1 Selecting file systems

              -
              • The selected file systems must have not been associated with a vault and must be in the Available state.
              • You can associate file systems with the vault you are creating if you skip this step.
              +
              • The selected file systems must have not been associated with any vault and must be in the Available state.
              • You can also associate file systems with the vault you are creating later if you skip this step.
              -

            7. Specify the vault capacity. This capacity indicates the total size of the file systems that you want to associate with this vault. You need to properly plan the vault capacity, which must be at least the same as the size of the file systems you want to back up. The capacity ranges from 10 GB to 10485760 GB.
            8. Determine whether to configure auto backup.

              • If you select Configure, you must then select an existing backup policy or create a new policy. After the vault is created, the system will apply the policy to this vault, and all file systems associated with this vault will be automatically backed up based on this policy.
              • If you select Skip, file systems associated with this vault will not be automatically backed up until you apply a backup policy to it.
              -

            9. (Optional) Add tags to the vault.

              A tag is represented in the form of a key-value pair. Tags are used to identify, classify, and search for vaults. Vault tags are used to filter and manage vaults only. A vault can have a maximum of 10 tags.

              +

            10. Specify a vault capacity ranging from 10 GB to 10,485,760 GB. Properly plan the vault capacity, which must be at least the same as the size of the file systems you want to back up.
            11. Configure auto backup.

              • If you select Configure, you must then select an existing backup policy or create a new policy. After the vault is created, CBR will apply the policy to this vault, and all file systems associated with this vault will be automatically backed up based on this policy.
              • If you select Skip, file systems associated with this vault will not be automatically backed up until you apply a backup policy to the vault.
              +

            12. (Optional) Add tags to the vault.

              Tags are key-value pairs, which are used to identify, classify, and search for vaults. You can add a maximum of 10 tags for a vault, and vault tags are only used for vault search and management.

              Table 1 describes the parameters of a tag.
              @@ -24,7 +24,7 @@ - @@ -44,8 +44,8 @@
              Table 1 Tag parameter description

              Parameter

              Key

              Each tag has a unique key. You can customize the key or select the key of an existing tag created in TMS.

              +

              Each tag has a unique key. You can customize a key or select the key of an existing tag created in TMS.

              A tag key:

              • Can contain 1 to 36 Unicode characters.
              • Can contain only letters, digits, hyphens (-), and underscores (_).
              -

            13. Specify a name for the vault.

              A name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-), for example, vault-612c.

              -

              You can use the default name, which is in the format of vault_xxxx.

              +

            14. Specify a name for the vault.

              The name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-), for example, vault-612c.

              +

              You can also use the default name vault_xxxx.

            15. Complete the creation as prompted.
            16. Go back to the SFS Turbo Backups page. You can see the created vault in the vault list.

              You can associate file systems to the new vault or perform backup for the file systems. For details, see Vault Management.

            diff --git a/docs/cbr/umn/cbr_02_0012.html b/docs/cbr/umn/cbr_02_0012.html index b8b4aa27a..23a815ace 100644 --- a/docs/cbr/umn/cbr_02_0012.html +++ b/docs/cbr/umn/cbr_02_0012.html @@ -2,7 +2,7 @@

            Creating an SFS Turbo Backup

            This section describes how to quickly create an SFS Turbo file system backup.

            -

            During the SFS Turbo file system backup, the performance of the file system is not affected. To ensure data integrity, back up the file system during off-peak hours when no write operation is performed on the file system.

            +

            Backing up an SFS Turbo file system does not impact the file system performance. To ensure data integrity, you are advised to back up the file system during off-peak hours when no data is written to the file system.

            Prerequisites

            A file system can be backed up only when its status is Available or In-use. If you have performed operations such as expanding, mounting, unmounting, or deleting a file system, refresh the page first to ensure that the operation is complete and then determine whether to back up the file system.

            Procedure

            1. Log in to CBR Console.

              1. Log in to the management console.
              2. Click in the upper left corner and select your region and project.
              3. Choose Storage > Cloud Backup and Recovery > SFS Turbo Backups.
              @@ -12,7 +12,7 @@

              -

            2. Set the Name and Description for the backup. Table 1 describes the parameters.

              +

            3. Set Name and Description for the backup. Table 1 describes the parameters.

              @@ -43,13 +43,13 @@
              Table 1 Parameter description

              Parameter

              Description

              @@ -25,7 +25,7 @@

              Name of the backup you are creating.

              A name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-).

              -
              NOTE:

              You can use the default name, which is in the format of manualbk_xxxx.

              +
              NOTE:

              You can also use the default name manualbk_xxxx.

              If multiple file systems are to be backed up, the system automatically adds suffixes to their backup names, for example, backup-0001 and backup-0002.
              -

            4. (Optional) You can also click the vault name to open the detailed page of the vault. On the Associated File Systems tab page, locate the target file system. Click Perform Backup in the Operation column of the file system. See Figure 2.

              Figure 2 Perform Backup
              +

            5. (Optional) Click the vault name to go to the vault details page. On the Associated File Systems tab page, locate the target file system. Click Perform Backup in the Operation column of the file system. See Figure 2.

              Figure 2 Perform Backup

              -

            6. Click Yes. The system automatically creates a backup for the file system.

              On the Backups tab page, if the status of the backup is Available, the backup task is successful.

              -

              If you delete files from the file system during the backup, the deleted files may fail to be backed up. To ensure data integrity, you are advised to wait until the backup task is complete and then delete data and perform a backup again.

              +

            7. Click Yes. CBR automatically creates a backup for the file system.

              On the Backups tab page, if the status of the backup is Available, the backup task is successful.

              +

              If you delete data from the file system during the backup, the deleted data may fail to be backed up. To ensure data integrity, you are advised to wait until the backup task is complete and then make the change and perform a backup again.

              After the backup is complete, you can create a new SFS Turbo file system using the backup. For details, see Using a Backup to Create a File System.

            diff --git a/docs/cbr/umn/cbr_03_0002.html b/docs/cbr/umn/cbr_03_0002.html index 5a0c4afb7..888fd4808 100644 --- a/docs/cbr/umn/cbr_03_0002.html +++ b/docs/cbr/umn/cbr_03_0002.html @@ -4,7 +4,7 @@

            You can set search criteria for querying desired vaults in the vault list.

            Prerequisites

            A vault has been created.

            -

            Viewing Vault Details

            1. Log in to CBR Console.

              1. Log in to the management console.
              2. Click in the upper left corner and select your region and project.
              3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
              +

              Viewing Vault Details

              1. Log in to CBR Console.

                1. Log in to the management console.
                2. Click in the upper left corner and select your region and project.
                3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

              2. View the basic information about vaults. Related parameters are described in the following table. See Figure 1.

                Figure 1 Vault list
                Table 1 Basic information parameters

                Parameter

                diff --git a/docs/cbr/umn/cbr_03_0003.html b/docs/cbr/umn/cbr_03_0003.html index fc573b8d3..2bc01d229 100644 --- a/docs/cbr/umn/cbr_03_0003.html +++ b/docs/cbr/umn/cbr_03_0003.html @@ -5,7 +5,7 @@

                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.
                -

                Procedure

                1. Log in to CBR Console.

                  1. Log in to the management console.
                  2. Click in the upper left corner and select your region and project.
                  3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                  +

                  Procedure

                  1. Log in to CBR Console.

                    1. Log in to the management console.
                    2. Click in the upper left corner and select your region and project.
                    3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                  2. 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.

                    Figure 1 Deleting a vault

                    diff --git a/docs/cbr/umn/cbr_03_0005.html b/docs/cbr/umn/cbr_03_0005.html index 01056cd9b..2a5846f1d 100644 --- a/docs/cbr/umn/cbr_03_0005.html +++ b/docs/cbr/umn/cbr_03_0005.html @@ -4,7 +4,7 @@

                    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.

                    Dissociating a resource from a vault does not affect the performance of services on the resource.

                    -

                    Procedure

                    1. Log in to CBR Console.

                      1. Log in to the management console.
                      2. Click in the upper left corner and select your region and project.
                      3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                      +

                      Procedure

                      1. Log in to CBR Console.

                        1. Log in to the management console.
                        2. Click in the upper left corner and select your region and project.
                        3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                      2. On any backup page, locate the target vault and click the vault name.
                      3. 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.
                        Figure 1 Dissociating a server

                        diff --git a/docs/cbr/umn/cbr_03_0006.html b/docs/cbr/umn/cbr_03_0006.html index cf130a06b..1a083f158 100644 --- a/docs/cbr/umn/cbr_03_0006.html +++ b/docs/cbr/umn/cbr_03_0006.html @@ -2,7 +2,7 @@

                        Expanding Vault Capacity

                        You can expand the size of a vault if its total capacity is insufficient.

                        -

                        Procedure

                        1. Log in to CBR Console.

                          1. Log in to the management console.
                          2. Click in the upper left corner and select your region and project.
                          3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                          +

                          Procedure

                          1. Log in to CBR Console.

                            1. Log in to the management console.
                            2. Click in the upper left corner and select your region and project.
                            3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                          2. On any backup page, locate the target vault and choose More > Expand Capacity in the Operation column. See Figure 1.

                            Figure 1 Expanding vault capacity

                            diff --git a/docs/cbr/umn/cbr_03_0010.html b/docs/cbr/umn/cbr_03_0010.html index 2d2f1d692..6210c9dd3 100644 --- a/docs/cbr/umn/cbr_03_0010.html +++ b/docs/cbr/umn/cbr_03_0010.html @@ -2,7 +2,7 @@

                            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

                            1. Log in to CBR Console.

                              1. Log in to the management console.
                              2. Click in the upper left corner and select your region and project.
                              3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                              +

                              Procedure

                              1. Log in to CBR Console.

                                1. Log in to the management console.
                                2. Click in the upper left corner and select your region and project.
                                3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                              2. Click the name of a vault and select the Tag tab in the displayed vault information page.

                                • Adding a tag
                                  1. Click Add Tag in the upper left corner.
                                  2. 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.

                                    Figure 1 Adding a tag
                                    Table 1 describes the parameters of a tag. diff --git a/docs/cbr/umn/cbr_03_0013.html b/docs/cbr/umn/cbr_03_0013.html index 63f0401b8..61837f8c2 100644 --- a/docs/cbr/umn/cbr_03_0013.html +++ b/docs/cbr/umn/cbr_03_0013.html @@ -4,7 +4,7 @@

                                    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.

                                    -

                                    Viewing Backup Details

                                    1. Log in to CBR Console.

                                      1. Log in to the management console.
                                      2. Click in the upper left corner and select your region and project.
                                      3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                                      +

                                      Viewing Backup Details

                                      1. Log in to CBR Console.

                                        1. Log in to the management console.
                                        2. Click in the upper left corner and select your region and project.
                                        3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                                      2. On any backup page, click the Backups tab and set filter criteria to view the backups. See Figure 1.

                                        Figure 1 Viewing a backup
                                        • You can search for backups by selecting a status from the All statuses drop-down list in the upper right corner of the backup list. Table 1 describes the backup statuses.
                                          - - + + + - - - - - - - - - - - - - - - - diff --git a/docs/cbr/umn/cbr_03_0104.html b/docs/cbr/umn/cbr_03_0104.html index a667cf21e..3c87b21eb 100644 --- a/docs/cbr/umn/cbr_03_0104.html +++ b/docs/cbr/umn/cbr_03_0104.html @@ -13,7 +13,7 @@

                                          Constraints

                                          • The vaults you have cannot be used for migration. The system will automatically migrate resources to the vaults created by the system.
                                          • Backup resources of one account need to be migrated only once.
                                          • After resources are migrated, disk backups and server backups will be automatically stored in CBR vaults. No further operations are required.
                                          -

                                          Procedure

                                          1. Log in to CBR Console.

                                            1. Log in to the management console.
                                            2. Click in the upper left corner and select your region and project.
                                            3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                                            +

                                            Procedure

                                            1. Log in to CBR Console.

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select your region and project.
                                              3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                                            2. Click Migrate to CBR in the upper right corner. Read the content in the displayed dialog box and click OK. See Figure 1.

                                              Figure 1 Migrating resources to CBR

                                              diff --git a/docs/cbr/umn/cbr_03_0107.html b/docs/cbr/umn/cbr_03_0107.html index fcb3a1b82..212327e1a 100644 --- a/docs/cbr/umn/cbr_03_0107.html +++ b/docs/cbr/umn/cbr_03_0107.html @@ -2,7 +2,7 @@

                                              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

                                              1. Log in to CBR Console.

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select your region and project.
                                                3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                                                +

                                                Procedure

                                                1. Log in to CBR Console.

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select your region and project.
                                                  3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                                                2. Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
                                                3. If the status of the target backup is Available, click Create File System in the Operation column of the backup.
                                                4. Set the file system parameters. See Figure 1.

                                                  Figure 1 Creating a file system
                                                  • 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_05_0003.html b/docs/cbr/umn/cbr_05_0003.html index 9d568e081..25840ad1d 100644 --- a/docs/cbr/umn/cbr_05_0003.html +++ b/docs/cbr/umn/cbr_05_0003.html @@ -6,13 +6,13 @@

                                                  Possible Cause

                                                  After the server creation, the configuration parameters contained in the /etc/fstab file in the system disk of the new server are that of the backup source server, causing the UUID information to be inconsistent with the new data disks. As a result, the ECS encounters an error when uploading /etc/fstab during the bootup and enters maintenance mode.

                                                  Solution

                                                  The following uses CentOS as an example.

                                                  -
                                                  1. After creating an ECS using an image, log in to the ECS console, click Remote Login in the row of the ECS.
                                                  2. On the maintenance mode page that is displayed, access the system as prompted.

                                                    Figure 1 Maintenance mode of the system
                                                    -

                                                  3. Run the cat /etc/fstab command to check the disk attachment information.

                                                    Figure 2 Data disk UUIDs
                                                    -

                                                  4. Run the vi /etc/fstab command to open the file, press i to enter the editing mode, and delete the attachment information of all data disks. Then, press Esc to exit the editing mode and run :wq! to save the change and exit.

                                                    Figure 3 /etc/fstab after being updated
                                                    -

                                                  5. Run the reboot command to restart the system.

                                                    Figure 4 Normal bootup page
                                                    -

                                                  6. After entering the system, attach the data disks manually.

                                                    Figure 5 Attaching the data disks manually
                                                    -

                                                  7. Run the blkid command to obtain the UUID information of the data disks.

                                                    Figure 6 Obtaining UUIDs of data disks
                                                    -

                                                  8. Run the vi /etc/fstab command to open the file, press i to enter the editing mode, and add the attachment information of all data disks. Then, press Esc to exit the editing mode and run :wq! to save the change and exit.

                                                    Figure 7 Adding attachment information of data disks
                                                    +
                                                    1. After creating an ECS using an image, log in to the ECS console, click Remote Login in the row of the ECS.
                                                    2. On the maintenance mode page that is displayed, access the system as prompted.

                                                      Figure 1 Maintenance mode of the system
                                                      +

                                                    3. Run the cat /etc/fstab command to check the disk attachment information.

                                                      Figure 2 Data disk UUIDs
                                                      +

                                                    4. Run the vi /etc/fstab command to open the file, press i to enter the editing mode, and delete the attachment information of all data disks. Then, press Esc to exit the editing mode and run :wq! to save the change and exit.

                                                      Figure 3 /etc/fstab after being updated
                                                      +

                                                    5. Run the reboot command to restart the system.

                                                      Figure 4 Normal bootup page
                                                      +

                                                    6. After entering the system, attach the data disks manually.

                                                      Figure 5 Attaching the data disks manually
                                                      +

                                                    7. Run the blkid command to obtain the UUID information of the data disks.

                                                      Figure 6 Obtaining UUIDs of data disks
                                                      +

                                                    8. Run the vi /etc/fstab command to open the file, press i to enter the editing mode, and add the attachment information of all data disks. Then, press Esc to exit the editing mode and run :wq! to save the change and exit.

                                                      Figure 7 Adding attachment information of data disks

                                                      After the information is added, the system will automatically attach the data disks on restart.

                                                  @@ -23,3 +23,10 @@
                                              + + \ No newline at end of file diff --git a/docs/cbr/umn/en-us_image_0000001462955128.png b/docs/cbr/umn/en-us_image_0000001462955128.png new file mode 100644 index 000000000..f49ccb4c9 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001462955128.png differ diff --git a/docs/cbr/umn/en-us_image_0000001463274188.png b/docs/cbr/umn/en-us_image_0000001463274188.png new file mode 100644 index 000000000..4d9cc8fb8 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001463274188.png differ diff --git a/docs/cbr/umn/en-us_image_0000001478036586.png b/docs/cbr/umn/en-us_image_0000001478036586.png new file mode 100644 index 000000000..cbc792104 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001478036586.png differ diff --git a/docs/cbr/umn/en-us_image_0000001513434281.png b/docs/cbr/umn/en-us_image_0000001513434281.png new file mode 100644 index 000000000..75ab525ed Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001513434281.png differ diff --git a/docs/cbr/umn/en-us_image_0000001513435141.png b/docs/cbr/umn/en-us_image_0000001513435141.png new file mode 100644 index 000000000..b8bb9e59e Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001513435141.png differ diff --git a/docs/cbr/umn/en-us_image_0000001513555957.png b/docs/cbr/umn/en-us_image_0000001513555957.png new file mode 100644 index 000000000..4e8c3b9f9 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001513555957.png differ diff --git a/docs/cbr/umn/en-us_image_0000001513556381.png b/docs/cbr/umn/en-us_image_0000001513556381.png new file mode 100644 index 000000000..7a25b7789 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001513556381.png differ diff --git a/docs/cbr/umn/en-us_image_0000001513691041.png b/docs/cbr/umn/en-us_image_0000001513691041.png new file mode 100644 index 000000000..e7649ed25 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001513691041.png differ diff --git a/docs/cbr/umn/en-us_image_0160524684.jpg b/docs/cbr/umn/en-us_image_0160524684.jpg deleted file mode 100644 index fdf630eaa..000000000 Binary files a/docs/cbr/umn/en-us_image_0160524684.jpg and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0160524685.jpg b/docs/cbr/umn/en-us_image_0160524685.jpg deleted file mode 100644 index c4b7494a1..000000000 Binary files a/docs/cbr/umn/en-us_image_0160524685.jpg and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0160524686.jpg b/docs/cbr/umn/en-us_image_0160524686.jpg deleted file mode 100644 index f33c62b8f..000000000 Binary files a/docs/cbr/umn/en-us_image_0160524686.jpg and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0160524687.jpg b/docs/cbr/umn/en-us_image_0160524687.jpg deleted file mode 100644 index 3cbc82d2b..000000000 Binary files a/docs/cbr/umn/en-us_image_0160524687.jpg and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0160524688.jpg b/docs/cbr/umn/en-us_image_0160524688.jpg deleted file mode 100644 index dd82a3f84..000000000 Binary files a/docs/cbr/umn/en-us_image_0160524688.jpg and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0160524689.jpg b/docs/cbr/umn/en-us_image_0160524689.jpg deleted file mode 100644 index 73f2a90fe..000000000 Binary files a/docs/cbr/umn/en-us_image_0160524689.jpg and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0160524690.jpg b/docs/cbr/umn/en-us_image_0160524690.jpg deleted file mode 100644 index d2827790b..000000000 Binary files a/docs/cbr/umn/en-us_image_0160524690.jpg and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251477850.png b/docs/cbr/umn/en-us_image_0251477850.png deleted file mode 100644 index e1c7a7190..000000000 Binary files a/docs/cbr/umn/en-us_image_0251477850.png and /dev/null differ
                                          Table 1 Backup statuses

                                          Status

                                          diff --git a/docs/cbr/umn/cbr_03_0014.html b/docs/cbr/umn/cbr_03_0014.html index 196a7ddc5..9a37817e8 100644 --- a/docs/cbr/umn/cbr_03_0014.html +++ b/docs/cbr/umn/cbr_03_0014.html @@ -3,29 +3,29 @@

                                          Sharing a Backup

                                          You can share a server or disk backup with other domains. Shared backups can be used to create servers or disks.

                                          Context

                                          Sharer

                                          -
                                          • Backups can only be shared among domains in the same region.
                                          • Encrypted backups cannot be shared. Backups cannot be shared across regions. Account to which a backup is shared must be in the same region as the backup.
                                          • Accepted shared backups will be deleted once the sharer deletes the original backup. If a shared backup has been used to create new disks or servers, the created resources will not be deleted.
                                          +
                                          • Backups can only be shared among domains in the same region. They cannot be shared across regions.
                                          • Encrypted backups cannot be shared.
                                          • When a sharer deletes a shared backup, the backup will also be deleted from the recipient's account, but the disks or servers previously created using the backup will be retained.

                                          Recipient

                                          -
                                          • A recipient must have at least one backup vault to store the accepted shared backup, and the vault remaining space must be greater than the size of the backup to be accepted.
                                          • A recipient can choose whether to accept a backup. After accepting a backup, the recipient can use the backup to create new servers or disks.
                                          • Accepted shared backups will be deleted once the sharer deletes the original backup. If a shared backup has been used to create new disks or servers, the created resources will not be deleted.
                                          +
                                          • 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

                                          1. Log in to CBR Console.

                                            1. Log in to the management console.
                                            2. Click in the upper left corner and select your region and project.
                                            3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                                            -

                                          2. On the cloud server or cloud disk backup page, click the Backups tab and set filter criteria to view the backups.
                                          3. Locate the target backup and choose More > Share Backup in the Operation column.

                                            The backup name, server name, backup ID, and backup type are displayed.

                                            +

                                            Procedure for the Sharer

                                            1. Log in to CBR Console.

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select your region and project.
                                              3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
                                              +

                                            2. Click the Backups tab and set filter criteria to view the backups.
                                            3. 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 backup
                                                Figure 1 Sharing a backup

                                                -

                                                +

                                              -
                                              1. Click the Share Backup tab.
                                              2. Enter the account name of the tenant to whom the backup is to be shared.
                                              3. Click Add. The account name and project to be added are displayed in the list. You can continue to add account names. A backup can be shared to a maximum of ten projects.
                                              4. Click OK.
                                              +
                                              1. Click the Share Backup tab.
                                              2. Enter the project ID of the recipient.
                                              3. 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.
                                              4. Click OK.
                                              • Canceling sharing
                                              1. Locate the target backup and choose More > Share Backup in the Operation column.
                                              2. On the displayed page, click the Cancel Sharing tab and select the backup that no longer needs to be shared. Then, click OK.

                                            -

                                            Procedure for the Recipient

                                            1. Log in to CBR Console.

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select your region and project.
                                              3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                                              -

                                            2. On the cloud server or cloud disk backup page, click the Backups tab and then click Backups Shared with Me.
                                            3. 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.
                                            4. 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.

                                              -

                                            5. After a shared backup is accepted, it will be displayed in the backup list.
                                            +

                                            Procedure for the Recipient

                                            1. Log in to CBR Console.

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select your region and project.
                                              3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.
                                              +

                                            2. On the selected backup page, click the Backups tab and then click Backups Shared with Me.
                                            3. 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.
                                            4. 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.

                                              +

                                            5. 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 7d5cf495d..3847e778d 100644 --- a/docs/cbr/umn/cbr_03_0015.html +++ b/docs/cbr/umn/cbr_03_0015.html @@ -6,7 +6,7 @@

                                            Prerequisites

                                            • At least one backup exists.
                                            • The backup to be deleted is in the Available or Error state.
                                            -

                                            Procedure

                                            1. Log in to CBR Console.

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select your region and project.
                                              3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                                              +

                                              Procedure

                                              1. Log in to CBR Console.

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select your region and project.
                                                3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                                              2. On any backup page, click the Backups tab and locate the desired backup. For details, see Viewing a Backup.
                                              3. 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.

                                                Figure 1 Deleting a backup

                                                diff --git a/docs/cbr/umn/cbr_03_0016.html b/docs/cbr/umn/cbr_03_0016.html index 0063f5e96..3597d80dd 100644 --- a/docs/cbr/umn/cbr_03_0016.html +++ b/docs/cbr/umn/cbr_03_0016.html @@ -9,7 +9,7 @@

                                              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.
                                              -

                                              Procedure

                                              1. Log in to CBR Console.

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select your region and project.
                                                3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                                                +

                                                Procedure

                                                1. Log in to CBR Console.

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select your region and project.
                                                  3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                                                2. Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
                                                3. In the row of the backup, choose More > Create Image. See Figure 1.

                                                  Figure 1 Creating an image

                                                4. Create an image by referring to section "Creating a Full-ECS Image from a CBR Backup" in the Image Management Service User Guide.
                                                5. 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.
                                                diff --git a/docs/cbr/umn/cbr_03_0017.html b/docs/cbr/umn/cbr_03_0017.html index fba30fe6a..30a587e20 100644 --- a/docs/cbr/umn/cbr_03_0017.html +++ b/docs/cbr/umn/cbr_03_0017.html @@ -3,7 +3,7 @@

                                                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

                                                1. Log in to CBR Console.

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select your region and project.
                                                  3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                                                  +

                                                  Procedure

                                                  1. Log in to CBR Console.

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select your region and project.
                                                    3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                                                  2. Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
                                                  3. If the status of the target backup is Available, click Create Disk in the Operation column of the backup.
                                                  4. 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.

                                                      diff --git a/docs/cbr/umn/cbr_03_0025.html b/docs/cbr/umn/cbr_03_0025.html index 9d1165fc1..b6387b5cf 100644 --- a/docs/cbr/umn/cbr_03_0025.html +++ b/docs/cbr/umn/cbr_03_0025.html @@ -6,7 +6,7 @@

                                                      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.
                                                      -

                                                      Procedure

                                                      1. Log in to CBR Console.

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select your region and project.
                                                        3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                                                        +

                                                        Procedure

                                                        1. Log in to CBR Console.

                                                          1. Log in to the management console.
                                                          2. Click in the upper left corner and select your region and project.
                                                          3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                                                        2. Choose Policies and click the Backup Policies tab. In the upper right corner, click Create Policy. See Figure 1.

                                                          Figure 1 Creating a backup policy

                                                          diff --git a/docs/cbr/umn/cbr_03_0027.html b/docs/cbr/umn/cbr_03_0027.html index ba8fc1a3d..8c2f651c9 100644 --- a/docs/cbr/umn/cbr_03_0027.html +++ b/docs/cbr/umn/cbr_03_0027.html @@ -4,7 +4,7 @@

                                                          This section describes how to modify a policy.

                                                          Prerequisites

                                                          You have created at least one policy.

                                                          -

                                                          Procedure

                                                          1. Log in to CBR Console.

                                                            1. Log in to the management console.
                                                            2. Click in the upper left corner and select your region and project.
                                                            3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                                                            +

                                                            Procedure

                                                            1. Log in to CBR Console.

                                                              1. Log in to the management console.
                                                              2. Click in the upper left corner and select your region and project.
                                                              3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                                                            2. On any backup page, find the target vault and click the vault name to view the vault details.
                                                            3. In the Policies area, click Edit in the row of a policy to open the policy editing page. See Figure 1.

                                                              Figure 1 Editing a backup policy

                                                              diff --git a/docs/cbr/umn/cbr_03_0028.html b/docs/cbr/umn/cbr_03_0028.html index 2d195f4a7..bfa32ea15 100644 --- a/docs/cbr/umn/cbr_03_0028.html +++ b/docs/cbr/umn/cbr_03_0028.html @@ -4,7 +4,7 @@

                                                              You can delete backup and replication policies if needed.

                                                              Prerequisites

                                                              You have created at least one policy.

                                                              -

                                                              Procedure

                                                              1. Log in to CBR Console.

                                                                1. Log in to the management console.
                                                                2. Click in the upper left corner and select your region and project.
                                                                3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                                                                +

                                                                Procedure

                                                                1. Log in to CBR Console.

                                                                  1. Log in to the management console.
                                                                  2. Click in the upper left corner and select your region and project.
                                                                  3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                                                                2. 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.

                                                                3. Confirm the information and click Yes.
                                                                diff --git a/docs/cbr/umn/cbr_03_0029.html b/docs/cbr/umn/cbr_03_0029.html index 17687c86d..d47087ca5 100644 --- a/docs/cbr/umn/cbr_03_0029.html +++ b/docs/cbr/umn/cbr_03_0029.html @@ -2,7 +2,7 @@

                                                                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

                                                                1. Log in to CBR Console.

                                                                  1. Log in to the management console.
                                                                  2. Click in the upper left corner and select your region and project.
                                                                  3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                                                                  +

                                                                  Procedure

                                                                  1. Log in to CBR Console.

                                                                    1. Log in to the management console.
                                                                    2. Click in the upper left corner and select your region and project.
                                                                    3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                                                                  2. On any backup page, find the target vault and choose More > Apply Backup Policy. See Figure 1.

                                                                    Figure 1 Setting a backup policy

                                                                    diff --git a/docs/cbr/umn/cbr_03_0030.html b/docs/cbr/umn/cbr_03_0030.html index d37cf5629..f7a0e6eeb 100644 --- a/docs/cbr/umn/cbr_03_0030.html +++ b/docs/cbr/umn/cbr_03_0030.html @@ -4,7 +4,7 @@

                                                                    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

                                                                    1. Log in to CBR Console.

                                                                      1. Log in to the management console.
                                                                      2. Click in the upper left corner and select your region and project.
                                                                      3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                                                                      +

                                                                      Procedure

                                                                      1. Log in to CBR Console.

                                                                        1. Log in to the management console.
                                                                        2. Click in the upper left corner and select your region and project.
                                                                        3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                                                                      2. On any backup page, find the target vault and click the vault name to view the vault details.
                                                                      3. In the Policies area, click Remove Policy. See Figure 1.

                                                                        Figure 1 Removing a policy

                                                                        diff --git a/docs/cbr/umn/cbr_03_0032.html b/docs/cbr/umn/cbr_03_0032.html index 81f7a7c87..74536f08d 100644 --- a/docs/cbr/umn/cbr_03_0032.html +++ b/docs/cbr/umn/cbr_03_0032.html @@ -6,7 +6,7 @@

                                                                      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.
                                                                      -

                                                                      Procedure

                                                                      1. Log in to CBR Console.

                                                                        1. Log in to the management console.
                                                                        2. Click in the upper left corner and select your region and project.
                                                                        3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                                                                        +

                                                                        Procedure

                                                                        1. Log in to CBR Console.

                                                                          1. Log in to the management console.
                                                                          2. Click in the upper left corner and select your region and project.
                                                                          3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                                                                        2. Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
                                                                        3. 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.

                                                                          Figure 1 Restoring a server
                                                                          diff --git a/docs/cbr/umn/cbr_03_0033.html b/docs/cbr/umn/cbr_03_0033.html index b2ea62294..765b6b028 100644 --- a/docs/cbr/umn/cbr_03_0033.html +++ b/docs/cbr/umn/cbr_03_0033.html @@ -6,7 +6,7 @@

                                                                        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.
                                                                        -

                                                                        Procedure

                                                                        1. Log in to CBR Console.

                                                                          1. Log in to the management console.
                                                                          2. Click in the upper left corner and select your region and project.
                                                                          3. Choose Storage > Cloud Backup and Recovery. Select a backup tab from the left navigation pane.
                                                                          +

                                                                          Procedure

                                                                          1. Log in to CBR Console.

                                                                            1. Log in to the management console.
                                                                            2. Click in the upper left corner and select your region and project.
                                                                            3. Choose Storage > Cloud Backup and Recovery. Choose a backup tab from the left navigation pane.

                                                                          2. Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
                                                                          3. 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.
                                                                            Figure 1 Restore Disk
                                                                            diff --git a/docs/cbr/umn/cbr_03_0037.html b/docs/cbr/umn/cbr_03_0037.html index c50384d36..201046a76 100644 --- a/docs/cbr/umn/cbr_03_0037.html +++ b/docs/cbr/umn/cbr_03_0037.html @@ -13,7 +13,6 @@
                                                                            • 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
                                                                            -

                                                                            Learn how to obtain the service hotline and email address.

                                                                        diff --git a/docs/cbr/umn/cbr_03_0046.html b/docs/cbr/umn/cbr_03_0046.html index ea79b7b69..975bd54f3 100644 --- a/docs/cbr/umn/cbr_03_0046.html +++ b/docs/cbr/umn/cbr_03_0046.html @@ -8,105 +8,111 @@

                                          2022-12-02

                                          +

                                          2023-03-02

                                          This issue incorporates the following changes:

                                          +

                                          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."
                                          +

                                          2022-12-02

                                          +

                                          This issue is the eighteenth official release, which incorporates the following changes:

                                          • Added section "Permissions Management" in "Service Overview."
                                          • Added section "Permissions Management" in "User Guide."

                                          2022-11-16

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the seventeenth official release, which incorporates the following change:

                                          Added the description of disk-level backup in section "Creating a Server Backup Vault."

                                          2022-07-28

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the sixteenth official release, which incorporates the following change:

                                          Updated the screenshot in section "Using Backup to Create a File System."

                                          2022-07-20

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the fifteenth official release, which incorporates the following changes:

                                          • Added a screenshot about SFS Turbo backup.
                                          • Added the description about file system backup in section "What Is CBR."
                                          • Modified the architecture in section "What Is CBR."
                                          • Added descriptions of file system backup throughout the document.

                                          2022-07-19

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the fourteenth official release, which incorporates the following change:

                                          Modified section "Creating an Alarm Rule."

                                          2022-07-15

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the thirteenth official release, which incorporates the following change:

                                          Modified section "Creating an Alarm Rule."

                                          2022-06-23

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the twelfth official release, which incorporates the following change:

                                          Added sections "Monitoring" and "Creating an Alarm Rule."

                                          2022-04-26

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the eleventh official release, which incorporates the following change:

                                          Added a screenshot in section "(Optional) Migrating Resources from CSBS/VBS."

                                          2022-04-21

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the tenth official release, which incorporates the following change:

                                          Modified descriptions in section "(Optional) Migrating Resources from CSBS/VBS."

                                          2022-03-29

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the ninth official release, which incorporates the following change:

                                          Added the description of migrating resources from CSBS/VBS to CBR.

                                          2022-03-15

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the eighth official release, which incorporates the following changes:

                                          • Added the description about automatic association by tag in section "Creating a Server Backup Vault."
                                          • Added the description about automatic association by tag in section "Creating a Disk Backup Vault."
                                          • Added the description about automatic association by tag in section "Associate a Resource with a Vault."

                                          2021-12-07

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the seventh official release, which incorporates the following change:

                                          Added descriptions of enhanced backup in section "Basic Concepts."

                                          2020-06-05

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the sixth official release, which incorporates the following changes:

                                          • Deleted section "Managing the Enterprise Projects of Vaults" and other content related to enterprise projects.
                                          • Deleted content about BMS backup support.
                                          • Deleted the description about automatic association from section "Associate a Resource with the Vault."

                                          2020-02-14

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the fifth official release, which incorporates the following changes:

                                          • Added screenshots in section "Creating a Server Backup Vault."
                                          • Added screenshots in section "Creating a Disk Backup Vault."
                                          • Added screenshots in section "Querying a Vault."
                                          • Added screenshots in section "Managing Vault Tags."
                                          • Deleted section "Managing the Enterprise Projects of Vaults."
                                          • Added screenshots in section "Querying a Backup."
                                          • Added screenshots in section "Sharing a Backup."
                                          • Added the description of parameters for and screenshots of daily, weekly, and yearly backup in section "Creating a Backup Policy."
                                          • Added screenshots in section "Managing Tasks."
                                          • Added screenshots in section "Auditing."

                                          2019-09-11

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the fourth official release, which incorporates the following change:

                                          Accepted for RM-530.

                                          2019-09-04

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the third official release, which incorporates the following changes:

                                          • Modified descriptions in sections "What Is CBR", "Related Services", "Basic Concepts", "Constraints", "Creating a Server Backup Vault", and "Deleting a Vault."
                                          • Modified description in sections "Using a Backup to Create an Image", "Restoring Data Using a Cloud Disk Backup", and FAQ "Can I Use a System Disk Backup to Recover an ECS?"
                                          • Modified the architecture of CBR in section "What Is CBR?"

                                          2019-08-08

                                          This issue incorporates the following changes:

                                          +

                                          This issue is the second official release, which incorporates the following changes:

                                          • Deleted description about cross-region replication and application-consistent backup.
                                          • Added screenshots.