Server Backup 5.2.2 Release Notes

Important Upgrade Considerations Component upgrade order For Server Backup 5.2.x, you must upgrade the components in the following order or your backups may fail: Data Center Console (if applicable) Backup Manager Backup Agent

Initial merge speed Initial merges after an upgrade may be slow. The issue is due to calculations and identification of what needs to be merged. Once the calculations are 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 Some manual steps may be required when upgrading the Backup Agent on Linux. See: Upgrade Backup Agent on CentOS, RHE and Fedora Upgrade Backup Agent on Debian and Ubuntu Read special instructions for upgrading from 5.0.0 or 5.0.1  When upgrading from Backup Agent version 5.0.0 or 5.0.1, we suggest you perform the following manual steps before the upgrade: 1. Type this command to terminate all cdp-2-6 agent processes: ps ax | egrep -i c[d]p | awk '{print $1}' | xargs kill -9 Verify that there are no running or defunct cdp-2-6 processes by running: ps ax | egrep –i c[d]p 2. Proceed with the upgrade: For Centos/RHEL/rpm-based: yum update Or: yum install serverbackup-enterprise-agent For Debian/Ubuntu/apt-based: apt-get update followed by apt-get upgrade Or: apt-get install serverbackup-enterprise-agent 3. Start the new Server Backup Agent: For Centos/RHEL/rpm-based: service cdp-agent start For Debian/Ubuntu/apt-based: /etc/init.d/cdp-agent start To verify the 5.0.2 Agent is running, run the following command: egrep "Agent Version|Starting" /usr/sbin/r1soft/log/cdp.log | tail -n2

FIXED ISSUES

• This release fixes an issue causing some users to experience a READ/WRITE exception error after upgrading to cPanel v11.38 and enabling virtfs.
• Users who submit merge tasks now can successfully cancel the action while in calculating mode.
• An issue causing the Server Backup Web interface to suffer performance issues after upgrading to v5.2.1 no longer occurs.
• After upgrading to this release, users no longer experience slow merges of backup points.

KNOWN ISSUES

Notice For Server Backup 5.2.x, you must upgrade Server Backup Manager before upgrading the Agent. Failure to follow this procedure may result in failed backups.

• Users upgrading Server Backup Agent before upgrading Server Backup Manager may experience failed backups if:
  - the device path is greater than 255 characters in length, or
  - device is mounted more than once, causing the total device paths to be greater than 255 characters.
  If your backups fail after upgrading, and you believe this issue may be the cause, check your logs for the following error message:
  2013-05-01 15:13:58,500 ERROR  - A truncation error was encountered trying to shrink VARCHAR () FOR BIT DATA '(Binary data value not displayed)' to length 255.
  If you see the above message in your log, upgrade Backup Manager to version 5.2.2.
• Users who experience issues when attempting to browse recovery points after upgrading their Backup Agent to 5.2.2 can resolve this issue by upgrading Backup Manager to version 5.2.2.
• 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.
• Server Backup 5.2.x does not support remote deployment to a Windows 2003 server because installing drivers requires user interaction.
• If you are running Cloud Server 6.0 but not running the beta kernel module, you may experience an issue where Server Backup does not back up Ploop devices that have major/minor version numbers larger than 255 characters.  An error is logged in the backup policy if this situation occurs.
• Parallels Cloud Server 6 users may notice that Virtuozzo virtual machines are not detected as devices in the Disk Safe wizard. You can back up the VM data by installing a Server Backup Agent and then attempting the backup.
• Some users may experience an unknown exception error when adding a server and attempting to display disk information. This issue results when CDP 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.
• Disk safe verification verifies only those recovery points with an available status. DSV does not verify recovery points with a locked or incomplete status.