Server Backup 5.6.0 Release Notes

MySQL users planning an upgrade MySQL database backups can be affected if only one of the Server Backup components is upgraded to version 5.6.0 by the time a MySQL backup occurs. In cases where either the Backup Agent is upgraded to 5.6.0 before the Server Backup Manager, or the Server Backup Manager is upgraded before the Agent, Server Backup will be unable to connect to the MySQL database. The following are example errors which may appear in the log: 2014-04-21 00:00:000,000 WARN - TASK(MySQL1): Failed to perform discovery on database instance 'NAME' com.r1soft.backup.server.worker.WorkerException: Database instance discovery error ... Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Could not create connection to database server. Attempted reconnect 3 times. Giving up. ... Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server. ... Caused by: java.io.EOFException: Can not read response from server. Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost. ... Caused by: java.sql.SQLException: null, message from server: "NAME/IP' is not allowed to connect to this MySQL server"

Important Upgrade Considerations Supported versions Server Backup Manager 5.6.0 only supports upgrades from versions 5.2.0 and later. If you are on a previous version of SBM, upgrade to version 5.2.0 before attempting to upgrade to version 5.6.0. Component upgrade order For Server Backup 5.2.0 and later, you must upgrade the components in the following order or your backups may fail: Data Center Console (if applicable) Backup Manager Backup Agent Upgrading the Data Center Console When users who have environments with Debian (deb) packages upgrade the Data Center Console, the system displays a message similar to the following: Configuration file `/usr/sbin/r1soft-datacenter-console/conf/server.properties' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it? All DCC data is overwritten and lost if you respond by pressing "Y" or "I." The default action keeps your current version. This issue does not affect environments with RPM packages. Upgrade window When upgrading Server Backup, Idera recommends that you select a window of time when no jobs are running. MSSQL or Exchange backups 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.

Initial merge speed Initial merges after an upgrade may be slow. The issue is due to calculations and identification of what items need merging. Once the calculations complete, the actual merge process is relatively quick. We are aware of this issue and we are working toward a resolution.

Upgrading Backup Agent on Linux Server Backup Manager may require additional manual steps when upgrading the Backup Agent on Linux. For more information about this process, see: Upgrade Backup Agent on CentOS, RHE and Fedora Upgrade Backup Agent on Debian and Ubuntu

NEW FEATURES

• Improved the speed of initial seed backups by performing fast inserts.
• Server Backup Manager now includes the API method getFileRestoreStatistics. This method returns details of a file restore task including the total files to be restored, the total count of successful restores, and the total count of failed restores. For more information about this API method, see getFileRestoreStatistics.
• Create and update a disk safe replica via the Server Backup Manager. Allows the creation of a new disk safe from any recovery point, and scheduling of disk safe replica updates as archive points.
• cPanel Users can restore their MySQL Databases.
• Server logs contain user account information for all logged user actions from the user interface or from API calls.
• You can also configure your logs to go to a syslog log host.
• Server Backup Manager can now be put into maintenance mode, where running tasks will complete and no new tasks will start. For more information about enabling maintenance mode, see Manager Options.
• You now can redirect all requests to https for security. Click Configuration > Web Server Options, and then check the SSL Redirect checkbox and redirect all requests to https. Note that you must manually restart the CDPServer to complete the process. For more information about setting the redirect, see Web Server Options.
• serverbackup-setup now supports http proxy servers for linux module updates.

FIXED ISSUES

• This release of Server Backup Manager fixes an issue affecting Linux Backup Agent users that caused the Agent to default to full block scan on every backup.
• An issue that caused the service to not start after upgrading the Data Center Console no longer occurs.
• Users now can select all disk safes in the Choose Volume/Disk Safe window accessed when setting up a Quota report.
• The "Server/Agent Backup Status Report" now provides the correct subject line instead of, "One or More Tasks In Report are failing since 1 days."
• File excludes are no longer deleted after updating the policy via API using the updatePolicy call.
• Users will notice that this release of Server Backup Manager offers increased speed of initial "seed" backups. This improvement is based on SBM performing fast inserts instead of ordered inserts which are not necessary in a seed backup.
• A disk safe replica will not contain MS SQL or Exchange backups.
• A error message “MySQL error closing connection” is logged after performing a MySQL database restore.

KNOWN ISSUES

Important Upgrade Considerations For an up-to-minute review of issues affecting upgrades to SBM 5.6, see Known issues affecting upgrades to Server Backup Manager 5.6.0.

General Issues

• Some users may experience an issue causing server replication to complete with alerts concerning Microsoft Exchange verification. If this issue occurs, the workaround is to set Verify Exchange to Never verify.
• 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 ROM and DEB packages installed is recognized as RPM-based only by Server Backup Manager.
• Users cannot set heap memory 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.
• Reports are incorrect if the Data Protection Policy task for a server is deleted from Task History.
• When setting up multi-point replication, the shortcut for Backup Agent Configuration Utility runs C:\Program Files\Idera Server Backup\bin\CDPConfig.exe, which starts the Backup Manager Configuration Utility instead of the Agent utility.
• 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.
• If you attempt to import a server that already exists in Server Backup Manager, it does not import the data but does display an incorrect message that reads, “A server to import was not found in the disk safe.” In addition, the error is logged in the server.log file as something similar to the following message:
  2014-03-21 06:54:53,351 INFO   - Could not locate Agent (6c4bc523-85de-4e3d-a2e0-5868ce73cfbb) while importing DiskSafe (imported)
  2014-03-21 06:54:53,352 ERROR  - Failed to import agent from disk safe 'imported'
  com.r1soft.backup.server.facade.AgentException: Hostname and port are in use
          at com.r1soft.backup.server.facade.AgentFacade.validateAgentHostnameAndPort(AgentFacade.java:443)
          at com.r1soft.backup.server.facade.AgentFacade.validateAgent(AgentFacade.java:367)
• When Server Backup Manager is in maintenance mode, the policies can still be driven by DCC.
• 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.
• You cannot delete a volume located at the root of a mount point. It is not recommended to create volumes in this location. If you want to delete a volume that resides at the root of a mount point:
  1. Unmount the drive.
  2. Create a directory that includes folders on the mounted device. This is the location where you can store your volumes.
  3. Delete the volume using Server Backup.

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.

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.

Data Center Console issues

• The Data Center Console does not automatically restart after a new Windows or Linux installation.
• The Data Center Console Bulk Edit functionality is experiencing issues, such as not allowing a user to edit merge schedule policies with two disk safes and Data Retention selected.
• 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.
• The Data Center Console service is stopped after using a 5.2.1 > 5.4.1 > 5.4.2 upgrade path with RPM packages.
• When a report is sent out via email, the message include the incorrect icon for warnings. The icon should be a yellow exclamation point instead of a red "x."

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.

ADDITIONAL NOTES

Bare-metal restore boot CD

Server Backup Manager 5.6 does not include an updated bare-metal restore boot CD as this feature is not changed since version 5.4.1.

Server Backup Advanced, Server Backup Free, and R1Soft Standard Edition (non-Enterprise) users

There are no changes to Server Backup Advanced, Server Backup Free, and Server Backup Standard Edition, and therefore no Server Backup 5.6 upgrades are available at this time. These non-Enterprise products are still fully supported as Server Backup 5.2.x and no upgrade is required. In order to receive *future* upgrades for these non-Enterprise products, please replace the repository upgrade path(s) stored in your Idera/R1Soft repository source list with the following URLs:

• Apt Non-Enterprise: http://repo.r1soft.com/apt-non-enterprise
• Yum Non-Enterprise: http://repo.r1soft.com/yum-non-enterprise/stable/

Server Backup Enterprise and SE users

To receive the Server Backup 5.6 upgrade, please replace the repository upgrade path(s) stored in your Idera/R1Soft repository source list with the following URLs:

• Apt Enterprise: http://repo.r1soft.com/apt/
• Yum Enterprise: http://repo.r1soft.com/yum/stable/