Release notes for Cloud Backup for Windows
8.4.0
ADDED
SOS-14244
Support for AWS S3 as a Bring Your Own Storage (BYOS) solution
CHANGED
SOS-14495
Improved the UltraSafe MAX account type
FIXED
SOS-14339
Incorrect links to the Microsoft SQL and Microsoft Exchange backup knowledge base articles on the DOCS portal
FIXED
SOS-13594
An issue where the cache folder was not always cleared after backup completion
FIXED
SOS-14376
An issue where backed-up data could incorrectly include system files and folders from the root of the C:\ drive, even when those items were neither selected for backup nor present on the system.
REMOVED
SOS-13251
The ability to create a trial account from the backup client
REMOVED
SOS-13059
The Upgrade button from the backup client
8.3.1
FIXED
SOS-13857
Backup failed with the error “The file or directory is not a reparse point”
8.3.0
CHANGED
SOS-13353
Optimized and improved disk space usage during the upload of large files
CHANGED
SOS-13602
Implemented automatic backup resume if the upload is interrupted because of the connection issues
FIXED
SOS-13779
OBRM skipped the locked files during backup if the whole system drive was added to the backup set
FIXED
SOS-13815
The log-in window appeared after you installed OBRM in the silent mode
8.2.0
ADDED
SOS-13540
Ability to force the use of the Microsoft VSS provider instead of the default one set in the system
CHANGED
SOS-13452
Optimized and improved disk space usage during the upload of large files
CHANGED
SOS-13444
OBRM window does not show up after the silent installation is completed
FIXED
SOS-13625
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.
FIXED
SOS-13595
OBRM did not remove some files from the cache folder if the backup was canceled
REMOVED
SOS-13558
OBRM installation step where user had to accept the Terms of Service
8.1.4
CHANGED
SOS-13520
Implemented additional verification of the data packages before uploading
CHANGED
SOS-13474
Optimized and improved the local disk usage
8.1.2
FIXED
SOS-13476
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
ADDED
SOS-13399
Before performing a backup, the app cleans up the residual files from the previous backup that are stored in the temp folder
CHANGED
SOS-13236
The app now excludes the system cache files, temporary files, and needless system binary files from backup
FIXED
SOS-13274
Backup with direct GCP upload of the files locked by the system failed with the error (“Chunk sending failed”)
FIXED
SOS-13277
A long-running backup with direct GCP uploading failed with the error (“An error occurred while initializing resumable request”)
FIXED
SOS-13210
Canceled backup was marked as failed
8.0.0
ADDED
SOS-13007
Support of direct data protection in the Google Cloud object storage
CHANGED
SOS-12261
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
CHANGED
SOS-13112
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.
FIXED
SOS-13132
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