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.

Fixed Issues

• Focusing on improving certificate management and overall product hardening, per our ongoing security and reliability initiatives, we have updated the digital signing certificates used with our Windows Server Backup Agent packages. To maintain version compatibility, all Server Backup Manager and Server Backup Agent packages have been updated to the latest version. We strongly recommend you update the Server Backup Manager and Windows Server Backup Agents in your client environments before Friday, June 20, 2025, at 8:00pm ET. 

Frequently Asked Questions about the release:

1. Who is required to take action immediately?
A. If you have Windows protected machines in your environment, you need to take action before Friday, June 20, 2025, at 8:00pm ET because the previous certificates are being revoked.

2. If I have Linux protected machines only in my R1Soft environment, do I need to take action immediately?
A. There shouldn't be a major impact if you have Linux protected machines only in your environment. However, we recommend you update both Server Backup Manager and Server Backup Agents to the latest version at the earliest.

3. If a Windows agent is not updated before Friday, June 20, 2025, at 8:00pm ET, what is the experience like?
A. Depending on the EDR/AV product being used and how it is currently set up to scan against our products, it may quarantine the application and create a notification to the end users. 

For more information on upgrading R1Soft Server Backup Manager and Server Backup Agents:

• Server Backup Manager: Please refer: https://wiki.r1soft.com/display/ServerBackupManager/Install+and+Upgrade+Server+Backup+Manager+on+Linux
• Server Backup Agent: Please refer: https://wiki.r1soft.com/display/ServerBackupManager/Deploy+Agent+Software+from+Backup+Manager

Upgrading

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: Server Backup Manager Server Backup Agent

Data Center Console

Data Center Console (DCC) is not compatible with Server Backup Manager v6.18.

Backup Agent

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.

Historical updates for kernel module development and release can be found in the Release Notes of previous versions.

UPDATE 01/30/25: 
- Modules for RHEL 9.5 operating systems have been promoted to production stable. These versions will now auto build from the agent using the "getmodule" command 
- We are working on promoting AlmaLinux 9.5, Rocky Linux 9.5, and CloudLinux 9.5 to stable in the coming weeks. 

UPDATE 03/20/2025: 
Modules for the following operating systems have been promoted to production stable. The following versions will now auto build from the agent using the "getmodule" command 
-RHEL 9.5 - 5.14 kernels 
-AlmaLinux 9.5 - 5.14 kernels 
-Rocky Linux 9.5 - 5.14 kernels  
-CloudLinux 9.5 - 5.14 kernels 

Known Issues

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

Installation issues

• Server Backup Agent installation on Windows Server 2022 fails as .NET 3.5 isn't enabled on Windows servers 2019 or 2022. If Microsoft .NET 3.5 is manually installed, remote agent installation completes successfully.
• Remote agent deployment on Windows 11 machine fails because of User Account Control Settings. Disable "Run all administrators in Admin Approval Mode" under User Account Control before running remote agent install. Note: A reboot of the Windows computer will be required.
• Server Backup 5.2.x and later do not support remote deployment to a Windows 2003 server because installing drivers requires user interaction..

Restore issues

• After performing backup, unable to browse software RAID + LVM partition formatted with XFS filesystem.
• 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.