diff --git a/docs/cbr/umn/ALL_META.TXT.json b/docs/cbr/umn/ALL_META.TXT.json index 1cf9d948..4624ebd2 100644 --- a/docs/cbr/umn/ALL_META.TXT.json +++ b/docs/cbr/umn/ALL_META.TXT.json @@ -1015,7 +1015,7 @@ "node_id":"cbr_03_0037.xml", "product_code":"cbr", "code":"57", - "des":"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 ", + "des":"Quotas can limit the number or amount of resources available to users, such as the maximum number of ECS or EVS disks that can be created.If the existing resource quota c", "doc_type":"usermanual", "kw":"Quotas,User Guide", "search_title":"", @@ -1249,7 +1249,7 @@ "node_id":"cbr_06_0011.xml", "product_code":"cbr", "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", + "des":"No. CBR supports only backup and restoration within a region but not across regions.", "doc_type":"usermanual", "kw":"Does CBR Support Cross-Region Backup?,Backup,User Guide", "search_title":"", diff --git a/docs/cbr/umn/CLASS.TXT.json b/docs/cbr/umn/CLASS.TXT.json index 8a197cc2..2341cb98 100644 --- a/docs/cbr/umn/CLASS.TXT.json +++ b/docs/cbr/umn/CLASS.TXT.json @@ -504,7 +504,7 @@ "code":"56" }, { - "desc":"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 ", + "desc":"Quotas can limit the number or amount of resources available to users, such as the maximum number of ECS or EVS disks that can be created.If the existing resource quota c", "product_code":"cbr", "title":"Quotas", "uri":"cbr_03_0037.html", @@ -621,7 +621,7 @@ "code":"69" }, { - "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", + "desc":"No. CBR supports only backup and restoration within a region but not across regions.", "product_code":"cbr", "title":"Does CBR Support Cross-Region Backup?", "uri":"cbr_06_0011.html", diff --git a/docs/cbr/umn/cbr_02_0006.html b/docs/cbr/umn/cbr_02_0006.html index 97e81dda..084e270f 100644 --- a/docs/cbr/umn/cbr_02_0006.html +++ b/docs/cbr/umn/cbr_02_0006.html @@ -23,6 +23,7 @@

+

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

    Table 1 Parameter description

    Parameter

    @@ -58,7 +59,7 @@

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

    Figure 3 Full Backup

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

    +
    • 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 Creating an Image from a Cloud Server Backup.

    • diff --git a/docs/cbr/umn/cbr_02_0007.html b/docs/cbr/umn/cbr_02_0007.html index 7ac3bf14..b506ae9c 100644 --- a/docs/cbr/umn/cbr_02_0007.html +++ b/docs/cbr/umn/cbr_02_0007.html @@ -21,6 +21,7 @@

    +

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

    @@ -58,7 +59,7 @@

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

    Figure 3 Full Backup

  • Click OK. CBR automatically creates a backup for the disk.

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

    -

    If you delete data from the disk during the backup, the deleted data may fail to be backed up. Therefore, to ensure data integrity, delete the target data after the backup is complete, and then perform the backup.

    +
    • If you delete data from the disk 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 use the backup to restore disk data. For details, see Restoring from a Cloud Disk Backup.

    • diff --git a/docs/cbr/umn/cbr_02_0012.html b/docs/cbr/umn/cbr_02_0012.html index 232b5d83..0cb9f4aa 100644 --- a/docs/cbr/umn/cbr_02_0012.html +++ b/docs/cbr/umn/cbr_02_0012.html @@ -13,11 +13,13 @@

    +

    • 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

      +

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

    @@ -52,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.

    +
    • 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 Creating a File System from an SFS Turbo Backup.

    • diff --git a/docs/cbr/umn/cbr_03_0003.html b/docs/cbr/umn/cbr_03_0003.html index 616cfb1a..ac3f8902 100644 --- a/docs/cbr/umn/cbr_03_0003.html +++ b/docs/cbr/umn/cbr_03_0003.html @@ -10,6 +10,7 @@

    +

    diff --git a/docs/cbr/umn/cbr_03_0005.html b/docs/cbr/umn/cbr_03_0005.html index 03dfaef8..2683011b 100644 --- a/docs/cbr/umn/cbr_03_0005.html +++ b/docs/cbr/umn/cbr_03_0005.html @@ -11,6 +11,7 @@

    +

  • Confirm the information and click Yes.
    • diff --git a/docs/cbr/umn/cbr_03_0006.html b/docs/cbr/umn/cbr_03_0006.html index 6a58be21..06b3ff45 100644 --- a/docs/cbr/umn/cbr_03_0006.html +++ b/docs/cbr/umn/cbr_03_0006.html @@ -10,6 +10,7 @@

    +

    diff --git a/docs/cbr/umn/cbr_03_0014.html b/docs/cbr/umn/cbr_03_0014.html index af08d930..2475fbcd 100644 --- a/docs/cbr/umn/cbr_03_0014.html +++ b/docs/cbr/umn/cbr_03_0014.html @@ -16,6 +16,7 @@

    +

    @@ -30,6 +31,7 @@

    +

    @@ -45,6 +47,7 @@

    +

    diff --git a/docs/cbr/umn/cbr_03_0015.html b/docs/cbr/umn/cbr_03_0015.html index 67ae0df1..9abed435 100644 --- a/docs/cbr/umn/cbr_03_0015.html +++ b/docs/cbr/umn/cbr_03_0015.html @@ -15,6 +15,7 @@

    +

  • Click Yes.
    • diff --git a/docs/cbr/umn/cbr_03_0018.html b/docs/cbr/umn/cbr_03_0018.html index 9ebe2381..40359c37 100644 --- a/docs/cbr/umn/cbr_03_0018.html +++ b/docs/cbr/umn/cbr_03_0018.html @@ -17,7 +17,6 @@

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

    Figure 1 Creating a replica

    -

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

    diff --git a/docs/cbr/umn/cbr_03_0025.html b/docs/cbr/umn/cbr_03_0025.html index 7c9316a8..1dc6e31d 100644 --- a/docs/cbr/umn/cbr_03_0025.html +++ b/docs/cbr/umn/cbr_03_0025.html @@ -3,6 +3,7 @@

    Creating a Backup Policy

    A backup policy allows CBR to automatically back up vaults at specified times or intervals. Periodic backups can be used to restore data quickly against data corruption or loss.

    To implement periodic backups, you need a backup policy first. You can use the default backup policy or create one as needed.

    +

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

    Constraints

    • Backup policies can be applied to the following types of vaults: server backup vaults, disk backup vaults
    • A backup policy must be enabled before it can be used for periodic backups.
    • A maximum of 32 backup policies can be created in each account.
    • When expired backups are deleted, automatic backups will be deleted, but manual backups will not.
    • Only servers in the Running or Stopped state and disks in the Available or In-use state can be backed up.
    • CBR by default performs a full backup for a resource in the initial backup and incremental backups in all subsequent backups.
    • The minimum interval between two full backups is 1 day.

    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.
      @@ -13,65 +14,66 @@

      +

    2. Set the backup policy parameters. Table 1 describes the parameters.

      -

      Table 1 Backup policy parameters

      Parameter

      +
      - - - - - - - - - - - - - - - - - - - - diff --git a/docs/cbr/umn/cbr_03_0029.html b/docs/cbr/umn/cbr_03_0029.html index 97b7b94e..ef209514 100644 --- a/docs/cbr/umn/cbr_03_0029.html +++ b/docs/cbr/umn/cbr_03_0029.html @@ -7,9 +7,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. 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

        +

        -

        -

        diff --git a/docs/cbr/umn/cbr_03_0030.html b/docs/cbr/umn/cbr_03_0030.html index 4fe46cc7..aae3da24 100644 --- a/docs/cbr/umn/cbr_03_0030.html +++ b/docs/cbr/umn/cbr_03_0030.html @@ -7,9 +7,9 @@

      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
        +

        -

        diff --git a/docs/cbr/umn/cbr_03_0032.html b/docs/cbr/umn/cbr_03_0032.html index ac3ba7cc..cea941d1 100644 --- a/docs/cbr/umn/cbr_03_0032.html +++ b/docs/cbr/umn/cbr_03_0032.html @@ -18,6 +18,7 @@

        +

      4. (Optional) Deselect Start the server immediately after restoration.

        If you do so, manually start the server after the restoration is complete.

        Servers will be shut down during restoration, so you are advised to perform a restoration during off-peak hours.

        diff --git a/docs/cbr/umn/cbr_03_0033.html b/docs/cbr/umn/cbr_03_0033.html index 2679d2d1..44bd9698 100644 --- a/docs/cbr/umn/cbr_03_0033.html +++ b/docs/cbr/umn/cbr_03_0033.html @@ -22,7 +22,7 @@

      5. Click Yes. You can check whether data is successfully restored on the Backups tab page of Cloud Disk Backups or on the EVS console.

        When the status of the backup changes to Available, the restoration is successful. The resource is restored to the state when that backup was created.

        -

      6. After the restoration is complete, re-attach the disk to the server. For details, see section "Attaching an Existing Non-Shared Disk" in the Elastic Volume Service User Guide.
      +

    3. After the restoration is complete, re-attach the disk to the server. For details, see section "Attaching a Non-Shared Disk" in the Elastic Volume Service User Guide.
      4. diff --git a/docs/cbr/umn/cbr_03_0037.html b/docs/cbr/umn/cbr_03_0037.html index 5368f8fa..42deb415 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 ECS 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.

        diff --git a/docs/cbr/umn/cbr_03_0107.html b/docs/cbr/umn/cbr_03_0107.html index ed14032b..e5a4ffdf 100644 --- a/docs/cbr/umn/cbr_03_0107.html +++ b/docs/cbr/umn/cbr_03_0107.html @@ -6,7 +6,6 @@

      4. Click the Backups tab and locate the desired backup. For details, see Viewing a Backup.
      5. Click Create File System in the Operation column of the backup. The button is available only when the backup status is Available.
      6. 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.

      7. Click Create Now.
      8. Go back to the file system list and check whether the file system is successfully created.

        You will see the file system status change as follows: Creating, Available, Restoring, Available. You may not notice the Restoring status because Instant Restore is supported and the restoration speed is very fast. After the file system status has changed from Creating to Available, the file system is successfully created. After the status has changed from Restoring to Available, backup data has been successfully restored to the created file system.

        diff --git a/docs/cbr/umn/cbr_03_0115.html b/docs/cbr/umn/cbr_03_0115.html index 240f5f01..40a082c0 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.

        -

        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 +

            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
      Table 1 Backup policy parameters

      Parameter

      Description

      +

      Description

      Example Value

      +

      Example Value

      Type

      +

      Type

      Select a policy type. In this section, we select the backup policy.

      +

      Select a policy type. In this section, we select the backup policy.

      Backup policy

      +

      Backup policy

      Name

      +

      Name

      Backup policy name

      +

      Backup policy name

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

      backup_policy

      +

      backup_policy

      Status

      +

      Status

      Whether to enable the backup policy.

      +

      Whether to enable the backup policy.

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

      +

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

      Backup Frequency

      +

      Backup Frequency

      Select a 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

      +

      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

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

      +

      00:00, 02:00

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

      Retention Rule

      +

      Retention Rule

      Rule that specifies how backups will be retained

      +

      Rule that specifies how backups will be retained

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

        @@ -81,7 +83,7 @@

      6 months

      +

      6 months

      Parameter

      Description

      diff --git a/docs/cbr/umn/cbr_03_0116.html b/docs/cbr/umn/cbr_03_0116.html index 9bcc5f92..f18b2131 100644 --- a/docs/cbr/umn/cbr_03_0116.html +++ b/docs/cbr/umn/cbr_03_0116.html @@ -9,7 +9,7 @@

      Figure 1 Migrating a resource
      -

      +

    4. Select the destination vault and click OK.
    5. View the migration progress on the Tasks page. If Status changes to Successful, the resource has been migrated.
    6. Go to the destination vault to confirm that the resource has been associated and all its backups have been migrated.
      7. diff --git a/docs/cbr/umn/cbr_06_0011.html b/docs/cbr/umn/cbr_06_0011.html index 8b36b3fd..15224e56 100644 --- a/docs/cbr/umn/cbr_06_0011.html +++ b/docs/cbr/umn/cbr_06_0011.html @@ -2,8 +2,6 @@

      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/en-us_image_0000001706852702.png b/docs/cbr/umn/en-us_image_0000001706852702.png index f67dc278..b81ae767 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_0000001754810509.png b/docs/cbr/umn/en-us_image_0000001754810509.png index 680e60eb..838e5dfc 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_0000001992180742.png b/docs/cbr/umn/en-us_image_0000001992180742.png index 689c0538..acff1d94 100644 Binary files a/docs/cbr/umn/en-us_image_0000001992180742.png and b/docs/cbr/umn/en-us_image_0000001992180742.png differ diff --git a/docs/cbr/umn/en-us_image_0224256701.png b/docs/cbr/umn/en-us_image_0224256701.png index 7f974864..cb7ff0e2 100644 Binary files a/docs/cbr/umn/en-us_image_0224256701.png and b/docs/cbr/umn/en-us_image_0224256701.png differ