|Linux Manager/Agent Build Version:||5.4.1 build 39|
|Windows Manager/Agent Build Version:||5.4.1 build 39|
|Recommended Module Version:||4.4.0 build 18929|
|Important Upgrade Considerations|
For Server Backup 5.2.0 and later, you must upgrade the components in the following order or your backups may fail:
When users who have environments with Debian (deb) packages upgrade the Data Center Console, the system displays a message similar to the following:
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.
When upgrading Server Backup, Idera recommends that you select a window of time when no jobs are running.
|Upgrade Note: 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.4.x 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 non-Enterprise products, please replace the repository upgrade path(s) stored in your Idera/R1Soft repository source list with the following URLs:
|Upgrade Note: Server Backup Enterprise and SE users|
To receive the Server Backup 5.4.x upgrade, please replace the repository upgrade path(s) stored in your Idera/R1Soft repository source list with the following URLs:
|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:
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 the following command to terminate all cdp-2-6 agent processes:
Verify that there are no running or defunct cdp-2-6 processes by running:
2. Proceed with the upgrade:
3. Start the new Server Backup Agent:
To verify the 5.0.2 Backup Agent is running, run the following command:
- Users no longer experience inaccessible disk safes caused by a foreign key constraint violation when Server Backup Manager attempts to delete from table 'RECOVERYPOINTMEMBERSHIP'.
- This release fixes an issue that caused a null pointer exception when attempting to update a disk safe’s SigarDiskCache.
- This release provides additional protection against some malformed disk errors. This release does not correct existing malformed disk errors.
- Server Backup 5.2.x and later do not support remote deployment to a Windows 2003 server because installing drivers requires user interaction.
- Fedora users who upgrade from Server Backup 4.2.1 should note that the cdp-server and cdp-agent services do not automatically restart after the upgrade. You must manually restart these services.
- 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.
- Server Backup does not display a warning message when you attempt to perform a backup on databases in two different devices and you do not enable multi-volume snapshot (MVS) in the policy settings.
- 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 may notice grayed-out and unbrowsable database backups that contain recovery points created with versions earlier than 5.4.x. This issue will be resolved in a future release. To restore browseability, please refer to this knowledge base article: http://wiki.r1soft.com/x/eRGBAQ
- Disk safe verification verifies only those recovery points with an available status. DSV does not verify recovery points with a locked or incomplete status.
- 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:
- Unmount the drive.
- Create a directory that includes folders on the mounted device. This is the location where you can store your volumes.
- Delete the volume using Server Backup.
- 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.
- 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.
- 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.
- Some Virtuozzo users receive incomplete compressed files when downloading data for either the first or last container listed in the recovery points list.
- Parallels Cloud Server 6.0 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.
- If you are running Parallels 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.