diff --git a/docs/cbr/umn/ALL_META.TXT.json b/docs/cbr/umn/ALL_META.TXT.json index f5835c5e..1cf9d948 100644 --- a/docs/cbr/umn/ALL_META.TXT.json +++ b/docs/cbr/umn/ALL_META.TXT.json @@ -349,7 +349,7 @@ "node_id":"cbr_02_0007.xml", "product_code":"cbr", "code":"20", - "des":"This section describes how to quickly create a cloud disk backup.Backing up a server does not impact the disk performance.Peak hours of the backup service are from 00:00 ", + "des":"This section describes how to quickly create a cloud disk backup.Backing up a server does not impact the disk performance.Peak hours of the backup service are from 22:00 ", "doc_type":"usermanual", "kw":"Creating a Cloud Disk Backup,Step 3: Create a Backup,User Guide", "search_title":"", @@ -403,7 +403,7 @@ "node_id":"cbr_03_0048.xml", "product_code":"cbr", "code":"23", - "des":"This section describes how to use IAM to implement fine-grained permissions control for your CBR resources. With IAM, you can:Create IAM users for employees based on your", + "des":"This section describes how to use IAM to implement fine-grained permissions control for your CBR resources. With IAM, you can:Create IAM users for personnel based on your", "doc_type":"usermanual", "kw":"Creating a User and Granting CBR Permissions,Permissions Management,User Guide", "search_title":"", @@ -495,7 +495,7 @@ "code":"28", "des":"If you no longer need to back up an associated resource, dissociate it from your vault.After a resource is dissociated, the vault's backup policy no longer applies to the", "doc_type":"usermanual", - "kw":"Dissociating a Resource,Vault Management,User Guide", + "kw":"Dissociating Resources from a Vault,Vault Management,User Guide", "search_title":"", "metedata":[ { @@ -503,7 +503,7 @@ "documenttype":"usermanual" } ], - "title":"Dissociating a Resource", + "title":"Dissociating Resources from a Vault", "githuburl":"" }, { @@ -513,7 +513,7 @@ "code":"29", "des":"Migrating a resource means that you dissociate a resource from a vault and then associate it to another vault. All backups of the resource will be migrated to the destina", "doc_type":"usermanual", - "kw":"Migrating a Resource,Vault Management,User Guide", + "kw":"Migrating Resources from a Vault,Vault Management,User Guide", "search_title":"", "metedata":[ { @@ -521,7 +521,7 @@ "documenttype":"usermanual" } ], - "title":"Migrating a Resource", + "title":"Migrating Resources from a Vault", "githuburl":"" }, { @@ -547,9 +547,9 @@ "node_id":"cbr_03_0009.xml", "product_code":"cbr", "code":"31", - "des":"CBR allows you to replicate server backup vaults entirely to replication vaults in a different region. Replicas of server backups in the destination region can be used to", + "des":"CBR allows you to replicate server backup vaults entirely to replication vaults in other regions of the same account. Replicas of server backups in the destination region", "doc_type":"usermanual", - "kw":"Replicating a Vault,Vault Management,User Guide", + "kw":"Replicating a Vault Across Regions,Vault Management,User Guide", "search_title":"", "metedata":[ { @@ -557,7 +557,7 @@ "documenttype":"usermanual" } ], - "title":"Replicating a Vault", + "title":"Replicating a Vault Across Regions", "githuburl":"" }, { @@ -619,7 +619,7 @@ "node_id":"cbr_03_0014.xml", "product_code":"cbr", "code":"35", - "des":"You can share a server or disk backup with other domains. Shared backups can be used to create servers or disks.SharerBackups can only be shared among domains in the same", + "des":"You can share server or disk backups with domains. Shared backups can be used to create servers or disks.SharerBackups can only be shared among domains in the same region", "doc_type":"usermanual", "kw":"Sharing a Backup,Backup Management,User Guide", "search_title":"", @@ -650,66 +650,12 @@ "title":"Deleting a Backup", "githuburl":"" }, - { - "uri":"cbr_03_0016.html", - "node_id":"cbr_03_0016.xml", - "product_code":"cbr", - "code":"37", - "des":"CBR allows you to create images using ECS backups. You can use the images to provision ECSs to rapidly restore service running environments.You can also use server backup", - "doc_type":"usermanual", - "kw":"Using a Backup to Create an Image,Backup Management,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"cbr", - "documenttype":"usermanual" - } - ], - "title":"Using a Backup to Create an Image", - "githuburl":"" - }, - { - "uri":"cbr_03_0017.html", - "node_id":"cbr_03_0017.xml", - "product_code":"cbr", - "code":"38", - "des":"You can create new disks from backups. Once created, the new disks will contain the backup data.The new disks created using system disk backups can only be used as data d", - "doc_type":"usermanual", - "kw":"Using a Backup to Create a Disk,Backup Management,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"cbr", - "documenttype":"usermanual" - } - ], - "title":"Using a Backup to Create a Disk", - "githuburl":"" - }, - { - "uri":"cbr_03_0107.html", - "node_id":"cbr_03_0107.xml", - "product_code":"cbr", - "code":"39", - "des":"In case of a virus attack, accidental deletion, or software or hardware fault, you can use an SFS Turbo file system backup to create a new file system. Once created, data", - "doc_type":"usermanual", - "kw":"Using a Backup to Create a File System,Backup Management,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"cbr", - "documenttype":"usermanual" - } - ], - "title":"Using a Backup to Create a File System", - "githuburl":"" - }, { "uri":"cbr_03_0018.html", "node_id":"cbr_03_0018.xml", "product_code":"cbr", - "code":"40", - "des":"CBR enables you to replicate backups of server backup vaults from one region to another.Replicas of server backups can be used to create images and provision servers.With", + "code":"37", + "des":"Cross-region replication of server backup vaults allows you to replicate backups from one region to another under the same account.Replicas of server backups can be used ", "doc_type":"usermanual", "kw":"Replicating a Backup Across Regions,Backup Management,User Guide", "search_title":"", @@ -726,7 +672,7 @@ "uri":"cbr_03_0024.html", "node_id":"cbr_03_0024.xml", "product_code":"cbr", - "code":"41", + "code":"38", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Policy Management", @@ -744,7 +690,7 @@ "uri":"cbr_03_0025.html", "node_id":"cbr_03_0025.xml", "product_code":"cbr", - "code":"42", + "code":"39", "des":"A backup policy allows CBR to automatically back up vaults at specified times or intervals. Periodic backups can be used to restore data quickly against data corruption o", "doc_type":"usermanual", "kw":"Creating a Backup Policy,Policy Management,User Guide", @@ -762,7 +708,7 @@ "uri":"cbr_03_0026.html", "node_id":"cbr_03_0026.xml", "product_code":"cbr", - "code":"43", + "code":"40", "des":"A replication policy allows CBR to periodically replicate backups that have not been replicated or failed to be replicated to the destination region.When a backup time an", "doc_type":"usermanual", "kw":"Creating a Replication Policy,Policy Management,User Guide", @@ -780,8 +726,8 @@ "uri":"cbr_03_0027.html", "node_id":"cbr_03_0027.xml", "product_code":"cbr", - "code":"44", - "des":"You can modify a policy to better suit your services.At least one policy has been created.Log in to the management console.Click in the upper left corner and select a re", + "code":"41", + "des":"You can modify backup policies if needed.At least one policy has been created.Log in to the management console.Click in the upper left corner and select a region.Click ", "doc_type":"usermanual", "kw":"Modifying a Policy,Policy Management,User Guide", "search_title":"", @@ -798,7 +744,7 @@ "uri":"cbr_03_0028.html", "node_id":"cbr_03_0028.xml", "product_code":"cbr", - "code":"45", + "code":"42", "des":"You can delete policies if they are no longer needed.At least one policy has been created.Log in to the management console.Click in the upper left corner and select a re", "doc_type":"usermanual", "kw":"Deleting a Policy,Policy Management,User Guide", @@ -816,8 +762,8 @@ "uri":"cbr_03_0029.html", "node_id":"cbr_03_0029.xml", "product_code":"cbr", - "code":"46", - "des":"You can apply a backup policy to a vault to execute backup tasks at specified times or intervals.Log in to the management console.Click in the upper left corner and sele", + "code":"43", + "des":"You can apply a backup policy to a vault to execute backup tasks at specified times or intervals.You can create multiple policies, but a can apply only one backup policy", "doc_type":"usermanual", "kw":"Applying a Policy to a Vault,Policy Management,User Guide", "search_title":"", @@ -834,8 +780,8 @@ "uri":"cbr_03_0030.html", "node_id":"cbr_03_0030.xml", "product_code":"cbr", - "code":"47", - "des":"If you no longer need automatic backup for a vault, remove the policy from the vault.A policy has been applied to the vault.Log in to the management console.Click in the", + "code":"44", + "des":"If you need to cancel auto backup of a vault, remove the policy from the vault, or disable the policy. This section describes how to remove a policy from a vault.A policy", "doc_type":"usermanual", "kw":"Removing a Policy from a Vault,Policy Management,User Guide", "search_title":"", @@ -852,7 +798,7 @@ "uri":"cbr_03_0031.html", "node_id":"cbr_03_0031.xml", "product_code":"cbr", - "code":"48", + "code":"45", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Restoring Data", @@ -870,8 +816,8 @@ "uri":"cbr_03_0032.html", "node_id":"cbr_03_0032.xml", "product_code":"cbr", - "code":"49", - "des":"When disks on a server are faulty or their data is lost, you can use a backup to restore the server to its state when the backup was created.When restoring from a cloud s", + "code":"46", + "des":"When disks on a server are faulty or their data is lost, you can use a backup to restore the server to its state when the backup was created.The system shuts down the ser", "doc_type":"usermanual", "kw":"Restoring from a Cloud Server Backup,Restoring Data,User Guide", "search_title":"", @@ -884,12 +830,30 @@ "title":"Restoring from a Cloud Server Backup", "githuburl":"" }, + { + "uri":"cbr_03_0016.html", + "node_id":"cbr_03_0016.xml", + "product_code":"cbr", + "code":"47", + "des":"CBR allows you to create images using ECS backups. You can use the images to provision ECSs to rapidly restore service running environments.You can also use server backup", + "doc_type":"usermanual", + "kw":"Creating an Image from a Cloud Server Backup,Restoring Data,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cbr", + "documenttype":"usermanual" + } + ], + "title":"Creating an Image from a Cloud Server Backup", + "githuburl":"" + }, { "uri":"cbr_03_0033.html", "node_id":"cbr_03_0033.xml", "product_code":"cbr", - "code":"50", - "des":"You can use a disk backup to restore the disk to its state when the backup was created.The disk to be restored is Available.Before restoring the disk data, stop the serve", + "code":"48", + "des":"You can use a disk backup to restore the disk to its state when the backup was created.Before restoring the disk data, stop the server to which the disk is attached and d", "doc_type":"usermanual", "kw":"Restoring from a Cloud Disk Backup,Restoring Data,User Guide", "search_title":"", @@ -902,6 +866,42 @@ "title":"Restoring from a Cloud Disk Backup", "githuburl":"" }, + { + "uri":"cbr_03_0017.html", + "node_id":"cbr_03_0017.xml", + "product_code":"cbr", + "code":"49", + "des":"You can use a disk backup to create a disk that contains the same data as the backup.Disks created using system disk backups can only be used as data disks on servers. Th", + "doc_type":"usermanual", + "kw":"Creating a Disk from a Cloud Disk Backup,Restoring Data,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cbr", + "documenttype":"usermanual" + } + ], + "title":"Creating a Disk from a Cloud Disk Backup", + "githuburl":"" + }, + { + "uri":"cbr_03_0107.html", + "node_id":"cbr_03_0107.xml", + "product_code":"cbr", + "code":"50", + "des":"In case of a virus attack, accidental deletion, or software or hardware fault, you can use an SFS Turbo file system backup to create a new file system. Once created, data", + "doc_type":"usermanual", + "kw":"Creating a File System from an SFS Turbo Backup,Restoring Data,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cbr", + "documenttype":"usermanual" + } + ], + "title":"Creating a File System from an SFS Turbo Backup", + "githuburl":"" + }, { "uri":"cbr_03_0104.html", "node_id":"cbr_03_0104.xml", @@ -945,7 +945,7 @@ "code":"53", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Monitoring", + "kw":"Cloud Eye Monitoring", "search_title":"", "metedata":[ { @@ -953,7 +953,7 @@ "documenttype":"usermanual" } ], - "title":"Monitoring", + "title":"Cloud Eye Monitoring", "githuburl":"" }, { @@ -963,7 +963,7 @@ "code":"54", "des":"This section describes metrics reported by CBR as well as their namespaces and dimensions. You can use the console or APIs provided by Cloud Eye to query the metrics gene", "doc_type":"usermanual", - "kw":"CBR Metrics,Monitoring,User Guide", + "kw":"Viewing Basic CBR Monitoring Data,Cloud Eye Monitoring,User Guide", "search_title":"", "metedata":[ { @@ -971,7 +971,7 @@ "documenttype":"usermanual" } ], - "title":"CBR Metrics", + "title":"Viewing Basic CBR Monitoring Data", "githuburl":"" }, { @@ -981,7 +981,7 @@ "code":"55", "des":"Cloud Eye allows you to use alarm templates to create alarm rules, making it easy and convenient to add or modify alarm rules for resources or cloud services, especially ", "doc_type":"usermanual", - "kw":"Creating an Alarm Rule,Monitoring,User Guide", + "kw":"Creating an Alarm Rule,Cloud Eye Monitoring,User Guide", "search_title":"", "metedata":[ { @@ -999,7 +999,7 @@ "code":"56", "des":"You can use Cloud Trace Service (CTS) to trace operations in CBR.CTS has been enabled.For how to view audit logs, see section \"Querying Real-Time Traces\" in the Cloud Tra", "doc_type":"usermanual", - "kw":"Auditing,User Guide", + "kw":"Recording CBR Operations Using CTS,User Guide", "search_title":"", "metedata":[ { @@ -1007,7 +1007,7 @@ "documenttype":"usermanual" } ], - "title":"Auditing", + "title":"Recording CBR Operations Using CTS", "githuburl":"" }, { @@ -1069,7 +1069,7 @@ "node_id":"cbr_06_0003.xml", "product_code":"cbr", "code":"60", - "des":"CBR by default performs a full backup for a resource in the initial backup and incremental backups in all subsequent backups. If a resource has been backed up for many ti", + "des":"A full backup backs up all data at a certain time point.An incremental backup backs up the changed data since the last full or incremental backup.CBR uses the permanent i", "doc_type":"usermanual", "kw":"What Are Full Backup and Incremental Backup?,Concepts,User Guide", "search_title":"", @@ -1118,11 +1118,29 @@ "title":"What Are the Differences Between Backups and Snapshots?", "githuburl":"" }, + { + "uri":"cbr_06_00110.html", + "node_id":"cbr_06_00110.xml", + "product_code":"cbr", + "code":"63", + "des":"There were files on a server, and the server was backed up. After deleting some files, the server was backed up again. By viewing the used vault capacity, we came to a co", + "doc_type":"usermanual", + "kw":"Why Is My Backup Size Larger Than My Disk Size?,Concepts,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cbr", + "documenttype":"usermanual" + } + ], + "title":"Why Is My Backup Size Larger Than My Disk Size?", + "githuburl":"" + }, { "uri":"cbr_06_0054.html", "node_id":"cbr_06_0054.xml", "product_code":"cbr", - "code":"63", + "code":"64", "des":"Table 1 describes the differences between cloud server backup and cloud disk backup.", "doc_type":"usermanual", "kw":"What Are the Differences Between Cloud Server Backup and Cloud Disk Backup?,Concepts,User Guide", @@ -1140,7 +1158,7 @@ "uri":"cbr_06_0006.html", "node_id":"cbr_06_0006.xml", "product_code":"cbr", - "code":"64", + "code":"65", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Backup", @@ -1158,8 +1176,8 @@ "uri":"cbr_06_0007.html", "node_id":"cbr_06_0007.xml", "product_code":"cbr", - "code":"65", - "des":"No. You can back up servers that are in use. When a server is running, data is written into disks on the server, and some newly generated data is cached in the server mem", + "code":"66", + "des":"No. You can back up servers that are in use.When a server is running, data is written into disks on the server, and some newly generated data is cached in the server memo", "doc_type":"usermanual", "kw":"Do I Need to Stop the Server Before Performing a Backup?,Backup,User Guide", "search_title":"", @@ -1176,7 +1194,7 @@ "uri":"cbr_06_0008.html", "node_id":"cbr_06_0008.xml", "product_code":"cbr", - "code":"66", + "code":"67", "des":"Yes. To back up applications requiring strict consistency, such as databases and email systems, you are advised to suspend all write operations and then perform backup. I", "doc_type":"usermanual", "kw":"Can I Back Up a Server Deployed with Databases?,Backup,User Guide", @@ -1194,7 +1212,7 @@ "uri":"cbr_06_0009.html", "node_id":"cbr_06_0009.xml", "product_code":"cbr", - "code":"67", + "code":"68", "des":"They can be distinguished by name prefix:Automatic backups: autobk_xxxxManual backups: manualbk_xxxx or custom names", "doc_type":"usermanual", "kw":"How Can I Distinguish Automatic Backups From Manual Backups?,Backup,User Guide", @@ -1212,7 +1230,7 @@ "uri":"cbr_06_0010.html", "node_id":"cbr_06_0010.xml", "product_code":"cbr", - "code":"68", + "code":"69", "des":"No. The minimum backup granularity supported by CBR is disks.", "doc_type":"usermanual", "kw":"Can I Choose to Back Up Only Some Partitions of a Disk?,Backup,User Guide", @@ -1230,8 +1248,8 @@ "uri":"cbr_06_0011.html", "node_id":"cbr_06_0011.xml", "product_code":"cbr", - "code":"69", - "des":"No. CBR supports only backup and restoration within a region but not across regions.", + "code":"70", + "des":"No. CBR supports only backup and restoration within a region but not across regions.You can replicate backups in either of the following methods on the CBR console:Select", "doc_type":"usermanual", "kw":"Does CBR Support Cross-Region Backup?,Backup,User Guide", "search_title":"", @@ -1248,7 +1266,7 @@ "uri":"cbr_06_0053.html", "node_id":"cbr_06_0053.xml", "product_code":"cbr", - "code":"70", + "code":"71", "des":"No. Backups are not stored on a server. Therefore, deleting its backups has no impact on the server performance.", "doc_type":"usermanual", "kw":"Will the Server Performance Be Affected If I Delete Its Backups?,Backup,User Guide", @@ -1266,7 +1284,7 @@ "uri":"cbr_06_0055.html", "node_id":"cbr_06_0055.xml", "product_code":"cbr", - "code":"71", + "code":"72", "des":"Yes. Resources and backups are not stored together. If a resource is deleted, its backup still stays in your CBR vault. You can use the backup to restore the resource to ", "doc_type":"usermanual", "kw":"Can I Use Its Backup for Restoration After a Resource Is Deleted?,Backup,User Guide", @@ -1284,7 +1302,7 @@ "uri":"cbr_06_0056.html", "node_id":"cbr_06_0056.xml", "product_code":"cbr", - "code":"72", + "code":"73", "des":"You can create as many backups for a resource as needed.", "doc_type":"usermanual", "kw":"How Many Backups Can I Create for a Resource?,Backup,User Guide", @@ -1302,7 +1320,7 @@ "uri":"cbr_06_0062.html", "node_id":"cbr_06_0062.xml", "product_code":"cbr", - "code":"73", + "code":"74", "des":"No. An ongoing backup task cannot be stopped.", "doc_type":"usermanual", "kw":"Can I Stop an Ongoing Backup Task?,Backup,User Guide", @@ -1316,24 +1334,6 @@ "title":"Can I Stop an Ongoing Backup Task?", "githuburl":"" }, - { - "uri":"cbr_06_0026.html", - "node_id":"cbr_06_0026.xml", - "product_code":"cbr", - "code":"74", - "des":"There is no difference or an increase in size between the original backup and a backup generated after a file is deleted.The ECS backup size is larger than the used disk ", - "doc_type":"usermanual", - "kw":"Why Is My Backup Size Larger Than My Disk Size?,FAQs,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"cbr", - "documenttype":"usermanual" - } - ], - "title":"Why Is My Backup Size Larger Than My Disk Size?", - "githuburl":"" - }, { "uri":"cbr_06_0012.html", "node_id":"cbr_06_0012.xml", @@ -1429,7 +1429,7 @@ "node_id":"cbr_06_0017.xml", "product_code":"cbr", "code":"80", - "des":"Yes. After restoration, the capacity of the expanded disk goes back to the original capacity before expansion. If you want to use the capacity added to the disk, you need", + "des":"Yes. After restoration, the capacity of the expanded disk goes back to the original capacity before expansion.If you want to use the capacity added to the disk, you need ", "doc_type":"usermanual", "kw":"Can a Disk Be Restored Using Its Backups After Its Capacity Is Expanded?,Restoration,User Guide", "search_title":"", @@ -1713,8 +1713,8 @@ "githuburl":"" }, { - "uri":"cbr_03_0046.html", - "node_id":"cbr_03_0046.xml", + "uri":"cbr_03_0160.html", + "node_id":"cbr_03_0160.xml", "product_code":"cbr", "code":"96", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", diff --git a/docs/cbr/umn/CLASS.TXT.json b/docs/cbr/umn/CLASS.TXT.json index 1f4b347a..8a197cc2 100644 --- a/docs/cbr/umn/CLASS.TXT.json +++ b/docs/cbr/umn/CLASS.TXT.json @@ -171,7 +171,7 @@ "code":"19" }, { - "desc":"This section describes how to quickly create a cloud disk backup.Backing up a server does not impact the disk performance.Peak hours of the backup service are from 00:00 ", + "desc":"This section describes how to quickly create a cloud disk backup.Backing up a server does not impact the disk performance.Peak hours of the backup service are from 22:00 ", "product_code":"cbr", "title":"Creating a Cloud Disk Backup", "uri":"cbr_02_0007.html", @@ -198,7 +198,7 @@ "code":"22" }, { - "desc":"This section describes how to use IAM to implement fine-grained permissions control for your CBR resources. With IAM, you can:Create IAM users for employees based on your", + "desc":"This section describes how to use IAM to implement fine-grained permissions control for your CBR resources. With IAM, you can:Create IAM users for personnel based on your", "product_code":"cbr", "title":"Creating a User and Granting CBR Permissions", "uri":"cbr_03_0048.html", @@ -245,7 +245,7 @@ { "desc":"If you no longer need to back up an associated resource, dissociate it from your vault.After a resource is dissociated, the vault's backup policy no longer applies to the", "product_code":"cbr", - "title":"Dissociating a Resource", + "title":"Dissociating Resources from a Vault", "uri":"cbr_03_0005.html", "doc_type":"usermanual", "p_code":"25", @@ -254,7 +254,7 @@ { "desc":"Migrating a resource means that you dissociate a resource from a vault and then associate it to another vault. All backups of the resource will be migrated to the destina", "product_code":"cbr", - "title":"Migrating a Resource", + "title":"Migrating Resources from a Vault", "uri":"cbr_03_0116.html", "doc_type":"usermanual", "p_code":"25", @@ -270,9 +270,9 @@ "code":"30" }, { - "desc":"CBR allows you to replicate server backup vaults entirely to replication vaults in a different region. Replicas of server backups in the destination region can be used to", + "desc":"CBR allows you to replicate server backup vaults entirely to replication vaults in other regions of the same account. Replicas of server backups in the destination region", "product_code":"cbr", - "title":"Replicating a Vault", + "title":"Replicating a Vault Across Regions", "uri":"cbr_03_0009.html", "doc_type":"usermanual", "p_code":"25", @@ -306,7 +306,7 @@ "code":"34" }, { - "desc":"You can share a server or disk backup with other domains. Shared backups can be used to create servers or disks.SharerBackups can only be shared among domains in the same", + "desc":"You can share server or disk backups with domains. Shared backups can be used to create servers or disks.SharerBackups can only be shared among domains in the same region", "product_code":"cbr", "title":"Sharing a Backup", "uri":"cbr_03_0014.html", @@ -324,40 +324,13 @@ "code":"36" }, { - "desc":"CBR allows you to create images using ECS backups. You can use the images to provision ECSs to rapidly restore service running environments.You can also use server backup", - "product_code":"cbr", - "title":"Using a Backup to Create an Image", - "uri":"cbr_03_0016.html", - "doc_type":"usermanual", - "p_code":"33", - "code":"37" - }, - { - "desc":"You can create new disks from backups. Once created, the new disks will contain the backup data.The new disks created using system disk backups can only be used as data d", - "product_code":"cbr", - "title":"Using a Backup to Create a Disk", - "uri":"cbr_03_0017.html", - "doc_type":"usermanual", - "p_code":"33", - "code":"38" - }, - { - "desc":"In case of a virus attack, accidental deletion, or software or hardware fault, you can use an SFS Turbo file system backup to create a new file system. Once created, data", - "product_code":"cbr", - "title":"Using a Backup to Create a File System", - "uri":"cbr_03_0107.html", - "doc_type":"usermanual", - "p_code":"33", - "code":"39" - }, - { - "desc":"CBR enables you to replicate backups of server backup vaults from one region to another.Replicas of server backups can be used to create images and provision servers.With", + "desc":"Cross-region replication of server backup vaults allows you to replicate backups from one region to another under the same account.Replicas of server backups can be used ", "product_code":"cbr", "title":"Replicating a Backup Across Regions", "uri":"cbr_03_0018.html", "doc_type":"usermanual", "p_code":"33", - "code":"40" + "code":"37" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -366,7 +339,7 @@ "uri":"cbr_03_0024.html", "doc_type":"usermanual", "p_code":"", - "code":"41" + "code":"38" }, { "desc":"A backup policy allows CBR to automatically back up vaults at specified times or intervals. Periodic backups can be used to restore data quickly against data corruption o", @@ -374,8 +347,8 @@ "title":"Creating a Backup Policy", "uri":"cbr_03_0025.html", "doc_type":"usermanual", - "p_code":"41", - "code":"42" + "p_code":"38", + "code":"39" }, { "desc":"A replication policy allows CBR to periodically replicate backups that have not been replicated or failed to be replicated to the destination region.When a backup time an", @@ -383,17 +356,17 @@ "title":"Creating a Replication Policy", "uri":"cbr_03_0026.html", "doc_type":"usermanual", - "p_code":"41", - "code":"43" + "p_code":"38", + "code":"40" }, { - "desc":"You can modify a policy to better suit your services.At least one policy has been created.Log in to the management console.Click in the upper left corner and select a re", + "desc":"You can modify backup policies if needed.At least one policy has been created.Log in to the management console.Click in the upper left corner and select a region.Click ", "product_code":"cbr", "title":"Modifying a Policy", "uri":"cbr_03_0027.html", "doc_type":"usermanual", - "p_code":"41", - "code":"44" + "p_code":"38", + "code":"41" }, { "desc":"You can delete policies if they are no longer needed.At least one policy has been created.Log in to the management console.Click in the upper left corner and select a re", @@ -401,26 +374,26 @@ "title":"Deleting a Policy", "uri":"cbr_03_0028.html", "doc_type":"usermanual", - "p_code":"41", - "code":"45" + "p_code":"38", + "code":"42" }, { - "desc":"You can apply a backup policy to a vault to execute backup tasks at specified times or intervals.Log in to the management console.Click in the upper left corner and sele", + "desc":"You can apply a backup policy to a vault to execute backup tasks at specified times or intervals.You can create multiple policies, but a can apply only one backup policy", "product_code":"cbr", "title":"Applying a Policy to a Vault", "uri":"cbr_03_0029.html", "doc_type":"usermanual", - "p_code":"41", - "code":"46" + "p_code":"38", + "code":"43" }, { - "desc":"If you no longer need automatic backup for a vault, remove the policy from the vault.A policy has been applied to the vault.Log in to the management console.Click in the", + "desc":"If you need to cancel auto backup of a vault, remove the policy from the vault, or disable the policy. This section describes how to remove a policy from a vault.A policy", "product_code":"cbr", "title":"Removing a Policy from a Vault", "uri":"cbr_03_0030.html", "doc_type":"usermanual", - "p_code":"41", - "code":"47" + "p_code":"38", + "code":"44" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -429,24 +402,51 @@ "uri":"cbr_03_0031.html", "doc_type":"usermanual", "p_code":"", - "code":"48" + "code":"45" }, { - "desc":"When disks on a server are faulty or their data is lost, you can use a backup to restore the server to its state when the backup was created.When restoring from a cloud s", + "desc":"When disks on a server are faulty or their data is lost, you can use a backup to restore the server to its state when the backup was created.The system shuts down the ser", "product_code":"cbr", "title":"Restoring from a Cloud Server Backup", "uri":"cbr_03_0032.html", "doc_type":"usermanual", - "p_code":"48", - "code":"49" + "p_code":"45", + "code":"46" }, { - "desc":"You can use a disk backup to restore the disk to its state when the backup was created.The disk to be restored is Available.Before restoring the disk data, stop the serve", + "desc":"CBR allows you to create images using ECS backups. You can use the images to provision ECSs to rapidly restore service running environments.You can also use server backup", + "product_code":"cbr", + "title":"Creating an Image from a Cloud Server Backup", + "uri":"cbr_03_0016.html", + "doc_type":"usermanual", + "p_code":"45", + "code":"47" + }, + { + "desc":"You can use a disk backup to restore the disk to its state when the backup was created.Before restoring the disk data, stop the server to which the disk is attached and d", "product_code":"cbr", "title":"Restoring from a Cloud Disk Backup", "uri":"cbr_03_0033.html", "doc_type":"usermanual", - "p_code":"48", + "p_code":"45", + "code":"48" + }, + { + "desc":"You can use a disk backup to create a disk that contains the same data as the backup.Disks created using system disk backups can only be used as data disks on servers. Th", + "product_code":"cbr", + "title":"Creating a Disk from a Cloud Disk Backup", + "uri":"cbr_03_0017.html", + "doc_type":"usermanual", + "p_code":"45", + "code":"49" + }, + { + "desc":"In case of a virus attack, accidental deletion, or software or hardware fault, you can use an SFS Turbo file system backup to create a new file system. Once created, data", + "product_code":"cbr", + "title":"Creating a File System from an SFS Turbo Backup", + "uri":"cbr_03_0107.html", + "doc_type":"usermanual", + "p_code":"45", "code":"50" }, { @@ -470,7 +470,7 @@ { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"cbr", - "title":"Monitoring", + "title":"Cloud Eye Monitoring", "uri":"cbr_03_0113.html", "doc_type":"usermanual", "p_code":"", @@ -479,7 +479,7 @@ { "desc":"This section describes metrics reported by CBR as well as their namespaces and dimensions. You can use the console or APIs provided by Cloud Eye to query the metrics gene", "product_code":"cbr", - "title":"CBR Metrics", + "title":"Viewing Basic CBR Monitoring Data", "uri":"cbr_03_0114.html", "doc_type":"usermanual", "p_code":"53", @@ -497,7 +497,7 @@ { "desc":"You can use Cloud Trace Service (CTS) to trace operations in CBR.CTS has been enabled.For how to view audit logs, see section \"Querying Real-Time Traces\" in the Cloud Tra", "product_code":"cbr", - "title":"Auditing", + "title":"Recording CBR Operations Using CTS", "uri":"cbr_03_0036.html", "doc_type":"usermanual", "p_code":"", @@ -531,7 +531,7 @@ "code":"59" }, { - "desc":"CBR by default performs a full backup for a resource in the initial backup and incremental backups in all subsequent backups. If a resource has been backed up for many ti", + "desc":"A full backup backs up all data at a certain time point.An incremental backup backs up the changed data since the last full or incremental backup.CBR uses the permanent i", "product_code":"cbr", "title":"What Are Full Backup and Incremental Backup?", "uri":"cbr_06_0003.html", @@ -557,6 +557,15 @@ "p_code":"59", "code":"62" }, + { + "desc":"There were files on a server, and the server was backed up. After deleting some files, the server was backed up again. By viewing the used vault capacity, we came to a co", + "product_code":"cbr", + "title":"Why Is My Backup Size Larger Than My Disk Size?", + "uri":"cbr_06_00110.html", + "doc_type":"usermanual", + "p_code":"59", + "code":"63" + }, { "desc":"Table 1 describes the differences between cloud server backup and cloud disk backup.", "product_code":"cbr", @@ -564,7 +573,7 @@ "uri":"cbr_06_0054.html", "doc_type":"usermanual", "p_code":"59", - "code":"63" + "code":"64" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -573,16 +582,16 @@ "uri":"cbr_06_0006.html", "doc_type":"usermanual", "p_code":"58", - "code":"64" + "code":"65" }, { - "desc":"No. You can back up servers that are in use. When a server is running, data is written into disks on the server, and some newly generated data is cached in the server mem", + "desc":"No. You can back up servers that are in use.When a server is running, data is written into disks on the server, and some newly generated data is cached in the server memo", "product_code":"cbr", "title":"Do I Need to Stop the Server Before Performing a Backup?", "uri":"cbr_06_0007.html", "doc_type":"usermanual", - "p_code":"64", - "code":"65" + "p_code":"65", + "code":"66" }, { "desc":"Yes. To back up applications requiring strict consistency, such as databases and email systems, you are advised to suspend all write operations and then perform backup. I", @@ -590,8 +599,8 @@ "title":"Can I Back Up a Server Deployed with Databases?", "uri":"cbr_06_0008.html", "doc_type":"usermanual", - "p_code":"64", - "code":"66" + "p_code":"65", + "code":"67" }, { "desc":"They can be distinguished by name prefix:Automatic backups: autobk_xxxxManual backups: manualbk_xxxx or custom names", @@ -599,8 +608,8 @@ "title":"How Can I Distinguish Automatic Backups From Manual Backups?", "uri":"cbr_06_0009.html", "doc_type":"usermanual", - "p_code":"64", - "code":"67" + "p_code":"65", + "code":"68" }, { "desc":"No. The minimum backup granularity supported by CBR is disks.", @@ -608,17 +617,17 @@ "title":"Can I Choose to Back Up Only Some Partitions of a Disk?", "uri":"cbr_06_0010.html", "doc_type":"usermanual", - "p_code":"64", - "code":"68" + "p_code":"65", + "code":"69" }, { - "desc":"No. CBR supports only backup and restoration within a region but not across regions.", + "desc":"No. CBR supports only backup and restoration within a region but not across regions.You can replicate backups in either of the following methods on the CBR console:Select", "product_code":"cbr", "title":"Does CBR Support Cross-Region Backup?", "uri":"cbr_06_0011.html", "doc_type":"usermanual", - "p_code":"64", - "code":"69" + "p_code":"65", + "code":"70" }, { "desc":"No. Backups are not stored on a server. Therefore, deleting its backups has no impact on the server performance.", @@ -626,8 +635,8 @@ "title":"Will the Server Performance Be Affected If I Delete Its Backups?", "uri":"cbr_06_0053.html", "doc_type":"usermanual", - "p_code":"64", - "code":"70" + "p_code":"65", + "code":"71" }, { "desc":"Yes. Resources and backups are not stored together. If a resource is deleted, its backup still stays in your CBR vault. You can use the backup to restore the resource to ", @@ -635,8 +644,8 @@ "title":"Can I Use Its Backup for Restoration After a Resource Is Deleted?", "uri":"cbr_06_0055.html", "doc_type":"usermanual", - "p_code":"64", - "code":"71" + "p_code":"65", + "code":"72" }, { "desc":"You can create as many backups for a resource as needed.", @@ -644,8 +653,8 @@ "title":"How Many Backups Can I Create for a Resource?", "uri":"cbr_06_0056.html", "doc_type":"usermanual", - "p_code":"64", - "code":"72" + "p_code":"65", + "code":"73" }, { "desc":"No. An ongoing backup task cannot be stopped.", @@ -653,16 +662,7 @@ "title":"Can I Stop an Ongoing Backup Task?", "uri":"cbr_06_0062.html", "doc_type":"usermanual", - "p_code":"64", - "code":"73" - }, - { - "desc":"There is no difference or an increase in size between the original backup and a backup generated after a file is deleted.The ECS backup size is larger than the used disk ", - "product_code":"cbr", - "title":"Why Is My Backup Size Larger Than My Disk Size?", - "uri":"cbr_06_0026.html", - "doc_type":"usermanual", - "p_code":"58", + "p_code":"65", "code":"74" }, { @@ -711,7 +711,7 @@ "code":"79" }, { - "desc":"Yes. After restoration, the capacity of the expanded disk goes back to the original capacity before expansion. If you want to use the capacity added to the disk, you need", + "desc":"Yes. After restoration, the capacity of the expanded disk goes back to the original capacity before expansion.If you want to use the capacity added to the disk, you need ", "product_code":"cbr", "title":"Can a Disk Be Restored Using Its Backups After Its Capacity Is Expanded?", "uri":"cbr_06_0017.html", @@ -858,7 +858,7 @@ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"cbr", "title":"Change History", - "uri":"cbr_03_0046.html", + "uri":"cbr_03_0160.html", "doc_type":"usermanual", "p_code":"95", "code":"96" diff --git a/docs/cbr/umn/cbr_01_0002.html b/docs/cbr/umn/cbr_01_0002.html index b9b3bc11..5b20540c 100644 --- a/docs/cbr/umn/cbr_01_0002.html +++ b/docs/cbr/umn/cbr_01_0002.html @@ -5,13 +5,13 @@

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. There are the following types of backups:

+

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:

Vault

-

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.

-

-

Vaults can be either backup vaults or replication vaults. Backup vaults store resource backups, and replication vaults store backup replicas.

-

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.

+

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

There are backup policies and replication policies.

@@ -30,7 +30,7 @@

What to back up

-

All disks (system and data disks) on a server

+

All disks (system and data disks) on a server or part of disks

One or more specific disks (system or data disks)

@@ -60,7 +60,7 @@

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 a backup is deleted, data blocks will not be deleted if they are 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.

@@ -114,6 +114,7 @@

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.

+

Theoretically, you can create as many backups for a resource as needed. This number is not limited.

Figure 2 Use of the two backup options

Access to CBR

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

@@ -131,7 +132,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_01_0003.html b/docs/cbr/umn/cbr_01_0003.html index 76bf75fe..18846349 100644 --- a/docs/cbr/umn/cbr_01_0003.html +++ b/docs/cbr/umn/cbr_01_0003.html @@ -19,31 +19,36 @@

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

-   +

Cloud disk backup

+

Policy-based backup

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

-   +

Cloud disk backup

+

Backup management

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.

-   +

Cloud disk backup

+

Disk restoration using backups

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

-   +

Cloud disk backup

+

Disk creation using backups

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

-   +

Cloud disk backup

+

Sharing a Backup

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

@@ -53,34 +58,39 @@

Manual server backup

-

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

+

Cloud server backup uses the consistency snapshot technology to protect data for ECSs without the need to install the Agent. You can use CBR to back up an entire server to protect their data.

-   +

Cloud server backup

+

Policy-based backup

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

-   +

Cloud server backup

+

Backup management

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.

-   +

Cloud server backup

+

Server restoration using backups

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

-   +

Cloud server backup

+

Sharing a Backup

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

-   +

Cloud server backup

+

Image creation using server backups

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

@@ -93,19 +103,22 @@

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

-   +

SFS Turbo backup

+

Policy-based backup

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

-   +

SFS Turbo backup

+

Backup management

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.

-   +

SFS Turbo backup

+

File system creation using backups

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

diff --git a/docs/cbr/umn/cbr_01_0005.html b/docs/cbr/umn/cbr_01_0005.html index 66bf40b2..e2c3eafd 100644 --- a/docs/cbr/umn/cbr_01_0005.html +++ b/docs/cbr/umn/cbr_01_0005.html @@ -16,7 +16,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_01_0006.html b/docs/cbr/umn/cbr_01_0006.html index dbcc7e94..946afa79 100644 --- a/docs/cbr/umn/cbr_01_0006.html +++ b/docs/cbr/umn/cbr_01_0006.html @@ -43,7 +43,7 @@

CTS

-

Auditing

+

Recording CBR Operations Using CTS

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

diff --git a/docs/cbr/umn/cbr_01_0008.html b/docs/cbr/umn/cbr_01_0008.html index fe093d3e..1ce26b5f 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.

-

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 6006324d..30f66aac 100644 --- a/docs/cbr/umn/cbr_01_0009.html +++ b/docs/cbr/umn/cbr_01_0009.html @@ -6,8 +6,7 @@

Cloud Disk Backup

  • Only disks in the Available or In-use state can be backed up.
  • Frozen disks in the retention period cannot be backed up.
  • A new disk must be at least as large as the backup's source disk.
  • Cloud disk backups cannot be replicated to other regions.

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.
  • Frozen servers in the retention period cannot be backed up.
  • 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.
  • Backups can be replicated only to regions that have replication capabilities.
    • A backup can be replicated only when it meets all of the following conditions:
      1. It is an ECS backup.
      2. It contains system disk data.
      3. It is in the Available state.
      -
    • Only backups can be replicated. Backup replicas cannot be replicated again but can be used to create images.
    • A backup can be replicated to multiple regions but can have only one replica in each destination region. The replication rule varies with the replication method:
      • Manual replication: A backup can be replicated to the destination region as long as it has no replica in that region. A backup can be replicated again if its replica in the destination region has been deleted.
      • Policy-based replication: A backup can only be automatically replicated to a destination region once. It cannot be automatically replicated to that region again, even if its replica has been deleted.
      -
    • Only replication-supported regions can be selected as destination regions.
    +
  • Only backups can be replicated. Backup replicas cannot be replicated again but can be used to create images.
  • A backup can be replicated to multiple regions but can have only one replica in each destination region. Manual replication: A backup can be manually replicated to the destination region as long as it has no replica in that region. A backup can be manually replicated again if its replica in the destination region has been deleted.
  • Only replication-supported regions can be selected as destination regions.

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_0011.html b/docs/cbr/umn/cbr_01_0011.html index 256e1dbc..325d20b2 100644 --- a/docs/cbr/umn/cbr_01_0011.html +++ b/docs/cbr/umn/cbr_01_0011.html @@ -136,7 +136,7 @@

Not supported

-

Applying policies to a vault

+

Applying policies to vaults

Supported

@@ -145,7 +145,7 @@

Not supported

-

Removing policies from a vault

+

Removing policies from vaults

Supported

@@ -199,7 +199,7 @@

Not supported

-

Restoring data using backups

+

Restoring data from backups

Supported

diff --git a/docs/cbr/umn/cbr_01_0013.html b/docs/cbr/umn/cbr_01_0013.html index 44fa89b9..4aa41dab 100644 --- a/docs/cbr/umn/cbr_01_0013.html +++ b/docs/cbr/umn/cbr_01_0013.html @@ -10,7 +10,8 @@

Easy to Use

CBR is easier to use than conventional backup systems. You can complete backup in just three steps, and no professional backup skills are required.

-

Secure

  • If the disks are encrypted, their backups are also encrypted to ensure data security.
  • You can also replicate backups across regions to implement remote disaster recovery.
+

Secure

If the disks are encrypted, their backups are also encrypted to ensure data security.

+

You can also replicate backups across regions to implement remote disaster recovery.

diff --git a/docs/cbr/umn/cbr_02_0003.html b/docs/cbr/umn/cbr_02_0003.html index 931f7df8..ff4cb611 100644 --- a/docs/cbr/umn/cbr_02_0003.html +++ b/docs/cbr/umn/cbr_02_0003.html @@ -6,19 +6,20 @@

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

    • Backup: A server backup vault stores server backups.
    • Replication: A server replication vault stores replicas of server backups. If you select Replication, you do not need to select a server.

    For example, if you want to back up a server, select Backup for the vault protection type. If you want to replicate backups of a server from one region to another, select Replication for the vault in this other region.

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

    +

    If you want to back up only some of the disks to reduce costs, ensure that data on the backed up disks does not depend on the disks that are not backed up. Or, data inconsistency may occur.

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

    Figure 1 Selecting servers
    +

    -

    -

    +

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

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

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

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

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

  • Configure auto backup. See Figure 3.

    • If you select Configure, you must then select an existing backup policy or create a new policy. After the vault is created, CBR will apply the policy to this vault, and all servers associated with this vault will be automatically backed up based on this policy.
    • If you select Skip, servers associated with this vault will not be automatically backed up until you apply a backup policy to the vault.
    Figure 3 Configuring auto backup
    @@ -75,7 +76,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_02_0004.html b/docs/cbr/umn/cbr_02_0004.html index 2ea75d74..d79ddf98 100644 --- a/docs/cbr/umn/cbr_02_0004.html +++ b/docs/cbr/umn/cbr_02_0004.html @@ -4,14 +4,17 @@

    This section describes how to create a disk backup vault.

    Procedure

    1. Log in to the CBR console.

      1. Log in to the management console.
      2. Click in the upper left corner and select a region.
      3. Click and choose Storage > Cloud Backup and Recovery. Select a backup type 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 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 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
      +

    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. 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
      @@ -70,7 +73,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_02_0006.html b/docs/cbr/umn/cbr_02_0006.html index fb14f11b..97e81dda 100644 --- a/docs/cbr/umn/cbr_02_0006.html +++ b/docs/cbr/umn/cbr_02_0006.html @@ -4,20 +4,22 @@

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

      -

      Peak hours of the backup service are from 00:00 to 06:00, during which backup schedules may be delayed. So you are advised to evaluate your service types and schedule backups outside of the backup peak hours.

      +

      Peak hours of the backup service are from 22:00 to 08:00, during which there may be delays. So you are advised to evaluate your service types and schedule backups in discrete time periods.

      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 the CBR console.

        1. Log in to the management console.
        2. Click in the upper left corner and select a region.
        3. Click and choose Storage > Cloud Backup and Recovery. Select a backup type 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. Perform backup in either of the following ways:

        • Choose More > Perform Backup in the Operation column. In the server list, select the server you want to back up. After a server is selected, it is added to the list of selected servers. See Figure 1.
          Figure 1 Selecting the server to be backed up
          +

          +

        -

        -

        -

        +

        • Click the vault name to go to the vault details page. On the Associated Servers tab page, locate the target server and click Perform Backup in the Operation column. See Figure 2.
          Figure 2 Perform Backup
          +

          -

          +

          +

          @@ -58,7 +60,7 @@

        • Click OK. 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.

          A server can be restarted if the backup progress exceeds 10%. However, to ensure data integrity, 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 from a Cloud Server Backup and Using a Backup to Create an Image.

          +

          After the backup is complete, you can use the backup to restore server data or create an image. For details, see Restoring from a Cloud Server Backup and Creating an Image from a Cloud Server Backup.

      @@ -71,7 +73,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_02_0007.html b/docs/cbr/umn/cbr_02_0007.html index 167c4214..7ac3bf14 100644 --- a/docs/cbr/umn/cbr_02_0007.html +++ b/docs/cbr/umn/cbr_02_0007.html @@ -3,18 +3,19 @@

      Creating a Cloud Disk Backup

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

      Backing up a server does not impact the disk performance.

      -

      Peak hours of the backup service are from 00:00 to 06:00, during which backup schedules may be delayed. So you are advised to evaluate your service types and schedule backups outside of the backup peak hours.

      +

      Peak hours of the backup service are from 22:00 to 08:00, during which there may be delays. So you are advised to evaluate your service types and schedule backups in discrete time periods.

      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 the CBR console.

        1. Log in to the management console.
        2. Click in the upper left corner and select a region.
        3. Click and choose Storage > Cloud Backup and Recovery. Select a backup type 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. Perform backup in either of the following ways:

        • Click Perform Backup in the Operation column. In the disk list, select the disk you want to back up. After a disk is selected, it is added to the list of selected disks. See Figure 1.
          Figure 1 Selecting the disk to be backed up
          +

          +

        -

        -

        -

        +

        • Click the vault name to go to the vault details page. On the Associated Disks tab page, locate the target disk and click Perform Backup in the Operation column. See Figure 2.
          Figure 2 Perform Backup
          +

          @@ -72,7 +73,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_02_0009.html b/docs/cbr/umn/cbr_02_0009.html index a4c02f97..6b39a5af 100644 --- a/docs/cbr/umn/cbr_02_0009.html +++ b/docs/cbr/umn/cbr_02_0009.html @@ -33,9 +33,10 @@

          Procedure

          1. Log in to the CBR console.

            1. Log in to the management console.
            2. Click in the upper left corner and select a region.
            3. Click and choose Storage > Cloud Backup and Recovery. Select a backup type 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

            +

            -

            -

            +

            +

          4. Click OK. Then on the Associated Servers tab page, you can view the number of resources that have been 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.

            @@ -43,14 +44,16 @@

          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 both 40 GB and the associated capacity. 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.
          +
          • The vault's remaining capacity should be greater than both 40 GB and the associated capacity. The vault will automatically scan and associate unprotected servers in the next backup cycle and perform backup. Remaining capacity of a vault = Total capacity of the vault - Capacity of resources associated with the vault. 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, the vault will automatically associate unprotected servers in the next backup cycle and perform backup.
          • 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 the CBR console.

            1. Log in to the management console.
            2. Click in the upper left corner and select a region.
            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 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
            +

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

            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. Check that Automatic association is displayed in the Associated Servers column of the vault list.
          7. (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
            +

          @@ -65,7 +68,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_02_0010.html b/docs/cbr/umn/cbr_02_0010.html index 26a16afc..7e2846fd 100644 --- a/docs/cbr/umn/cbr_02_0010.html +++ b/docs/cbr/umn/cbr_02_0010.html @@ -6,8 +6,8 @@

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

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

        • (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 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.
          @@ -62,7 +62,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_02_0012.html b/docs/cbr/umn/cbr_02_0012.html index b5984699..232b5d83 100644 --- a/docs/cbr/umn/cbr_02_0012.html +++ b/docs/cbr/umn/cbr_02_0012.html @@ -3,18 +3,19 @@

          Creating an SFS Turbo Backup

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

          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.

          -

          Peak hours of the backup service are from 00:00 to 06:00, during which backup schedules may be delayed. So you are advised to evaluate your service types and schedule backups outside of the backup peak hours.

          +

          Peak hours of the backup service are from 22:00 to 08:00, during which there may be delays. So you are advised to evaluate your service types and schedule backups in discrete time periods.

          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 the CBR console.

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

          2. On the SFS Turbo Backups page, click the Vaults tab and find the vault to which the file system is associated.
          3. Perform backup in either of the following ways:

            • Choose More > Perform Backup in the Operation column. In the file system list, select the file system to be backed up. After a file system is selected, it is added to the list of selected file systems. See Figure 1.
              Figure 1 Selecting the file system to be backed up
              +

              +

            -

            -

            +

            • Click the vault name to go to the vault details page. On the Associated File Systems tab page, locate the target file system and click Perform Backup in the Operation column. See Figure 2.
              Figure 2 Perform Backup
              -

              +

              @@ -53,7 +54,7 @@

            • Click OK. 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. Therefore, to ensure data integrity, delete the target data after the backup is complete, and then perform the backup.

              -

              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.

              +

              After the backup is complete, you can create a new SFS Turbo file system using the backup. For details, see Creating a File System from an SFS Turbo Backup.

          @@ -66,7 +67,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0001.html b/docs/cbr/umn/cbr_03_0001.html index 8548b926..3dd86260 100644 --- a/docs/cbr/umn/cbr_03_0001.html +++ b/docs/cbr/umn/cbr_03_0001.html @@ -8,13 +8,13 @@
        • Deleting a Vault
          • -
        • Dissociating a Resource
          +
        • Dissociating Resources from a Vault
          • -
        • Migrating a Resource
          +
        • Migrating Resources from a Vault
        • Expanding Vault Capacity
          • -
        • Replicating a Vault
          +
        • Replicating a Vault Across Regions
        • Managing Vault Tags
          • diff --git a/docs/cbr/umn/cbr_03_0002.html b/docs/cbr/umn/cbr_03_0002.html index 5167b2f3..245b9e5d 100644 --- a/docs/cbr/umn/cbr_03_0002.html +++ b/docs/cbr/umn/cbr_03_0002.html @@ -5,96 +5,98 @@

          Prerequisites

          A vault has been created.

          Viewing Vault Details

          1. Log in to the CBR console.

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

          2. On the Vaults tab, view basic information about all vaults. Related parameters are described in the following table. See Figure 1.

            Figure 1 Vault list
            +

          3. On the Vaults tab, view basic information about all vaults. Related parameters are described in the following table. See Figure 1.

            Figure 1 Vault list
            +

            -
            Table 1 Basic information parameters

            Parameter

            +
            - - - - - - - - - - - - -
            Table 1 Basic information parameters

            Parameter

            Description

            +

            Description

            Name/ID

            +

            Name/ID

            Name and ID of the vault. Click the vault name to view details about the vault.

            +

            Name and ID of the vault. Click the vault name to view details about the vault.

            Type

            +

            Type

            Vault type

            +

            Vault type

            Status

            +

            Status

            Vault status. Table 2 describes the vault statuses.

            +

            Vault status. Table 2 describes the vault statuses.

            Specifications

            +

            Specifications

            Vault specifications

            +

            Vault specifications

            • A server backup vault stores backups of non-database servers.

            Vault Capacity (GB)

            +

            Vault Capacity (GB)

            Capacity used by the backups in the vault. It shows the space used by backups and the total vault capacity.

            +

            Capacity used by the backups in the vault. It shows the space used by backups and the total vault capacity.

            For example: If 20/100 is displayed, 20 GB has been used out of the 100 GB vault capacity.

            Associated Servers/File Systems/Disks

            +

            Associated Servers/File Systems/Disks

            Number of servers, file systems, and disks associated with the vault. You can click the number to view details of associated resources. The associated capacity shown on the details page is the total capacity of all the resources that have been associated with this vault.

            +

            Number of servers, file systems, and disks associated with the vault. You can click the number to view details of associated resources. The associated capacity shown on the details page is the total capacity of all the resources that have been associated with this vault.
            -

          4. On the Vaults tab page, set filter criteria to view specific vaults. See Figure 2.

            Figure 2 Querying a vault
            +

          5. On the Vaults tab page, set filter criteria to view specific vaults. See Figure 2.

            Figure 2 Querying a vault
            +

            • Select a value from the status drop-down list to query vaults by status. Table 2 describes the vault statuses. -
              Table 2 Vault statuses

              Status

              +
              - - - - - - - - - - - - - - - - - @@ -104,7 +106,7 @@
            • Search a vault by its name or ID.
            • Click Search by Tag in the upper right corner to search for vaults by tag.
              • On the displayed Search by Tag page, enter an existing tag key and value and click . The added tag search criteria are displayed under the text boxes. Click Search in the lower right corner.
              • You can add a maximum of 20 tags by clicking . They will be applied together for a combination search.
              • You can click Reset in the lower right corner to reset the search criteria.
              • -

            • Click the name of a specific vault to view vault details.

              The values of used capacity and backup space are rounded off to integers. CBR will display 0 GB for any backup space less than 1 GB. For example, there may be 200 MB backup space used, but it will be displayed as 0 GB on the console.

              +

            • Click the name of a specific vault to view vault details.

              • The values of used capacity and backup space are rounded off to integers. CBR will display 0 GB for any backup space less than 1 GB. For example, there may be 200 MB backup space used, but it will be displayed as 0 GB on the console.

              • @@ -118,7 +120,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0003.html b/docs/cbr/umn/cbr_03_0003.html index 23e34517..616cfb1a 100644 --- a/docs/cbr/umn/cbr_03_0003.html +++ b/docs/cbr/umn/cbr_03_0003.html @@ -7,11 +7,12 @@

              Procedure

              1. Log in to the CBR console.

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

              2. Find the target vault and choose More > Delete in the Operation column. See Figure 1. All backups stored in the vault will be deleted once you delete a vault.

                Figure 1 Deleting a vault
                -

                -

                +

                +

                +

              3. Click Yes.
              @@ -25,7 +26,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0005.html b/docs/cbr/umn/cbr_03_0005.html index 7ce1e042..03dfaef8 100644 --- a/docs/cbr/umn/cbr_03_0005.html +++ b/docs/cbr/umn/cbr_03_0005.html @@ -1,13 +1,15 @@ -

              Dissociating a Resource

              +

              Dissociating Resources from a Vault

              If you no longer need to back up an associated resource, dissociate it from your vault.

              After a resource is dissociated, the vault's backup policy no longer applies to the resource. In addition, all manual and automatic backups of this resource will be deleted. Deleted backups cannot be used to restore data.

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

              Procedure

              1. Log in to the CBR console.

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

              2. Find the target vault and click its 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.

                Figure 1 Dissociating a server
                -

                -

                +

                +

                +

                +

                @@ -23,7 +25,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0006.html b/docs/cbr/umn/cbr_03_0006.html index 9ccd89a3..6a58be21 100644 --- a/docs/cbr/umn/cbr_03_0006.html +++ b/docs/cbr/umn/cbr_03_0006.html @@ -4,8 +4,11 @@

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

                Procedure

                1. Log in to the CBR console.

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

                2. Find the target vault and choose More > Expand Capacity in the Operation column. See Figure 1.

                  Figure 1 Expanding vault capacity
                  +

                  +

                  -

                  +

                  +

                  @@ -23,7 +26,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0009.html b/docs/cbr/umn/cbr_03_0009.html index 4ff50519..3c100b11 100644 --- a/docs/cbr/umn/cbr_03_0009.html +++ b/docs/cbr/umn/cbr_03_0009.html @@ -1,35 +1,38 @@ -

                  Replicating a Vault

                  -

                  CBR allows you to replicate server backup vaults entirely to replication vaults in a different region. Replicas of server backups in the destination region can be used to create images and provision servers.

                  +

                  Replicating a Vault Across Regions

                  +

                  Scenarios

                  CBR allows you to replicate server backup vaults entirely to replication vaults in other regions of the same account. Replicas of server backups in the destination region can be used to create images and provision servers. to quickly deploy services across regions.

                  There are two methods available for replicating a vault.

                  • Manual replication: Select a backup vault and manually replicate it.
                  • Policy-based replication: Configure a replication policy to periodically replicate backups that have not been replicated or failed to be replicated to the destination region.
                  +

                  Constraints

                  • Disk backup vaults cannot be replicated to other regions.
                  • Backup data can be replicated to vaults in different regions, and backup replicas occupy the replication vault space.
                  • A server backup vault can be replicated only when it contains at least one backup that meets all the following conditions:
                    1. The backup is an ECS backup.
                    2. The backup contains system disk data.
                    3. The backup is in the Available state.
                    -
                  • Only backup vaults can be replicated. Replicated vaults cannot be replicated again but their replicas can be used to create images.
                  • A backup vault can be replicated to different destination regions. The replication rule varies with the replication method:
                    • Manual replication: A backup can be manually replicated to the destination region as long as it has no replica in that region. A backup can be manually replicated again if its replica in the destination region has been deleted.
                    • Policy-based replication: A backup can only be automatically replicated to a destination region once. It cannot be automatically replicated to that region again, even if its replica has been deleted.
                    -
                  • Only replication-supported regions can be selected as destination regions.
                  +
                3. Only backup vaults of the same type can be replicated. Replicated vaults cannot be replicated again but their replicas can be used to create images.
                4. A backup vault can be replicated to different destination regions. For manual and policy-based vault replication, a vault can only be replicated to a destination region once. It cannot be replicated to that region again, even if its backups have been deleted. +
                5. Only replication-supported regions can be selected as destination regions.

                Procedure

                1. Log in to the CBR console.

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

                2. On the Vaults tab, find the target backup vault.
                3. Choose More > Create Replica in the Operation column of the vault. See Figure 1.

                  Figure 1 Creating a replica
                  +

                  +

                4. In the displayed dialog box, configure the parameters as described in Table 1.

                  -

              Table 2 Vault statuses

              Status

              Attribute

              +

              Attribute

              Description

              +

              Description

              All statuses

              +

              All statuses

              --

              +

              --

              All vaults are displayed if this value is selected.

              +

              All vaults are displayed if this value is selected.

              Available

              +

              Available

              A stable state

              +

              A stable state

              A stable state after a vault task is complete.

              +

              A stable state after a vault task is complete.

              This state allows most of the operations.

              Locked

              +

              Locked

              An intermediate state

              +

              An intermediate state

              An intermediate state displayed when a capacity expansion is in progress.

              +

              An intermediate state displayed when a capacity expansion is in progress.

              If a vault is in this state, you can perform operations, such as applying a policy and associating servers, file systems, or disks. However, the following operations are not allowed on such a vault: expanding the vault capacity and changing the vault specifications. Once those operations are complete, the vault status will become Available.

              Deleting

              +

              Deleting

              An intermediate state

              +

              An intermediate state

              An intermediate state displayed when a vault is being deleted.

              +

              An intermediate state displayed when a vault is being deleted.

              In this state, a progress bar is displayed indicating the deletion progress. If the progress bar remains unchanged for an extended time, an exception has occurred. Contact technical support.

              Error

              +

              Error

              A stable state

              +

              A stable state

              A vault enters the Error state when an exception occurs during task execution.

              +

              A vault enters the Error state when an exception occurs during task execution.

              You can click Tasks in the navigation pane on the left to view the error cause. If the error persists, contact technical support.
              Table 1 Parameter description

              Parameter

              +
              - - - - - @@ -47,7 +50,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0010.html b/docs/cbr/umn/cbr_03_0010.html index d38c9f22..45a7e900 100644 --- a/docs/cbr/umn/cbr_03_0010.html +++ b/docs/cbr/umn/cbr_03_0010.html @@ -52,7 +52,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0012.html b/docs/cbr/umn/cbr_03_0012.html index 8fc6e06f..d60f434b 100644 --- a/docs/cbr/umn/cbr_03_0012.html +++ b/docs/cbr/umn/cbr_03_0012.html @@ -10,12 +10,6 @@
            • Deleting a Backup
              • -
            • Using a Backup to Create an Image
              -
              • -
            • Using a Backup to Create a Disk
              -
              • -
            • Using a Backup to Create a File System
              -
            • Replicating a Backup Across Regions
              • diff --git a/docs/cbr/umn/cbr_03_0013.html b/docs/cbr/umn/cbr_03_0013.html index cb768cac..ee03f296 100644 --- a/docs/cbr/umn/cbr_03_0013.html +++ b/docs/cbr/umn/cbr_03_0013.html @@ -4,69 +4,71 @@

              In the backup list, you can set search criteria to filter backups and view their details. The results contain backup tasks that are running or have completed.

              Prerequisites

              At least one backup task has been created.

              -

              Viewing Backup Details

              1. Log in to the CBR console.

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

              2. 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. -
              Table 1 Parameter description

              Parameter

              Description

              +

              Description

              Destination Region

              +

              Destination Region

              Region to which the vault is replicated

              +

              Region to which the vault is replicated

              Only the regions that support replication will be displayed.

              • If the selected region contains only one project, you can directly select the region name.
              • If the selected region has multiple projects, the default project of the region is selected. You can select another project if needed.

              Destination Vault

              +

              Destination Vault

              A replication vault in the destination region

              +

              A replication vault in the destination region
              - diff --git a/docs/cbr/umn/en-us_image_0000001088492789.png b/docs/cbr/umn/en-us_image_0000001088492789.png deleted file mode 100644 index dc3fcfba..00000000 Binary files a/docs/cbr/umn/en-us_image_0000001088492789.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0000001091176765.png b/docs/cbr/umn/en-us_image_0000001091176765.png deleted file mode 100644 index 61a9a22b..00000000 Binary files a/docs/cbr/umn/en-us_image_0000001091176765.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0000001478036586.png b/docs/cbr/umn/en-us_image_0000001478036586.png deleted file mode 100644 index cbc79210..00000000 Binary files a/docs/cbr/umn/en-us_image_0000001478036586.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0000001533313766.png b/docs/cbr/umn/en-us_image_0000001533313766.png deleted file mode 100644 index 126230b1..00000000 Binary files a/docs/cbr/umn/en-us_image_0000001533313766.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0000001706852702.png b/docs/cbr/umn/en-us_image_0000001706852702.png index f38adab1..f67dc278 100644 Binary files a/docs/cbr/umn/en-us_image_0000001706852702.png and b/docs/cbr/umn/en-us_image_0000001706852702.png differ diff --git a/docs/cbr/umn/en-us_image_0000001754617465.png b/docs/cbr/umn/en-us_image_0000001754617465.png deleted file mode 100644 index 50730a89..00000000 Binary files a/docs/cbr/umn/en-us_image_0000001754617465.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0000001754810509.png b/docs/cbr/umn/en-us_image_0000001754810509.png index 937e7be5..680e60eb 100644 Binary files a/docs/cbr/umn/en-us_image_0000001754810509.png and b/docs/cbr/umn/en-us_image_0000001754810509.png differ diff --git a/docs/cbr/umn/en-us_image_0000001898884424.png b/docs/cbr/umn/en-us_image_0000001898884424.png new file mode 100644 index 00000000..5c285506 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001898884424.png differ diff --git a/docs/cbr/umn/en-us_image_0000001926048954.png b/docs/cbr/umn/en-us_image_0000001926048954.png new file mode 100644 index 00000000..2b3b28bb Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001926048954.png differ diff --git a/docs/cbr/umn/en-us_image_0000001926064008.png b/docs/cbr/umn/en-us_image_0000001926064008.png new file mode 100644 index 00000000..e7e7208c Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001926064008.png differ diff --git a/docs/cbr/umn/en-us_image_0000001926206410.png b/docs/cbr/umn/en-us_image_0000001926206410.png new file mode 100644 index 00000000..16e701a8 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001926206410.png differ diff --git a/docs/cbr/umn/en-us_image_0000001926225120.png b/docs/cbr/umn/en-us_image_0000001926225120.png new file mode 100644 index 00000000..9779e63f Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001926225120.png differ diff --git a/docs/cbr/umn/en-us_image_0000001926329360.png b/docs/cbr/umn/en-us_image_0000001926329360.png new file mode 100644 index 00000000..4b68dc08 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001926329360.png differ diff --git a/docs/cbr/umn/en-us_image_0000001926384488.png b/docs/cbr/umn/en-us_image_0000001926384488.png new file mode 100644 index 00000000..cd9429f7 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001926384488.png differ diff --git a/docs/cbr/umn/en-us_image_0000001926426770.png b/docs/cbr/umn/en-us_image_0000001926426770.png new file mode 100644 index 00000000..5f019da2 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001926426770.png differ diff --git a/docs/cbr/umn/en-us_image_0000001926565432.png b/docs/cbr/umn/en-us_image_0000001926565432.png new file mode 100644 index 00000000..9780bcec Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001926565432.png differ diff --git a/docs/cbr/umn/en-us_image_0000001953185673.png b/docs/cbr/umn/en-us_image_0000001953185673.png new file mode 100644 index 00000000..07c32567 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001953185673.png differ diff --git a/docs/cbr/umn/en-us_image_0000001953465457.png b/docs/cbr/umn/en-us_image_0000001953465457.png new file mode 100644 index 00000000..93bc1b30 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001953465457.png differ diff --git a/docs/cbr/umn/en-us_image_0000001953505157.png b/docs/cbr/umn/en-us_image_0000001953505157.png new file mode 100644 index 00000000..18ed5847 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001953505157.png differ diff --git a/docs/cbr/umn/en-us_image_0000001953568037.png b/docs/cbr/umn/en-us_image_0000001953568037.png new file mode 100644 index 00000000..46270d35 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001953568037.png differ diff --git a/docs/cbr/umn/en-us_image_0000001953569833.png b/docs/cbr/umn/en-us_image_0000001953569833.png new file mode 100644 index 00000000..b4b3d9de Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001953569833.png differ diff --git a/docs/cbr/umn/en-us_image_0000001953593985.png b/docs/cbr/umn/en-us_image_0000001953593985.png new file mode 100644 index 00000000..b9514b66 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001953593985.png differ diff --git a/docs/cbr/umn/en-us_image_0000001953594521.png b/docs/cbr/umn/en-us_image_0000001953594521.png new file mode 100644 index 00000000..8ba05f5b Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001953594521.png differ diff --git a/docs/cbr/umn/en-us_image_0000001992180742.png b/docs/cbr/umn/en-us_image_0000001992180742.png new file mode 100644 index 00000000..689c0538 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001992180742.png differ diff --git a/docs/cbr/umn/en-us_image_0000001992181570.png b/docs/cbr/umn/en-us_image_0000001992181570.png new file mode 100644 index 00000000..a6905f41 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001992181570.png differ diff --git a/docs/cbr/umn/en-us_image_0000001992338654.png b/docs/cbr/umn/en-us_image_0000001992338654.png new file mode 100644 index 00000000..5416a73c Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001992338654.png differ diff --git a/docs/cbr/umn/en-us_image_0000001995695954.png b/docs/cbr/umn/en-us_image_0000001995695954.png new file mode 100644 index 00000000..e8d7f323 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001995695954.png differ diff --git a/docs/cbr/umn/en-us_image_0000001995856846.png b/docs/cbr/umn/en-us_image_0000001995856846.png new file mode 100644 index 00000000..27250b29 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001995856846.png differ diff --git a/docs/cbr/umn/en-us_image_0000001995858070.png b/docs/cbr/umn/en-us_image_0000001995858070.png new file mode 100644 index 00000000..60e0fe9d Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000001995858070.png differ diff --git a/docs/cbr/umn/en-us_image_0000002022201825.png b/docs/cbr/umn/en-us_image_0000002022201825.png new file mode 100644 index 00000000..ead21822 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002022201825.png differ diff --git a/docs/cbr/umn/en-us_image_0000002022208757.png b/docs/cbr/umn/en-us_image_0000002022208757.png new file mode 100644 index 00000000..7ddd5a3f Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002022208757.png differ diff --git a/docs/cbr/umn/en-us_image_0000002028777013.png b/docs/cbr/umn/en-us_image_0000002028777013.png new file mode 100644 index 00000000..c6dafda0 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002028777013.png differ diff --git a/docs/cbr/umn/en-us_image_0000002028782365.png b/docs/cbr/umn/en-us_image_0000002028782365.png new file mode 100644 index 00000000..e6b55ae0 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002028782365.png differ diff --git a/docs/cbr/umn/en-us_image_0000002028900293.png b/docs/cbr/umn/en-us_image_0000002028900293.png new file mode 100644 index 00000000..d90b033d Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002028900293.png differ diff --git a/docs/cbr/umn/en-us_image_0000002032295753.png b/docs/cbr/umn/en-us_image_0000002032295753.png new file mode 100644 index 00000000..7fc131e8 Binary files /dev/null and b/docs/cbr/umn/en-us_image_0000002032295753.png differ diff --git a/docs/cbr/umn/en-us_image_0184118425.png b/docs/cbr/umn/en-us_image_0184118425.png deleted file mode 100644 index 944cc887..00000000 Binary files a/docs/cbr/umn/en-us_image_0184118425.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0184119856.png b/docs/cbr/umn/en-us_image_0184119856.png deleted file mode 100644 index ae2dd793..00000000 Binary files a/docs/cbr/umn/en-us_image_0184119856.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0184119988.png b/docs/cbr/umn/en-us_image_0184119988.png deleted file mode 100644 index c0c6f972..00000000 Binary files a/docs/cbr/umn/en-us_image_0184119988.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0224255894.png b/docs/cbr/umn/en-us_image_0224255894.png deleted file mode 100644 index b7da699b..00000000 Binary files a/docs/cbr/umn/en-us_image_0224255894.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0224256775.png b/docs/cbr/umn/en-us_image_0224256775.png deleted file mode 100644 index 493beefb..00000000 Binary files a/docs/cbr/umn/en-us_image_0224256775.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251429559.png b/docs/cbr/umn/en-us_image_0251429559.png deleted file mode 100644 index e55251f5..00000000 Binary files a/docs/cbr/umn/en-us_image_0251429559.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251455468.png b/docs/cbr/umn/en-us_image_0251455468.png deleted file mode 100644 index 033729a9..00000000 Binary files a/docs/cbr/umn/en-us_image_0251455468.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251464008.png b/docs/cbr/umn/en-us_image_0251464008.png deleted file mode 100644 index 70134104..00000000 Binary files a/docs/cbr/umn/en-us_image_0251464008.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251464113.png b/docs/cbr/umn/en-us_image_0251464113.png deleted file mode 100644 index 5c41699b..00000000 Binary files a/docs/cbr/umn/en-us_image_0251464113.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251464955.png b/docs/cbr/umn/en-us_image_0251464955.png deleted file mode 100644 index cafeae9b..00000000 Binary files a/docs/cbr/umn/en-us_image_0251464955.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251464982.png b/docs/cbr/umn/en-us_image_0251464982.png deleted file mode 100644 index 8bbcad64..00000000 Binary files a/docs/cbr/umn/en-us_image_0251464982.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251465011.png b/docs/cbr/umn/en-us_image_0251465011.png deleted file mode 100644 index 43047b3a..00000000 Binary files a/docs/cbr/umn/en-us_image_0251465011.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251465753.png b/docs/cbr/umn/en-us_image_0251465753.png deleted file mode 100644 index c079ba5c..00000000 Binary files a/docs/cbr/umn/en-us_image_0251465753.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251470380.png b/docs/cbr/umn/en-us_image_0251470380.png deleted file mode 100644 index e26183e1..00000000 Binary files a/docs/cbr/umn/en-us_image_0251470380.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251473302.png b/docs/cbr/umn/en-us_image_0251473302.png deleted file mode 100644 index 6bd9ba0e..00000000 Binary files a/docs/cbr/umn/en-us_image_0251473302.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251474682.png b/docs/cbr/umn/en-us_image_0251474682.png deleted file mode 100644 index 81eace8b..00000000 Binary files a/docs/cbr/umn/en-us_image_0251474682.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251476754.png b/docs/cbr/umn/en-us_image_0251476754.png deleted file mode 100644 index 7ff5cbe0..00000000 Binary files a/docs/cbr/umn/en-us_image_0251476754.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251478661.png b/docs/cbr/umn/en-us_image_0251478661.png deleted file mode 100644 index e4d7c86c..00000000 Binary files a/docs/cbr/umn/en-us_image_0251478661.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251479636.png b/docs/cbr/umn/en-us_image_0251479636.png deleted file mode 100644 index e98a4b73..00000000 Binary files a/docs/cbr/umn/en-us_image_0251479636.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0251480774.png b/docs/cbr/umn/en-us_image_0251480774.png deleted file mode 100644 index bdcab4e7..00000000 Binary files a/docs/cbr/umn/en-us_image_0251480774.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0252971476.png b/docs/cbr/umn/en-us_image_0252971476.png deleted file mode 100644 index 752ef4cc..00000000 Binary files a/docs/cbr/umn/en-us_image_0252971476.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0252972053.png b/docs/cbr/umn/en-us_image_0252972053.png deleted file mode 100644 index 752ef4cc..00000000 Binary files a/docs/cbr/umn/en-us_image_0252972053.png and /dev/null differ diff --git a/docs/cbr/umn/en-us_image_0277693887.png b/docs/cbr/umn/en-us_image_0277693887.png index c67fa17a..c6fb7d3d 100644 Binary files a/docs/cbr/umn/en-us_image_0277693887.png and b/docs/cbr/umn/en-us_image_0277693887.png differ
              Table 1 Backup statuses

              Status

              +

              Procedure

              1. Log in to the CBR console.

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

              2. Click the Backups tab and set filter criteria to view the backups. See Figure 1.

                Figure 1 Viewing a backup
                +

                +
                • You can search for backups by selecting a status from the All statuses drop-down list above the backup list. Table 1 describes the backup statuses. +
                  - - - - - - - - - - - - - - - - - - - -
                  Table 1 Backup statuses

                  Status

                  Status Attribute

                  +

                  Status Attribute

                  Description

                  +

                  Description

                  All statuses

                  +

                  All statuses

                  --

                  +

                  --

                  All backups are displayed if this value is selected.

                  +

                  All backups are displayed if this value is selected.

                  Available

                  +

                  Available

                  A stable state

                  +

                  A stable state

                  A stable state of a backup after the backup is created, indicating that the backup is currently not being used.

                  +

                  A stable state of a backup after the backup is created, indicating that the backup is currently not being used.

                  This state allows most of the operations.

                  Creating

                  +

                  Creating

                  An intermediate state

                  +

                  An intermediate state

                  An intermediate state of a backup from the start of a backup job to the completion of this job.

                  +

                  An intermediate state of a backup from the start of a backup job to the completion of this job.

                  In the Tasks list, a progress bar is displayed for a backup task in this state. If the progress bar remains unchanged for an extended time, an exception has occurred. Contact technical support.

                  Restoring

                  +

                  Restoring

                  An intermediate state

                  +

                  An intermediate state

                  An intermediate state when using the backup to restore data.

                  +

                  An intermediate state when using the backup to restore data.

                  In the Tasks list, a progress bar is displayed for a restoration task in this state. If the progress bar remains unchanged for an extended time, an exception has occurred. Contact technical support.

                  Deleting

                  +

                  Deleting

                  An intermediate state

                  +

                  An intermediate state

                  An intermediate state from the start of deleting the backup to the completion of deleting the backup.

                  +

                  An intermediate state from the start of deleting the backup to the completion of deleting the backup.

                  In the Tasks list, a progress bar is displayed for a deletion task in this state. If the progress bar remains unchanged for an extended time, an exception has occurred. Contact technical support.

                  Error

                  +

                  Error

                  A stable state

                  +

                  A stable state

                  A backup enters the Error state when an exception occurs.

                  +

                  A backup enters the Error state when an exception occurs.

                  A backup in this state cannot be used for restoration, and must be deleted manually. If manual deletion fails, contact technical support.
                  -
                • You can search for backups by clicking Advanced Search in the upper right corner of the backup list.

                  You can search by specifying a backup status, backup name, backup ID, vault ID, server name, server ID, server type, or the creation date. See Figure 2.

                  -
                  Figure 2 Advanced Search
                  +
                • You can search for backups by clicking Advanced Search above the backup list.

                  You can search by specifying a backup name, backup ID, backup type, backup status, vault ID, server name, server ID, server type, protection type, or the creation date. See Figure 2.

                  +
                  Figure 2 Advanced Search
                  +

              3. Click the backup name to view details about the backup.
              @@ -81,7 +83,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0014.html b/docs/cbr/umn/cbr_03_0014.html index 13039870..af08d930 100644 --- a/docs/cbr/umn/cbr_03_0014.html +++ b/docs/cbr/umn/cbr_03_0014.html @@ -1,28 +1,36 @@

              Sharing a Backup

              -

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

              +

              Scenarios

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

              +

              Context

              Sharer

              -
              • 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.
              +
              • Backups can only be shared among domains in the same region. They cannot be shared across regions.
              • Encrypted backups cannot be shared. Backups cannot be shared across regions. Account to which a backup is shared must be in the same region as the backup.
              • When a sharer deletes a shared backup, the backup will also be deleted from the recipient's account, but the disks or servers previously created using the backup will be retained.

              Recipient

              • A recipient must have at least one backup vault to store the accepted shared backup, and the vault's remaining space must be greater than the size of the backup to be accepted.
              • A recipient can choose to accept or reject a backup. After accepting a backup, the recipient can use the backup to create new servers or disks.
              • When a sharer deletes a shared backup, the backup will also be deleted from the recipient's account, but the disks or servers previously created using the backup will be retained.

              Procedure for the Sharer

              1. Log in to the CBR console.

                1. Log in to the management console.
                2. Click in the upper left corner and select a region.
                3. Click and choose Storage > Cloud Backup and Recovery. Select a backup type 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 or disk name, backup ID, and backup type are displayed.

                • Sharing a backup
                  Figure 1 Share Backup
                  -

                  +

                  -

                  +

                  +

                  -

                  +

                  +

                -
                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.
                +
                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 10 projects.

                  +
                4. Click OK.
                • Canceling sharing
                -
                1. Click the Cancel Sharing tab, select the projects you want to cancel sharing, and click OK.

                  +
                  1. Click the Cancel Sharing tab, select the projects you want to cancel sharing, and click OK.

                    +

                    +

                    +

                @@ -49,7 +57,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0015.html b/docs/cbr/umn/cbr_03_0015.html index 8efa1647..67ae0df1 100644 --- a/docs/cbr/umn/cbr_03_0015.html +++ b/docs/cbr/umn/cbr_03_0015.html @@ -3,12 +3,17 @@

                Deleting a Backup

                You can delete unwanted backups to reduce space usage and costs.

                CBR supports manual deletion of backups and automatic deletion of expired backups. The latter is executed based on the backup retention rule in the backup policy. For details, see Creating a Backup Policy.

                +

                Backups are not stored on a server. Deleting backups has no impact on the server performance.

                +

                Prerequisites

                • There is at least one backup.
                • The backup to be deleted is in the Available or Error state.

                Procedure

                1. Log in to the CBR console.

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

                2. Click the Backups tab and locate the desired backup. For details, see Viewing a Backup.
                3. Choose More > Delete from the Operation column. See Figure 1. Alternatively, select the backups you want to delete in a batch and click Delete in the upper left corner to delete them.

                  Figure 1 Deleting a backup
                  +

                  +

                  -

                  +

                  +

                  @@ -24,7 +29,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0016.html b/docs/cbr/umn/cbr_03_0016.html index 27be3b1b..6fc5bb46 100644 --- a/docs/cbr/umn/cbr_03_0016.html +++ b/docs/cbr/umn/cbr_03_0016.html @@ -1,32 +1,33 @@ -

                  Using a Backup to Create an Image

                  +

                  Creating an Image from a Cloud Server Backup

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

                  You can also use server backups to create images and then provision servers to restore data if your servers were accidentally deleted.

                  Prerequisites

                  • The following operations have been performed: -
                  • The backup is in the Available state or in the Creating state which is marked with "Image can be created."

                    Once a backup creation starts, the backup enters the Creating state. After a period of time, a message stating "Image can be created" is displayed under Creating. In this case, the backup can be used for creating an image, even though it is still being created and cannot be used for restoration.

                    +
                  • The backup is in the Available state, or the backup is in the Creating state that is marked with "Image can be created."

                    Once a backup creation starts, the backup enters the Creating state. After a period of time, a message stating "Image can be created" is displayed under Creating. In this case, the backup can be used for creating an image, even though it is still being created and cannot be used for restoration.

                  • The backup contains the system disk data.
                  • Only ECS backups can be used to create images.

                  Notes

                  • Images created using a backup are the same, so CBR allows you to use a backup to create only one full-ECS image that contains the whole data of the system disk and data disks of an ECS, in order to save the image quota. After an image is created, you can use the image to provision multiple ECSs in a batch.
                  • A backup with an image created cannot be deleted directly. To delete such a backup, delete its image first. If a backup is automatically generated based on a backup policy and the backup has been used to create an image, the backup will not be counted as a retained backup and will not be deleted automatically.
                  • A backup is compressed when it is used to create an image, so the size of the generated image may be smaller than the backup size.

                  Procedure

                  1. Log in to the CBR console.

                    1. Log in to the management console.
                    2. Click in the upper left corner and select a region.
                    3. Click and choose Storage > Cloud Backup and Recovery. Select a backup type 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. Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
                  5. In the row of the backup, choose More > Create Image. See Figure 1.

                    Figure 1 Creating an image
                    +

                    -

                  6. Create an image by referring to section "Creating a Full-ECS Image Using a Cloud Server Backup" in the Image Management Service User Guide.
                  7. Use the image to provision ECSs when needed. For details, see section "Creating an ECS from an Image" in the Image Management Service User Guide.
                  +

                4. Create an image by referring to section "Creating a Full-ECS Image Using a Cloud Server Backup" in the Image Management Service User Guide.
                5. Use the image to provision ECSs when needed. For details, see section "Creating an ECS from an Image" in the Image Management Service User Guide.
                -
                Parent topic: Backup Management
                +
                Parent topic: Restoring Data
                \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0017.html b/docs/cbr/umn/cbr_03_0017.html index ac05ee50..05befa23 100644 --- a/docs/cbr/umn/cbr_03_0017.html +++ b/docs/cbr/umn/cbr_03_0017.html @@ -1,8 +1,8 @@ -

                Using a Backup to Create a Disk

                -

                You can create new disks from backups. Once created, the new disks will contain the backup data.

                -

                The new disks created using system disk backups can only be used as data disks on servers. They cannot be used as system disks.

                +

                Creating a Disk from a Cloud Disk Backup

                +

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

                +

                Disks created using system disk backups can only be used as data disks on servers. They cannot be used as system disks.

                Procedure

                1. Log in to the CBR console.

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

                2. Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
                3. Click Create Disk in the Operation column of the backup. The button is available only when the backup status is Available.
                4. Configure the disk parameters.

                  See the parameter description table in section "Create an EVS Disk" of the Elastic Volume Service User Guide for more information.

                  Pay attention to the following:

                  @@ -15,7 +15,7 @@
                  -
                  Parent topic: Backup Management
                  +
                  Parent topic: Restoring Data
                  diff --git a/docs/cbr/umn/cbr_03_0018.html b/docs/cbr/umn/cbr_03_0018.html index c6bf2cfc..9ebe2381 100644 --- a/docs/cbr/umn/cbr_03_0018.html +++ b/docs/cbr/umn/cbr_03_0018.html @@ -1,52 +1,54 @@

                  Replicating a Backup Across Regions

                  -

                  CBR enables you to replicate backups of server backup vaults from one region to another.

                  +

                  Scenarios

                  Cross-region replication of server backup vaults allows you to replicate backups from one region to another under the same account.

                  Replicas of server backups can be used to create images and provision servers.

                  With cross-region replication, you can quickly deploy services in a different region. Data on the new resource in the destination region is the same as that on the original resource when you took the backup.

                  You can replicate backups in either of the following methods on the CBR console:

                  • Select a backup from the backup list and manually perform a replication.
                  • Select a backup vault and manually replicate it. Alternatively, you can configure a replication policy to periodically replicate backups that have not been replicated or failed to be replicated to the destination region.
                  -

                  This section uses the first method to describe how to replicate a backup. For details about the second method, see Replicating a Vault.

                  -

                  The replication constraints apply to both replication methods.

                  -
                  +

                  This section uses the first method to describe how to replicate a backup. For details about the second method, see Replicating a Vault Across Regions.

                  +

                  Constraints

                  • A server backup can be replicated only when it meets all the following conditions:
                    1. It is an ECS backup.
                    2. It contains system disk data.
                    3. It is in the Available state.
                    -
                  • Only backups or backup vaults can be replicated. Replicated backups and vaults cannot be replicated again but their replicas can be used to create images.
                  • A backup can be replicated to multiple regions but can have only one replica in each destination region. The replication rule varies with the replication method:
                    • Manual replication: A backup can be manually replicated to the destination region as long as it has no replica in that region. A backup can be manually replicated again if its replica in the destination region has been deleted.
                    • Policy-based replication: A backup can only be automatically replicated to a destination region once. It cannot be automatically replicated to that region again, even if its replica has been deleted.
                    +
                  • Only backups or backup vaults can be replicated. Replicated backups and vaults cannot be replicated again but their replicas can be used to create images.
                  • A backup can be replicated to multiple regions but can have only one replica in each destination region. The replication rule varies with the replication method:

                    Manual replication: A backup can be manually replicated to the destination region as long as it has no replica in that region. A backup can be manually replicated again if its replica in the destination region has been deleted.

                    +

                    For manual and policy-based vault replication, a vault can only be replicated to a destination region once. It cannot be replicated to that region again, even if its backups have been deleted.

                  • Only replication-supported regions can be selected as destination regions.

                  Procedure

                  1. Log in to the CBR console.

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

                  2. Click the Backups tab and locate the desired backup. For details, see Viewing a Backup.
                  3. Choose More > Create Replica in the Operation column of the backup. See Figure 1.

                    Figure 1 Creating a replica
                    +

                    +

                  4. In the displayed dialog box, configure the parameters as described in Table 1.

                    -

                    - - -
                    Table 1 Parameter description

                    Parameter

                    +
                    - - - - - - - - - @@ -67,7 +69,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0025.html b/docs/cbr/umn/cbr_03_0025.html index 85c7e687..7c9316a8 100644 --- a/docs/cbr/umn/cbr_03_0025.html +++ b/docs/cbr/umn/cbr_03_0025.html @@ -7,9 +7,10 @@

                    Procedure

                    1. Log in to the CBR console.

                      1. Log in to the management console.
                      2. Click in the upper left corner and select a region.
                      3. Click and choose Storage > Cloud Backup and Recovery.

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

                      Figure 1 Creating a backup policy
                      +

                      -

                      -

                      +

                      +

                      @@ -44,28 +45,28 @@
                    + + + + - - - -
                    Table 1 Parameter description

                    Parameter

                    Description

                    +

                    Description

                    Name

                    +

                    Name

                    Replica name

                    +

                    Replica name

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

                    Description

                    +

                    Description

                    Replica description

                    +

                    Replica description

                    It cannot exceed 255 characters.

                    Destination Region

                    +

                    Destination Region

                    Region to which the backup is replicated

                    +

                    Region to which the backup is replicated

                    Only the regions that support replication will be displayed.

                    • If the selected region contains only one project, you can directly select the region name.
                    • If the selected region has multiple projects, the default project of the region is selected. You can select another project if needed.

                    Destination Vault

                    +

                    Destination Vault

                    A replication vault in the destination region

                    +

                    A replication vault in the destination region

                    You can replicate backups to vaults in multiple destination regions. Creating replica will replicate all backups in the source vault to the destination vault.

                    Only after a backup policy is enabled and applied will CBR automatically backs up the vault resources and deletes expired backups.

                    Backup Frequency

                    +

                    Select a backup frequency.

                    +
                    • Weekly

                      Specifies on which days of each week the backup task will be executed. You can select multiple days.

                      +
                    • Day based

                      Specifies the interval (every 1 to 30 days) for executing the backup task.

                      +
                    +

                    Every day

                    +

                    If you select day-based backup, the first backup is supposed to be executed on the day when the backup policy is created. If the execution time on the day you create the backup policy has passed, the first backup will be executed in the next backup cycle.

                    +

                    It is recommended that backups be performed during off-peak hours or when no services are running.

                    +

                    Execution Time

                    Execution time

                    Backups can be scheduled at the beginning of each hour, and you can select multiple hours.

                    -
                    NOTICE:
                    • There may be a time difference between the scheduled backup time and the actual backup time.
                    • If a large amount of data needs to be backed up, you are advised to make backup less frequent to prevent the system from skipping any execution time.

                      For example, a disk is scheduled to be backed up at 00:00, 01:00, and 02:00. A backup task starts at 00:00. Because a large amount of incremental data needs to be backed up or a heap of backup tasks are executed at the same time, this backup task takes 90 minutes and completes at 01:30. The system performs the next backup at 02:00. In this case, only two backups are generated in total, one at 00:00, and the other at 02:00.

                      +
                      NOTICE:
                      • There may be a time difference between the scheduled backup time and the actual backup time.
                      • If a large amount of data needs to be backed up, you are advised to make backup less frequent to prevent the system from skipping any execution time.

                        For example, a disk is scheduled to be backed up at 00:00, 01:00, and 02:00. A backup task starts at 00:00. Because a large amount of incremental data needs to be backed up or a heap of backup tasks are executed at the same time, this backup task takes 90 minutes and completes at 01:30. CBR performs the next backup at 02:00. In this case, only two backups are generated in total, one at 00:00, and the other at 02:00.

                      • The execution times refer to the local times of clients, not the time zone and times of the region.

                    00:00, 02:00

                    -
                    • It is recommended that backups be performed during off-peak hours or when no services are running.
                    • Peak hours of the backup service are from 00:00 to 06:00, during which backup schedules may be delayed. So you are advised to evaluate your service types and schedule backups outside of the backup peak hours.
                    -

                    Backup Cycle

                    -

                    Select a backup cycle.

                    -
                    • Week-based cycle

                      Specifies on which days of each week the backup task will be executed. You can select multiple days.

                      -
                    • Custom cycle

                      Specifies the interval (every 1 to 30 days) for executing the backup task.

                      -
                    -

                    Every day

                    -

                    If you select day-based backup, the first backup is supposed to be executed on the day when the backup policy is created. If the execution time on the day you create the backup policy has passed, the first backup will be executed in the next backup cycle.

                    -

                    It is recommended that backups be performed during off-peak hours or when no services are running.

                    +
                    • It is recommended that backups be performed during off-peak hours or when no services are running.
                    • Peak hours of the backup service are from 00:00 to 06:00, during which there may be scheduling delays. So you are advised to evaluate your service types and schedule backups outside of the backup peak hours.

                    Retention Rule

                    @@ -74,8 +75,8 @@
                    • Time period

                      You can choose to retain backups for one month, three months, six months, one year, or for any desired number (2 to 99999) of days.

                    • Backup quantity

                      You can set the maximum number of backups to retain for each resource. The value ranges from 2 to 99999.

                    • Advanced Options

                      You can also set long-term retention rules with advanced options. Long-term retention rules and quantity-based retention rules will be both applied.

                      -
                      • Day-based: 0–100
                      • Weekly: 0–100
                      • Monthly: 0–100
                      • Yearly: 0–100
                      -

                      A resource may be backed up multiple times in a day. If day-based backup is configured, only the most recent backup of that day is retained. If you set Day-based to 5, the most recent backup of each of the last five days that have backups generated will be retained and the earliest backups will be deleted automatically. If day-based, weekly, monthly, and yearly retention rules are all configured, all the rules will apply and the union set of backups will be retained. For example, if Day-based is set to 5 and Weekly to 1, five backups will be retained. The long-term retention rule and the quantity-based retention rule both apply.

                      +
                      • Day-based: 0–100
                      • Weekly: 0–100
                      • Monthly: 0–100
                      • Yearly: 0–100
                      +

                      A resource may be backed up multiple times in a day. If day-based backup is configured, only the most recent backup of that day is retained. If you set Day-based to 5, the most recent backup of each of the last five days that have backups generated will be retained If there are more than five backup replicas, the system automatically deletes the earliest backup replicas. If day-based, weekly, monthly, and yearly retention rules are all configured, all the rules will apply and the union set of backups will be retained. For example, if Day-based is set to 5 and Weekly to 1, five backups will be retained. The long-term retention rule and the quantity-based retention rule both apply.

                    • Permanent
                      NOTE:
                      • The system automatically deletes the earliest and expired backups every other day to avoid exceeding the maximum number of backups to retain or retaining any backup longer than the maximum retention period.
                      • Expired backups are not deleted right after they are expired. They will be deleted from 12:00 to 00:00 in batches.
                      • The retention rules apply only to auto-generated backups, but not manual backups. Manual backups need to be deleted manually.
                      • If a backup is used to create an image, the backup will not be deleted by the retention rule.
                      • A maximum of 10 backups are retained for failed periodic backup tasks. They are retained for one month and can be deleted manually.
                    @@ -86,6 +87,7 @@
                    +

                    More frequent backups create more backups or retain backups for a longer time, protecting data to a greater extent but occupying more storage space. Set an appropriate backup frequency as needed.

                  5. Click OK.

                    You can locate the desired vault and choose More > Apply Backup Policy to apply the policy to the vault. Then you can view the applied policy on the vault details page. After the policy is applied, data will be periodically backed up to the vault based on the policy.

                    @@ -104,7 +106,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0026.html b/docs/cbr/umn/cbr_03_0026.html index e1c64a60..546666f9 100644 --- a/docs/cbr/umn/cbr_03_0026.html +++ b/docs/cbr/umn/cbr_03_0026.html @@ -6,16 +6,16 @@

                    Constraints

                    • You can only apply replication policies to server backup vaults.

                    Procedure

                    1. Log in to the CBR console.

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

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

                      Figure 1 Creating a replication policy
                      -

                      -

                      -

                      +

                    3. Choose Policies in the left navigation pane and click the Replication Policies tab. In the upper right corner, click Create Policy. See Figure 1.

                      Figure 1 Creating a replication policy
                      +

                      +

                      +

                    4. Set the replication policy parameters. Table 1 describes the parameters.

                      - @@ -50,15 +50,15 @@

                      It is recommended that replication be performed during off-peak hours or when no services are running.

                      - - - @@ -78,16 +78,17 @@ - + -
                      Table 1 Replication policy parameters

                      Parameter

                      Description

                      Remarks

                      +

                      Example Value

                      Replication Cycle

                      +

                      Replication Frequency

                      Select a replication cycle.

                      -
                      • Week-based cycle

                        Specifies on which days of each week the replication task will be executed. You can select multiple days.

                        -
                      • Custom cycle

                        Specifies the interval (every 1 to 30 days) for executing the replication task.

                        +

                      Select a replication frequency.

                      +
                      • Weekly

                        Specifies on which days of each week the replication task will be executed. You can select multiple days.

                        +
                      • Day based

                        Specifies the interval (every 1 to 30 days) for executing the replication task.

                      Every day

                      -

                      If you select day-based replication, the first replication is supposed to be executed on the day when the replication policy is created. If the execution time on the day you create the replication policy has passed, the first replication will be performed in the next replication cycle.

                      +

                      Every day

                      +

                      If you select day-based replication, the first replication is supposed to be executed on the day when the replication policy is created. If the execution time on the day you create the replication policy has passed, the first replication will be performed in the next replication cycle.

                      Retention Rule

                      @@ -69,7 +69,7 @@
                      • Day-based: 0–100
                      • Weekly: 0–100
                      • Monthly: 0–100
                      • Yearly: 0–100

                      A resource may be replicated multiple times in a day. If day-based replication is configured, only the most recent backup replica of that day is retained. If you set Day-based to 5, the most recent backup replica of each of the last five days that have backup replicas generated will be retained and the earliest backup replicas will be deleted automatically. If day-based, weekly, monthly, and yearly retention rules are all configured, all the rules will apply and the union set of backup replicas will be retained. For example, if Day-based is set to 5 and Weekly to 1, five backup replicas will be retained. The long-term retention rule and the quantity-based retention rule both apply.

                    5. Time period

                      You can choose to retain backup replicas for one month, three months, six months, one year, or for any desired number (2 to 99999) of days.

                      -
                    6. Permanent
                      NOTE:
                      • The system automatically deletes the earliest and expired backup replicas every other day to avoid exceeding the maximum number of backup replicas to retain or retaining any backup replica longer than the maximum retention period.
                      • There is a delay in deleting expired backup replicas, but normally this delay will not be over 24 hours.
                      • The retention rules apply only to auto-generated backup replicas, but not manual ones. Manual backup replicas need to be deleted manually.
                      • After a backup replica is used to create an image, the replica will not be deleted by the retention rule.
                      +
                    7. Permanent
                      NOTE:
                      • The system automatically deletes the earliest and expired backup replicas every other day to avoid exceeding the maximum number of backup replicas to retain or retaining any backup replica longer than the maximum retention period.
                      • There will be delays for CBR to delete expired backup replicas, but normally these delays will not be over 24 hours.
                      • The retention rules apply only to auto-generated backup replicas, but not manual ones. Manual backup replicas need to be deleted manually.
                      • After a backup replica is used to create an image, the replica will not be deleted by the retention rule.

                      8. Destination Region

                      Region to which the backup is replicated

                      +

                      Region to which backups are replicated

                      Only the regions that support replication will be displayed.

                      -
                      • If the selected region contains only one project, you can directly select the region name.
                      • If the selected region has multiple projects, the default project of the region is selected. You can select another project if needed.
                      +
                      • If the selected region contains only one project, you can directly select the region name.
                      • If the selected region has multiple projects, the default project of the region is preselected. You can select another project if needed.
                      +

                      -
                      -

                    8. Click OK.
                    9. Locate the desired vault and choose More > Apply Replication Policy to apply the replication policy to the vault. You can view the applied policy on the vault details page.

                      After the policy is applied, backups will be periodically replicated to the destination vault based on the policy.

                      +

                    10. Click OK.
                    11. Locate the desired vault and choose More > Apply Replication Policy to apply the replication policy to the vault. Then you can view the applied policy on the vault details page.

                      After the policy is applied, backups will be periodically replicated to the destination vault based on the policy.

                    Example

                    A user applies a replication policy to a vault in a given region at 11:00 a.m. on Thursday. According to this policy, backups will be replicated to the destination region on 02:00 a.m. everyday, and only two backup replicas will be retained. According to this vault's backup policy, two backups are automatically generated at 00:00 everyday. At 12:00 p.m. on Saturday, the replication vault will contain two backup replicas, which are replicated on Saturday. Backup replicas generated at 02:00 a.m. on Friday have been automatically deleted according to the replication policy.

                    @@ -102,7 +103,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0027.html b/docs/cbr/umn/cbr_03_0027.html index e3eac614..b4379e82 100644 --- a/docs/cbr/umn/cbr_03_0027.html +++ b/docs/cbr/umn/cbr_03_0027.html @@ -1,15 +1,16 @@

                    Modifying a Policy

                    -

                    You can modify a policy to better suit your services.

                    +

                    You can modify backup policies if needed.

                    Prerequisites

                    At least one policy has been created.

                    Procedure

                    1. Log in to the CBR console.

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

                    2. Find the target vault and click the vault name to view its details.
                    3. In the Policies area, click Edit in the row of the policy to be edited. See Figure 1.

                      Figure 1 Editing a backup policy
                      +

                      +

                      -

                      -

                      +

                      Related parameters are described in Table 1.

                      @@ -26,7 +27,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0029.html b/docs/cbr/umn/cbr_03_0029.html index f006b95e..97b7b94e 100644 --- a/docs/cbr/umn/cbr_03_0029.html +++ b/docs/cbr/umn/cbr_03_0029.html @@ -2,12 +2,15 @@

                      Applying a Policy to a Vault

                      You can apply a backup policy to a vault to execute backup tasks at specified times or intervals.

                      +

                      Constraints

                      You can create multiple policies, but a can apply only one backup policy to a vault.

                      +

                      Procedure

                      1. Log in to the CBR console.

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

                      2. Find the target vault and choose More > Apply Backup Policy. See Figure 1.

                        Figure 1 Setting a backup policy

                        +

                        -

                        -

                        +

                        +

                      3. Select an existing backup policy from the drop-down list or create a new one. For how to create a policy, see Creating a Backup Policy.
                      4. After the policy is successfully applied, view details in the Policies area of the vault details page.
                      @@ -22,7 +25,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0030.html b/docs/cbr/umn/cbr_03_0030.html index 467b1ce1..4fe46cc7 100644 --- a/docs/cbr/umn/cbr_03_0030.html +++ b/docs/cbr/umn/cbr_03_0030.html @@ -1,17 +1,20 @@

                      Removing a Policy from a Vault

                      -

                      If you no longer need automatic backup for a vault, remove the policy from the vault.

                      +

                      Scenarios

                      If you need to cancel auto backup of a vault, remove the policy from the vault, or disable the policy. This section describes how to remove a policy from a vault.

                      +

                      Prerequisites

                      A policy has been applied to the vault.

                      Procedure

                      1. Log in to the CBR console.

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

                      2. Find the target vault and click the vault name to view its details.
                      3. In the Policies area, click Remove Policy. See Figure 1.

                        Figure 1 Removing a policy
                        -

                        +

                        +

                        -

                        +

                        +

                        -
                        • If a policy is removed when a backup task is being executed for a resource in the vault, the backup task will continue and backups will be generated.
                        • After a policy is removed, backups retained by Time period will expire based on the retention rule, but backups retained by Backup quantity will not. You need manually delete unwanted backups.
                        +
                        • You can remove a policy from a vault when the vault resources are being backed up. In this case, backup tasks will continue, and backups will be generated.
                        • After a policy is removed, backups retained by Time period will expire based on the retention rule, but backups retained by Backup quantity will not. You need manually delete unwanted backups.

                      4. Click Yes.

                        Tasks will no longer be executed based on this policy for the vault.

                      @@ -26,7 +29,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0031.html b/docs/cbr/umn/cbr_03_0031.html index ffd4247b..3c6eb3b6 100644 --- a/docs/cbr/umn/cbr_03_0031.html +++ b/docs/cbr/umn/cbr_03_0031.html @@ -6,8 +6,14 @@
                      diff --git a/docs/cbr/umn/cbr_03_0032.html b/docs/cbr/umn/cbr_03_0032.html index 4a4d1200..ac3ba7cc 100644 --- a/docs/cbr/umn/cbr_03_0032.html +++ b/docs/cbr/umn/cbr_03_0032.html @@ -2,16 +2,21 @@

                      Restoring from a Cloud Server Backup

                      When disks on a server are faulty or their data is lost, you can use a backup to restore the server to its state when the backup was created.

                      -

                      Constraints

                      • When restoring from a cloud server backup, backup of a data disk cannot be restored to the system disk.
                      • Data cannot be restored to servers in the Faulty state.
                      +

                      The system shuts down the server before restoring server data, and automatically starts up the server after the restoration is complete. If you deselect Start the server immediately after restoration, you need to manually start the server after the restoration is complete.

                      +
                      +

                      Notes and Constraints

                      • When restoring from a cloud server backup, backup of a data disk cannot be restored to the system disk.
                      • Data cannot be restored to servers in the Faulty state.

                      Prerequisites

                      • Disks are running properly on the server whose data needs to be restored.
                      • The server has at least one Available backup.

                      Procedure

                      1. Log in to the CBR console.

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region.
                        3. Click and choose Storage > Cloud Backup and Recovery. Select a backup type 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 current server data will be overwritten by the data captured at the time of backup. The restoration cannot be undone.

                        +

                      4. Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
                      5. Click Restore Server in the Operation column, as shown in Figure 1.

                        The current server data will be overwritten by the data captured at the time of backup. The restoration cannot be undone.

                        Figure 1 Restoring a server
                        +

                        +

                        -

                        +

                        +

                        @@ -40,7 +45,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0033.html b/docs/cbr/umn/cbr_03_0033.html index 0a9ae45b..2679d2d1 100644 --- a/docs/cbr/umn/cbr_03_0033.html +++ b/docs/cbr/umn/cbr_03_0033.html @@ -2,17 +2,21 @@

                        Restoring from a Cloud Disk Backup

                        You can use a disk backup to restore the disk to its state when the backup was created.

                        +

                        Before restoring the disk data, stop the server to which the disk is attached and detach the disk from the server. After the disk data is restored, attach the disk to the server and start the server.

                        Prerequisites

                        • The disk to be restored is Available.
                        • Before restoring the disk data, stop the server to which the disk is attached and detach the disk from the server. After the disk data is restored, attach the disk to the server and start the server.

                        Constraints

                        • Backups can only be restored to original disks. If you want to restore a backup to a different disk, use the backup to create a new disk.

                        Procedure

                        1. Log in to the CBR console.

                          1. Log in to the management console.
                          2. Click in the upper left corner and select a region.
                          3. Click and choose Storage > Cloud Backup and Recovery. Select a backup type 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 dialog box is displayed. See Figure 1.

                          +

                        4. Click the Backups tab. Locate the desired backup. For details, see Viewing a Backup.
                        5. In the row of the backup, click Restore Disk. The Restore Disk dialog box is displayed. See Figure 1.

                          +

                          • The backup data will overwrite the current disk data, and the restoration cannot be undone.
                          • If the restore button is grayed out, stop the server, detach the disk, and then try again. After the disk data is restored, attach the disk to the server and start the server.
                          Figure 1 Restore Disk
                          +

                          +

                          @@ -30,7 +34,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0035.html b/docs/cbr/umn/cbr_03_0035.html index d9ca153e..3c0dee5d 100644 --- a/docs/cbr/umn/cbr_03_0035.html +++ b/docs/cbr/umn/cbr_03_0035.html @@ -6,7 +6,8 @@

                        Procedure

                        1. Log in to the CBR console.

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

                          See Figure 1.

                          -
                          Figure 1 Viewing tasks
                          +
                          Figure 1 Viewing tasks
                          +

                        2. Filter tasks by task type, task status, task ID, resource ID, resource name, vault ID, vault name, and time.
                        3. Click in front of the task to view the task details.

                          If a task fails, you can view the failure cause in the task details.

                        @@ -17,7 +18,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0036.html b/docs/cbr/umn/cbr_03_0036.html index 451723a1..c35b7af4 100644 --- a/docs/cbr/umn/cbr_03_0036.html +++ b/docs/cbr/umn/cbr_03_0036.html @@ -1,6 +1,6 @@ -

                        Auditing

                        +

                        Recording CBR Operations Using CTS

                        You can use Cloud Trace Service (CTS) to trace operations in CBR.

                        Prerequisites

                        CTS has been enabled.

                        @@ -231,7 +231,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0037.html b/docs/cbr/umn/cbr_03_0037.html index 877f76d3..5368f8fa 100644 --- a/docs/cbr/umn/cbr_03_0037.html +++ b/docs/cbr/umn/cbr_03_0037.html @@ -1,7 +1,7 @@

                        Quotas

                        -

                        What Is Quota?

                        Quotas can limit the number or amount of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.

                        +

                        What Is Quota?

                        Quotas can limit the number or amount of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.

                        If the existing resource quota cannot meet your service requirements, you can apply for a higher quota.

                        How Do I View My Quotas?

                        1. Log in to the management console.
                        2. Click in the upper left corner and select the desired region and project.
                        3. In the upper right corner of the page, click .

                          The Service Quota page is displayed.

                          @@ -10,7 +10,7 @@

                        How Do I Apply for a Higher Quota?

                        The system does not support online quota adjustment. If you need to adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email.

                        Before dialing the hotline number or sending an email, make sure that the following information has been obtained:

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

                          +
                          • 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_0039.html b/docs/cbr/umn/cbr_03_0039.html index d4da7f85..00a828c0 100644 --- a/docs/cbr/umn/cbr_03_0039.html +++ b/docs/cbr/umn/cbr_03_0039.html @@ -4,7 +4,7 @@
                          diff --git a/docs/cbr/umn/cbr_03_0046.html b/docs/cbr/umn/cbr_03_0046.html deleted file mode 100644 index e8958f0c..00000000 --- a/docs/cbr/umn/cbr_03_0046.html +++ /dev/null @@ -1,157 +0,0 @@ - - -

                          Change History

                          -
                          -
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

                          Released On

                          -

                          Description

                          -

                          2023-10-30

                          -

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

                          -

                          Added support for cross-region replication.

                          -

                          2023-09-13

                          -

                          This issue is the twenty-third official release, which incorporates the following change:

                          -

                          Added support for resource migration.

                          -

                          2023-07-02

                          -

                          This issue is the twenty-second official release, which incorporates the following change:

                          -

                          Modified the maximum number of tags that can be added to a vault.

                          -

                          2023-04-18

                          -

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

                          -

                          Added some CBR operations that can be recorded by CTS in section "Auditing."

                          -

                          2023-03-02

                          -

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

                          -
                          • Updated the screenshots in section "A Server Created Using an Image Enters Maintenance Mode After Login."
                          • Modified section "Sharing a Backup."
                          -

                          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 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 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 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 is the fourteenth official release, which incorporates the following change:

                          -

                          Modified section "Creating an Alarm Rule."

                          -

                          2022-07-15

                          -

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

                          -

                          Modified section "Creating an Alarm Rule."

                          -

                          2022-06-23

                          -

                          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 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 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 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 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 is the seventh official release, which incorporates the following change:

                          -

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

                          -

                          2020-06-05

                          -

                          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 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 is the fourth official release, which incorporates the following change:

                          -

                          Accepted for RM-530.

                          -

                          2019-09-04

                          -

                          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 is the second official release, which incorporates the following changes:

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

                          2019-07-30

                          -

                          This issue is the first official release.

                          -
                          -
                          -
                          -
                          -
                          -
                          Parent topic: Appendix
                          -
                          -
                          - diff --git a/docs/cbr/umn/cbr_03_0048.html b/docs/cbr/umn/cbr_03_0048.html index 3c8c4901..b3c5a9c6 100644 --- a/docs/cbr/umn/cbr_03_0048.html +++ b/docs/cbr/umn/cbr_03_0048.html @@ -2,7 +2,7 @@

                          Creating a User and Granting CBR Permissions

                          This section describes how to use IAM to implement fine-grained permissions control for your CBR resources. With IAM, you can:

                          -
                          • Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing CBR resources.
                          • Grant only the permissions required for users to perform a specific task.
                          • Entrust a cloud account or cloud service to perform efficient O&M on your CBR resources.
                          +
                          • Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing CBR resources.
                          • Grant users only the permissions required to perform a given task based on their job responsibilities.
                          • Entrust a cloud account or cloud service to perform efficient O&M on your CBR resources.

                          If your cloud account does not require individual IAM users, skip this section. If your account cannot meet your requirements, create IAM users by referring to Identity and Access Management User Guide.

                          Figure Figure 1 illustrates the procedure for granting permissions.

                          Prerequisites

                          Learn about the permissions (see Permissions) supported by CBR and choose policies or roles according to your requirements. For the system policies of other services, see section "Permissions".

                          @@ -24,7 +24,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0104.html b/docs/cbr/umn/cbr_03_0104.html index d1f89c34..8e13151d 100644 --- a/docs/cbr/umn/cbr_03_0104.html +++ b/docs/cbr/umn/cbr_03_0104.html @@ -12,12 +12,10 @@

                    6. Servers or disks are associated with a backup policy.

                    +

                    Servers or disks are associated with a backup policy.

                    If backups have been generated, CBR will create a vault with the same name (up to 64 characters) as the policy name (regardless of whether the policy is enabled) and apply the policy to the vault after the vault is created.

                    -

                    If no backup is generated, CBR will create a vault only when the policy is enabled. The policy applying rule and vault naming rule are the same as above.

                    +

                    If no backup is generated, CBR will create a vault only when the policy is enabled. The policy applying rule and vault naming rule are the same as above.

                    Servers or disks are associated with a backup or replication policy.

                    @@ -50,7 +48,7 @@

                    Base on the preceding rules, the capacity of each vault created by the system is predefined as 1.2 times of the total backup size.

                    For example, a user has a 100 GB ECS and a 50 GB ECS. The used storage capacity of the two ECSs is 20 GB and 10 GB, respectively. The user manually has backed up the two entire ECSs using cloud server backup. During migration, the capacity of the vault automatically created will be 1.2 times of the total backup size. In this example, the total backup size multiplied by 1.2 is 36 GB. So the system will automatically create a 36 GB vault.

                    -

                    Constraints

                    • The vaults you have cannot be used for migration. 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.
                    +

                    Constraints

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

                    Procedure

                    1. Log in to the CBR console.

                      1. Log in to the management console.
                      2. Click in the upper left corner and select a region.
                      3. Click and choose Storage > Cloud Backup and Recovery. Select a backup type 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
                      @@ -59,7 +57,7 @@

                    3. The system will automatically migrate resources. After the migration, a vault named default will be created and a message will be displayed in the upper part of the page indicating that the migration is successful.

                    FAQ

                    1. Why Are CBR Backups Displayed on VBS Console?

                      If you have migrated data from CSBS and VBS to CBR, and created a backup on the CBR console, the same backup record will be generated on VBS Console. This is due to an underlying mechanism. VBS Console displays all backups generated by CBR, CSBS, and VBS.

                      -
                    2. How Do I Delete Backups from VBS Console?

                      After you have migrated data from CSBS and VBS to CBR, backups displayed in VBS Console cannot be deleted alone. Find these backups in CBR and delete them. Then, the backups will also be deleted from VBS Console.

                      +
                    3. How Do I Delete Backups from VBS Console?

                      After you have migrated data from CSBS and VBS to CBR, backups displayed in the VBS console cannot be deleted alone. Find these backups in CBR and delete them. Then, the backups will also be deleted from the VBS console.

                    4. What Are the Differences Between CBR, CSBS, and VBS?

                      CBR integrates CSBS and VBS. In addition, CBR supports SFS Turbo backup.

                    5. What Can I Do If a Message Is Displayed Indicating that a Resource Has Been Bound with CSBS or VBS?

                      Choose Cloud Server Backup Service or Volume Backup Service from the service list. On the corresponding service console, check whether there are resources bound with policies on the Policies tab. If so, unbind the resources from the policy and go to the CBR console to associate the resources with a vault.

                    @@ -69,7 +67,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0107.html b/docs/cbr/umn/cbr_03_0107.html index 37a23c0b..ed14032b 100644 --- a/docs/cbr/umn/cbr_03_0107.html +++ b/docs/cbr/umn/cbr_03_0107.html @@ -1,9 +1,11 @@ -

                    Using a Backup to Create a File System

                    +

                    Creating a File System from an SFS Turbo Backup

                    In case of a virus attack, accidental deletion, or software or hardware fault, you can use an SFS Turbo file system backup to create a new file system. Once created, data on the new file system is the same as that in the backup.

                    Procedure

                    1. Log in to the CBR console.

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

                    2. Click the Backups tab and locate the desired backup. For details, see Viewing a Backup.
                    3. Click Create File System in the Operation column of the backup. The button is available only when the backup status is Available.
                    4. Configure the file system parameters. See Figure 1.

                      Figure 1 Creating a file system
                      +

                    5. Click the Backups tab and locate the desired backup. For details, see Viewing a Backup.
                    6. Click Create File System in the Operation column of the backup. The button is available only when the backup status is Available.
                    7. Configure the file system parameters. See Figure 1.

                      Figure 1 Creating a file system
                      +

                      +

                      • You can learn about the parameter descriptions in table "Parameter description" under "Creating an SFS Turbo File System" in "Create a File System" of the Scalable File Service User Guide.
                      @@ -13,14 +15,14 @@
                    -
                    Parent topic: Backup Management
                    +
                    Parent topic: Restoring Data
                    \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0113.html b/docs/cbr/umn/cbr_03_0113.html index d9982451..65f10336 100644 --- a/docs/cbr/umn/cbr_03_0113.html +++ b/docs/cbr/umn/cbr_03_0113.html @@ -1,14 +1,11 @@ - -

                    Monitoring

                    - -

                    +

                    Cloud Eye Monitoring

                    +

                    -
                      -
                    • CBR Metrics
                      +
                    • Viewing Basic CBR Monitoring Data
                    • Creating an Alarm Rule
                      • diff --git a/docs/cbr/umn/cbr_03_0114.html b/docs/cbr/umn/cbr_03_0114.html index ee100b9f..22e2fb49 100644 --- a/docs/cbr/umn/cbr_03_0114.html +++ b/docs/cbr/umn/cbr_03_0114.html @@ -1,6 +1,6 @@ -

                      CBR Metrics

                      +

                      Viewing Basic CBR Monitoring Data

                      Scenarios

                      This section describes metrics reported by CBR as well as their namespaces and dimensions. You can use the console or APIs provided by Cloud Eye to query the metrics generated for CBR.

                      Namespace

                      SYS.CBR

                      @@ -67,14 +67,16 @@
                  -

                  Viewing Monitoring Statistics

                  1. Log in to the management console.
                  2. View the monitoring graphs using either of the following methods.

                    • Method 1: Choose Storage > Cloud Backup and Recovery. In the vault list, locate the vault whose monitoring data you want to view and choose More > View Monitoring Data in the Operation column.
                    • Method 2: Choose Management & Deployment > Cloud Eye > Cloud Service Monitoring > Cloud Backup and Recovery. In the vault list, click View Metric in the Operation column of the vault whose monitoring data you want to view.
                    +

                    Viewing Monitoring Statistics

                    1. Log in to the management console.
                    2. View the monitoring graphs using either of the following methods.

                      • Method 1: Choose Storage > Cloud Backup and Recovery. In the vault list, locate the vault whose monitoring data you want to view and choose More > View Monitoring Data in the Operation column.

                        +
                      • Method 2: Choose Management & Deployment > Cloud Eye > Cloud Service Monitoring > Cloud Backup and Recovery. In the vault list, click View Metric in the Operation column of the vault whose monitoring data you want to view.

                    3. View the vault monitoring data by metric or monitored duration.

                      For more information, see the Cloud Eye User Guide.

                      +

                  -
                  Parent topic: Monitoring
                  +
                  Parent topic: Cloud Eye Monitoring
                  diff --git a/docs/cbr/umn/cbr_03_0115.html b/docs/cbr/umn/cbr_03_0115.html index 343e678c..240f5f01 100644 --- a/docs/cbr/umn/cbr_03_0115.html +++ b/docs/cbr/umn/cbr_03_0115.html @@ -3,7 +3,7 @@

                  Creating an Alarm Rule

                  Cloud Eye allows you to use alarm templates to create alarm rules, making it easy and convenient to add or modify alarm rules for resources or cloud services, especially for a large number of resources and cloud services.

                  You can create alarm rules for CBR.

                  -

                  Procedure

                  1. Log in to the management console.
                  2. In the upper left corner of the page, click and select a region.
                  3. Under Management & Deployment, select Cloud Eye. In the navigation pane on the left, choose Alarm Management > Alarm Rules.
                  4. On the displayed page, click Create Alarm Rule in the upper right corner.
                  5. On the displayed Create Alarm Rule page, configure the parameters.
                    1. Set Name and Description.
                      Parameters for configuring the rule name and description +

                      Creating an Alarm Rule Using Cloud Eye

                      1. Log in to the management console.
                      2. In the upper left corner of the page, click and select a region.
                      3. Under Management & Deployment, select Cloud Eye. In the navigation pane on the left, choose Alarm Management > Alarm Rules.
                      4. On the displayed page, click Create Alarm Rule in the upper right corner.
                      5. On the displayed Create Alarm Rule page, configure the parameters.
                        1. Set Name and Description.
                          Parameters for configuring the rule name and description
                          @@ -142,12 +142,12 @@
                        2. Click Create.
                          3. -

                          After the alarm rule is created, if the metric data reaches the specified threshold or a CBR event happens, Cloud Eye immediately informs you that an exception has occurred. For details, see the Cloud Eye User Guide.

                          +

                          After the alarm rule is created, if the metric data reaches the specified threshold or a CBR event happens, Cloud Eye immediately informs you that an exception has occurred. For details, see the Cloud Eye User Guide.

                          -
                          Parent topic: Monitoring
                          +
                          Parent topic: Cloud Eye Monitoring
                          diff --git a/docs/cbr/umn/cbr_03_0116.html b/docs/cbr/umn/cbr_03_0116.html index 340acd59..9bcc5f92 100644 --- a/docs/cbr/umn/cbr_03_0116.html +++ b/docs/cbr/umn/cbr_03_0116.html @@ -1,11 +1,12 @@ -

                          Migrating a Resource

                          +

                          Migrating Resources from a Vault

                          Migrating a resource means that you dissociate a resource from a vault and then associate it to another vault. All backups of the resource will be migrated to the destination vault.

                          -

                          Constraints

                          • Resources can be migrated only when the source and destination vaults are in the Available or Locked state.
                          • The source and destination vaults for resource migration must be of the same specifications.
                          • The remaining capacity of the destination vault must be greater than the size of resource backups to be migrated.
                          • Cross-account resource migration is currently not supported.
                          • The source and destination vaults must be in the same region.
                          +

                          Notes and Constraints

                          • Resources can be migrated only when the source and destination vaults are in the Available or Locked state.
                          • The source and destination vaults for resource migration must be of the same types. For example, resources in a server backup vault can be migrated to another server backup vault, but cannot be migrated to another disk backup vault.
                          • The remaining capacity of the destination vault must be greater than the size of resource backups to be migrated.
                          • Cross-account resource migration is currently not supported.
                          • The source and destination vaults must be in the same region.

                          Procedure

                          1. Log in to the CBR console.

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

                          2. Find the target vault and click its name. In this example, we will be using the Cloud Server Backups page to illustrate the process.
                          3. Click the Associated Servers tab. Find the target server and click Migrate in the Operation column.

                            +

                          4. Find the target vault and click its name. In this example, we will be using the Cloud Server Backups page to illustrate the process.
                          5. Click the Associated Servers tab. Find the target server and click Migrate in the Operation column.

                            +

                            Figure 1 Migrating a resource

                            @@ -21,7 +22,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_03_0160.html b/docs/cbr/umn/cbr_03_0160.html new file mode 100644 index 00000000..74d0b6e2 --- /dev/null +++ b/docs/cbr/umn/cbr_03_0160.html @@ -0,0 +1,185 @@ + + +

                            Change History

                            +
                            +

                          Parameter

                          Description

                          @@ -125,7 +125,7 @@

                          Notification Object

                          The name of the topic the alarm notification is to be sent to.

                          -

                          If you enable alarm notification, you need to select a topic. If no desirable topics are available, you need to create one first, whereupon the SMN service is invoked. For details about how to create a topic, see the Simple Message Notification User Guide.

                          +

                          If you enable alarm notification, you need to select a topic. If no desirable topics are available, create one and subscribe to it first. For details about how to create a topic, see the Simple Message Notification User Guide.

                          -
                          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

                          Released On

                          +

                          Description

                          +

                          2024-6-30

                          +

                          This issue is the twenty-fifth official release.

                          +

                          Updated the following content:

                          +
                          • Updated some console screenshots.
                          • Modified the constraints in sections "Cross-Region Replication" and "Cross-Region Backup Replication".
                          +

                          2023-10-30

                          +

                          This issue is the twenty-fourth official release.

                          +

                          Updated the following content:

                          +

                          Added support for cross-region replication.

                          +

                          2023-09-13

                          +

                          This issue is the twenty-third official release.

                          +

                          Updated the following content:

                          +

                          Added support for resource migration.

                          +

                          2023-07-02

                          +

                          This issue is the twenty-second official release.

                          +

                          Updated the following content:

                          +

                          Modified the maximum number of tags that can be added to a vault.

                          +

                          2023-04-18

                          +

                          This issue is the twentieth official release.

                          +

                          Updated the following content:

                          +

                          Added some CBR operations that can be recorded by CTS in section "Auditing."

                          +

                          2023-03-02

                          +

                          This issue is the nineteenth official release.

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

                          +

                          Updated the following content:

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

                          2022-11-16

                          +

                          This issue is the seventeenth official release.

                          +

                          Updated the following content:

                          +

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

                          +

                          2022-07-28

                          +

                          This issue is the sixteenth official release.

                          +

                          Updated the following content:

                          +

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

                          +

                          2022-07-20

                          +

                          This issue is the fifteenth official release.

                          +

                          Updated the following content:

                          +
                          • 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 is the fourteenth official release.

                          +

                          Updated the following content:

                          +

                          Modified section "Creating an Alarm Rule."

                          +

                          2022-07-15

                          +

                          This issue is the thirteenth official release.

                          +

                          Updated the following content:

                          +

                          Modified section "Creating an Alarm Rule."

                          +

                          2022-06-23

                          +

                          This issue is the twelfth official release.

                          +

                          Updated the following content:

                          +

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

                          +

                          2022-04-26

                          +

                          This issue the eleventh official release.

                          +

                          Updated the following content:

                          +

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

                          +

                          2022-04-21

                          +

                          This issue is the tenth official release.

                          +

                          Updated the following content:

                          +

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

                          +

                          2022-03-29

                          +

                          This issue is the ninth official release.

                          +

                          Updated the following content:

                          +

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

                          +

                          2022-03-15

                          +

                          This issue is the eighth official release.

                          +

                          Updated the following content:

                          +
                          • 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 is the seventh official release.

                          +

                          Updated the following content:

                          +

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

                          +

                          2020-06-05

                          +

                          This issue is the sixth official release.

                          +

                          Updated the following content:

                          +
                          • 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 is the fifth official release.

                          +

                          Updated the following content:

                          +
                          • 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 is the fourth official release.

                          +

                          Updated the following content:

                          +

                          Accepted for RM-530.

                          +

                          2019-09-04

                          +

                          This issue is the third official release.

                          +

                          Updated the following content:

                          +
                          • 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 is the second official release.

                          +

                          Updated the following content:

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

                          2019-07-30

                          +

                          This issue is the first official release.

                          +
                          +
                          +
                          +
                          +
                          +
                          Parent topic: Appendix
                          +
                          +
                          + diff --git a/docs/cbr/umn/cbr_05_0002.html b/docs/cbr/umn/cbr_05_0002.html index 93e92375..ff0631ae 100644 --- a/docs/cbr/umn/cbr_05_0002.html +++ b/docs/cbr/umn/cbr_05_0002.html @@ -23,7 +23,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_05_0003.html b/docs/cbr/umn/cbr_05_0003.html index dbaff285..4e9c192b 100644 --- a/docs/cbr/umn/cbr_05_0003.html +++ b/docs/cbr/umn/cbr_05_0003.html @@ -26,7 +26,7 @@ \ No newline at end of file diff --git a/docs/cbr/umn/cbr_06_0001.html b/docs/cbr/umn/cbr_06_0001.html index e38bcbd9..9d3b5a36 100644 --- a/docs/cbr/umn/cbr_06_0001.html +++ b/docs/cbr/umn/cbr_06_0001.html @@ -8,8 +8,6 @@
                        3. Backup
                          4. -
                        4. Why Is My Backup Size Larger Than My Disk Size?
                          -
                        5. Restoration
                        6. Policies
                          diff --git a/docs/cbr/umn/cbr_06_0002.html b/docs/cbr/umn/cbr_06_0002.html index 08643876..2fd09e17 100644 --- a/docs/cbr/umn/cbr_06_0002.html +++ b/docs/cbr/umn/cbr_06_0002.html @@ -10,6 +10,8 @@
                        7. What Are the Differences Between Backups and Snapshots?
                          8. +
                        8. Why Is My Backup Size Larger Than My Disk Size?
                          +
                        9. What Are the Differences Between Cloud Server Backup and Cloud Disk Backup?
                          10. diff --git a/docs/cbr/umn/cbr_06_0003.html b/docs/cbr/umn/cbr_06_0003.html index 91513078..8f258bdf 100644 --- a/docs/cbr/umn/cbr_06_0003.html +++ b/docs/cbr/umn/cbr_06_0003.html @@ -1,11 +1,17 @@

                          What Are Full Backup and Incremental Backup?

                          -

                          CBR by default performs a full backup for a resource in the initial backup and incremental backups in all subsequent backups. If a resource has been backed up for many times, and then all of its generated backups are deleted, and the resource is backed up again, the system will also perform a full backup for the resource.

                          -
                          • The initial full backup covers only the used capacity of a disk. If a 100 GB disk contains 40 GB data, the initial backup consumes 40 GB backup space.
                          • Subsequent incremental backup backs up data changed since the last backup. If 5 GB data changed since the last backup, only the 5 GB changed data will be backed up.
                          -

                          CBR allows you to use any backup, no matter it is a full or incremental one, to restore the full data of a resource. By virtue of this, manual or automatic deletion of a backup will not affect the restoration function.

                          -

                          Suppose server X has backups A, B, and C (in time sequence) and every backup involves data changes. If backup B is deleted, you can use backup A or C to restore data. If backup A and backup B are both deleted, you can still use backup C to restore data.

                          -

                          In extreme cases, the size of a backup is the same as the disk size. The used capacity in a full backup and the changed capacity in an incremental backup are calculated based on the data block change in a disk, not by calculating the file change in the operating system. The size of a full backup cannot be evaluated based on the file capacity in the operating system, and the size of an incremental backup cannot be evaluated based on the file size change.

                          +

                          Description

                          A full backup backs up all data at a certain time point.

                          +

                          An incremental backup backs up the changed data since the last full or incremental backup.

                          +

                          CBR uses the permanent incremental backup technology. A full backup is performed for a resource in the initial backup and incremental backups in all subsequent backups. If a full backup expires and is deleted, its next incremental backup will be regarded as the resource's full backup.

                          +

                          Suppose that server X has backups A, B, and C in time sequence. Backup A is a full backup, and backups B and C are incremental backups. Only changed data blocks are backed up in incremental backups and unchanged data blocks are indexed using pointers, so each incremental backup can be regarded as a virtual full backup.

                          +

                          If backup A is deleted, data blocks in backup A indexed by subsequent backups will not be deleted. Only data blocks that are exclusive to backup A are deleted. So, backups B and C can still be used to restore data. Or if backups A and B are deleted, backup C can also be used to restore data independently. There is no obvious difference between their restoration speeds.

                          +
                          Figure 1 Backup mechanism
                          +
                          +

                          Differences

                          • Backup duration: A full backup backs up the entire resource data which is usually larger than an incremental backup, so full backup take a longer time.
                          • Restoration duration: Both full backups and incremental backups can be restored. There is no obvious difference between their restoration speeds.
                          • Reliability: The latest incremental backup depends on the last full backup and intermediate incremental backups. If any backup data block is damaged, subsequent backups may be affected, which will reduce the backup reliability. All full backup data is independent and does not depend on previous backups. So full backups are more reliable.

                            You are advised to configure periodic full backup (for example, once every 30 days) and daily incremental backup to reduce the interval of full backup on which incremental backup depends and improve the reliability of backups.

                            +
                          +
                          +

                          In extreme cases, the size of a backup is the same as the disk size. The used capacity in a full backup and the changed capacity in an incremental backup are calculated based on the data block change in a disk rather than the file change in the operating system. The size of a full backup cannot be evaluated based on the file capacity in the operating system, and the size of an incremental backup cannot be evaluated based on the file size change.

                          @@ -14,3 +20,10 @@
                          + + \ No newline at end of file diff --git a/docs/cbr/umn/cbr_06_0007.html b/docs/cbr/umn/cbr_06_0007.html index 0ee9a53c..70edcf48 100644 --- a/docs/cbr/umn/cbr_06_0007.html +++ b/docs/cbr/umn/cbr_06_0007.html @@ -1,8 +1,10 @@

                          Do I Need to Stop the Server Before Performing a Backup?

                          -

                          No. You can back up servers that are in use. When a server is running, data is written into disks on the server, and some newly generated data is cached in the server memory. During a backup task, data in the memory will not be automatically written into disks, so the disk data and their backups may be inconsistent.

                          -

                          To ensure data integrity, you are advised to perform the backup during off-peak hours when no data is written to the disks.

                          +

                          No. You can back up servers that are in use.

                          +

                          When a server is running, data is written into disks on the server, and some newly generated data is cached in the server memory. During a backup task, data in the memory will not be automatically written into disks, so the disk data and their backups may be inconsistent.

                          +

                          To ensure data integrity, you are advised to perform the backup during off-peak hours when no data is written to the disks.

                          +

                          diff --git a/docs/cbr/umn/cbr_06_0011.html b/docs/cbr/umn/cbr_06_0011.html index 15224e56..8b36b3fd 100644 --- a/docs/cbr/umn/cbr_06_0011.html +++ b/docs/cbr/umn/cbr_06_0011.html @@ -2,6 +2,8 @@

                          Does CBR Support Cross-Region Backup?

                          No. CBR supports only backup and restoration within a region but not across regions.

                          +

                          You can replicate backups in either of the following methods on the CBR console:

                          +
                          • Select a backup from the backup list and manually perform a replication.
                          • Select a backup vault and manually replicate it. Alternatively, you can configure a replication policy to periodically replicate backups that have not been replicated or failed to be replicated to the destination region.
                          diff --git a/docs/cbr/umn/cbr_06_00110.html b/docs/cbr/umn/cbr_06_00110.html new file mode 100644 index 00000000..ff6ebfe4 --- /dev/null +++ b/docs/cbr/umn/cbr_06_00110.html @@ -0,0 +1,16 @@ + + +

                          Why Is My Backup Size Larger Than My Disk Size?

                          +

                          Symptoms

                          • There were files on a server, and the server was backed up. After deleting some files, the server was backed up again. By viewing the used vault capacity, we came to a conclusion that the backup size was not changed or even became bigger.

                            For example, a user backed up a server that contains 100 files. The used vault capacity was A. Then the user deleted 10 files and backed up the server again. The used vault capacity changed to B. B may be the same as A or even larger.

                            +
                          • The ECS backup size is larger than the used disk space obtained from the file system.
                          +
                          +

                          Possible Causes

                          Possible causes are as follows:

                          +
                          • The backup mechanism itself causes this problem. The cloud server backups, SFS Turbo backups, and cloud disk backups created using CBR are all block-level backups. Different from file-level backups, block-level backups are performed by sector (512 bytes) each time.
                          • The metadata of the file systems on the disk occupies disk space.
                          • To reduce performance overhead, the file system adds a delete marker for the deleted file, but does not erase the data that has been written to the sector, and the metadata on the sector still exists. Block-level backups cannot detect whether data on a sector is deleted or not, but only determine whether a backup needs to be performed by checking whether all data blocks are zero blocks.
                          • CBR determines whether data in each sector changes by comparing two snapshots. Data changes include data addition, modification, and deletion. Backup is not performed if there are no data changes. If there are data changes, CBR further checks whether data blocks in the sector are all zero blocks. If so, backup is also not performed. Backups are performed only when there are non-zero blocks. If the data is deleted but metadata in the sector is not, the data block is also recognized as a non-zero block, and backups will be performed.
                          +
                          +
                          +
                          +
                          +
                          Parent topic: Concepts
                          +
                          +
                          + diff --git a/docs/cbr/umn/cbr_06_0013.html b/docs/cbr/umn/cbr_06_0013.html index 15078fc7..15735528 100644 --- a/docs/cbr/umn/cbr_06_0013.html +++ b/docs/cbr/umn/cbr_06_0013.html @@ -3,6 +3,7 @@

                          Do I Need to Stop the Server Before Restoring Data Using Backups?

                          The system shuts down the server before restoring server data, and automatically starts up the server after the restoration is complete.

                          If you deselect Start the server immediately after restoration, you need to manually start the server after the restoration is complete.

                          +

                          Before restoring the disk data, stop the server to which the disk is attached and detach the disk from the server. After the disk data is restored, attach the disk to the server and start the server.

                          diff --git a/docs/cbr/umn/cbr_06_0017.html b/docs/cbr/umn/cbr_06_0017.html index f7fe5f8c..aaf5ba8b 100644 --- a/docs/cbr/umn/cbr_06_0017.html +++ b/docs/cbr/umn/cbr_06_0017.html @@ -1,7 +1,9 @@

                          Can a Disk Be Restored Using Its Backups After Its Capacity Is Expanded?

                          -

                          Yes. After restoration, the capacity of the expanded disk goes back to the original capacity before expansion. If you want to use the capacity added to the disk, you need to attach the restored disk to a server, log in to the server, and then manually modify the file system configuration. For detailed operations, see sections about post-expansion operations on disks in the Elastic Volume Service User Guide.

                          +

                          Yes. After restoration, the capacity of the expanded disk goes back to the original capacity before expansion.

                          +

                          If you want to use the capacity added to the disk, you need to attach the restored disk to a server, log in to the server, and then manually modify the file system configuration.

                          +

                          For details, see Disk Capacity Expansion in the Elastic Volume Service User Guide.

                          diff --git a/docs/cbr/umn/cbr_06_0026.html b/docs/cbr/umn/cbr_06_0026.html deleted file mode 100644 index 395e60ce..00000000 --- a/docs/cbr/umn/cbr_06_0026.html +++ /dev/null @@ -1,15 +0,0 @@ - - -

                          Why Is My Backup Size Larger Than My Disk Size?

                          -

                          Symptoms

                          • There is no difference or an increase in size between the original backup and a backup generated after a file is deleted.
                          • The ECS backup size is larger than the used disk space obtained from the file system.
                          -
                          -

                          Possible Causes

                          Possible causes are as follows:

                          -
                          • The backup mechanism itself causes this problem. The cloud server backups, SFS Turbo backups, and cloud disk backups created using CBR are all block-level backups. Different from file-level backups, block-level backups are performed by sector (512 bytes) each time.
                          • The metadata of the file systems on the disk occupies disk space.
                          • To reduce performance overhead, the file system adds a delete marker for the deleted file, but does not erase the data that has been written to the sector, and the metadata on the sector still exists. Block-level backups cannot detect whether data on a sector is deleted or not, but only determine whether a backup needs to be performed by checking whether all data blocks are zero blocks.
                          • CBR determines whether data in each sector changes by comparing two snapshots. Data changes include data addition, modification, and deletion. Backup is not performed if there are no data changes. If there are data changes, CBR further checks whether data blocks in the sector are all zero blocks. If so, backup is also not performed. Backups are performed only when there are non-zero blocks. If the data is deleted but metadata in the sector is not, the data block is also recognized as a non-zero block, and backups will be performed.
                          -
                          -
                          -
                          -
                          -
                          Parent topic: FAQs
                          -
                          -
                          - diff --git a/docs/cbr/umn/cbr_06_0054.html b/docs/cbr/umn/cbr_06_0054.html index 69a6b0cb..7e359b75 100644 --- a/docs/cbr/umn/cbr_06_0054.html +++ b/docs/cbr/umn/cbr_06_0054.html @@ -13,7 +13,7 @@

              Resources to be backed up or restored

              All disks (system and data disks) on a server

              +

              All disks (system disks and data disks) or some disks on a server

              One or more specified disks (system or data disks)