View Source

| *Release Date:* | 28 Oct, 2022 |
| *Build Date:* | 20 Oct, 2022 \\ |
| *Linux Manager/Agent Build Version:* | {color:#252423}6.16.4 Build 117{color}\\ |
| *Windows Agent Build Version:* | {color:#252423}6.16.4 Build 117{color}\\ |
{note:title=Important Upgrade Notice}
Customers upgrading from Server Backup Manager 6.2.2\+ can upgrade as normal, otherwise please upgrade to 6.2.2 first.  {note}
{note:title=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. {note}

h1. {color:#172b4d}Fixed Issues{color}

* A new server backup agent version is released to include support for 4.18 kernels installed on Alma Linux 8.x, Rocky Linux 8.x, RedHat Enterprise Linux 8.x, CentOS Stream 8, Cloud Linux 7.x etc. (Note: Please do not update the agent on systems running 5.11 kernel)
* A critical security issue related to an underlying framework used by the Server Backup Manager is fixed.
* {color:#172b4d}An issue resulting in users randomly getting automatically logged out from the SBM Web UI is fixed.{color}

h1. {color:#172b4d}Upgrading{color}


{color:#172b4d}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 {color}{color:#172b4d}{_}https{_}{color}{color:#172b4d} 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. {color}

{note}{color:#172b4d}{*}Component upgrade order{*}{color}
{color:#172b4d}Server Backup Manager software must be upgraded in the following order:{color}

* {color:#172b4d}Server Backup Manager{color}
* {color:#172b4d}Server Backup Agent{color}

h5. {color:#172b4d}Data Center Console{color}

{color:#172b4d}After completing the software updates in environments using Data Center Console, R1Soft recommends refreshing the associated SBM server data for proper syncing. In some cases a restart of the SBM service may be necessary.{color}

h5. {color:#172b4d}Backup Agent{color}

{color:#172b4d}Backup Agent software requires a glibc version of 2.5 or greater.{color}
{info:title=GNU C Library Compatibility}
{color:#172b4d}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: {color}{color:#172b4d}[Error - Linux cdp agent fails with "Floating Point Exception"|kb3:Error - Linux cdp agent fails with "Floating Point Exception"]{color}{color:#172b4d}.{color}{info}

h1. Kernel Modules Update 

We are pleased to announce that BETA support for 4.18 kernels is available again with the latest server backup agent. With the release of the v6.16.4 agent, it is no longer necessary to downgrade the agent to protect 4.18 kernels. Our immediate next priority is to provide support for Ubuntu 22.04/5.15 kernels and Debian 11/5.10 kernels along with automated module builds for 5.4s & 4.19s. Please watch this space in the coming weeks for updates & timelines related to these kernel versions. We thank you for your patience.


*{+}UPDATE 11/11/2022{+}*: We are targeting the week of 11/28/2022 to promote 5.4 and 4.19 kernel modules to GA/stable, and enable them for automatic builds via the serverbackup-setup utility.

*{+}UPDATE 12/02/2022{+}*: 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.

*{+}UPDATE 12/15/2022{+}* : We are tentatively targeting the last week of January 2023 for the GA release of Server Backup Manager 6.16.5.
The 6.16.5 release is expected to introduce support for 5.10/5.11 kernels, as well as multiple product fixes and improvements.
The next update will be provided the first week of 2023

*{+}UPDATE 01/05/2023{+}* : We are targeting the week of January 23rd for the release of Server Backup Manager 6.16.5
This release will introduce beta support for 5.10/5.11 kernels, will contain multiple product fixes and improvements, and will provide the necessary framework for future support of 5.13/5.14/5.15 kernels.

h1. {color:#172b4d}Known Issues{color}

{color:#000000}{*}Common Problems and Issues{*}{color}
* {color:#172b4d}When Disk Safes grow larger than 32TB, backups fail with : "reset(): database or disk is full", even when sufficient storage space is available.{color}
* {color:#172b4d}If you are using DCC to centrally monitor and manage SBMs and you see a loss of synchronization post upgrade to SBM 6.16.2, as a first step click Refresh SBM on the DCC UI to force fetch the updates. If the issue remains, "Restart" the SBM that is failing to sync.{color}
* {color:#172b4d}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.{color}
* {color:#172b4d}Multipath I/O storage configurations with duplicate device UUIDs are not supported and have been found to not function in some configurations.{color}
* {color:#172b4d}When upgrading DCC and SBM from 5.6.2 to 5.12+, associated SBM servers may appear "offline". To resolve this issue, remove and re-add the SBM servers.{color}
* {color:#172b4d}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.{color}
* {color:#172b4d}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.{color}
* {color:#172b4d}Users cannot set heap memory for more than 1024 MB using {color}{color:#172b4d}{*}serverbackup-setup \-m{*}{color}{color:#172b4d}. 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.{color}
* {color:#172b4d}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.{color}

h5. {color:#172b4d}Installation issues{color}

* {color:#172b4d}Server Backup 5.2.x and later do not support remote deployment to a Windows 2003 server because installing drivers requires user interaction..{color}

h5. {color:#172b4d}Restore issues{color}

* {color:#172b4d}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 {color}{color:#172b4d}_/dev/dm-1{_}{color}{color:#172b4d}, you should choose {color}{color:#172b4d}_/dev/dm-3{_}{color}{color:#172b4d} as your target.{color}
* {color:#172b4d}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.{color}
* {color:#172b4d}Some users may receive an exception error message when attempting to exclude a large group of files in a directory when performing a restore.{color}
* {color:#172b4d}Microsoft Exchange Server 2007 users cannot restore a mailbox database to an alternate location.{color}

h5. {color:#172b4d}Data Center Console issues{color}

* {color:#172b4d}When editing a Policy in DCC, the Recovery Point limit set at the Volume level can be exceeded. Volume objects must be refreshed in order to see the limit changes. This is done by refreshing SBM or by editing and re-saving the Volume.{color}
* {color:#172b4d}The Data Center Console displays incorrect values in the {color}{color:#172b4d}{*}Compression Type{*}{color}{color:#172b4d} section of the Edit Disk Safe window after editing the values.{color}
* {color:#172b4d}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.{color}

h5. {color:#172b4d}Parallels Virtuozzo user issues{color}

* {color:#172b4d}Not all files are downloaded for a container on Virtuozzo and system displays the error message, {color}{color:#172b4d}{{{}ERROR - Failed to download file{}}}{color}{color:#172b4d}, in the log file.{color}
* {color:#172b4d}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.{color}
* {color:#172b4d}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.{color}