This shows you the differences between two versions of the page.
Next revision | Previous revision Last revision Both sides next revision | ||
public:announcement:upgrade_advisory_34490 [2022/06/02 16:40] klim created |
public:announcement:upgrade_advisory_34490 [2022/07/08 17:52] klim [What action do I need to take to fix this problem?] |
||
---|---|---|---|
Line 2: | Line 2: | ||
**Posted:** 2022-06-02 | **Posted:** 2022-06-02 | ||
+ | **Revised:** 2022-07-08 | ||
We have recently identified and confirmed a critical bug found in CloudBacko Pro / Lite / Home (v5.1.4.0 to v5.1.4.21) that affects all types of Backup Sets, where source backup data is >32MB, resulting in unrestorable v5.1.4.x data. | We have recently identified and confirmed a critical bug found in CloudBacko Pro / Lite / Home (v5.1.4.0 to v5.1.4.21) that affects all types of Backup Sets, where source backup data is >32MB, resulting in unrestorable v5.1.4.x data. | ||
- | Not affected is restoring data from time period prior to v5.1.4.0 backup dates (ie v5.1.2.0 data is not affected). | + | Not affected is restoring data from time period prior to v5.1.4.0 backup dates (ie v5.1.0.0 data is not affected). |
+ | * <color #FFFFFF>**UPDATE: On 2022-July-11 CloudBacko v5.3.2.0 is released; upgrade to this latest release to fix the issue.**</color> | ||
===== What does this mean? ===== | ===== What does this mean? ===== | ||
- | * Affecting CloudBacko v5.1.4.0 up to v5.1.4.21 , issue that affects **ANY Backup Set types where source files have raw size greater-than 32MB**. | + | * Affecting CloudBacko v5.1.4.0 up to v5.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. |
* v5.1.4.0 to v5.1.4.21 will always find duplicated data from index even Deduplication is OFF. The lookup result will be wrong, hence, the file data is already corrupt. | * v5.1.4.0 to v5.1.4.21 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 | ||
- | ===== What are the affected Ahsay versions? ===== | + | ===== What are the affected CloudBacko versions? ===== |
* CloudBacko v5.1.4.0 up to v5.1.4.21 , where **Deduplication = OFF** at any point during backup runs within these versions | * CloudBacko v5.1.4.0 up to v5.1.4.21 , where **Deduplication = OFF** at any point during backup runs within these versions | ||
- | * CloudBacko v5.1.4.0 up to v5.1.4.21 , where **Deduplication = ON and Migrate Data = ENABLED** (checkbox marked) | + | * <del>CloudBacko v5.1.4.0 up to v5.1.4.21 , where **Deduplication = ON and Migrate Data = ENABLED** (checkbox marked)</del> |
- | * CloudBacko v5.1.4.0 up to v5.1.4.21 , where **Deduplication = ON and Migrate Data = DISABLED** (checkbox unmarked) | + | * <del>CloudBacko v5.1.4.0 up to v5.1.4.21 , where **Deduplication = ON and Migrate Data = DISABLED** (checkbox unmarked)</del> |
+ | * <color #22b14c>[Updated: 2022-06-22] Additional analysis has shown that Backup Sets where **Deduplication = ON (Enabled)** , are __not affected__ by this corruption.</color> | ||
+ | |||
+ | ===== What is the default Deduplication settings? ===== | ||
+ | * By default, Deduplication is ON (enabled), both module and Backup Set. | ||
+ | * It will be OFF (disabled) if Deduplication toggle is OFF manually per Backup Set | ||
+ | * Above are sample default behavior, as there can be other contributing factors that may affect settings, you should review your settings to verify behavior in your environment. | ||
===== What if the user's Source data is less-than 32MB? ===== | ===== What if the user's Source data is less-than 32MB? ===== | ||
Line 35: | Line 44: | ||
===== 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 **hotfix v5.1.4.22 (or higher)** via CloudBacko website (https://www.cloudbacko.com/cloudbacko-support)</color>. | + | * <color #ed1c24>**Take immediate action** to download and install latest <del>**hotfix v5.1.4.22 (or higher)**</del> via CloudBacko website (https://www.cloudbacko.com/cloudbacko-support)</color>. |
- | * 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-July-11 we released CloudBacko v5.3.2.0; it is recommended to upgrade to this latest release as it includes prior hotfixes. Hotfixes for v5.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.] | ||
===== What if my maintenance has already expired? How do I upgrade? ===== | ===== What if my maintenance has already expired? How do I upgrade? ===== |