|Release Date:||24 May, 2023|
|Build Date:|| 10 May, 2022
|Linux Manager/Agent Build Version:|| 6.18 Build 22
|Windows Agent Build Version:|| 6.18 Build 21
|Important Upgrade Notice|
Customers upgrading from Server Backup Manager 6.2.2+ can upgrade as normal, otherwise please upgrade to 6.2.2 first.
|MySQL and Virtuozzo|
If you have MySQL in Virtuozzo containers you will need to upgrade both the agent and the Backup Manager to address issues with recovery.
- JAVA version used in the Server Backup Manager is upgraded to OpenJDK 8.
- Apache Tomcat version used in the Server Backup Manager is upgraded to a latest version compatible with OpenJDK 8.
- R1Soft Server Backup Manager has been upgraded to use TLS v1.2 to transfer data securely over the network.
- Server Backup Agent (SBA) is upgraded to offer support for newer kernel versions in the coming weeks
- Ubuntu 22.04 LTS / Kernel 5.15
- RHEL/AlmaLinux/Rocky Linux/CentOS Stream 9.x / Kernel 5.14 (Coming Soon!)
- Ubuntu 20.04 LTS / Kernel 5.13 (Coming Soon!)
- Bugfix: Unable to edit backup policy when a file path has soft link defined in the file exclusion
- Bugfix: DirectAdmn : "Could not connect to the protected machine 'Error fetching direct admin version!'"
1. Data Center Console (DCC) is not supported with SBM v6.18. If you are using DCC to monitor and manage Server Backup Manager(s) and wish to continue to use it, then we highly recommend you to stay on SBM v6.16.5 or below. Upgrading Server Backup Manager to SBM v6.18 will make it incompatible with DCC.
2. Site to Site replication between Server Backup Managers require both the source and destination SBMs on SBM v6.18.
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.
|Component upgrade order|
Server Backup Manager software must be upgraded in the following order:
Data Center Console
Data Center Console (DCC) is not compatible with Server Backup Manager v6.18.
Backup Agent software requires a glibc version of 2.5 or greater.
|GNU C Library Compatibility|
Backup Agents on Linux distributions with older glibc libraries should remain on version 5.10 or earlier versions of the Backup Agent software. Refer to the following Knowledge Base article for more information: Error - Linux cdp agent fails with "Floating Point Exception".
Kernel Modules Update
Please watch this space for updates & timelines related to upcoming Stable and Beta kernel module releases. We thank you for your patience.
------------ Archived Highlights
: Modules for 4.19 kernels (Debian 10) and 5.4 kernels (Ubuntu 18.04/20.04) have been promoted to stable this week.
Modules for these kernel versions will now build automatically from the protected machine by restarting the agent, or running "serverbackup-setup --get-module".
We are now working towards adding support for 5.10/5.11 kernels to the upcoming 6.16.5 release. A release timeline should be available within the next 2 weeks.
: Modules for 4.18 kernels (Alma Linux 8, Rocky Linux 8, CloudLinux 8, RHEL 8) have been promoted to stable this week.
Modules for these kernel versions can now be built automatically from the protected machine by restarting the backup agent, or by running "serverbackup-setup --get-module".
Our team continues to work towards adding support for 5.14/5.15 kernels.
We are targeting the month of May 2023 for the release of Server Backup Manager v6.18. This release will coincide with the release of a new BETA kernel module for 5.15 kernels. A release of a BETA kernel module for 5.14 kernels will soon follow.
Additionally, at this time we are temporarily disabling automatic builds of 4.18 kernel modules for CloudLinux operating systems, while we address a performance concern.
In the meantime, pre-built CloudLinux modules can be found on the R1Soft Repo, and can be individually requested by opening a new Support ticket.
: Server Backup Manager v6.18 was released today, introducing Beta support for 5.15 kernels. Beta kernel modules for 5.15 kernels are now available by request, by opening a new Support ticket, or by downloading a pre-built module from the R1Soft Beta Repo. Beta Support for 5.14 kernels is expected in the coming weeks, followed by Beta support for 5.13 kernels.
Common Problems and Issues
- When Disk Safes grow larger than 32TB, backups fail with : "reset(): database or disk is full", even when sufficient storage space is available.
- File search will run forever for protected machines with EFI partitions, the search will get stuck in /boot/efi. As a workaround, specify the starting path for the search.
- Multipath I/O storage configurations with duplicate device UUIDs are not supported and have been found to not function in some configurations.
- 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 for 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.
- 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.
- (Cosmetic) zk-web messages in SBM log after install or upgrade. Steps to resolve can be found here
- 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 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.
Parallels Virtuozzo user issues
- 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.