diff --git a/docs/cbr/umn/cbr_01_0035.html b/docs/cbr/umn/cbr_01_0035.html index 06399ca62..04f94817e 100644 --- a/docs/cbr/umn/cbr_01_0035.html +++ b/docs/cbr/umn/cbr_01_0035.html @@ -1,7 +1,7 @@

Enabling Backup Locking

-

Scenarios

To prevent the backup data from being deleted by mistake or maliciously, you can enable backup locking for vaults to improve data security (eu-nl).

+

Scenarios

To prevent the backup data from being deleted by mistake or maliciously, you can enable backup locking for vaults to improve data security.

Once enabled, all backups in the vault enter the WORM (write once, read many) status. No one can delete the backups that are in their retention periods.

This section describes how to enable backup locking for a vault. You can also enable it when creating a vault.

  • Backup locking does not affect normal backup, restoration, and replication operations.
  • Manual backups are not affected by backup locking and can be manually deleted.
diff --git a/docs/cbr/umn/cbr_02_0003.html b/docs/cbr/umn/cbr_02_0003.html index 1def97a4d..110f27bc6 100644 --- a/docs/cbr/umn/cbr_02_0003.html +++ b/docs/cbr/umn/cbr_02_0003.html @@ -5,7 +5,7 @@

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 Server Backup Vault.
  3. 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.

    -

  4. Determine whether to enable backup locking (eu-nl).

    If enabled, backups in the vault will not be deleted maliciously or by mistake, improving data reliability.

    +

  5. Determine whether to enable backup locking.

    If enabled, backups in the vault will not be deleted maliciously or by mistake, improving data reliability.

    Backup locking cannot be disabled after it is enabled.

    diff --git a/docs/cbr/umn/cbr_02_0004.html b/docs/cbr/umn/cbr_02_0004.html index 522ccd644..e1cf60cea 100644 --- a/docs/cbr/umn/cbr_02_0004.html +++ b/docs/cbr/umn/cbr_02_0004.html @@ -3,7 +3,7 @@

    Creating a Disk Backup Vault

    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. Determine whether to enable backup locking (eu-nl).

      If backup locking is enabled, backups in the vault will not be deleted maliciously or by mistake. This improves data reliability.

      +

    4. In the upper right corner of the page, click Create Disk Backup Vault.
    5. Determine whether to enable backup locking.

      If backup locking is enabled, backups in the vault will not be deleted maliciously or by mistake. This improves data reliability.

      Backup locking cannot be disabled after it is enabled.

      diff --git a/docs/cbr/umn/cbr_02_0010.html b/docs/cbr/umn/cbr_02_0010.html index da66b82ef..2a2a31baa 100644 --- a/docs/cbr/umn/cbr_02_0010.html +++ b/docs/cbr/umn/cbr_02_0010.html @@ -4,7 +4,7 @@

      This section describes how to create an SFS Turbo 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 > SFS Turbo Backups.

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

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

      4. Determine whether to enable backup locking (eu-nl).

        If backup locking is enabled, backups in the vault will not be deleted maliciously or by mistake. This improves data reliability.

        +

      5. Determine whether to enable backup locking.

        If backup locking is enabled, backups in the vault will not be deleted maliciously or by mistake. This improves data reliability.

        Backup locking cannot be disabled after it is enabled.

        diff --git a/docs/cbr/umn/cbr_03_0160.html b/docs/cbr/umn/cbr_03_0160.html index 631c1ff89..ae002ea8b 100644 --- a/docs/cbr/umn/cbr_03_0160.html +++ b/docs/cbr/umn/cbr_03_0160.html @@ -8,7 +8,14 @@ -

        2025-05-27

        +

        2025-06-22

        + +

        This is the thirty-first official release.

        +

        Updated the following content:

        +

        Modified the descriptions in section "Why Is My Backup Size Larger Than My Disk Size?"

        + + +

        2025-05-27

        This issue is the thirtieth official release.

        Updated the following content:

        diff --git a/docs/cbr/umn/cbr_06_00110.html b/docs/cbr/umn/cbr_06_00110.html index ff6ebfe41..f8060eae9 100644 --- a/docs/cbr/umn/cbr_06_00110.html +++ b/docs/cbr/umn/cbr_06_00110.html @@ -5,7 +5,7 @@
      6. 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.
      +
      • 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, the data blocks will not be backed up and will not be counted in the new backup capacity. If there are non-zero blocks, they will be backed up and will be counted in the new backup capacity. 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.