|Linux Manager/Agent Build Version:||5.10.0 build 20|
|Windows Manager/Agent Build Version:|| 5.10.0 build 20
|Recommended Module Version:||4.6.0 build 27|
A 64-bit operating system is required for the Backup Manager. See the Systems Requirements section for details.
|MySQL users planning an upgrade|
|Important Upgrade Considerations|
Server Backup Manager 5.10.0 only supports upgrades from versions 5.6.0 and later. If you are on a previous version of SBM, upgrade to version 5.6.0 before attempting to upgrade to version 5.10.0.
Server Backup Manager software must be upgraded in the following order:
After completing the software updates in environments using Data Center Console, R1Soft recommends refreshing the associated SBM server data for proper syncing.
When users who have environments with Debian (deb) packages upgrade the Data Center Console, the system displays a message similar to the following:
All DCC data is overwritten and lost if you respond by pressing "Y" or "I." The default action keeps your current version. This issue does not affect environments using RPM packages.
When upgrading Server Backup Manager, R1Soft recommends that you select a window of time when no jobs are running. Place Server Backup Manager in Maintenance Mode and allow running tasks to complete before upgrading.
New configuration options and internal changes are provided to support policy based site to site replication of server backups to additional SBM servers. This new feature provides a simple means to replicate backup data across SBM servers regardless of their physical location. While this feature does not support synchronization of multi-tenant accounts or server configuration, replicated SBM server data can be used to restore an SBM server. Another nice feature of our SBM Site to Site replication is that you can actually restore data to a server downline from your SBM replica. Data is transferred securely over SSL channels. Replication of data can be enable or disabled at the Disk Safe level.
In alignment with recent changes, references to “Idera” have been removed from the interface.
The ext4 filesystem support has been expanded to support the 64bit Feature found in modern Linux distributions. This change applies to both the Server Backup Manager and its agents.
File downloads from recovery points are now logged as an event. Additionally, downloads are prevented when the Server Backup Manager is in Maintenance Mode
When Maintenance Mode is enabled, it will remain enabled after server restarts.
In the Servers listing, an new action icon has been added to fetch the log files from any of configured servers. You can specify the download path on the SBM server in the "Configuration > Manager Options" interface.
The h2 database is used internally by the SBM to record configuration information and activity records. SBM now offers improved tuning options to control its runtime characteristics. The new tuning options can be set in /usr/sbin/r1soft/conf/h2.properties. The options are:
- CACHE_SIZE (default value: 16384)
- The database keeps most frequently used data in the main memory. The amount of memory used for caching can be changed using the setting CACHE_SIZE. The value of CACHE_SIZE is specified in kilobytes.
- DEFAULT_LOCK_TIMEOUT (default value: 60000)
- The number of milliseconds until a lock timeout exception is thrown.
- LARGE_RESULT_BUFFER_SIZE (default value: 4096)
- The buffer size for large result sets. The value of LARGE_RESULT_BUFFER_SIZE is specified in kilobytes. Set this value to 0 to disable the buffer.
- LOCK_TIMEOUT (default value: 60000)
- The number of milliseconds until a lock timeout exception is thrown. The initial lock timeout for new connections is set by DEFAULT_LOCK_TIMEOUT.
- QUERY_CACHE_SIZE (default value: 8)
- The size of the query cache, in number of cached statements. Each session has it's own cache with the given size. The cache is only used if the SQL statement and all parameters match. Only the last returned result per query is cached.
- Addressed a timeout issue which may result in failed replication of recovery points. This issue would be seen associated with an error message of "Could not read from socket: null"
- DCC user filters were not working as intended.
- SBM to DCC policy syncing was not reliable.
- MSSQL database detection shows an error, but database backups are successful.
- Multipath I/O storage configurations are not tested and have been found to not function in some configurations.
- Flashcache support is incomplete at this time. Some systems may experience successful seed backups, but subsequent recovery points will not be restorable.
- Partition table information is not gathered on KVM systems using the virtio driver. In order to perform a bare metal restore on these systems, the partition table must be manually recreated prior to the restore.
- When upgrading DCC and SBM from 5.6.2 to 5.10.0, associated SBM servers may appear "offline". To resolve this issue, remove and re-add the SBM servers.
- The merge task may fail when you attempt to merge a recovery point that was interrupted due to CLOB/BLOB issues. If the merge fails due to this issue, merge the points one by one. After the merge fails, merge each recovery point one by one until the task is successful.
- Users who have Debian installations should note that a Debian-based machine that has both RPM and DEB packages installed is recognized as RPM-based only by Server Backup Manager.
- Users cannot set heap memory more than 1024 MB using serverbackup-setup -m. Even if there is more than enough space, Server Backup Manager displays a message indicating that memory specified must be smaller than 1024 MB. Edit server.conf to update memory settings.
- Some users are unable to create backup reports and receive the message, "Unknown exception:java.lang.NullPointerException." A workaround is to add a FROM: address to the Set Report Options.
- When Server Backup Manager is in Maintenance Mode, the policies can still be driven by DCC.
- Server Backup displays an incorrect error message, during agent deployment, when there is not enough space available in /tmp. The current message, “Path not found /tmp,” is not correct. The message should read, “Not enough usable space in <tempdir> on host <hostname>.”
- Some users may experience an unknown exception error when adding a server and attempting to display disk information. This issue results when Server Backup runs as a local system account which does not have rights to read the disk. You can resolve this issue by changing the process to run as an administrator.
- Users who have more than 1,500 mount points per device may experience performance issues during a file restore or when attempting to browse recovery and archive points.
- When using the API you must designate the type of user on the "user=" line, as either--user=dcc/someuser
Otherwise, the user defaults to local users.
- If your Windows environment contains an MSSQL or Exchange database on two different partitions, you should enable multi-volume snapshot (MVS) in the policy settings.
- Server Backup 5.2.x and later do not support remote deployment to a Windows 2003 server because installing drivers requires user interaction.
- Users who attempt to install Server Backup Manager on a Microsoft Windows 2003 operating system must note that .NET 2.x or 3.5 is required. .NET 4.0 does not satisfy this requirement. When installing SBM on Windows 2003, the installer fails if the proper .NET version is not installed. Note that the installer does not prompt you to install the correct .NET version before failing.
- The temporary (.tmp) folder is not deleted after completing a silent install of Server Backup Manager or Backup Agent using the default values. The folder is empty, but still exists on the server.
- Users who use Centos LiveCD on any bare-metal restores that have LVM may receive error messages that they failed to restore deltas to a certain device number. This issue results from the fact that because the Centos LiveCD uses its own LVM to manage its file systems, dm-0 and dm-1 are always in use. To avoid this issue, choose a target that is two LVM devices higher than the original. For example, if /tmp is originally on /dev/dm-1, you should choose /dev/dm-3 as your target.
- RecoveryCD versions 4.2.0 and 5.0.0 do not work when performing a bare-metal restore to a target that includes mdadm and LVM devices.
- Some users may receive an exception error message when attempting to exclude a large group of files in a directory when performing a restore.
- Microsoft Exchange Server 2007 users cannot restore a mailbox database to an alternate location.
- Some users may experience Java heap space out-of-memory error messages when attempting to restore a database with large LongBlob or LongText types.
- Disk safe verification verifies only those recovery points with an available status. DSV does not verify recovery points with a locked or incomplete status.
- The Data Center Console does not automatically restart after a new Windows installation.
- The Data Center Console displays incorrect values in the Compression Type section of the Edit Disk Safe window after editing the values.
- Internet Explorer users who enable the Compatibility view may notice graphical display issues when attempting to view some Data Center Console pages, such as the Disk Usage, Volumes, and Policies pages. This issue does not occur in other Web browsers.
- Not all files are downloaded for a container on Virtuozzo and system displays the error message, ERROR - Failed to download file, in the log file.
- Parallels Cloud Server 6.0 users may notice that Virtuozzo virtual machines are not detected as devices in the Disk Safe wizard. The VMs are backed up. If you need granular file restore for a VM, you can back up the PCS VM by installing a Server Backup Agent in the VM guest operating system
- Virtuozzo users may notice that when some containers are downloaded, the compressed file does not contain the first and last container listed in the recovery points.
There are no changes to Server Backup Advanced, Server Backup Free, and Server Backup Standard Edition, and therefore no Server Backup 5.8.x upgrades are available at this time. These non-Enterprise products are still fully supported as Server Backup 5.2.x and no upgrade is required. In order to receive *future* upgrades for these non-Enterprise products, please replace the repository upgrade path(s) stored in your R1Soft repository source list with the following URLs:
- Apt Non-Enterprise: http://repo.r1soft.com/apt-non-enterprise
- Yum Non-Enterprise: http://repo.r1soft.com/yum-non-enterprise/stable/
To receive the Server Backup 5.10.0 upgrade, please replace the repository upgrade path(s) stored in your R1Soft repository source list with the following URLs: