Note	Cisco Unity Connection migration is not supported. Use the manual upgrade option.

The following three tables identify the functions supported by Cisco Prime Collaboration Deployment, Platform Manager and Infrastructure Platform Automation. Each table lists the UC application and their versions that supported by the platform function, irrespective of Cisco HCS releases.

Cisco only supports virtualized deployments of Cisco Prime Collaboration Deployment. The application is deployed using an OVA that contains the pre-installed application. This OVA is obtained with a licensed copy of Cisco Unified Communications Manager software. For information about how to extract and deploy the PCD_VAPP.OVA file, see topics relating to the installation of Cisco Prime Collaboration Deployment at http:/​/​www.cisco.com/​c/​en/​us/​support/​unified-communications/​unified-communications-manager-callmanager/​products-maintenance-guides-list.html.

A single instance of Cisco Prime Collaboration Deployment should be installed in the Cisco HCS Management Extranet so it can access all Cisco Unified Communications Manager clusters for all customers including those behind a NAT. The Cluster Discovery feature should be used to initially find application clusters to perform fresh installs, migration, and upgrade functions. This discovery needs to be performed on a blade-by-blade basis.

Details on available features, along with installation, configuration and administration, best practices, and troubleshooting information can be found in the Administration Guide at:http:/​/​www.cisco.com/​c/​en/​us/​support/​unified-communications/​unified-communications-manager-callmanager/​products-maintenance-guides-list.html and in the Release Notes at: http:/​/​www.cisco.com/​c/​en/​us/​support/​unified-communications/​unified-communications-manager-callmanager/​products-release-notes-list.html.

We recommend that you implement regular daily/nightly backups for Cisco Unified Communications (UC) and Management Applications to ensure that data is not lost due to an unexpected outage. For large Cisco HCS systems with many UC application instances, this can become a tedious and potentially error-prone task.

Following the engineering recommendations, you can create a backup schedule to provide a guide for backup order so that the Cisco HCS system is not overwhelmed during scheduled backups. Safeguards should be set in place so that you do not overrun the CPU on a per-blade basis and the IOPS engineering of the SAN while maintaining an acceptable backup time.

To facilitate the process, we recommend using the Platform Manager Automation Tool to schedule upgrades and backups for the UC applications. The Platform Manager Automation Tool lets the System Administrator schedule the backups at a regular, predetermined time. A schedule helps to reduce the number of personnel required, and the process is much less error-prone.

We recommend that you perform the following steps to create a backup schedule:

1. Map Virtual Machines (VMs) to physical LUNs in the storage system.

2. Determine the oversubscribed and non-oversubscribed pools.

3. Partition the process into oversubscribed and non-oversubscribed pools.

   1. For the non-oversubscribed clusters with SSD for storage, the VM backups can be scheduled according to the available bandwidth to the backup server. (Cisco assumes that you have SSD storage, so IOPS is not a factor.)

   2. For the oversubscribed clusters that use 20% HA, Cisco recommends that you back up or upgrade a maximum of two VMs for each blade at a time. This recommendation is based on possible contention for computing resources.

   3. For the oversubscribed clusters that use less than 20% HA, Cisco recommends that you back up or upgrade a maximum of one VM for each blade at a time. This recommendation is based on possible contention for computing resources.

   4. List the order of applications to be backed up (at a system level). In order to maximize the backup timing, ensure that you conform to the stated Engineering Rules when prioritizing the applications for backup.

      Note	For upgrades, Cisco recommends that you follow the stated Engineering Rules, but prioritize the applications to be upgraded on a per-customer basis. For example, if you have three tenants, create three separate lists of orders based on the application mix that is provisioned for each tenant.

      Cisco recommends a scheduled backup list based on the following priorities:

      • Priority 1 - Based on Application importance. For example, set Cisco Unified Communications Manager to the highest application priority, and Cisco Unified Communications Manager IM and Presence Service to the lowest priority. Other Cisco UC Applications that are provided in the compatibility matrix can be given a running order priority as well. There is no specific rule about how the application priority can be set.

      • Priority 2 - Based on OVA size. This priority allows you to back up the application based on tenant size. Each scheduled list should give the desired results and conform to the engineering rules.

4. Develop a matrix that describes the number of provisioned VMs for each size on a per-blade basis, and the mapping as it relates to the SAN storage that it points to. Create the matrix manually. The following table is an example of this type of matrix.

   Table 4 Example Matrix

   Chassis 1 Provisioning								Chassis 1 RAID Group ID Map
   Blade 1	Blade 2	Blade 3	Blade 4	Blade 5	Blade 6	Blade 7	Blade 8	Blade 1	Blade 2	Blade 3	Blade 4	Blade 5	Blade 6	Blade 7	Blade 8
   4	3	3	3	3	3	3	3	RG1,2,5,	RG1,2,1	6,2,5	1,2,6	1,2,7	1,2,8	1,2,9	1,2,10
   4	4	4	4	4	4	4	4	7,8,9,12	7,8,9,11	7,8,9,11	7,8,9,13	7,8,9,14	7,8,9,15	7,8,9,16	7,8,9,17
   1	1	1	1	1	1	1	1	22	13	13	13	13	13	13	13
   1	1	1	1	1	1	1	1	20	11	11	11	11	11	11	11
   4	3	3	3	3	3	3	3	4,5,8,3	2,3,7	2,3,7	6,7,9	4,8,10	2,5,11	4,10,12	1,5,13
   1	1	1	1	1	1	1	1	21	12	12	12	12	12	12	12
   1	1	1	1	1	1	1	1	23	14	14	14	14	14	14	14
   1	1	1	1	1	1	1	1	24	15	15	15	15	15	15	15
   1	1	1	1	1	1	1	1	25	16	16	16	16	16	16	16
   1	1	1	1	1	1	1	1	26	17	17	17	17	17	17	17
   1	1	1	1	1	1	1	1	27	18	18	18	18	18	18	18

5. Create a backup list. In the following example, the Timeline Sequence column identifies the order that backups are scheduled for Blade 1. For example, Time Sequence 1 is completed first, then Time Sequence 2 is executed, and so on. Applications with the same priority (for example, Priority 3) can be completed at the same time. The Application and Size columns show the application and its size based on priority.

Upgrade information is as follows:

• Cisco Unified Communications Manager and Cisco Unified Communications Manager IM and Presence versions must be aligned and upgraded simultaneously.
• Cisco Unified Communications Manager IM and Presence versions must match at the major and minor release level (for example, 10.0 works with 10.0; 10.x works with 10.x).
• In 10.x, a Cisco Unified Communications Manager IM and Presence install fails if the Cisco Unified Communications Manager publisher does not have the same major and minor release level.
• Upgrade Cisco Unified Communications Manager to 10.x before you upgrade Cisco Unified Communications Manager IM and Presence to 10.x.
• Cisco Unified Communications Manager IM and Presence switch version to 10.x or later fails if the Cisco Unified Communications Manager version does not match at the major and minor release level.
• All upgrades to 10.x are refresh upgrades and are service impacting.
• The Cisco Unified Communications Manager cluster must be upgraded and running 10.x before IM and Presence nodes are upgraded to 10.x.

• Upgrade Cisco Unity Connection