8.3.1
Backup failed with the error “The file or directory is not a reparse point”
8.3.0
Optimized and improved disk space usage during the upload of large files
Implemented automatic backup resume if the upload is interrupted because of the connection issues
OBRM skipped the locked files during backup if the whole system drive was added to the backup set
The log-in window appeared after you installed OBRM in the silent mode
8.2.0
Ability to force the use of the Microsoft VSS provider instead of the default one set in the system
Optimized and improved disk space usage during the upload of large files
OBRM window does not show up after the silent installation is completed
If a backup set included files with unsupported characters in their paths, the backup failed, and user could not edit the backup set (error “Illegal characters: [] in path. Parameter name: path”). Now such files are skipped during backup.
OBRM did not remove some files from the cache folder if the backup was canceled
OBRM installation step where user had to accept the Terms of Service
8.1.4
Implemented additional verification of the data packages before uploading
Optimized and improved the local disk usage
8.1.2
An issue introduced in 8.1.0 release where a file recently added to the backup set might be removed if the backup was canceled interrupted, and all of the following were true:
- the file was a .qbw, .db, .lrcat, or .pst larger than 5 GB (per the default settings); and
- the file (except for .pst) was locked by the system at the start of the backup, and was later no longer locked when the backup was canceled or interrupted.
8.1.0
Before performing a backup, the app cleans up the residual files from the previous backup that are stored in the temp folder
The app now excludes the system cache files, temporary files, and needless system binary files from backup
Backup with direct GCP upload of the files locked by the system failed with the error (“Chunk sending failed”)
A long-running backup with direct GCP uploading failed with the error (“An error occurred while initializing resumable request”)
Canceled backup was marked as failed
8.0.0
Support of direct data protection in the Google Cloud object storage
If the backup engine cannot get the current state of a locked file (because of a VSS issue) within a specified time, it reports the file in the app logs and skips it so the current and further backups could continue
If a backup set included files with unsupported characters in their paths, the backup failed, and user could not edit the backup set (error “Illegal characters: [] in path. Parameter name: path”). Now such files are skipped during backup.
On the first try, the app failed to upload a delta (changed data blocks) for the file version that was recently deleted from the cloud