Backup and Restore - Cisco

Backup and Restore

• Backup and Restore Strategies, on page 1• Operational Parameters , on page 2• Backup and Restore Tools, on page 6• Component Backup and Restore , on page 11• Data Center Infrastructure Components , on page 14• Aggregation / Shared Components Elements, on page 15• Cisco HCS Fulfillment and UC Applications, on page 16• Cisco HCS Service Assurance (SA), on page 25• Endpoint Elements, on page 26• SRST and Voice Gateways Components , on page 26• Cisco HCS for Contact Center Components , on page 27

Backup and Restore Strategies

Backup StrategyReview 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 occasionallyand those that are backed up daily.

Step 1 Group the components in your deployment under the following groups. The components in each group have similarbackup 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

Backup and Restore1

• 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 yourinstallation.

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 StrategyYour workflow for restoring components varies by component. For some components, you can restore theconfiguration from backup. Other components require more complex restoration, potentially involvingsynchronization with other components.

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

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 ParametersUse 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 configurationsor user data-provisioning activities. Schedule additional backups before anymajor configuration and softwareupdates. 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 requirementsper backup by the number of backups the service provider maintains per UC cluster, as specified in the servicelevel agreement (SLA).

Backup and restore duration

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

Backup and Restore2

Backup and RestoreRestoration Strategy

IOPS

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

SFTP Server Considerations and RequirementsSFTP servers store backup data collected from HCS components. You can set up SFTP servers in differentways for a Hosted Collaboration Solution.

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

• 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 backupsare completed.

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

SAN ConsiderationsTypically, 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 RAID5, 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 3000and 10,000 IOPS. It would take one SSD (450/3,000 = 1) to support the throughput required in the example.

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

Note

Backup and Restore3

Backup and RestoreSFTP Server Considerations and Requirements

Scheduling Backups of UC ApplicationsWe recommend that you implement regular backups for Cisco Unified Communications (UC) andmanagementapplications to ensure that data is not lost due to outages. For large Cisco HCS systems with many UCapplication 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 isnot overwhelmed during scheduled backups. Institute safeguards so that you do not overrun per-blade CPUor 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. ThePlatform 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 muchless 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.

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

b. For the oversubscribed clusters that use less than 20% HA, back up or upgrade a maximum of oneVM for each blade at a time. This recommendation is based on possible contention for computingresources.

c. 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 CommunicationsManager to the highest application priority, and Cisco Unified Communications Manager IMand Presence Service to the lowest priority. Other Cisco UC applications in the compatibilitymatrix can be given a running order priority as well. There is no specific rule about how theapplication priority can be set.

• Priority 2 - Based on OVA size. This priority allows you to back up the application based ontenant size. Each scheduled list provides the desired results and conforms to the engineeringrules.

4. Develop a matrix that describes the number of provisioned VMs for each size on a per-blade basis, andthe mapping to the associated SAN storage. The following table is an example of this type of matrix.

Table 1: Example Matrix

Chassis 1 RAID Group ID MapChassis 1 Provisioning

Blade 8Blade 7Blade 6Blade 5Blade 4Blade 3Blade 2Blade 1Blade8

Blade7

Blade6

Blade5

Blade4

Blade3

Blade2

Blade1

1,2,101,2,91,2,81,2,71,2,66,2,5RG1,2,1RG1,2,5,33333334

Backup and Restore4

Backup and RestoreScheduling Backups of UC Applications

Chassis 1 RAID Group ID MapChassis 1 Provisioning

7,8,9,177,8,9,167,8,9,157,8,9,147,8,9,137,8,9,117,8,9,117,8,9,1244444444

131313131313132211111111

111111111111112011111111

1,5,134,10,122,5,114,8,106,7,92,3,72,3,74,5,8,333333334

121212121212122111111111

141414141414142311111111

151515151515152411111111

161616161616162511111111

171717171717172611111111

181818181818182711111111

5. Create a backup list. In the following example, the Timeline Sequence column identifies the order thatbackups are scheduled for Blade 1. For example, Time Sequence 1 is completed first, then Time Sequence2 is executed, and so on. Applications with the same priority (for example, Priority 3) can be completedat 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)

RAID Group IDApprox. BackupTime

SizeApplicationTimeline SequenceLine #

RG1,2,5,6500CUCM - PUB(1)1

RG1,2,5,6500CUCM - PUB(2)1

500CUCM - PUB(1)2

500CUCM - PUB(2)2

7,8,9,121000CUCM - PUB(1)3

7,8,9,121000CUCM - PUB(2)3

1000CUCM - PUB(1)4

1000CUCM - PUB(2)4

225000CUCM - PUB(1)5

2010000CUCM - PUB(2)6

4,5,8,3500CUCxn - PUB(1)7

4,5,8,3500CUCxn - PUB(2)7

500CUCxn - PUB(1)8

500CUCxn - PUB(2)8

Backup and Restore5

Backup and RestoreScheduling Backups of UC Applications

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

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

Disaster Recovery System (DRS)The Cisco Disaster Recovery System (DRS) backup feature provides a reliable, efficient ,and simple methodto back up the Unified CommunicationsApplications. Alternatively, you can use the CiscoHosted CollaborationMediation Fulfillment PlatformManager service to back up Unified Communication Applications separately;see the Platform Manager section.

The DRS Administration Guide for Cisco Unified Communications Manager and Cisco UnifiedCommunications 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/restoreactivity 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 betweenMA and LA for authenticationand data encryption among Cisco Unified CommunicationsManager cluster nodes. DRS uses IPSec certificatesfor public/private key encryption.

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

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

Backup and Restore6

Backup and RestoreBackup and Restore Tools





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

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

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

Note

Cisco Hosted Collaboration Platform Manager ServiceThe Platform Manager service included with Cisco Hosted Collaboration Mediation Fulfillment, is a backupmanagement 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 PlatformManager organizes servers into server groups. Server groups allow you to logically join togetherdifferent servers that you want to back up as a group. You can back up all servers in a server group with asingle task that performs sequential backups. Server groups are user-defined and consist of servers frommultiple clusters. All servers in a particular group, however, must have the same product. For example, youcannot mix Cisco Unified Communications Manager and Cisco Unified Communications Manager IM andPresence Service nodes in the same server group. To setup and configure the server groups, follow the stepsand recommendations in section Scheduling Backups of UC Applications, on page 4.

The PlatformManager allows you to set up the system server inventory as well as select, schedule, and monitorbackups of one or more servers across one or more clusters. You can set up the server inventory to beautomatically synchronized from the Shared Data Repository to avoid manual setup. The Platform Manageroffers a wide range of different user-defined server types to accommodate the management of potentiallythousands of servers.

After scheduling backup on your servers and setting up your servers and server groups within PlatformManager, you can manage and monitor backup tasks of your system using the Backup Schedule feature toperform DRS backups on groups of servers. For details, refer to the "Backup Task List" section in CiscoHosted 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

ProcedureStep

Syncing Unified Communications Applications, onpage 8

1. Sync Unified Communications Applications

Sync Platform Manager with SDR, on page 82. Sync server information from SDR with PlatformManager.

Backup and Restore7

Backup and RestoreCisco Hosted Collaboration Platform Manager Service

http://www.globalscape.com/gsftps/cisco.aspx


ProcedureStep

Create a Server Group, on page 83. Create a server group.

Automate Backup and Restore Operations, on page8

4. Automate Backup operations.

PlatformManager - Disaster Recovery SystemBackup, on page 9

5. Manually add DRS configuration to the Server.

Syncing Unified Communications Applications

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

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

Step 1 On the left menu, select Inventory Menu > Server Group and click the Add button.Step 2 Note A server group can only have servers of the same application.

Fill in the required information to create a Server Group for each 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 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.

Select the servers to add to the server group and click the Save button.This will populate the information into Platform Manager.

Automate Backup and Restore Operations

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.

Backup and Restore8

Backup and RestoreSyncing Unified Communications Applications

Platform Manager - Disaster Recovery System Backup

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 RestoreThis section describes the virtual machine backup options for solution-level backup and restore.

Backup Options for Virtual MachinesFor 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 isrunning and there is no quiescing (pausing or temporarily in inactive or disabled state) of the applicationfor the backup.

• An application-consistent backup is a backup taken of an entire virtual machine when the VM is poweredoff, 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 orapplication-consistent.

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

Full Virtual Machine (VM) BackupsA Full VM backup is a backup taken of a full virtual machine. It might be crash-consistent orapplication-consistent.

Full VM backups have two significant advantages:

• The backup process is the same for any virtual machine, thus allowing a consistent backup process acrossany 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 usedto quiesce the application, it can only take a crash-consistent backup.

VM Backups for HCS Management ApplicationsFor Cisco HCSManagement Applications, (Cisco Hosted CollaborationMediation Fulfillment, Prime LicenseManager, Cisco Unified Communications Domain Manager(s), Cisco Prime Collaboration Assurance) the

Backup and Restore9

Backup and RestorePlatform Manager - Disaster Recovery System Backup

applications quiesce when entering a maintenance window, or daily (nightly) provisioning quiet period. Thismakes 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, incase there is an upgrade failure that would require the application to be restored. The application specificrestore process is very time consuming, compared to the restore from a full VM backup. In addition to therecommended application specific backup, CiscoHCS recommends taking a full VMbackup of theManagementapplication before performing the software upgrade. If the service provider experiences a catastrophic failureduring themanagement application(s) upgrademaintenance 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 ApplicationsCisco DRS backs up only the configuration data of the application, not the binaries. The DRS restore processis time-consuming and requires some user intervention because it request application re-install as part of therestore process. The complexity and duration of the restore process using Cisco DRS has created interest inusing 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 fullVM 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. Itis 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 offull VM backup that can be taken of the Cisco Unified Communications Applications without powering themoff.

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

SummaryFull 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 VMbackups are less likely to successfully restore.

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

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

Backup and Restore10

Backup and RestoreVM Backups Before Software Upgrades

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

Full VM backups, with very high likelihood, can be used to restore the Cisco Unified CommunicationsApplications instance, but there is no guarantee. This is why the Cisco DRS backup should always be doneas an alternative way to restore the UC instance. Cisco recommends that any full VM backups should be madewhile the VM is powered off. If taking crash-consistent backups, Cisco recommends you take them during alow-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 ensurethat the method they are using works to restore both the cluster and individual application instances. Ciscodoes not test or validate any specific full VM backup methods. The service provider chooses the method andtests it. It is very likely the service provider will have to manually synchronize the database when restoring acluster.

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

Statistically, using VDR, it is possible to back up a virtual machine reliably. The memory cache not writtento disk does not seem to affect the outcome of a restore. The backups taken by VDR generate no noticeableerrors over the course of time. No errors were observed after a restore of an active server. There is minimumimpact 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, monitorand troubleshoot the solution is the Cisco Prime LAN Management Solution (LMS). LMS provides thefunctionality to perform configuration backup, software image management, compliance, and changemanagement required to maintain and update Cisco network elements.

For a detailed description on howCisco Prime LANManagement Solution can be used for Backup and Restoreof systemwide configuration information see:Configuration Management with Cisco Prime LAN ManagementSolution 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 LANManagement Solution see SupportedDevices 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 RestoreThis section provides information and references for backup and restore for components.

HCS Solution Components and GroupsThe recommended backup and restore strategy is to group Cisco HCS solution components into sets of elementswith 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, asfollows


Backup and RestoreCisco Prime LAN Management Solution (LMS)

http://www.cisco.com/c/en/us/td/docs/net_mgmt/ciscoworks_lan_management_solution/4-1/user/guide/configuration/config.html

http://www.cisco.com/c/en/us/td/docs/net_mgmt/ciscoworks_lan_management_solution/4-1/user/guide/configuration/config.html

http://www.cisco.com/en/US/partner/docs/net_mgmt/ciscoworks_lan_management_solution/4.1/device_support/table/lms41sdt.html

http://www.cisco.com/en/US/partner/docs/net_mgmt/ciscoworks_lan_management_solution/4.1/device_support/table/lms41sdt.html

• Data Center Infrastructure Components

• Aggregation / Shared Components Elements

• Cisco HCS Service Assurance

• Cisco HCS Service Fulfillment


• Endpoints

• SRST and Voice Gateways Components

• Cisco HCS for Contact Center Components

• Third Party Applications

Quick Reference Guide by ComponentThe following information provides a quick reference for backup and restore options for components.

Restore OptionFrequencyBackup ToolComponent

Aggregation

Applications

Administrator consoleAI, AU, UPGAdministratorconsole

Cisco Expressway

DRS or Platform ManagerAI, AMU, UPG DADRS or PlatformManager

Cisco Unified CommunicationsManager

DRS or Platform ManagerAI, AMU, UPG, DADRS or PlatformManager

Cisco Unified CommunicationsManager IM and PresenceService

DRS or Platform ManagerAI, AMU, UPG, DADRS or PlatformManager

Cisco Unity Connection

DRSAI, AMU, UPG, DADRSCisco Emergency Responder

Administrator Console or Full VM BackupAI, AMU, UPG, DAAdministratorConsole or Full VMBackup

CiscoUnifiedAttendant Console- Advanced

Administrator ConsoleAI, AMU, UPG, DAAdministratorconsole

Cisco Paging Server (Singlewire- InformaCast Basic Paging)

Contact Center

DRS + CLI Scripts + SQL Server toolsAI, AMU, UPG, DADRS +CLI Scripts +SQL Server tools

Cisco Unified Contact CenterEnterprise

Shared

Administrator consoleAI, AU, UPGAdministratorconsole

TelePresence


Backup and RestoreQuick Reference Guide by Component

Service Mgmt - Fulfillment

CLIAI, AMU, UPG, DACLIHCM-F

CLIAI, AMU, UPG§, DACLI ¥Cisco Unified CommunicationsDomain Manager

Administrator consoleAI, AMU, UPG, DAAdministratorconsole

Cisco Prime License Manager

Service Mgmt - Assurance

CLIAI, AMU, UPG, DAGUICisco Prime Collaboration forAssurance

HCS Virtualized Multi-Tenant Data Center -Infrastructure

Rebuild config after restoring failed deviceAI, AU, UPGAdministratorConsole or LMS

Nexus 7000 / Nexus 5000

HCS Virtualized Multi-Tenant Data Center -Compute

UCSM or CLIAI, AU, UPGUCSM CLI or GUIUCS Manager

Rebuild the VMAI, AU, UPGDB BackupsvCenter

Key

AI - After Installation

AU - After Configuration/Provisioning Updates

AMU - After Major Updates. For more information about Major Updates, see Cisco HCS Fulfillmentand UC Applications, on page 16.

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 ofCisco Unified Communications Domain Manager, on page 19.

§ - When you upgrade Cisco Unified Communications Domain Manager, you can reduce the amount oftime it takes to upgrade the system by performing backup activities before the upgrade maintenancewindow. You can also reduce the length of time for upgrade and backup by running node upgrades inparallel (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 theupgrade is a primary consideration. Consider the following when using VMware snapshots to back upCisco Unified Communications Domain Manager:

• Cisco cannot guarantee that a VMware snapshot can be used to successfully restore Cisco UnifiedCommunications DomainManager or any Cisco HCSManagement application. If you cannot restorethe 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 forrestore activities, delete the snapshot immediately to preserve LUN space.


Backup and RestoreQuick Reference Guide by Component

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 ComponentsThese include Cisco Network/Data Center Elements such as routers, switches, gateways, fabric interconnectdevices, 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 CiscoNetwork/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.

Related informationInfrastructure component

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

Cisco MDS 9000 Family

http://www.VMware.comVMware vCenter

http://www.cisco.com/en/US/products/ps6120/tsd_products_support_series_home.htmlCisco ASA 5500 Series

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

Cisco Nexus 5000 Series


Cisco Nexus 7000 Series

Use the supported SBC interface.Session Border Controller


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

Note

Cisco UCS Manager

Alternatively, Cisco Prime LANManagement Solution (LMS) can be used for these Cisco HCS DC/networkinfrastructure elements.

Components that do not follow standard procedures include Micro Node.

Micro Node deployments

The Cisco Hosted Collaboration SolutionMicro Node deployment approach is based on UCS C-series serversinstead of UCS blades in a chassis, and the Nexus 5548 switch. C-series servers have their own onboard disk


Backup and RestoreData Center Infrastructure Components



http://www.VMware.com

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







for storage, so the SAN disk (shared storage) approach is not used for Micro Node deployments. For moreinformation on Micro Node deployment architecture, see Cisco Hosted Collaboration Solution Release 12.5Solution 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 sameserver (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 tothe Cisco Hosted Collaboration Solution Release 12.5 End-to-End Planning Guide.

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

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


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

Telepresence Exchange System

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

Cisco Expressway

Telepresence Exchange SystemThe Database Backup window allows the administrator to view scheduled database backups that are configuredon 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 adatabase backup on the database server of the system.

Cisco ExpresswayThe backup and restore page (Maintenance > Back and Restore) is used to create and restore backup filesof your Cisco Expressway data.

The data in the backup includes:

• System configuration settings.

• Clustering configuration

• Security certificates


Backup and RestoreAggregation / Shared Components Elements

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

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





• Administrator account details

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

Log files are not included in the backup files.Note

Cisco HCS Fulfillment and UC ApplicationsCisco 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 UnifiedCommunication Applications. Both Cisco Hosted CollaborationMediation Fulfillment and the Cisco UnifiedCommunications DomainManager(s) have their own persistent provisioning database. But, some provisioningdata is duplicated between the two separate application databases. Similarly, the Cisco UC Applications havetheir own persistent databases. Cisco Unified Communications Domain Manager(s) duplicate Cisco UCApplication provisioning data as well, as it orchestrates the UC Application provisioning for the customersin its domain.

CiscoUnified Communications DomainManager is not considered theMaster of these duplicated data elementsfor the UC Applications that it manages. Cisco Unified Communications Domain Manager can DATASYNCwith 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 groupshould 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




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

Note

Backup FrequencyBackups of all these components should be performed:

• AU - After initial installation and provisioning.

• UPG – Before and After Software Upgrade


Backup and RestoreCisco HCS Fulfillment and UC Applications

• 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 UnifiedCommunications Domain Manager)

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

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

• Dial Plan (affects Cisco Hosted CollaborationMediation Fulfillment, Cisco Unified CommunicationsDomain Manager and Cisco UC Applications)

• DA - Daily

Backup OrderThe recommendation is to schedule backup activities for these applications to be completed in the followingorder:

1. DATASYNC Cisco Unified Communications Domain Manager to


• 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 CollaborationMediation Fulfillment

Manually Sync Cisco Unified CDM and Cisco Hosted Collaboration Mediation Fulfillment

Step 1 Login as hcsadminStep 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.


Backup and RestoreBackup Order

Manually Sync Cisco Unified CDM and Cisco Unified Communications Applications

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

Step 1 Login as hcsadminStep 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:

OptionField

data/DataSyncResource Type

nameResource Attribute

HcsHcmfPullDSResource

CheckedPerform Action

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

Step 1 Login as hcsadminStep 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:

OptionField

data/DataSyncResource Type

nameResource Attribute

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

CheckedPerform Action


Backup and RestoreManually Sync Cisco Unified CDM and Cisco Unified Communications Applications

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 FulfillmentThe 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 ManagerThe 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 upgrademedia/platform-install-1.2.0<version>.iso fast

• Serial upgrade of unified nodes, includes a backup: cluster upgrademedia/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 thismaintenance, for example:

• schedule add backuprotate backup clean localbackups keep 5

• schedule time backuprotate rotate 3 0


Backup and RestorePerform Backup of Cisco Hosted Collaboration Mediation Fulfillment

• 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 thespecified date

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

Cisco Unified CM/ Cisco Unified CM IM and Presence Service RestoreIf a Cisco Unified Communications Manager or Cisco Unified Communications Manager IM and PresenceService and Presence Subscriber node fails and has to be restored, after the Subscriber node is restored, thesurviving 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 UnifiedCommunications Manager supports restoring the Publisher node database from a surviving Subscriber nodedatabase in the cluster.

In these cases, there is no data loss in the Cisco Unified CommunicationsManager cluster after the restorationand database replication is complete.

Cisco Unified CM IM and Presence Service Cluster RestoreIf an entire Cisco Unified Communications Manager Cluster fails and has to be restored, the Cisco UnifiedCommunications Manager database will be restored to the latest backup. This probability of this happeningis very low.

For information on restoring the Cisco Unified CommunicationsManager 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 bechanges that were made in the Cisco HCS solution since the backup was taken, and thus are not present inthe restored application database. By following the backup frequency recommendations, the changes shouldbe 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 dataMaster. Further, the CiscoUnified CommunicationsDomainManager 10.x administratoris likely not aware of the data inconsistencies between the surviving Cisco Unified Communications DomainManager 10.x database and the restored. Cisco Unified Communications Manager Cluster database. If theCisco Unified Communications Domain Manager 10.x administrator attempts MACD operations for theelements that have inconsistencies, Cisco Unified Communications Domain Manager 10.x will detect theinconsistency and the operations will fail.

Cisco Unified Communications Domain Manager 10.x can DATASYNC the data inconsistencies betweenthe surviving Cisco Unified Communications Domain Manager 10.x database and the restored Cisco UnifiedCommunications Manager Cluster database. In this case, since the UC Application database is considered the


Backup and RestoreRestore

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



Master of the data, the Cisco Unified Communications Domain Manager 10.x database will be updated to therestored (latest backup) Cisco Unified Communications Manager database.

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

Cisco Unified CDM or Cisco HCM-F Failure/RestoreCisco Hosted CollaborationMediation Fulfillment and Cisco Unified Communications DomainManager 10.xare tightly integrated, and support synchronization mechanisms between their databases.

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

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

Using Cisco Unified Communications DomainManager, the devices (Cisco UCApplications publisher node)are considered the data Master. The Cisco Unified Communications Domain Manager administrator is likelynot aware of the data inconsistencies between the restored Cisco Unified Communications Domain Manager10.x database and the surviving Cisco Unified Communications Manager Clusters databases. if the CiscoUnified Communications Domain Manager administrator attempts MACD operations for the elements thathave inconsistencies, Cisco Unified Communications Domain Manager will detect the inconsistency and theoperations will fail.

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

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

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

However, the DATASYNC process in Cisco Unified Communications Domain Manager currently addsmissing elements into a Cisco Unified Communications Domain Manager database at the Customer, Reselleror Provider level in the Cisco Unified Communications Domain Manager hierarchy, potentially not the rightSite level hierarchy. The Cisco Unified Communications Domain Manager Site Admin won't be able to seethe data that was synced in at the wrong level. A higher level Cisco Unified Communications DomainManageradministrator would have to be engaged to move the data to the correct site in Cisco Unified CommunicationsDomain Manager


Backup and RestoreCisco Unified CDM or Cisco HCM-F Failure/Restore

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

If the entire Cisco Unified Communication DomainManager system or Cisco Hosted CollaborationMediationFulfillment fails, restore using the latest backup.

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

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

Cisco Hosted Collaboration Mediations FulfillmentUC 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, primarilyfor:

Cisco Hosted Collaboration Mediations FulfillmentUC Applications

5. Perform manual DATASYNC, primarily for:

Cisco Hosted Collaboration Mediations FulfillmentCisco UC Applications

Disable Sync Mechanisms

Disable Sync Between Cisco Unified Communication Domain Manager and Cisco Hosted Collaboration Mediation Fulfillment

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

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

Step 1 Open an SFTP client and connect to the Cisco Hosted CollaborationMediation Fulfillment platform by using the adminsftpuser and the administrator password that you set up during installation.


Backup and RestoreCisco Unified CDM / Cisco HCM-F Restore Activities/Order

Step 2 Copy the backup file to the Cisco Hosted Collaboration Mediation Fulfillment platform, by navigating to the backupdirectory. 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 theCisco Hosted Collaboration Mediation Fulfillment platform.

Step 4 Enter utils disaster_recovery restore local restore_server tarfilename device_name

DescriptionOption

the hostname of the server to be restoredrestore_server

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

tarfilename

the name of the backup devicedevice_name

Step 5 The backup data gets restored on the server that you chose. To view the status of the restore, enter utilsdisaster_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

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

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.

Service Fulfillment ComponentsFollow standard procedures to back up and restore fulfillment components.


Backup and RestoreRestore Cisco Unified CDM


http://www.cisco.com/en/US/partner/products/ps11363/prod_maintenance_guides_list.htmlCisco Unified CommunicationsDomain Manager 10.x or 11.5x

http://www.cisco.com/en/US/partner/products/ps11363/prod_maintenance_guides_list.htmlCisco Hosted CollaborationMediation Fulfillment (includesPlatform Manager)

Cisco Unified Communications Domain Manager SpecificsCisco Unified Communications Domain Manager backup and restore procedures are covered in the productdocumentation. The backup covers the contents of the database as well as themes. The configuration is notbacked up.

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

Cisco Unified Communication Applications SpecificsThis includes the following Cisco HCS Applications:




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

Cisco Unified Communication ApplicationsFor these applications the current recommendation is to use Cisco Voice Operating System (VOS) basedDisaster Recovery System (DRS) tools or Platform Manager (which uses DRS).

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

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


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



Backup and RestoreCisco Unified Communications Domain Manager Specifics






http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.htmlCisco Unity Connection

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 CommunicationsManager IM and PresenceService

http://www.cisco.com/en/US/products/ps7282/prod_maintenance_guides_list.htmlCisco Unified AttendantConsole - Advanced

Cisco HCS Service Assurance (SA)Cisco Prime Collaboration Assurance (PCA) provides the Service Assurance functionality in Cisco HCS.Cisco Hosted CollaborationMediation Fulfillment configures the elements (primarily Cisco UCApplications,users and devices, etc.) to be monitored into Cisco Prime Collaboration Assurance during initial configurationand setup of Cisco Prime Collaboration Assurance, as well as when new elements are added into the CiscoHCS 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 froma backup.

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

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


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

Cisco Prime CollaborationAssurance

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

Cisco Prime CollaborationAnalytics

BackupPrime 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 theCisco Hosted Collaboration Mediation Fulfillment component.


Backup and RestoreCisco HCS Service Assurance (SA)

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












RestoreAs with any restore from latest backup, there may be changes that were made in the Cisco HCS solution sincethe 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 ofCisco UC Application elements such as users, phones, etc.

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

Endpoint ElementsEndpoint elements include devices such as IP Phones and soft clients. Usually, an FTP server contains theimages and software running on these devices, and the configuration is typically pushed from Cisco UnifiedCommunications Manager. The backup strategy in this case is to back up the FTP server holding the softwareimages, 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.




SRST and Voice Gateways ComponentsSurvivable Remote Site Telephony (SRST) and Cisco voice gateways components have the followingcharacteristics:

• 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 forHCS.


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

Cisco 1900 Series, 2900 Series,and 3900 Series ISRG2 (SRST)


Cisco 1800 Series, 2800 Series,and 3800 Series ISRG1 (SRST)


Backup and RestoreRestore







Cisco HCS for Contact Center ComponentsFollow the standard procedures to back up and restore the Cisco HCS for Contact Center components. Thereare no deviations for Cisco HCS.


http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_installation_guides_list.htmlCisco Unified Contact CenterEnterprise

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

Cisco Unified Customer VoicePortal

http://www.cisco.com/en/US/products/ps9755/prod_maintenance_guides_list.htmlCisco Unified IntelligenceCenter

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

Cisco Unified Contact CenterDomain Manager

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

Cisco Unified CommunicationsManager (CUCM)

http://www.cisco.com/c/en/us/products/customer-collaboration/finesse/index.htmlCisco Finesse (Finesse)

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

Unified CommunicationsDomain Manager (UCDM)


Backup and RestoreCisco HCS for Contact Center Components

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








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




Backup and RestoreCisco HCS for Contact Center Components

Documents

Backup and Restore - Cisco