public:announcement:upgrade_advisory_34490

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
public:announcement:upgrade_advisory_34490 [2022/07/06 10:23]
klim
public:announcement:upgrade_advisory_34490 [2022/07/11 09:37] (current)
klim
Line 2: Line 2:
  
 **Posted:** 2022-06-02 **Posted:** 2022-06-02
-**Revised:​** 2022-06-27+**Revised:​** 2022-07-11
  
 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).
  
 +      * **UPDATE: On 2022-July-11 CloudBacko v5.3.2.0 is released; upgrade to this latest release to fix the issue.**
  
 ===== What does this mean? =====  ===== What does this mean? ===== 
Line 21: Line 22:
   * 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
   * <​del>​CloudBacko v5.1.4.0 up to v5.1.4.21 , where **Deduplication = ON and Migrate Data = ENABLED** (checkbox marked)</​del>​   * <​del>​CloudBacko v5.1.4.0 up to v5.1.4.21 , where **Deduplication = ON and Migrate Data = ENABLED** (checkbox marked)</​del>​
Line 43: 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 ​(removecorrupted ​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 will automatically ​remove Blocks ​(BAKfrom the Destination 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? ===== 
public/announcement/upgrade_advisory_34490.1657074225.txt.gz · Last modified: 2022/07/06 10:23 by klim