Backup and Restore

Backup and Restore Strategies

Backup Strategy

Review the components in your implementation to identify the backup requirements and sequence for backups. You can use the reference tables in this document to identify the components that are backed up occasionally and those that are backed up daily.

Procedure

Step 1

Group the components in your deployment under the following groups. The components in each group have similar backup requirements.

  • Data Center Infrastructure Components

  • Aggregation and Shared Component Elements

  • Cisco HCS Service Fulfillment

  • Cisco HCS Service Assurance

  • Cisco UC Applications

  • Endpoints

  • SRST and Voice Gateways Components

  • Cisco HCS for Contact Center Components

  • Third-Party Applications

Step 2

Review the component tables in this guide to identify and record the backup requirements for the components in your installation.

Step 3

For components that require occasional backup, identify the backup mechanism to use.

Step 4

For components that require frequent (daily) backup, identify the backup mechanism to use.

Restoration Strategy

Your workflow for restoring components varies by component. For some components, you can restore the configuration from backup. Other components require more complex restoration, potentially involving synchronization with other components.

The general workflow for determining the restoration steps is as follows.

Procedure

Step 1

Review the detailed restoration information for the component to be restored from the chapters that follow.

Step 2

Identify any specific components to synchronize or restart (or manage in some other way) based on the component being restored.

Step 3

Execute the restore operations in the order prescribed in the component sections.

Operational Parameters

Use these key operational parameters to optimize backup and restore performance.

Backup frequency

The frequency of backups depends on the frequency of changes in the network, such as platform configurations or user data-provisioning activities. Schedule additional backups before any major configuration and software updates. It is good practice to create a backup after successful software updates too.

Disk space

To calculate the cost of disk space requirements, multiply the frequency of backups and disk space requirements per backup by the number of backups the service provider maintains per UC cluster, as specified in the service level agreement (SLA).

Backup and restore duration

Backup and restore duration depends directly on the amount of disk space required for the backup or restore and the network bandwidth. Frequent backups and restores can adversely affect network traffic performance.

IOPS

The primary measurement used to determine backup demands on the system is input/output operations per second (IOPS). The higher the IOPS, the faster backups are completed.

SFTP Server Considerations and Requirements

SFTP servers store backup data collected from HCS components. You can set up SFTP servers in different ways for a Hosted Collaboration Solution.

  • Typically for HCS, Cisco recommends having a dedicated SFTP server (or dedicated servers) per UC cluster. The SFTP server can be a virtual server. Cisco does not require a separate UCS server for each deployment.

  • Schedule backups for HCS components so that they do not overwhelm input/output operations-per-second (IOPS) capabilities and available bandwidth on the SFTP server. The higher the IOPS, the faster backups are completed.

  • Micro Node deployments have special backup and restore SFTP considerations. For more information, see Micro Node deployments.

SAN Considerations

Typically, one disk drive at a given rotating speed can provide the following IOPS:

  • 15,000 RPM: 180-210 IOPS

  • 10,000 RPM: 130-150 IOPS

  • 7200 RPM: 80-100 IOPS

  • 5400 RPM: 50-80 IOPS

You can determine how many disks are needed if the number of required IOPS can be estimated:

  • For a mirrored configuration, IOPS = read IOPS + (2 * write IOPS).

  • For a redundant array of independent disks level 5 (RAID 5) configuration, IOPS = read IOPS + (4 * write IOPS).

For example, to support 50 read IOPS (50 reads/second) and 100 write IOPS (100 writes/second) using RAID 5, the disk array must support 50 reads/second + (4 * 100 writes/second), or 450 IOPS.

Using 7200 RPM drives requires (450/80 = 6) disk drives.

Using 10,000 RPM drives requires (450/130 = 4) disk drives.

Solid state drives (SSDs) have much higher IOPS than magnetic disk drives. SSDs can deliver between 3000 and 10,000 IOPS. It would take one SSD (450/3,000 = 1) to support the throughput required in the example.


Note

If you have a Micro Node deployment, there is no SAN. For backup and restore guidelines for Micro Node deployments, refer to Micro Node deployments.

Scheduling Backups of UC Applications

We recommend that you implement regular backups for Cisco Unified Communications (UC) and management applications to ensure that data is not lost due to outages. For large Cisco HCS systems with many UC application instances, backups can be a tedious and potentially error-prone task.

Follow engineering recommendations to create a backup schedule that ensures that the Cisco HCS system is not overwhelmed during scheduled backups. Institute safeguards so that you do not overrun per-blade CPU or the SAN's IOPS engineering while maintaining an acceptable backup duration.

We recommend using the Platform Manager Automation Tool to schedule backups for 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 oversubscribed clusters that use 20% HA, 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.

    2. For the oversubscribed clusters that use less than 20% HA, 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.

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

      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 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 provides the desired results and conforms 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 to the associated SAN storage. The following table is an example of this type of matrix.

    Table 1. 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.

Table 2. Example Backup List with Timeline Sequence
Backup Order (Blade 1)
Line # Timeline Sequence Application Size Approx. Backup Time RAID Group ID
1 CUCM - PUB(1) 500 RG1,2,5,6
1 CUCM - PUB(2) 500 RG1,2,5,6
2 CUCM - PUB(1) 500
2 CUCM - PUB(2) 500
3 CUCM - PUB(1) 1000 7,8,9,12
3 CUCM - PUB(2) 1000 7,8,9,12
4 CUCM - PUB(1) 1000
4 CUCM - PUB(2) 1000
5 CUCM - PUB(1) 5000 22
6 CUCM - PUB(2) 10000 20
7 CUCxn - PUB(1) 500 4,5,8,3
7 CUCxn - PUB(2) 500 4,5,8,3
8 CUCxn - PUB(1) 500
8 CUCxn - PUB(2) 500

Backup and Restore Tools

The Backup and Restore (B&R) tools documented in this section are a combination of Cisco tools and third party utilities from vendors such as VMware and EMC. A hybrid solution is required as not all applications run on the same platforms and/or operating systems. For instance, for the Cisco HCS solution it is necessary to provide backup and restore procedures for IOS devices such as switches, routers, and gateways and applications that utilize various host operating systems such as Cisco Unified Communications Manager IM and Presence Service, Cisco Unity Connection, and Cisco Emergency Responder, that use the Voice Operating System (VOS), running on VMware in the Service Provider Cisco HCS Data Center.

CLI or GUI or Console

Backup and Restore procedures for some components are accomplished through direct access to the component's Administrator Console, CLI or GUI.

Disaster Recovery System (DRS)

The Cisco Disaster Recovery System (DRS) backup feature provides a reliable, efficient ,and simple method to back up the Unified Communications Applications. Alternatively, you can use the Cisco Hosted Collaboration Mediation Fulfillment Platform Manager service to back up Unified Communication Applications separately; see the Platform Manager section.

The DRS Administration Guide for Cisco Unified Communications Manager and Cisco Unified Communications Manager IM and Presence Service can be found at :

http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-maintenance-guides-list.html

The DRS Administration Guide for Cisco Unity Connection Release can be found at :

http://www.cisco.com/c/en/us/support/unified-communications/unity-connection/products-maintenance-guides-list.html

DRS contains two key functions, Master Agent (MA) and Local Agent (LA). MA coordinates backup/restore activity with LAs, and DRS automatically activates MA and LA on all nodes in the cluster.

For security and data integrity, DRS uses SSL-based communications between MA and LA for authentication and data encryption among Cisco Unified Communications Manager cluster nodes. DRS uses IPSec certificates for public/private key encryption.

Access DRS through the Cisco Unified Communications Manager administration GUI. DRS provides full data backup and restore capabilities for all servers in a Cisco Unified Communications Manager cluster. The backups are archived on a physical storage device, which for Cisco HCS is an SFTP server. DRS supports scheduled or user-invoked backups. When performing a system restore, you can choose which nodes in the cluster to restore.

DRS archive backups can be stored to a physical tape drive or remote Secure FTP (SFTP) server. For the Cisco HCS solution it is recommended to use SFTP servers. The service providers have the option of using a dedicated SFTP server for large enterprises, or share an SFTP server among multiple enterprises. This decision should be based on disk capacity requirements and security policies established between the Service Provider and the client enterprises. For more information, see Scheduling Backups of UC Applications.

Cisco allows the use of any SFTP server product but recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner Program (CTDP). CTDP partners , such as GlobalSCAPE, certify their products with specific versions of Cisco Unified Communications Manager and other Cisco applications.

For information on using GlobalSCAPE with supported Cisco Unified Communications versions, refer to http://www.globalscape.com/gsftps/cisco.aspx.


Note

Cisco does not support using the SFTP product freeFTDP. This is because of the 1GB file size limit on this SFTP product.

Cisco Hosted Collaboration Platform Manager Service

The Platform Manager service included with Cisco Hosted Collaboration Mediation Fulfillment, is a backup management client for various Cisco Unified Communications applications, including but not limited to:

  • Cisco Unified Communications Manager IM and Presence Service

  • Cisco Unified Communications Manager

  • Cisco Unity Connection

The Platform Manager organizes servers into server groups. Server groups allow you to logically join together different servers that you want to back up as a group. You can back up all servers in a server group with a single task that performs sequential backups. Server groups are user-defined and consist of servers from multiple clusters. All servers in a particular group, however, must have the same product. For example, you cannot mix Cisco Unified Communications Manager and Cisco Unified Communications Manager IM and Presence Service nodes in the same server group. To setup and configure the server groups, follow the steps and recommendations in section Scheduling Backups of UC Applications.

The Platform Manager allows you to set up the system server inventory as well as select, schedule, and monitor backups of one or more servers across one or more clusters. You can set up the server inventory to be automatically synchronized from the Shared Data Repository to avoid manual setup. The Platform Manager offers a wide range of different user-defined server types to accommodate the management of potentially thousands of servers.

After scheduling backup on your servers and setting up your servers and server groups within Platform Manager, you can manage and monitor backup tasks of your system using the Backup Schedule feature to perform DRS backups on groups of servers. For details, refer to the "Backup Task List" section in Cisco Hosted Collaboration Mediation Fulfillment Maintain and Operate Guide at:

http://www.cisco.com/en/US/partner/products/ps11363/prod_maintenance_guides_list.html

Platform Manager Operation

Step Procedure
1. Sync Unified Communications Applications Syncing Unified Communications Applications
2. Sync server information from SDR with Platform Manager. Sync Platform Manager with SDR
3. Create a server group. Create a Server Group
4. Automate Backup operations. Automate Backup and Restore Operations
5. Manually add DRS configuration to the Server. Platform Manager - Disaster Recovery System Backup
Syncing Unified Communications Applications
Procedure
Step 1

On the left menu, select Administration and choose UC Applications Synchronization.

Step 2

Configure the Start Time and Frequency fields for the scheduled sync.

Step 3

Click Sync Now to perform the sync or the Save button to save the scheduled sync.

Sync Platform Manager with SDR
Procedure
Step 1

On the left menu, select the Administration menu and choose SDR Synchronization.

Step 2

Configure the scheduled Start Time and Frequency of the sync.

Step 3

Click the Sync Now button to perform a sync or the Save button to save the scheduled sync.

This should result in your UC servers showing up under Inventory -> Servers
Create a Server Group
Procedure
Step 1

On the left menu, select Inventory Menu > Server Group and click the Add button.

Step 2

Fill in the required information to create a Server Group for each application.

Note 

A server group can only have servers of the same application.

Step 3

Click on the name of the server you would like to edit, or click the leftmost box and click the Edit button.

Step 4

Select the servers to add to the server group and click the Save button.

Note 

To avoid potential issues with over-subscription or IOPS, a mapping of VMs to LUNs is required. Platform Manager is not aware of where the UC servers are located and would not be accounted for.

This will populate the information into Platform Manager.
Automate Backup and Restore Operations
Procedure
Step 1

On the left menu, select Tasks and choose Create a Backup Task.

Step 2

Configure the required fields and click the Save button.

Platform Manager - Disaster Recovery System Backup
Procedure
Step 1

Manually add the Disaster Recovery System configuration to the server for the Network Device and DRS Schedule.

Step 2

Set the DRS Schedule to disabled.

The Platform Manager will enable and trigger the DRS schedule.

Virtual Machine Backup and Restore

This section describes the virtual machine backup options for solution-level backup and restore.

Backup Options for Virtual Machines

For the purposes of this document, the following definitions apply:

  • A crash-consistent backup is a backup taken of an entire virtual machine while the virtual machine is running and there is no quiescing (pausing or temporarily in inactive or disabled state) of the application for the backup.

  • An application-consistent backup is a backup taken of an entire virtual machine when the VM is powered off, or if the application can and does quiesce (pause, temporarily inactive or disabled) before the backup.

  • A full VM backup is any backup taken of a full virtual machine. It might be crash-consistent or application-consistent.

  • The VMware Data Recovery (VDR) feature backs up entire virtual machines, in other words, a full VM backup. Many other solutions can also do this (vStorage API integration, copying VM files, third-party products like EMC Avamar, etc.). VDR is used in this document to represent any full VM backup method other than snapshots.

Full Virtual Machine (VM) Backups

A Full VM backup is a backup taken of a full virtual machine. It might be crash-consistent or application-consistent.

Full VM backups have two significant advantages:

  • The backup process is the same for any virtual machine, thus allowing a consistent backup process across any variety of applications.

  • The restore process is simple and straightforward.

There are also two significant disadvantages:

  • Backups consume significant CPU, IOPS, and disk space.

  • Unless the VM is powered off or the application has a backup agent or other mechanism that can be used to quiesce the application, it can only take a crash-consistent backup.

VM Backups for HCS Management Applications

For Cisco HCS Management Applications, (Cisco Hosted Collaboration Mediation Fulfillment, Prime License Manager, Cisco Unified Communications Domain Manager(s), Cisco Prime Collaboration Assurance) the applications quiesce when entering a maintenance window, or daily (nightly) provisioning quiet period. This makes it possible to capture application-consistent VM backups.

However, the application specific backup mechanisms are recommended for daily backups.

VM Backups Before Software Upgrades

Backups are recommended to be performed before initiating an upgrade of any Cisco HCS application, in case there is an upgrade failure that would require the application to be restored. The application specific restore process is very time consuming, compared to the restore from a full VM backup. In addition to the recommended application specific backup, Cisco HCS recommends taking a full VM backup of the Management application before performing the software upgrade. If the service provider experiences a catastrophic failure during the management application(s) upgrade maintenance window that requires the application to be restored, the full VM backup of the application can be used to restore within the upgrade maintenance window.

VM Backups for UC Applications

Cisco DRS backs up only the configuration data of the application, not the binaries. The DRS restore process is time-consuming and requires some user intervention because it request application re-install as part of the restore process. The complexity and duration of the restore process using Cisco DRS has created interest in using full VM backup instead, where both the binaries and configuration data are backed up.

VM ware Application-Consistent Backups

As long as the UC virtual machine is powered off when a full VM backup is taken, we expect that the full VM backup can be successfully used to restore an instance of a Cisco Unified Communications Application.

Unfortunately, it is not possible to know if a given full VM backup is application-consistent or crash-consistent. Therefore it is not possible for Cisco to guarantee that any given full VM backup will restore properly.

Crash-Consistent Backups

It is inconvenient and often impractical to power off the VMs in order to take backups on a regular basis. It is also generally not possible to automate the power down of the VM as part of any VDR-type backup process. Crash-consistent backups are of interest for the backup of UC applications because these are the only type of full VM backup that can be taken of the Cisco Unified Communications Applications without powering them off.

If crash-consistent backups are going to be taken, the service provider implements the process to ensure that adequate IOPS and other resources are available so that the Cisco Unified Communications Applications are not affected.

Summary

Full VM backups of UC VMs are never guaranteed to restore, due to quiescing dependencies. Application-consistent Full VM backups are most likely to successfully restore. Crash-consistent full VM backups are less likely to successfully restore.

Full VM backups of live UC VMs are statistically likely to be application-consistent, but they may only be crash-consistent. Full VM backups of powered-down VMs are always application-consistent.

The Cisco DRS backup feature is designed to properly back up the Cisco Unified Communications Applications, and it should always be used as the most fail-safe method to restore a UC application instance. Full VM backup is not a replacement for Cisco DRS, so service provider should continue to take Cisco DRS backups.

Cisco DRS backups or other Cisco Unified Communications Applications-specific backups should continue to be taken on a regular basis.

Full VM backups, with very high likelihood, can be used to restore the Cisco Unified Communications Applications instance, but there is no guarantee. This is why the Cisco DRS backup should always be done as an alternative way to restore the UC instance. Cisco recommends that any full VM backups should be made while the VM is powered off. If taking crash-consistent backups, Cisco recommends you take them during a low-traffic period to minimize the possibility that the application is negatively affected by the backup.

If service providers choose to perform full VM backups, they must test the restoration process first to ensure that the method they are using works to restore both the cluster and individual application instances. Cisco does not test or validate any specific full VM backup methods. The service provider chooses the method and tests it. It is very likely the service provider will have to manually synchronize the database when restoring a cluster.

Ultimately, Cisco cannot guarantee that by following these guidelines any full VM backups can be used to successfully restore a Cisco Unified Communications Applications instance. If a full VM backup cannot be used to restore the VM, the only recourse is to reinstall the application and restore via Cisco DRS backup instead.

Statistically, using VDR, it is possible to back up a virtual machine reliably. The memory cache not written to disk does not seem to affect the outcome of a restore. The backups taken by VDR generate no noticeable errors over the course of time. No errors were observed after a restore of an active server. There is minimum impact to call processing during the VM backup.

Cisco Prime LAN Management Solution (LMS)

With Cisco HCS being an end-to-end network solution, the right set of tools to configure, administer, monitor and troubleshoot the solution is the Cisco Prime LAN Management Solution (LMS). LMS provides the functionality to perform configuration backup, software image management, compliance, and change management required to maintain and update Cisco network elements.

For a detailed description on how Cisco Prime LAN Management Solution can be used for Backup and Restore of system wide configuration information see: Configuration Management with Cisco Prime LAN Management Solution 4.1 at http://www.cisco.com/c/en/us/td/docs/net_mgmt/ciscoworks_lan_management_solution/4-1/user/guide/configuration/config.html.

For a complete list of all Cisco devices supported by Cisco Prime LAN Management Solution see Supported Devices Table for Cisco Prime LAN Management Solution 4.1 at http://www.cisco.com/en/US/partner/docs/net_mgmt/ciscoworks_lan_management_solution/4.1/device_support/table/lms41sdt.html

Component Backup and Restore

This section provides information and references for backup and restore for components.

HCS Solution Components and Groups

The recommended backup and restore strategy is to group Cisco HCS solution components into sets of elements with common characteristics, and use a specific Cisco recommended tool for each one of these sets.

The Cisco HCS solution components are grouped into types of elements with common characteristics, as follows

  • Data Center Infrastructure Components

  • Aggregation / Shared Components Elements

  • Cisco HCS Service Assurance

  • Cisco HCS Service Fulfillment

  • Cisco UC Applications

  • Endpoints

  • SRST and Voice Gateways Components

  • Cisco HCS for Contact Center Components

  • Third Party Applications

Quick Reference Guide by Component

The following information provides a quick reference for backup and restore options for components.

Component Backup Tool Frequency Restore Option
Aggregation
Applications
Cisco Expressway Administrator console AI, AU, UPG Administrator console
Cisco Unified Communications Manager DRS or Platform Manager AI, AMU, UPG DA DRS or Platform Manager
Cisco Unified Communications Manager IM and Presence Service DRS or Platform Manager AI, AMU, UPG, DA DRS or Platform Manager
Cisco Unity Connection DRS or Platform Manager AI, AMU, UPG, DA DRS or Platform Manager
Cisco Emergency Responder DRS AI, AMU, UPG, DA DRS

Cisco Unified Attendant Console - Advanced

Administrator Console or Full VM Backup AI, AMU, UPG, DA Administrator Console or Full VM Backup
Cisco Paging Server (Singlewire - InformaCast Basic Paging) Administrator console AI, AMU, UPG, DA Administrator Console
Contact Center
Cisco Unified Contact Center Enterprise DRS + CLI Scripts + SQL Server tools AI, AMU, UPG, DA DRS + CLI Scripts + SQL Server tools
Shared
TelePresence Administrator console AI, AU, UPG Administrator console
Service Mgmt - Fulfillment
HCM-F CLI AI, AMU, UPG, DA CLI
Cisco Unified Communications Domain Manager CLI ¥ AI, AMU, UPG§, DA CLI
Cisco Prime License Manager Administrator console AI, AMU, UPG, DA Administrator console
Service Mgmt - Assurance
Cisco Prime Collaboration for Assurance GUI AI, AMU, UPG, DA CLI
HCS Virtualized Multi-Tenant Data Center -Infrastructure
Nexus 7000 / Nexus 5000 Administrator Console or LMS AI, AU, UPG Rebuild config after restoring failed device
HCS Virtualized Multi-Tenant Data Center -Compute
UCS Manager UCSM CLI or GUI AI, AU, UPG UCSM or CLI
vCenter DB Backups AI, AU, UPG Rebuild the VM
Key

AI - After Installation

AU - After Configuration/Provisioning Updates

AMU - After Major Updates. For more information about Major Updates, see Cisco HCS Fulfillment and UC Applications.

UPG - Before and After Software Upgrade

Da - Daily (every 24 hrs during quiet period)

¥ - For more information on the CLI commands used to back up and restore, see Perform Backup of Cisco Unified Communications Domain Manager.

§ - When you upgrade Cisco Unified Communications Domain Manager, you can reduce the amount of time it takes to upgrade the system by performing backup activities before the upgrade maintenance window. You can also reduce the length of time for upgrade and backup by running node upgrades in parallel (a process that includes a backup) with the following CLI command:

cluster upgrade media/platform-install-1.2.0-<version>.iso fast

Another alternative is to use VMware snapshots for your backup if reducing the length of time for the upgrade is a primary consideration. Consider the following when using VMware snapshots to back up Cisco Unified Communications Domain Manager:

  • Cisco cannot guarantee that a VMware snapshot can be used to successfully restore Cisco Unified Communications Domain Manager or any Cisco HCS Management application. If you cannot restore the application from a snapshot, your only recourse is to reinstall the application.

  • When the backup is complete and you are sure that you do not require the VMware snapshot for restore activities, delete the snapshot immediately to preserve LUN space.

For more information about the risks of using VMware snapshots, refer to the “Backup and Restore” chapter in the Cisco Hosted Collaboration Solution Release 12.5 Maintain and Operate Guide.

Data Center Infrastructure Components

These include Cisco Network/Data Center Elements such as routers, switches, gateways, fabric interconnect devices, and firewalls. These have the following characteristics:

  • Configuration provisioning could be manual or downloaded from an FTP server.

  • Configuration does not change often.

  • Configuration files take small amounts of disk space.

  • Backup configuration files are stored on FTP servers.

Backup for Cisco Network/Data Center Elements should be performed according to their product documentation. For the IOS based HCS Data Center components, the backup is simply saving the IOS configuration files. There is no particular concern for the order of backing up these components.

Infrastructure component Related information

Cisco MDS 9000 Family

http://www.cisco.com/c/en/us/support/docs/storage-networking/mds-9500-series-multilayer-directors/117621-configure-MDS-00.html

VMware vCenter

http://www.VMware.com

Cisco ASA 5500 Series

http://www.cisco.com/en/US/products/ps6120/tsd_products_support_series_home.html

Cisco Nexus 5000 Series

http://www.cisco.com/en/US/products/ps9670/products_installation_and_configuration_guides_list.html

Cisco Nexus 7000 Series

http://www.cisco.com/en/US/products/ps9402/products_installation_and_configuration_guides_list.html

Session Border Controller

Use the supported SBC interface.

Cisco UCS Manager

http://www.cisco.com/en/US/products/ps10281/products_installation_and_configuration_guides_list.html

Note 

To ensure that all virtual machines return online after a UCS Manager restart, enable automatic VM startup upon host recovery in the vCenter. This needs to be done for all hosts. Failure to do so can cause the vCenter to not fully recover after restore, and manual vCenter recovery may be required.

Alternatively, Cisco Prime LAN Management Solution (LMS) can be used for these Cisco HCS DC/network infrastructure elements.

Components that do not follow standard procedures include Micro Node.

Micro Node deployments

The Cisco Hosted Collaboration Solution Micro Node deployment approach is based on UCS C-series servers instead of UCS blades in a chassis, and the Nexus 5548 switch. C-series servers have their own onboard disk for storage, so the SAN disk (shared storage) approach is not used for Micro Node deployments. For more information on Micro Node deployment architecture, see Cisco Hosted Collaboration Solution Release 12.5 Solution Reference Network Design Guide, available at http://www.cisco.com/en/US/partner/products/ps11363/products_implementation_design_guides_list.html.

Cisco recommends the following backup and restore approach for Micro Node deployments:

  • Dedicate one or more C-series servers to host FTP servers, using the C-series server disk (local storage) for backup.

  • Back up multiple applications to the same FTP server if you want, but do not store a backup on the same server (disk) that hosts the application or component itself.

For best practices on planning your data center for backup and restore in a Micro Node deployment, refer to the Cisco Hosted Collaboration Solution Release 12.5 End-to-End Planning Guide.

Aggregation / Shared Components Elements

These are components of the solution that provide telephony aggregation functions in the Cisco HCS architecture, such as Border Elements/Controllers, and Shared functionality between multiple customers in Cisco HCS, such as Telepresence Exchange System, Cisco Expressway, etc.

Follow standard procedures to back up and restore telephony aggregation and shared components.

Infrastructure component Related information
Telepresence Exchange System

http://www.cisco.com/c/en/us/support/conferencing/telepresence-exchange-system/products-maintenance-guides-list.html

Cisco Expressway

http://www.cisco.com/c/en/us/support/unified-communications/expressway-series/products-maintenance-guides-list.html

Telepresence Exchange System

The Database Backup window allows the administrator to view scheduled database backups that are configured on the Cisco Telepresence Exchange System and to view past database backups and database restores.

Additionally, you can initiate a manual, on-demand backup of an existing scheduled backup and restore a database backup on the database server of the system.

Cisco Expressway

The backup and restore page (Maintenance > Back and Restore) is used to create and restore backup files of your Cisco Expressway data.

The data in the backup includes:

  • System configuration settings.

  • Clustering configuration

  • Security certificates

  • Administrator account details

  • Call detail records (if the CDR service on Expressway is enabled)


Note

Log files are not included in the backup files.

Cisco HCS Fulfillment and UC Applications

Cisco Hosted Collaboration Mediation Fulfillment and Cisco Unified Communications Domain Manager (10.x/11.5x) work together to provision various Cisco HCS components, primarily the Cisco Unified Communication Applications. Both Cisco Hosted Collaboration Mediation Fulfillment and the Cisco Unified Communications Domain Manager(s) have their own persistent provisioning database. But, some provisioning data is duplicated between the two separate application databases. Similarly, the Cisco UC Applications have their own persistent databases. Cisco Unified Communications Domain Manager(s) duplicate Cisco UC Application provisioning data as well, as it orchestrates the UC Application provisioning for the customers in its domain.

Cisco Unified Communications Domain Manager is not considered the Master of these duplicated data elements for the UC Applications that it manages. Cisco Unified Communications Domain Manager can DATASYNC with Cisco Hosted Collaboration Mediation Fulfillment and the UC Applications that it manages.

Therefore, the Cisco HCS Service Fulfillment component group and the UC applications component group should be considered together when planning their backup and restore strategy:

  • Cisco Hosted Collaboration Mediation Fulfillment

  • Cisco Unified Communications Domain Manager (10.x/11.5x)

  • Cisco Unified Communications Applications

    • Cisco Unified Communications Manager

    • Cisco Unified Communications Manager IM and Presence Service

    • Cisco Unity Connection


Note

Backups of Cisco Hosted Collaboration Mediation Fulfillment, Cisco Unified Communications Domain Manager (10.x/11.5x) and Cisco UC Applications should be performed when a provisioning FREEZE is in effect, to insure all provisioning transactions are complete in the system, i.e. overnight.

Backup Frequency

Backups of all these components should be performed:

  • AU - After initial installation and provisioning.

  • UPG – Before and After Software Upgrade

  • AMU – After a MAJOR change in Cisco HCS Customer / Cisco UC Application configuration, i.e. Add/delete/modify of:

    • Provider (affects Cisco Hosted Collaboration Mediation Fulfillment and Cisco Unified Communications Domain Manager)

    • CUSTOMER (affects Cisco Hosted Collaboration Mediation Fulfillment and Cisco Unified Communications Domain Manager)

    • SITE (affects Cisco Hosted Collaboration Mediation Fulfillment, Cisco Unified Communications Domain Manager and Cisco UC Applications)

    • Dial Plan (affects Cisco Hosted Collaboration Mediation Fulfillment, Cisco Unified Communications Domain Manager and Cisco UC Applications)

  • DA - Daily

Backup Order

The recommendation is to schedule backup activities for these applications to be completed in the following order:

  1. DATASYNC Cisco Unified Communications Domain Manager to

    • Cisco UC Applications

    • Cisco Hosted Collaboration Mediation Fulfillment

  2. Backup Data Center Infrastructure Components.

  3. Backup Management Cisco Hosted Collaboration Mediation Fulfillment

  4. Backup Aggregation Components

  5. Backup Cisco UC Applications

  6. Backup Optional Components such as Expressway and Paging Server

Perform Cisco Unified CDM DATASYNCH to Cisco UC Applications and Cisco Hosted Collaboration Mediation Fulfillment

Manually Sync Cisco Unified CDM and Cisco Hosted Collaboration Mediation Fulfillment
Procedure
Step 1

Login as hcsadmin

Step 2

From the left menu, choose Device Management > Advanced > Perform Actions .

Step 3

Select Action and choose Import.

Step 4

Select Device and choose HCM-F hostname.

Step 5

Click the Save button.

Manually Sync Cisco Unified CDM and Cisco Unified Communications Applications
Procedure
Step 1

Login as the provider admin.

Step 2

From the left menu, choose Device Management > Advanced > Perform Actions .

Step 3

Select Action and choose Import.

Step 4

Select App Type and choose CUCM device / CUC device.

Step 5

Highlight the appropriate clusters (corresponding to target publishers) in the Available box and press the Select button.

Step 6

Click the Save button.

Scheduled Sync of Cisco Unified CDM and Cisco Hosted Collaboration Mediation Fulfillment
Procedure
Step 1

Login as hcsadmin

Step 2

From the left menu, choose Administration Tools > Scheduling.

Step 3

Choose Add to create a new schedule to execute once (Schedule type = Single Execution) or multiple times (Schedule type = Multi Execution) .

Step 4

In the Schedule Resources box, set the following fields:

Field Option
Resource Type

data/DataSync

Resource Attribute

name

Resource

HcsHcmfPullDS

Perform Action

Checked

Step 5

In the Single/Multiple Executions tab, populate the fields to tailor when the schedule runs, as appropriate .

Scheduled Sync of Cisco Unified CDM and Cisco Unified Communications Applications
Procedure
Step 1

Login as hcsadmin

Step 2

From the left menu, choose Administration Tools > Scheduling.

Step 3

Choose Add to create a new schedule to execute once (Schedule type = Single Execution) or multiple times (Schedule type = Multi Execution) .

Step 4

In the Schedule Resources box, set the following fields:

Field Option
Resource Type

data/DataSync

Resource Attribute

name

Resource

HcsPull-<hostname+domain or IP>--<cluster name>-DS

Perform Action

Checked

Step 5

In the Single/Multiple Executions tab, populate the fields to tailor when the schedule runs, as appropriate

Perform Backup of Cisco Hosted Collaboration Mediation Fulfillment

The following CLIs can be used to setup Cisco Hosted Collaboration Mediation Fulfillment backups:

CLI examples

  • utils disaster_recovery device add network <name> <path>

  • utils disaster_recovery backup network HCS <name>

  • utils disaster_recovery schedule add <job> <network name> HCS

  • utils disaster_recovery schedule enable <job>

Perform Backup of Cisco Unified Communications Domain Manager

The following CLIs can be used to set up Cisco Unified Communications Domain Manager backups:

CLI Examples

  • Back up destination: cluster run all backup create <destination>

  • Manual backup: backup create localbackups or backup create myserverbackup

  • Basic (default) upgrade, includes a backup: cluster upgrade media/platform-install-1.2.0-<version>.iso

  • Parallel upgrade of unified nodes, includes a backup: cluster upgrade media/platform-install-1.2.0<version>.iso fast

  • Serial upgrade of unified nodes, includes a backup: cluster upgrade media/platform-install-1.2.0<version>.iso serial

Scheduling CLIs

  • schedule add <job-name> <user-command>

  • schedule time <job-name> <hour> <minute>

  • schedule time <job-name> every <N> hours

Scheduling Examples

  • schedule add mybackups backup create localbackups

  • schedule time mybackups 2 0

  • schedule time mybackups weekly 0

  • schedule enable mybackups

By default, there is no regular maintenance of backups and a scheduled job should be created to perform this maintenance, for example:

  • schedule add backuprotate backup clean localbackups keep 5

  • schedule time backuprotate rotate 3 0

  • schedule enable backuprotate

backup clean <location> keep <N> will delete older copies so that only N copies are kept

backup clean <location> before <yyyy-mm-dd [HH:MM] > will delete copies older than the specified date

Restore

The restore strategy depends on which component has failed that needs to be restored. The following sections consider the failure/restore of a single component.

Cisco Unified CM/ Cisco Unified CM IM and Presence Service Restore

If a Cisco Unified Communications Manager or Cisco Unified Communications Manager IM and Presence Service and Presence Subscriber node fails and has to be restored, after the Subscriber node is restored, the surviving Publisher node database will be replicated by the Subscriber node.

If a Cisco Unified Communications Manager Publisher node fails and has to be restored, Cisco Unified Communications Manager supports restoring the Publisher node database from a surviving Subscriber node database in the cluster.

In these cases, there is no data loss in the Cisco Unified Communications Manager cluster after the restoration and database replication is complete.

Cisco Unified CM IM and Presence Service Cluster Restore

If an entire Cisco Unified Communications Manager Cluster fails and has to be restored, the Cisco Unified Communications Manager database will be restored to the latest backup. This probability of this happening is very low.

For information on restoring the Cisco Unified Communications Manager Cluster, see http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/drs/10_0_1/CUCM_BK_D220A91D_00_disaster-recovery-system-cucm-100.html

Regardless of the low probability for this scenario, as with any restore from latest backup, there may be changes that were made in the Cisco HCS solution since the backup was taken, and thus are not present in the restored application database. By following the backup frequency recommendations, the changes should be limited to addition/deletion of Cisco UC Application elements such as users, phones, etc.

Cisco Unified Communications Domain Manager 10.x Managed Cluster

Using Cisco Unified Communications Domain Manager 10.x, the devices (UC application publisher node) are considered the data Master. Further, the Cisco Unified Communications Domain Manager 10.x administrator is likely not aware of the data inconsistencies between the surviving Cisco Unified Communications Domain Manager 10.x database and the restored. Cisco Unified Communications Manager Cluster database. If the Cisco Unified Communications Domain Manager 10.x administrator attempts MACD operations for the elements that have inconsistencies, Cisco Unified Communications Domain Manager 10.x will detect the inconsistency and the operations will fail.

Cisco Unified Communications Domain Manager 10.x can DATASYNC the data inconsistencies between the surviving Cisco Unified Communications Domain Manager 10.x database and the restored Cisco Unified Communications Manager Cluster database. In this case, since the UC Application database is considered the Master of the data, the Cisco Unified Communications Domain Manager 10.x database will be updated to the restored (latest backup) Cisco Unified Communications Manager database.

Even though there is likely data loss in this scenario, the recommendation is to manually perform the DATASYNC as soon as the Cisco Unified Communications Manager Cluster is restored.

Cisco Unified CDM or Cisco HCM-F Failure/Restore

Cisco Hosted Collaboration Mediation Fulfillment and Cisco Unified Communications Domain Manager 10.x are tightly integrated, and support synchronization mechanisms between their databases.

Cisco Unified Communications Domain Manager applications is required to be deployed in a HA multi-node cluster, where the database is replicated among all the nodes in the cluster. In the event of a single Cisco Unified Communications Domain Manager node failure, the failed node should be able to be restored, and the restored Cisco Unified Communications Domain Manager node database synchronized to the surviving Cisco Unified Communications Domain Manager nodes database.

Cisco Hosted Collaboration Mediation Fulfillment does not support HA, and the probability of needing to restore the node from the latest backup is higher. If Cisco Hosted Collaboration Mediation Fulfillment is required, use the restore procedures as in the product documentation.

Using Cisco Unified Communications Domain Manager, the devices (Cisco UC Applications publisher node) are considered the data Master. The Cisco Unified Communications Domain Manager administrator is likely not aware of the data inconsistencies between the restored Cisco Unified Communications Domain Manager 10.x database and the surviving Cisco Unified Communications Manager Clusters databases. if the Cisco Unified Communications Domain Manager administrator attempts MACD operations for the elements that have inconsistencies, Cisco Unified Communications Domain Manager will detect the inconsistency and the operations will fail.

If the entire Cisco Unified Communications Domain Manager system or Cisco Hosted Collaboration Mediation Fulfillment fails and has to be restored from the latest backup, both the Cisco Unified Communications Domain Manager system and the Cisco Hosted Collaboration Mediation Fulfillment application should be restored using the latest backups. As with any restore from the latest backup, there may be changes that were made in the Cisco HCS solution since the backup was taken, and thus are not present in the restored applications databases. By following the backup frequency recommendations, the changes should be limited to addition/deletion of UC Application elements such as users, phones, etc.

Cisco Unified Communications Domain Manager can DATASYNC the data inconsistencies between the surviving Cisco Unified Communications Manager Clusters databases and the restored Cisco Unified Communications Domain Manager database. When the DATASYNC is performed, the Cisco Unified Communications Domain Manager database will be synchronized with the surviving Cisco UC Applications databases, so there is effectively no data loss.

The recommendation is to manually perform the DATASYNC as soon as the Cisco Unified Communications Manager Cluster is restored.

However, the DATASYNC process in Cisco Unified Communications Domain Manager currently adds missing elements into a Cisco Unified Communications Domain Manager database at the Customer, Reseller or Provider level in the Cisco Unified Communications Domain Manager hierarchy, potentially not the right Site level hierarchy. The Cisco Unified Communications Domain Manager Site Admin won't be able to see the data that was synced in at the wrong level. A higher level Cisco Unified Communications Domain Manager administrator would have to be engaged to move the data to the correct site in Cisco Unified Communications Domain Manager

Cisco Unified CDM / Cisco HCM-F Restore Activities/Order

If the entire Cisco Unified Communication Domain Manager system or Cisco Hosted Collaboration Mediation Fulfillment fails, restore using the latest backup.

The order of restore activities for Cisco Hosted Collaboration Mediation Fulfillment and Cisco Unified Communication Domain Manager is as follows:

  1. Disable any/all DATASYNC schedules in surviving Cisco Unified Communication Domain Manager, primarily for:

    • Cisco Hosted Collaboration Mediations Fulfillment
    • UC Applications

  2. Restore Cisco Hosted Collaboration Mediations Fulfillment

  3. Restore Cisco Unified Communication Domain Manager

  4. Enable DATASYNC schedules in restored Cisco Unified Communication Domain Manager, primarily for:

    • Cisco Hosted Collaboration Mediations Fulfillment
    • UC Applications

  5. Perform manual DATASYNC, primarily for:

    • Cisco Hosted Collaboration Mediations Fulfillment
    • Cisco UC Applications
Disable Sync Mechanisms
Disable Sync Between Cisco Unified Communication Domain Manager and Cisco Hosted Collaboration Mediation Fulfillment
Procedure
Step 1

Login as hcsadmin.

Step 2

On the left menu, choose Device Management > Schedule and click on the HcsHcmfSyncSCHED schedule .

Step 3

Deselect the checkbox for Active.

Disable Sync between Cisco Unified Communication Domain Manager and Cisco Unified Communication Applications
Procedure
Step 1

Login as provider admin.

Step 2

From the left menu, choose Device Management > CUCM > Schedules or Device Management >CUC > Schedules depending on the app in question (Call manager or Unity respectively).

Step 3

Click on the schedule instance corresponding to the target UC app node.

Step 4

Deselect the Active checkbox.

Restore Cisco Hosted Collaboration Mediation Fulfillment
Procedure
Step 1

Open an SFTP client and connect to the Cisco Hosted Collaboration Mediation Fulfillment platform by using the adminsftp user and the administrator password that you set up during installation.

Step 2

Copy the backup file to the Cisco Hosted Collaboration Mediation Fulfillment platform, by navigating to the backup directory. Enter cd backup, and copy the backup file to the /common/adminsftp/restore directory.

Step 3

Access the Disaster Recovery System CLI admin prompt, by starting an SSH session and logging in to the CLI on the Cisco Hosted Collaboration Mediation Fulfillment platform.

Step 4

Enter utils disaster_recovery restore local restore_server tarfilename device_name

Option Description
restore_server

the hostname of the server to be restored

tarfilename

the name of the backup file to be restored without extension; for example, 2008-01-21-18-25-03

device_name

the name of the backup device

Step 5

The backup data gets restored on the server that you chose. To view the status of the restore, enter utils disaster_recovery status restore .

Step 6

Restart the Cisco Hosted Collaboration Mediation Fulfillment platform.

Restore Cisco Unified CDM

Cisco Unified CDM can be restored from a backup using the following CLI command:

backup restore <loc-name> <yyyy-mm-dd [hh:mm] >

Enable Sync Mechanisms
Enable Sync Between Cisco Unified CDM and Cisco Hosted Collaboration Mediation Fulfillment
Procedure
Step 1

Login as hcsadmin.

Step 2

On the left menu, choose Device Management > Schedule and click on the HcsHcmfSyncSCHED schedule .

Step 3

Select the checkbox for Active.

Enable Sync Between Cisco Unified CDM and Cisco UC Applications
Procedure
Step 1

Login as provider admin.

Step 2

From the left menu, choose Device Management > CUCM > Schedules or Device Management >CUC > Schedules depending on the app in question (Call manager or Unity respectively).

Step 3

Click on the schedule instance corresponding to the target UC app node.

Step 4

Select the Active checkbox.

Cisco Unified Communications Domain Manager Specifics

Cisco Unified Communications Domain Manager backup and restore procedures are covered in the product documentation. The backup covers the contents of the database as well as themes. The configuration is not backed up.

In Cisco HCS, Cisco Unified Communications Domain Manager deployments manage multiple customers. It not possible to backup Cisco Unified Communications Domain Manager configuration for a single or subset of Cisco Unified Communications Domain Manager managed customer(s). The entire Cisco Unified Communications Domain Manager database, and consequently all customers configuration stored in Cisco Unified Communications Domain Manager, is included in the Cisco Unified Communications Domain Manager backup.

Cisco Unified Communication Applications Specifics

This includes the following Cisco HCS Applications:

  • Cisco Unified Communications Manager

  • Cisco Unified Communications Manager IM and Presence Service

  • Cisco Unity Connection

For these applications we recommend that you use the Disaster Recovery System (DRS) tools or Platform Manager.

Cisco Unified Communication Applications

For these applications the current recommendation is to use Cisco Voice Operating System (VOS) based Disaster Recovery System (DRS) tools or Platform Manager (which uses DRS).

A key requirement when dealing with Cisco Unified Communications Applications is making sure that powering on and synchronizing virtual machines after a restore procedure can be accomplished as fast and efficiently as possible.

Cisco Unified Attendant Console is a Windows Server product and therefore does not use DRS or Platform Manager for backup or restore functionality. Please refer to the recommendations from the product documentation in the table below.

Infrastructure component Related information

Cisco Unified Communications Manager

http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/tsd-products-support-maintain-and-operate.html

Cisco Unity Connection

http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html

Cisco Unified Communications Manager IM and Presence Service

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/drs/9_1_1/CUCM_BK_D9A29FAD_00_disaster-recovery-system-cucm-91_chapter_010.html

Cisco Unified Attendant Console - Advanced

http://www.cisco.com/en/US/products/ps7282/prod_maintenance_guides_list.html

Cisco HCS Service Assurance (SA)

Cisco Prime Collaboration Assurance (PCA) provides the Service Assurance functionality in Cisco HCS. Cisco Hosted Collaboration Mediation Fulfillment configures the elements (primarily Cisco UC Applications, users and devices, etc.) to be monitored into Cisco Prime Collaboration Assurance during initial configuration and setup of Cisco Prime Collaboration Assurance, as well as when new elements are added into the Cisco HCS system (into Cisco Hosted Collaboration Mediation Fulfillment).

The Cisco Prime Collaboration Assurance backup and restore service allows you back up the database, configuration files, and log files to either a remote location or a local disk, and to subsequently restore from a backup.

For details on the Cisco Prime Collaboration Assurance backup and restore service, refer to Cisco Prime Collaboration Assurance Guide - Advanced guide.

For details on the Cisco Prime Collaboration Analytics backup and restore service, refer to Cisco Prime Collaboration Analytics guide.

Infrastructure component Related information

Cisco Prime Collaboration Assurance

http://www.cisco.com/c/en/us/support/cloud-systems-management/prime-collaboration/products-user-guide-list.html

Cisco Prime Collaboration Analytics

 http://www.cisco.com/c/en/us/support/cloud-systems-management/prime-collaboration-assurance-11-5/model.html

Backup

Prime Collaboration Assurance components should be backed up :

  • AU - After initial installation and provisioning

  • UPG - Before and after software upgrade

  • AMU - After a major change in Cisco HCS customer/Cisco UC Application configuration

  • DA - Daily

For DA or AMU backups, Cisco Prime Collaboration Assurance should be backed up after the backup of the Cisco Hosted Collaboration Mediation Fulfillment component.

Restore

As with any restore from latest backup, there may be changes that were made in the Cisco HCS solution since the backup was taken, and thus are not present in the restored application database.

By following the backup frequency recommendations, the changes should be limited to addition/deletion of Cisco UC Application elements such as users, phones, etc.

Prime Collaboration Assurance supports a discovery process to discover such element additions/deletions from the Cisco UC Applications. After the restore, this discovery process should be run to 'synch' any such discrepancies in Prime Collaboration Assurance, with the Cisco UC Applications.

Endpoint Elements

Endpoint elements include devices such as IP Phones and soft clients. Usually, an FTP server contains the images and software running on these devices, and the configuration is typically pushed from Cisco Unified Communications Manager. The backup strategy in this case is to back up the FTP server holding the software images, and to back up the configuration as part of the Unified Communications Manager backups.

Follow standard procedures to back up and restore endpoints. There are no deviations for HCS.

Infrastructure component Related information

Cisco Unified Communications Manager

http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/tsd-products-support-maintain-and-operate.html

SRST and Voice Gateways Components

Survivable Remote Site Telephony (SRST) and Cisco voice gateways components have the following characteristics:

  • Configuration provisioning could be manual or downloaded from an FTP server.

  • Configuration does not change often.

  • Configuration files take small amounts of disk space.

  • Backup configuration files are stored on FTP servers.

  • Cisco Unified Communications Domain Manager can provision SRST and voice gateways.

Follow standard procedures to back up and restore infrastructure components. There are no deviations for HCS.

Infrastructure component Related information

Cisco 1900 Series, 2900 Series, and 3900 Series ISR G2 (SRST)

http://www.cisco.com/en/US/partner/docs/routers/access/1900/software/configuration/guide/Software_Configuration.html

Cisco 1800 Series, 2800 Series, and 3800 Series ISR G1 (SRST)

http://www.cisco.com/en/US/products/ps5855/products_installation_and_configuration_guides_list.html

Cisco HCS for Contact Center Components

Follow the standard procedures to back up and restore the Cisco HCS for Contact Center components. There are no deviations for Cisco HCS.

Infrastructure component Related information

Cisco Unified Contact Center Enterprise

http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_installation_guides_list.html

Cisco Unified Customer Voice Portal

http://www.cisco.com/c/en/us/support/customer-collaboration/unified-customer-voice-portal/tsd-products-support-maintain-and-operate.html

Cisco Unified Intelligence Center

http://www.cisco.com/en/US/products/ps9755/prod_maintenance_guides_list.html

Cisco Unified Contact Center Domain Manager

http://www.cisco.com/c/en/us/support/customer-collaboration/unified-contact-center-domain-manager/tsd-products-support-series-home.html

Cisco Unified Communications Manager (CUCM)

http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-configuration-examples-list.html

Cisco Finesse (Finesse)

 http://www.cisco.com/c/en/us/products/customer-collaboration/finesse/index.html

Unified Communications Domain Manager (UCDM)

http://www.cisco.com/c/en/us/support/unified-communications/hosted-collaboration-solution-version-10-6-1/model.html