public:announcement:ahsay_upgrade_advisory_34490
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
public:announcement:ahsay_upgrade_advisory_34490 [2022/06/02 15:00] kirk.lim created |
public:announcement:ahsay_upgrade_advisory_34490 [2022/06/27 16:01] (current) kirk.lim |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| **Posted:** 2022-06-02 | **Posted:** 2022-06-02 | ||
| + | **Revised:** 2022-06-27 | ||
| We have recently identified and confirmed a critical bug found in AhsayCBS / OBM / ACB v9 (v9.1.2.17 to v9.1.4.21) that affects all types of Backup Sets, where source backup data is >32MB, resulting in unrestorable v9 data. | We have recently identified and confirmed a critical bug found in AhsayCBS / OBM / ACB v9 (v9.1.2.17 to v9.1.4.21) that affects all types of Backup Sets, where source backup data is >32MB, resulting in unrestorable v9 data. | ||
| Line 8: | Line 9: | ||
| Not affected are Client Agents (OBM, ACB) running v8, or pre-v9.1.2.17. | Not affected are Client Agents (OBM, ACB) running v8, or pre-v9.1.2.17. | ||
| + | |||
| + | * **UPDATE: On 2022-June-27 AhsayCBS v9.3.2.0 is released; upgrade to this latest release to fix the issue.** | ||
| ===== What does this mean? ===== | ===== What does this mean? ===== | ||
| - | * Affecting Ahsay v9.1.2.17 up to v9.1.4.21 , issue that affects **ANY Backup Set types where source files have raw size greater-than 32MB**. | + | * Affecting Ahsay v9.1.2.17 up to v9.1.4.21 , for **ANY Backup Set types where source files have raw size greater-than 32MB**, and Deduplication = OFF. |
| * Example, "tasks.zip" is 40MB, is affected. | * Example, "tasks.zip" is 40MB, is affected. | ||
| * Example, "mylist.txt" is 2MB, is not affected. | * Example, "mylist.txt" is 2MB, is not affected. | ||
| ===== What happened? ===== | ===== What happened? ===== | ||
| - | * This happens in lookup (find duplicated data) logic in backup of all Backup Set types, regardless if Deduplication is ON or OFF. | + | * This happens in lookup (find duplicated data) logic in backup of all Backup Set types, when Deduplication is OFF. |
| * v9 will always find duplicated data from index even Deduplication is OFF. The lookup result will be wrong, hence, the file data is already corrupt. | * v9 will always find duplicated data from index even Deduplication is OFF. The lookup result will be wrong, hence, the file data is already corrupt. | ||
| + | |||
| ===== What can the user expect? ===== | ===== What can the user expect? ===== | ||
| * Unable to restore due to corrupt backup data | * Unable to restore due to corrupt backup data | ||
| Line 23: | Line 27: | ||
| ===== What are the affected Ahsay versions? ===== | ===== What are the affected Ahsay versions? ===== | ||
| * Ahsay v9.1.2.17 up to v9.1.4.21 , where **Deduplication = OFF** at any point during backup runs within these versions | * Ahsay v9.1.2.17 up to v9.1.4.21 , where **Deduplication = OFF** at any point during backup runs within these versions | ||
| - | * Ahsay v9.1.2.17 up to v9.1.4.21 , where **Deduplication = ON and Migrate Data = ENABLED** (checkbox marked) | + | * <color #c3c3c3><del>Ahsay v9.1.2.17 up to v9.1.4.21 , where **Deduplication = ON and Migrate Data = ENABLED** (checkbox marked)</del></color> |
| - | * Ahsay v9.1.2.17 up to v9.1.4.21 , where **Deduplication = ON and Migrate Data = DISABLED** (checkbox unmarked) | + | * <color #c3c3c3><del>Ahsay v9.1.2.17 up to v9.1.4.21 , where **Deduplication = ON and Migrate Data = DISABLED** (checkbox unmarked)</del></color> |
| + | * <color #22b14c>[Updated: 2022-06-22] Additional analysis has shown that Backup Sets where **Deduplication = ON (Enabled)** , are __not affected__ by this corruption.</color> | ||
| - | <HTML> | ||
| - | <!-- | ||
| ===== What is the default Deduplication settings? ===== | ===== What is the default Deduplication settings? ===== | ||
| * By default, Deduplication is ON (enabled), both module and Backup Set. | * By default, Deduplication is ON (enabled), both module and Backup Set. | ||
| Line 34: | Line 37: | ||
| * Deduplication module is automatically assigned when CBS v7/v8 is upgraded to CBS v9, and Deduplication toggle=ON if In-File Delta was enabled in pre-v9 Backup Sets. | * Deduplication module is automatically assigned when CBS v7/v8 is upgraded to CBS v9, and Deduplication toggle=ON if In-File Delta was enabled in pre-v9 Backup Sets. | ||
| * It will be OFF (disabled) if either Deduplication toggle is OFF manually per Backup Set, by Policy, or Deduplication module is not enabled. If you use Ahsay API or third-party app to create or manage users, you should verify your behavior. | * It will be OFF (disabled) if either Deduplication toggle is OFF manually per Backup Set, by Policy, or Deduplication module is not enabled. If you use Ahsay API or third-party app to create or manage users, you should verify your behavior. | ||
| + | * Above are sample default behavior, as there can be other contributing factors that may affect settings, you should review your CBS and user settings to verify behavior in your environment. | ||
| + | |||
| + | <HTML> | ||
| + | <!-- | ||
| ===== What is the default Migrate Data setting? ===== | ===== What is the default Migrate Data setting? ===== | ||
| * The setting for pre-existing Backup Sets, created prior to v9, is OFF (disabled) | * The setting for pre-existing Backup Sets, created prior to v9, is OFF (disabled) | ||
| Line 78: | Line 85: | ||
| ===== What action do I need to take to fix this problem? ===== | ===== What action do I need to take to fix this problem? ===== | ||
| - | * <color #ed1c24>**Take immediate action** to download and install latest release of **AhsayCBS v9** and **hotfix v9.1.4.22 (or higher)** via Ahsay Partner Portal (https://www.ahsay.com/partners)</color>. The latest posted hotfix is bundled with Auto Update (AUA) binaries to push the client hotfix to OBM and ACB devices when CBS AUA feature is enabled per user. | + | * <color #ed1c24>**Take immediate action** to download and install latest release of **AhsayCBS v9** <del>and **hotfix v9.1.4.22 (or higher)** via Ahsay Partner Portal (https://www.ahsay.com/partners)</del></color>. <del>The latest posted hotfix is bundled with Auto Update (AUA) binaries to push the client hotfix to OBM and ACB devices when CBS AUA feature is enabled per user.</del> |
| - | * Once required minimum hotfix version is applied, the next backup job will automatically first run a PDIC to handle (remove) corrupted backup file, then reupload source backup file that was corrupted and correctly update the migrate status table. | + | * **UPDATE: On 2022-June-27 we released AhsayCBS v9.3.2.0; it is recommended to upgrade to this latest release as it includes prior hotfixes. Hotfixes for v9.1.4.x is no longer available.** |
| + | * Once required minimum hotfix version is applied, as a one-time routine the next backup job <del>will automatically first run a PDIC</del> [//corrected: 2022-06-21//] will automatically remove Blocks (BAK) containing backup files that reference invalid checksum file chunks, then reupload source backup file that was corrupted and correctly update the migrate status table. A flag will be set in the Index to denote fix was applied ( likewise reverting the Index to an older copy will retrigger the fix ). [Shared Blocks (BAK), a block containing multiple small source files (valid and corrupt), won't be purged until all contents of shared block has cycled through changes and surpass Retention period.] | ||
| + | * Showing when the fix was applied, you can review the next run's backup set log file, for entry "//Run to remove backup files referencing dummy checksum file chunks for once...Completed//" | ||
| ===== What if my maintenance has already expired? How do I upgrade? ===== | ===== What if my maintenance has already expired? How do I upgrade? ===== | ||
public/announcement/ahsay_upgrade_advisory_34490.1654153203.txt.gz · Last modified: 2022/06/02 15:00 by kirk.lim