Problem

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

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

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

Solution

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

Primary solution: to upgrade to these versions or higher as soon as possible.

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

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

Please contact Blueriq Support if these options prove to be challenging.