Server Backup 6.2.1 Release Notes

| *Release Date:* | 12/21/2016 |
| *Build Date:* | 12/19/2016 |
| *Linux Manager/Agent Build Version:* | 6.2.1 build 55 |
| *Windows Agent Build Version:* | 6.2.1 build 55 \\ |
----
{toc:location=top\|maxLevel=1\|minLevel=1\|type=flat\|separator=pipe\|style=border:1}
----
{note:title=Debian and Ubuntu Users}
You will be unable to upgrade from a pre-6.2.1 version using {{apt-get upgrade}}. Instead, you will need to upgrade using either {{apt-get dist-upgrade}} OR {{apt-get install <package name>}}.
{note}
{note:title=Important Upgrade Notice}
Customers upgrading from Server Backup Manager 5.14.3\+ can upgrade as normal.&nbsp;If you are upgrading to 6.2.1 from any release previous to 5.14.3, this release introduces significant changes to the Disk Safe format which are incompatible with previous releases. Refer to&nbsp;Important Upgrade Notices&nbsp;in the [5.14.3 Release Notes|ServerBackupManager:Server Backup 5.14.3 Release Notes] for information on how to upgrade.


{note}

h1. New Features

A *new user interface* has been implemented for Server Backup Manager version 6.2.1 to improve the experience for all our partners. The new UI offers an&nbsp;updated dashboard that displays the health of your entire backup environment on a single screen with notifications, active jobs, backup status, underlying server disk IO, memory, and CPU utilization.&nbsp;Some of the new UI features include:
* All core tasks, including protecting machines, restoring files, and viewing storage analytics, can be performed right from the main dashboard, allowing users to maximize their efficiency within the product.
* Simplified navigation allows you to drive the most common actions from the _Protected Machines_ screen.
* The _Actions_ icon on the main UI screens has been replaced with a more convenient drop-down menu that contains all possible actions for the relevant selection.
* New notifications icon alerts you to issues as they occur. Click the Alert icon at the top of any page in SBM to view alert details.
* The _Activity Monitor_ on the Dashboard allows for real-time monitoring of running tasks. You can click the *Details* button for any running task to view the task details.&nbsp;
* The new, simplified Main Menu allows users to navigate through SBM faster and more efficiently. All SBM tasks and functions are intuitively grouped and require fewer clicks to locate.
* New dashboard widgets include&nbsp;_Disk Performance_, _CPU and Memory_, and _Local Backup and Restore Performance_.
* Easily add new protected machines (servers) and set retention policies by clicking the&nbsp;*+ New Machine*&nbsp;button on the&nbsp;_Protected Machines_&nbsp;screen and completing the simplified form on the&nbsp;_New Machines_&nbsp;screen.
* Record and share notes regarding protected machines directly on the _Protected Machines_ screen.

h5. *Additional new features in SBM 6.2.1*

* Improvements to MySQL database restore performance (restores are now up to 10 times faster).
* Alerting and reporting can now leverage Gmail and Office 365.
* Retention policies for site-to-site replication are now also applied to the target SBM.
* Includes the new Linux kernel module with support for 4.X kernels.
* Microsoft Windows Server 2016, Exchange Server 2016, and SQL Server 2016 are now supported.
* Site-to-site archive merge schedules have been added.
* MySQL databases can now be restored to their original host via the API.





h1. Fixed Issues

h5. Server Backup Manager

* Gmail users who have activated the SMTP authenticated connections can now receive email reports by activating Gmail's "Less Secure" setting. For information on activating the "Less Secure" setting in Gmail,&nbsp;[click here|https://support.google.com/accounts/answer/6010255?hl=en].
* Resolved an issue where a MySQL database restore would fail if the database had a period in its name.
* Resolved an issue that adversely affected the speed of interface interactions.
* Increased the speed of MySQL restores.
* Temporary instances that were created as a result of failed MySQL restores now successfully recover from crashes.
* Resolved an issue where restored symlinks were always owned by "root:root".
* "Test authentication failed..." error no longer displays when specifying DLLN user format in the Username field on the New Server page.
* Resolves a Linux module build issue for 3.10 kernels (RHEL 7)

h5. Data Center Console

* Resolved an issue where DCC groups were unable to see servers.

h1. Upgrade Notes

You must have an active maintenance account to upgrade to SBM 6.2.1. 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.&nbsp;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.&nbsp;

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

XFS v5 is not supported in the SBM 6.2.1 release. We are currently working to add support for XFS v5 in a future release.&nbsp;

h5. Common Problems and Issues

* Some XFS volume groups are not recognized by SBM in Storage Configuration. This is due to a LVM static binary issue that should be fixed in a future product release.
* Site-to-Site (remote replication) Disk Safe replication tasks for Windows protected machines using Dynamic Disks may fail with protocol errors when replicating partition tables.
* Site-to-Site replication between a 5.12\+ SBM server and an older server is not possible due to SSL library changes.
* Multiple simultaneous Vacuum operations will significantly impact the overall performance of the SBM. R1Soft recommends running one Vacuum operation at a time.
* Multipath I/O storage configurations with duplicate device UUIDs are not supported and have been found to not function in some configurations.
* Partition table information is not gathered on KVM systems using the virtio driver. In order to perform a bare metal restore on these systems, the partition table must be manually recreated prior to the restore.
* 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.
* Some users are unable to create backup reports and receive the message, "Unknown exception:java.lang.NullPointerException." A workaround is to add a *FROM*: address to the *Set Report Options*.
* When Server Backup Manager is in Maintenance Mode, the policies can still be driven by DCC.
* During agent deployment,&nbsp;Server Backup displays an incorrect error message when there is not enough space available in {{/tmp}}. The current message, “Path not found /tmp,” is not correct. The message should read, “Not enough usable space in {{<tempdir>}} on host {{<hostname>}}.”
* Some users may experience an unknown exception error when adding a server and attempting to display disk information. This issue results when Server Backup runs as a local system account which does not have rights to read the disk. You can resolve this issue by changing the process to run as an administrator.
* 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.
* When using the API you must designate the type of user on the "user=" line as either _\--user=dcc/someuser_ or _\--user=sbm/someuser_. Otherwise, the user defaults to local users.
* *{_}If your Windows environment contains an MSSQL or Exchange database on two different partitions{_}*, you should enable multi-volume snapshot (MVS) in the policy settings.

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.
* Users who attempt to install Server Backup Manager on a Microsoft Windows 2003 operating system must note that .NET 2.x or 3.5 is required. .NET 4.0 does not satisfy this requirement. When installing SBM on Windows 2003, the installer fails if the proper .NET version is not installed. Note that the installer does not prompt you to install the correct .NET version before failing.
* The temporary (.tmp) folder is not deleted after completing a silent install of Server Backup Manager or Backup Agent using the default values. The folder is empty, but still exists on the server.

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.
* Some users may experience Java heap space out-of-memory error messages when attempting to restore a database with large LongBlob or LongText types.
* Disk safe verification verifies only those recovery points with an available status. DSV does not verify recovery points with a locked or incomplete status.

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 does not automatically restart after a new Windows installation.
* 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.

h5. Changes to the SBM API

* The policy object now only contains configuration information. Use the Agent API to get the state of the machine.



h1. Kernel Modules