![]() ![]() *This article was first published on July 4 2023, and updated on July 5 2023. ![]() If you need further assistance, please contact our Technical Support team. Following the release of v12.0.3r1, this scenario is now a standard inclusion in our QA test matrix. This issue was first discovered just over a week ago on June 23 2023. ![]() However, please note that backups created by v12.0.3 will NOT be recoverable.After upgrading to v12.0.3r1, you can continue your backups as normal with the existing job.This issue has been addressed in v12.0.3r1, and if you are affected, you will need to follow these steps: In v12.0.3 of BackupAssist Classic, (with the exception of Tape Drives) backups that generate Zip files greater than 4GB in size will encounter an error when trying to restore files that are less than 200MB in size. Encryption support across all destinations. Designed from the ground up by BackupAssist but utilising standard VHDX disk containers supporting many different backup destinations making it easy to manage your backups. NOTE: This issue does NOT affect File Archiving to Tape Drives (Tape Archiving Add-on). This is an alternative backup Engine to the Windows Imaging engine used in System protection Jobs. If you are running BackupAssist Classic v12.0.3 and are running File Archiving backups, your backups may be corrupted and you need to upgrade to v12.0.3r1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |