Server Backup 6.18.0 Release Notes

| *Release Date:* | 23 May, 2023 |
| *Build Date:* | 10 May, 2022 \\ |
| *Linux Manager/Agent Build Version:* | {color:#252423}6.18 Build 22{color}\\ |
| *Windows Agent Build Version:* | {color:#252423}6.18 Build 21{color}\\ |
----
{toc:location=top|maxLevel=1|minLevel=1|type=flat|separator=pipe|style=border:1}
----
{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}

* 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
** Ubuntu 20.04 LTS / Kernel 5.13
* Bugfix: Fail to create New Disk Safe when choosing standalone file instead of a volume
* 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\!'"


*Note*: 

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.

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


h5.

{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}
{note}


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

{color:#172b4d}As stated above, {color}Data Center Console (DCC) is not compatible with Server Backup Manager v6.18.


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 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.

*{+}UPDATE 02/03/2023{+}* : Our team is currently focused on adding support for 5.13/5.14/5.15 kernels, which will require an update to the backup agent.
We are currently working on the plan for the next release, which is also expected to include a few bug fixes. A timeline will be provided soon.

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

*{+}UPDATE 03/02/2023{+}* : Our team is currently focused on correcting an issue preventing modules for 3.10 kernels and certain 4.18 kernels from auto-building from the backup agent.
We continue to focus our efforts on adding support for 5.14/5.15 kernels. We are hoping to share a timeline very soon\!

*{+}UPDATE 03/30/2023{+}* : Work is progressing towards adding support for 5.15 kernels. The upcoming release of Server Backup Manager v6.18 will contain the framework enhancements necessary for new module support.
A 5.15 beta module release will follow soon after v6.18 is released, and a 5.14 beta module will be released soon after 5.15 beta modules are ready.

*{+}UPDATE 04/13/2023:+* 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|http://repo.r1soft.com/modules/], and can be individually requested by opening a new Support ticket.

{color:#000000}{*}{+}UPDATE 04/27/2023{+}{*}{color} {color:#000000}:{color}{color:#000000}We are {color}{color:#000000}tentatively{color}{color:#000000} targeting the third week of May 2023 for the release of R1Soft Server Backup Manager 6.18.{color}
{color:#000000}This release will bring long-awaited updates to core SBM components, include important Security updates, and will introduce the framework necessary for 5.15 kernel support (Beta). Beta support for 5.14 kernels is expected soon after.{color}

{color:#000000}{*}{+}UPDATE 05/11/2023{+}{*}{color} {color:#000000}: {color}{color:#000000}We are planning to release R1Soft Server Backup Manager 6.18 the week of May 22nd. {color}{color:#000000}This release will contain bug fixes, security updates, core component updates, and BETA support for 5.15 kernels. {color}
{color:#000000}Beta support for 5.14 kernels is expected to arrive soon after.  {color}





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}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}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. Parallels Virtuozzo user issues

* {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}