BackupAssist full changelog

New: added basic Server 2025 support:
All backup types, restores, and BMR recoveries are confirmed, including Exchange, SQL, and Hyper-V scenarios. CryptoSafeGuard and Cyber Black Box are also confirmed.
Note that Exchange EGR on Server 2025 is not yet fully confirmed, though it seems most functionality is working.
New System Protection:
Improve error message when the destination volume is sparse.
Include a new warning BA6127 if automount is disabled and the backup fails.
Improve stability through file copy retries where possible.
Use fallback file system traversal when NTFS errors occur (also when using Legacy System Protection).
Avoid infinite retries when write errors reoccur in early stages of reopening a vhd file.
Fixed regression since 14.0.1, where non-critical deduplication volumes are automatically added to every BMR backup with VSS applications selected, even if they are not necessary or selected.
Other backup types:
All backup types: Improve VSS warnings to indicate when the VSS writers are unstable. This could happen if the backup process is killed after VSS writers have become involved in a backup.
Cloud Backup: Fix rare issue "Only one asynchronous reader is allowed time at one time" that could theoretically affect Cloud Backups on some multi-core machines.
Cloud Backup: Fix “WebException” issues reported on rare installs of Cloud Backups caused by incorrect handling of some reparse points.
Legacy System Protection: New jobs using Data Container will only use VHDX format in all cases.
Network backups: Avoid retrying network writes and eventual timeouts if the destination becomes full.
Restores and Test Restores:
Show a warning message if Hyper-V Granular restores are attempted from an unsupported dynamic disk.
Avoid having CryptoSafeGuard Shield lock the whole destination drive during Test Restore of New System Protection backups.
Fixed the workflow for Cloud Backup restores when the access keys used for backup have subsequently changed.