...

Recently it has been noticed that the Studio backups can potentially be corrupted, without it being noticed in the backup process. In the specific case that we encountered the backup wasn't corrupted in total, but only partlypartially.

However we find We concluded that this is still a high risk problem that should be addressed as soon as possible by our clients customers and partners. It must be prevented that in the unfortunate situation that when you have to rely on restoring a backup that it is this backup has become corrupted.

There is no risk or impact on the regular versioning system being used dailly by the Studio. Only the backup system is impacted.

Solution

This issue has already been fixed and released in Blueriq versions 14.2.211, 13.13.3 and 12.13.28 (release released on August 17th 2021).

Primary solution: to upgrade to these versions or higher as soon as possible. Once the upgrade is complete perform a new backup.

If this is not possible the alternative temporary strategy, untill until the moment you can upgrade, is:

1. Check if your current backup is uncorrupted, by following these actions:
   1. restore your backup in your a non-primary (preferably even a temporary) Studio environment. If you need a temporary license file please contact the Blueriq Support Desk.
   2. open all repositories individually in Studio and check if you can perform a 'Validate project' for the projects in each repositorybranch.
2. Create a tempory temporary backup strategy by backing up the entire Studio server VM.

Please contact Blueriq Support if you have any questions regarding this topic or if these options solutions prove to be challenging.

Background information

asd