CDP 3.15.0 BETA Release Notes

h3. CDP 3.15.0 (BETA) Release Notes

This release includes 4 product editions: CDP Standard Edition, CDP Advanced Edition, CDP Enterprise Edition, and Data Center Console.

h4. WHO SHOULD INSTALL THIS BETA?

You should only install this Beta if you are in need the following fixes/enhancements:
* API - New function to enter backing file location (Linux only)

The backing file feature was added to the Policy tab (UI) in 3.14 and now API users have the ability to specify a backing file via backingFileLocation property. This new feature 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.

h6. DCC User Group Edit privileges

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

h6. DCC Losing CDP Group Assignment on Refresh

Refresh from DCC will no longer remove Agent assignments from Groups and Power Users

h6. CPD Shutdown message (Active MQ) is no longer written to the log file.

* 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|http://www.r1soft.com/windows-cdp/cdp-30-enterprise-edition/features/high-performance-backup/|http://www.r1soft.com/windows-cdp/cdp-30-enterprise-edition/features/high-performance-backup/].

h6. {color:#000000}Upgrading Windows Agent from 2.x to 3.14 or later:{color}

* 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.

h6. {color:#000000}Archiving Schedules Upgrading from CDP 3.10:{color}

* 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.

h6. {color:#000000}Customers Upgrading with Customized Heap Settings:{color}

* 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.

h6. {color:#000000}Upgrading customers (3.10 or earlier) may experience a delay when starting the WebUI:{color}

* Please be patient as important updates are in progress. The log file will display "CDP Started" when all database updates are complete.
bq. 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).

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.

h4. Policy SOAP API Archiving Support

At this time Archiving is not supported in the Policy API however there are plans to add support in a future version.

h4. Linux Agents

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]

h4. Linux Kernels with Severely Broken Ext4

*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

*More Information:*

Kernel.org Bug Report
[https://bugzilla.kernel.org/show_bug.cgi?id=16278]

Ubuntu Bug Report

# Log on to the support portal [http://support.r1soft.com]

You can access CDP 3 documentation here: [http://wiki.r1soft.com/display/CDP3/]