Sidebar

Announcement

CloudBacko Pro

CloudBacko Lite

CloudBacko Home

CloudBacko App

License

Features

Hotfix

Discussion

Can't Find What You Need?

FAQ

public:announcement:upgrade_advisory_34490

This is an old revision of the document!


CloudBacko Upgrade Advisory (#34490) - Data corruption issue on any v5.1.4.0 to v5.1.4.21 backup types

Posted: 2022-06-02

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

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.
  • Example, “tasks.zip” is 40MB, is affected.
  • Example, “mylist.txt” is 2MB, is not affected.

What happened?

  • This happens in lookup (find duplicated data) logic in backup of all Backup Set types, regardless if Deduplication is ON or 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.

What can the user expect?

  • Unable to restore due to corrupt backup data

What are the affected Ahsay 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)
  • CloudBacko v5.1.4.0 up to v5.1.4.21 , where Deduplication = ON and Migrate Data = DISABLED (checkbox unmarked)

What if the user's Source data is less-than 32MB?

  • It is not affected. These source data isn't chunked for Deduplication.

What if the user's Source data to backup is a mix of greater-than and less-than 32MB?

  • It depends on the conditions stated above.

Is there workaround?

  • No workaround. Data must be backup again after fix is applied.

What action do I need to take to fix this problem?

  • Take immediate action to download and install latest hotfix v5.1.4.22 (or higher) via CloudBacko website (https://www.cloudbacko.com/cloudbacko-support).
  • 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.

What if my maintenance has already expired? How do I upgrade?

  • Stop! Do not upgrade until you contact a member our Support team for assistance with your License upgrade.
public/announcement/upgrade_advisory_34490.1654159213.txt.gz · Last modified: 2022/06/02 16:40 by klim