Server Backup 6.14.1 Release Notes

----
{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. *Enhancements*


h5. *Full Block Scan improvements*

In this release, a series of changes have been made to the Network components of the Server Backup Manager that would have a positive impact on Full Block Scan (FBS) performance. These efforts are in continuation of the FBS-related performance improvement efforts put forth in the previous release. Optimization of the network and better management by the Backup Manager will help improve performance during read/write activities taking place during Full Block Scans and backup.
\\

h5.  


h5. *Control Panel Support*

Agent updates have been made to add support for Direct Admin and Plesk users to correct an issue that prevented some users from browsing and recovering their databases.
Now, users can recover their databases even if the database name is customized and not prefixed with the username.
\\

h5.  


h5. *Improvement to the SMTP support within Reports*

Previously, in the UI, a checkbox was provided for enabling encryption, defining that SMTPS needed to be used for communication.
In this release, we have replaced the checkbox with a drop-down that provides three options:
* *NONE*: When set to this encryption type, mails are sent without encryption using plain text mode only.
* *STARTTLS:* When set to STARTTLS (default), SBM uses STARTTLS encryption, if supported by the SMTP server. If not supported, the communication is completed using plain text mode.
* *TLS/SSL:* This option is equivalent to the prevalent selected checkbox option. When selected, it defines that the SBM needs to use SMTPS for communication. It needs appropriate certificates as well as port numbers to be made available in the SBM for the communication to take place.

h1. Fixed Issues


h6. *MySQL:*

* Addressed an intermittent issue related to database restore failures on cPanel that affected previous releases. This issue was observed to be a cause for another issue, which related to databases not being visible on MySQL for restore.
** The RCA identified the cause to be low memory availability, which was not allowing the CDP agent to buffer space when it read output/error streams from MySQL processes, leading to Segfault errors. 
** This has been resolved by a reduction in the buffer size, which resolves the low memory availability issue while still providing the same level of restore capabilities as before the change
* Addressed a typo in the “Restore Databases Introduction” window.

h6.  


h6. {color:#000000}{*}Security:*{color}

* Fixed issues related to remote deployment, where an issue was leading to failure in deployment of the agent.
This issue was seen to be affecting both Windows and Linux Servers.
* Fixed vulnerabilities around code injection and component security to deliver hardened components.

  

h6. *Other*:

* A timestamp issue was identified and resolved, where restored files would tend to get a wrong timestamp post-recovery.

h1. Upgrading


h5.

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. 

h5. Data Center Console

After completing the software updates in environments using Data Center Console, R1Soft recommends refreshing the associated SBM server data for proper syncing.

h5. Backup Agent

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

h1. Known Issues

{color:#000000}{*}Common Problems and Issues{*}{color}
* 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.
* 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.
* 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.

h5. Installation issues

* Server Backup 5.2.x and later do not support remote deployment to a Windows 2003 server because installing drivers requires user interaction..

h5. Restore issues

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

h5. Data Center Console issues

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

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