This release includes 4 product editions: CDP Standard Edition, CDP Advanced Edition, CDP Enterprise Edition, and Data Center Console.
Corrected an issue where Linux Agents failed when using Advanced Excludes that contained symlinks and the excluded drive was root "/".
Resolved an issue where scheduled policies fail to run although the UI reports next scheduled run time.
Agent OS version was not set and would reject backing file request via API calls if the agent OS was unknown. This issue is now resolved and a backing file location can be set via the API if the agents type is unknown or Linux.
The Backing File Location feature added in 3.14 allows Linux users to define a path by specifying a mount point of a device to use for changed block storage. Specifying a backing file is useful when experiencing disk full events or storing snapshots on a separate dedicated disk to help reduce the load during backup.
Performance issues were corrected for CDP Agent Kernel Driver versions between but not including 4.1.1-13785 (last known good) and 4.2.1-15846 (current release fixed)
CDP Agent Kernel Drivers caused excessive disk IO and used more disk space on servers already under high loads due to an increase in the chunk size (from 64 KB to 1 MB) used for COW operations. Kernel Driver 4.2.1-15846 has returned the chunk size to 64 KB.
Resolved an issue where the agent would start and then shut down if the Linux Kernel version was 3.x.
Distribute files needed for Interworx Control Panel Integration which were missing in 3.14 installation.
NPE's received during Task History Cleanup if task history included database restores and Control Panel backup task
Power User will no longer have the ability to view or edit Agents/Volumes to which they lack permissions and these changes will be saved in CDP
Refresh from DCC will no longer remove Agent assignments from Groups and Power Users
No longer will JMS Listener messages be sent to the LOG file when transactions cause an exception
- A Full Block Scan will be initiated after an agent upgrade due to a restart of the agent service/daemon. This ensures replicas are consistent even after a server crash or reboot. For more information or to better understand backup types see Benefits of CDP.
- Customers upgrading Windows agents from 2.x to 3.14 or later no longer require a manual uninstall of the 2.x windows agent. Users running the 3.14 installer will be prompted during installation to remove the 2.x agent (if detected). The installer will remove all 2.x binaries and require a reboot and re-run of the 3.14 installer to complete the installation process.
- Customers upgrading from version 3.10 with Archiving Limits set prior to upgrade will need to reset archive limits post upgrade. This can be easily accomplished using the bulk edit feature which can be accessed via the Policy tab.
- The upgrade will change the java heap size to 50% of physical memory if the server.conf file has been customized with a higher value. Reserving more than 50% of a system's memory for the Java Heap can result in situations where not enough memory is available for non-heap memory to the CDP server, or for other applications running on the system.
- Please be patient as important updates are in progress. The log file will display "CDP Started" when all database updates are complete.
Windows customers can watch their logs using Wordpad but will need to close and reopen the log file to see progress (example default path for Enterprise Install on Windows: C:\Program Files\R1Soft CDP Server Enterprise\log\server.log).
Linux customers can watch their server log file using the following command: tail --f /usr/sbin/r1soft/log/server.log
We have discovered an issue in Windows where restoring to an alternate location at drive level (e.g. C:\ to G) causes a restore failure. The work-around is to drill down one level, select ALL, then restore to an alternate location.
At this time Archiving is not supported in the Policy API however there are plans to add support in a future version.
We have discovered that many versions of the utility 'fdisk' are broken and do not correctly create the embedded partition ID in the partition table (it is all zeros).CDP 3 uses this partition ID to correctly locate partition tables on your server and is required for backing up partition tables.
If you see something like the following message: "Cannot back up /dev/xxx partition since /dev/xyz partition has the same identifier"; Then you will need to manually create a partition id. Please see the following knowledge base article:http://wiki.r1soft.com/display/kb3/Creating+a+unique+partition+id+with+fdisk
There was an issue with Ext4 introduced in "vanilla" Kernel.org kernel 2.6.32 and has been patched and released "down stream" into various Linux distributions. When any Ext4 file system snapshot is performed on an effected kernel the file system can deadlock causing a hung or crashed operating system.
**This is a Linux kernel bug completely out of the control of R1Soft**
Do not use the following Linux kernel versions with Ext4:
- Ubuntu Lucid (10.04) Betas and Release Candidates - we have reports that Ubuntu Lucid 2.6.32-24.41 and greater are fixed
- Ubuntu Maverick (10.10) Betas and Release Candidates
- Debian 6 (Squeeze) Betas and Release Candidates
- Fedora Core 12 Betas and Release Candidates
- Xen (4.0 / 4.1) - Do Not use Ext4 on 2.6.32-5-xen - 2.6.32-35-xen_02
Kernel.org Bug Report
Ubuntu Bug Report
- Log on to the support portal http://support.r1soft.com
- Create a new issue. Enter CDP 3 for the version.
You can access CDP 3 documentation here: http://wiki.r1soft.com/display/CDP3/