Backup server data at the block level bypassing the file system and reading data directly from the disk or volume. Block-level backup provides advantages over traditional file backup technologies including the speed of completing a backup operation, a drastic reduction in disk and network I/O, the ability to perform backups as often as every 15 minutes and no performance penalty for servers having a large number of files.
We are pleased to announce the release of Server Backup Manager 6.4. This release includes a new feature called Archive, which allows you to backup recovery points to Amazon Glacier or FTP/FTPS for offsite redundancy and long-term data archiving.
- A new Archive feature has been added that allows you to create offsite backup of recovery points using Amazon Glacier or FTP/FTPS.
- Archive replaces Disk Safe Replication.
- Archived recovery points are managed just like normal recovery points.
- Archived recovery points are added and removed from the archive automatically based on the retention policy you create.
- You can use archive along with site to site replication.
- Archive is a licensed add on, contact R1Soft sales for more information.
- The Server Backup Windows agent is now distributed as a msi package.
- Improvements to user interface responsiveness.
Server Backup Manager
- Resolved crash of Server Backup Manager due to RHEL stackguard update.
- Resolved an issue causing the Use Alternate Settings check box to be hidden in the Restore window.
- Fixed an issue that could result in an “Invalid Server” error when trying to restore an Exchange 2007 database to the original location.
- Resolved an issue that caused filters on the Dashboard to not work properly if protected machines were in an “unknown” state.
- Fixed an error that caused the Policy window to close without saving changes if the number of recovery points to retain was changed.
- Fixed an error resulting in snapshot unmount failures.
- Resolved an issue causing power users to see only one policy for a protected machine.
- Fixed a bug in the API causing the lastReplicationRunTime and nextReplicationRunTime fields to display incorrectly.
- Fixed a Java exception error that could have prevented a database from being restored.
- Resolved an issue where recovery points did not load if the protected machine had more than one Disk Safe.
- Resolved an issue that could result in MySQL and MariaDB authentication failures during a database restore.
- Resolved “Unable to open snapshot device” error that prevented a protected machine from backing up.
- An issue that resulted in UI timeouts and Server Error 500 has been resolved.
You must have an active maintenance account to upgrade. If you have a perpetual (non-heartbeat) license, it will be converted to a heartbeat license automatically upon upgrade. Make sure your SBM has https connectivity to complete this conversion. During the upgrade, you will be notified of the change and will be given the option to revert back to the previous version you were running.