Cisco IP Telephony Backup and Restore System (BARS ...

Cisco IP Telephony Backup and Restore System (BARS) Administration GuideVersion 4.0 (8)

Corporate HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 526-4100

Text Part Number: 78-16853-01

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Cisco IP Telephony Backup and Restore System (BARS) Administration GuideCopyright © <2005> Cisco Systems, Inc. All rights reserved.

CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, TeleRouter, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0502R)

Cisco IP Telephony Backup and Resto78-16853-01

C O N T E N T S

Preface vii

Overview vii

Audience vii

Organization viii

Conventions viii

Related Documentation ix

Obtaining Documentation ix

Cisco.com ix

Ordering Documentation x

Documentation Feedback x

Obtaining Technical Assistance x

Cisco TAC Website x

Opening a TAC Case xi

TAC Case Priority Definitions xi

Obtaining Additional Publications and Information xi

C H A P T E R 1 Backup and Restore System (BARS) Overview 1-1

System Requirements 1-3

Obtaining BARS 1-3

IP Telephony Applications That Use BARS 1-3

Versions of Applications That BARS Supports 1-4

Obtaining Release Notes for BARS 1-4

How the Backup Portion of the BARS Utility Works 1-4

About the Backup Server 1-5

About Backup Targets and Data Source Servers 1-6

About Backup Data and the Backup File 1-6

About the Scheduler 1-6

About the Backup Storage Destination 1-7

About the Created Backup Log File 1-7

What Data Does the BARS Utility Back Up? 1-7

Cisco CallManager Version 3.3(x) and 4.0(x) 1-7

Call Detail Records Administrative Reporting 1-8

Cisco Customer Response Solutions 1-9

iiire System (BARS) Administration Guide, Version 4.0 (8)

Contents

Cisco Emergency Responder 1-11

Understanding How the Restore Utility Works 1-11

Location of Trace Files 1-11

Setting the Trace Directory Path to Default C: Drive 1-12

C H A P T E R 2 BARS Installation 2-1

Restrictions When Installing or Upgrading BARS 2-1

About Terminal Services 2-1

About Third-Party Applications and Services 2-2

Installation Procedure 2-2

Procedure to Uninstall BARS 2-4

Changing the Purpose of a Server 2-4

Determining Which Version of BARS Runs on Your System 2-4

C H A P T E R 3 Backing Up the Data 3-1

Accessing BARS 3-2

Configuring BARS for the First Time 3-2

Configuring a Data Source Server 3-2

Adding or Modifying a Data Source Server Configuration 3-3

Deleting a Data Source Server 3-4

Configuring the Schedule 3-4

Enabling the Scheduler 3-5

Disabling the Scheduler 3-5

Updating the Schedule 3-6

Restoring the Default Schedule 3-6

Configuring the Backup Storage Location 3-7

Performing a Backup Now 3-8

Canceling the BARS Backup Process 3-9

Stopping the BARS Scheduler 3-9

Accessing the Backup Log File After the Backup Completes 3-9

C H A P T E R 4 Restoring the Data 4-1

Understanding How the Restore Process Works 4-1

Important Information About the Restore Process 4-2

Restoring the Data 4-3

Restoring the Cisco CallManager Cluster 4-4

Restoring Subscriber Servers 4-5

ivCisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0 (8)

78-16853-01

Contents

Guidelines on Restoring a CRS Server or CER Server 4-6

Restoring a CRS Release 4.x Cluster 4-6

Replacing an Existing or a Failed Server 4-8

Tasks to Perform After Restoration 4-9

C H A P T E R 5 Backing Up and Restoring Security for Cisco CallManager 5-1

Backing Up and Restoring Security for Cisco CallManager 4.0 5-1

Backing Up CAPF 1.0(1) Files For Cisco CallManager 4.0 5-2

Restoring Data Only When Security Exists in the Cisco CallManager 4.0 Cluster 5-2

Replacing a Secure 4.0 Publisher Database Server Where CAPF Utility 1.0(1) Was Installed 5-2

Replacing a Secure 4.0 Subscriber Server Where CAPF Utility 1.0 (1) Was Installed 5-3

Replacing a Secure 4.0 Publisher Database Server Where CAPF Was Not Installed 5-4

Replacing a Secure 4.0 Subscriber Server Where CAPF Was Not Installed 5-5

Backing Up and Restoring Security for Cisco CallManager 4.1 5-6

Restoring Data Only 5-6

Replacing an Existing or Failed Secure 4.1 Publisher Database Server 5-6

Replacing an Existing/Failed Secure 4.1 Subscriber Server 5-7

Restoring the 4.1 Cisco CallManager Cluster That Uses Security 5-8

A P P E N D I X A BARS Error Messages A-1

IN D E X

vCisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0 (8)

78-16853-01

Contents

viCisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0 (8)

78-16853-01

Preface

This preface describes the overview, audience, organization, and conventions of this guide and provides information on how to obtain related documentation.

The preface covers these topics:

• Overview, page vii

• Audience, page vii

• Organization, page viii

• Conventions, page viii

• Related Documentation, page ix

• Obtaining Documentation, page ix

• Documentation Feedback, page x

• Obtaining Technical Assistance, page x

• Obtaining Additional Publications and Information, page xi

OverviewThe Cisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0 (8) describes how to use the BARS utility and provides procedures for completing various backup-related tasks and restore-related tasks.

AudienceThis guide provides a reference and procedural guide for users of Cisco CallManager and other Cisco IP telephony applications.

viiCisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0 (8)

78-16853-01

PrefaceOrganization

OrganizationTable 1 provides an overview of this guide:

ConventionsNotes use the following conventions:

Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the publication.

Tips use the following convention:

Tip Means the following are useful tips.

Cautions use the following convention:

Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Table 1 Organization of this Manual

Chapter Description

Chapter 1, “Backup and Restore System (BARS) Overview”

This section provides overview information about some of the main components that make up the BARS utility.

Chapter 2, “BARS Installation” This section contains installation procedures and installation-related information.

Chapter 3, “Backing Up the Data”

This section contains procedures for backing up your data. Procedures include configuring the backup server and the data source servers.

Chapter 4, “Restoring the Data” This section contains procedures for restoring data that was backed up from the configured data source servers.

Chapter 5, “Backing Up and Restoring Security for Cisco CallManager,”

This section contains procedures for backing up and restoring security for Cisco CallManager 4.1 and Cisco CallManager 4.0.

Appendix A, “BARS Error Messages”

This section contains a list of error messages and their workarounds for messages that you may receive during BARS installation or usage.

viiiCisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0 (8)

78-16853-01

PrefaceRelated Documentation

Related DocumentationClick on the URLs in Table 2 to navigate to the appropriate documentation about related Cisco IP Telephony applications and products:

Obtaining DocumentationCisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.comYou can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:


International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Table 2 Quick Reference for URLs

Related Information and Software URL

Backup and restore release note documentation

http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/index.htm

Operating system documentation and Virtual Network Computing (VNC) documentation

http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/index.htm

Cisco CallManager Compatibility Matrix

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm

Cisco CallManager documentation, including Cisco CAR documentation


Cisco CallManager service releases

http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml

Related Cisco CRS and Cisco CER documentation

http://www.cisco.com/univercd/cc/td/doc/product/voice/index.htm

Cisco CRS documentation http://www.cisco.com/univercd/cc/td/doc/product/voice/sw_ap_to/index.htm

Cisco Integrated Communication System (ICS) 7750 documentation

http://www.cisco.com/univercd/cc/td/doc/product/voice/ics/index.htm

ixCisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0 (8)

78-16853-01

http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/index.htm

http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/index.htm

http://www.cisco.com/univercd/home/home.htm



http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml

http://www.cisco.com/univercd/cc/td/doc/product/voice/index.htm

http://www.cisco.com/univercd/cc/td/doc/product/voice/ics/index.htm

http://www.cisco.com/univercd/cc/td/doc/product/voice/sw_ap_to/index.htm



PrefaceDocumentation Feedback

Ordering DocumentationYou can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

• Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

• Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation FeedbackYou can submit e-mail comments about technical documentation to [email protected].

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco SystemsAttn: Customer Document Ordering170 West Tasman DriveSan Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical AssistanceFor all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.

Cisco TAC WebsiteThe Cisco TAC website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year. The Cisco TAC website is located at this URL:

http://www.cisco.com/tac

Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

http://tools.cisco.com/RPF/register/register.do

xCisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0 (8)

78-16853-01


http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

http://www.cisco.com/en/US/partner/ordering/index.shtml

http://www.cisco.com/tac


PrefaceObtaining Additional Publications and Information

Opening a TAC CaseUsing the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:

http://www.cisco.com/tac/caseopen

For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227) EMEA: +32 2 704 55 55 USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

TAC Case Priority DefinitionsTo ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—Your network is “down” or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and InformationInformation about Cisco products, technologies, and network solutions is available from various online and printed sources.

• Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Go to this URL to visit the company store:

http://www.cisco.com/go/marketplace/

• The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://cisco.com/univercd/cc/td/doc/pcat/

xiCisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0 (8)

78-16853-01


http://www.cisco.com/tac/caseopen

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

http://www.cisco.com/go/marketplace/


PrefaceObtaining Additional Publications and Information

• Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

• Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

• iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

• Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

• Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/index.html

xiiCisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0 (8)

78-16853-01


http://www.ciscopress.com

http://www.cisco.com/packet

http://www.cisco.com/go/iqmagazine

http://www.cisco.com/ipj

http://www.cisco.com/en/US/learning/index.html

Cisco IP Telephony Backup and Restore System (BAR78-16853-01

C H A P T E R 1
Backup and Restore System (BARS) Overview
The BARS utility provides a reliable and convenient way to perform regularly scheduled automatic or user-invoked backups of data for a variety of Cisco IP telephony products. BARS performs the following tasks:

• Saves all settings that are configured with the Cisco IP Telephony Applications Backup and Restore System (BARS) configuration. Figure 1-1 shows the main window of the Backup and Restore System configuration.

• Verifies authentication information that you provide during the configuration of the backup.

• Backs up the data that you choose.

• Creates separate logs for the backup and the restore utilities.

• Creates a trace for each task.

• Restores the data that was backed up.

Note Use the supported Cisco Backup and Restore System (BARS) utility if you are running Cisco CallManager 3.3 or later.

If you are using an earlier version of Cisco CallManager, use the Cisco IP Telephony Applications Backup Utility (3.5).

BARS only restores files that were backed up with BARS.

1-1S) Administration Guide, Version 4.0 (8)

Chapter 1 Backup and Restore System (BARS) Overview

Figure 1-1 Backup and Restore System Main Window

This section contains the following topics:

• System Requirements, page 1-3

• Obtaining BARS, page 1-3

• IP Telephony Applications That Use BARS, page 1-3

• Versions of Applications That BARS Supports, page 1-4

• Obtaining Release Notes for BARS, page 1-4

• How the Backup Portion of the BARS Utility Works, page 1-4

• What Data Does the BARS Utility Back Up?, page 1-7

• Understanding How the Restore Utility Works, page 1-11

• Location of Trace Files, page 1-11

• Setting the Trace Directory Path to Default C: Drive, page 1-12

1-2Cisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0 (8)

78-16853-01

Chapter 1 Backup and Restore System (BARS) Overview System Requirements

System RequirementsBe sure the following BARS requirements are met:

• For a standalone installation, you must use Microsoft Windows 2000 (server) and Internet Information Server (IIS) 5.0.

• Ensure that Cisco CallManager 3.3x or above (or one of its associated Cisco IP telephony applications) is installed.

• You must use SQL 2000 or above and MSDE 2000 for a standalone Customer Response Solutions (CRS) server to act as a backup target or for a standalone Cisco Emergency Responder (CER) server to act as a backup server for a Cisco CallManager 3.3 or 4.0 cluster.

For high availability, CRS supports only MS SQL 2000.

Obtaining BARSYou can obtain BARS from the web or from the CD-ROM that may ship with the supported application. To obtain the latest version of BARS, always download it from the web. The version that is available on the CD-ROM may not provide the latest utility. For the location of the latest web version of BARS, see the “Installation Procedure” section on page 2-2.

IP Telephony Applications That Use BARSBARS supports the following applications:

• Cisco CallManager

• Cisco Customer Response Solutions (CRS)

• Cisco CDR Analysis and Reporting (CAR)

• Cisco Emergency Responder (CER)


78-16853-01

Chapter 1 Backup and Restore System (BARS) Overview Versions of Applications That BARS Supports

Versions of Applications That BARS SupportsCisco IP Telephony BARS, version 4.0 (8), supports the following Cisco IP Telephony applications, which serve as minimum requirements:

• Cisco CallManager 3.3 or later

• All Cisco CRS and Cisco CAR releases that are compatible with Cisco CallManager

Be sure to check the Cisco CallManager Compatibility matrix at the following URL for information about which components have been tested with various BARS releases:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm

Note If you receive a warning while using BARS that indicates an incompatibility issue, double-check the matrix. If the matrix indicates that BARS has been tested with the component that the warning specifies, you can ignore the warning.

• Cisco Emergency Responder (CER) 1.2(1) or later

Obtaining Release Notes for BARSThe release notes document contains resolved/open caveats and workarounds that apply to this version of the utility. To obtain the document, click the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/voice/bars/index.htm

If you have an account with Cisco.com, you can use the Bug Toolkit to find caveats for this utility.

To use the Bug Toolkit, click http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl

How the Backup Portion of the BARS Utility WorksThis section describes important information about different components of the backup portion of BARS. This section includes the following topics:

• About the Backup Server, page 1-5

• About Backup Targets and Data Source Servers, page 1-6

• About Backup Data and the Backup File, page 1-6

• About the Scheduler, page 1-6

• About the Backup Storage Destination, page 1-7

• About the Created Backup Log File, page 1-7


78-16853-01

http://www.cisco.com/univercd/cc/td/doc/product/voice/bars/index.htm

http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm

Chapter 1 Backup and Restore System (BARS) Overview How the Backup Portion of the BARS Utility Works

About the Backup ServerAlthough any server in the Cisco CallManager cluster can act as the backup server, Cisco recommends that you designate the publisher database server as the backup server, which is the server that performs the backup. One backup server is required within a Cisco CallManager cluster. You designate a server as a backup server during BARS installation.

Note The Cisco CallManager publisher database contains all the information that you configure with Cisco CallManager Administration, and the database updates each time that you make a change. Cisco strongly recommends that you make a backup of the Cisco CallManager database, configuration, and directory information by using BARS every time that you make changes in Cisco CallManager Administration. Each Cisco CallManager cluster contains only one publisher database.

Other Related Definitions

In addition to backup server, two other related terms are used throughout this manual:

• Backup target—A server (not the backup server) that contains data to get backed up when a BARS backup is invoked. During BARS installation, you designate a server as either a backup server or backup target.

• Data source server—A server that you configure in the BARS user interface that contains data to get backed up. This includes all backup targets and can also include the backup server itself. This term is used in more detail in Chapter 3, “Backing Up the Data.”

Additional Information

For subscriber databases that are configured for backup, BARS backs up only TFTP files and CDR/CMR files.

However, you can configure BARS to back up more than one Cisco IP Telephony Applications Server, such as publishing database servers of other Cisco CallManager clusters, Cisco CER servers, or Cisco Customer Response Solutions (CRS) servers.

To successfully back up the Cisco CallManager database, the backup server and backup targets must exist in the same cluster and have the same version of BARS installed.

For backups to succeed for supported applications, the same version of Cisco CallManager must exist on the backup server and all backup servers.

For more information about the backup server, see Chapter 3, “Backing Up the Data.”

Note BARS will back up all nodes in a CRS 4.0 cluster, though you need to specify only one node in the cluster as data source server. That node will back up all the data in the CRS cluster and put the data on the BARS backup server.


78-16853-01

Chapter 1 Backup and Restore System (BARS) Overview How the Backup Portion of the BARS Utility Works

About Backup Targets and Data Source ServersA backup target contains the data to be backed up for Cisco CallManager, CAR, CRS, or CER. You designate a server as a backup target during BARS installation if this server contains data to be backed up and is not the backup server. Backup targets must be configured as data source servers during BARS configuration.

A Cisco CallManager cluster can contain one or more data source servers.

When you add a data source server by using the BARS configuration window, you can enter the computer name, the IP address or the fully qualified DNS name.

If a data source server is a remote server, you must provide a user name and password that has administrative privileges to the remote server.

Caution Verify that the backup targets and backup server have the same version of BARS installed. Verify that the backup targets and backup server exist in the same cluster.

Caution If the backup server and backup targets are not running and functional, the backup fails. Verify that all corresponding services, such as DC Directory, are running before you perform the backup. If the services are not running, the backup fails.

About Backup Data and the Backup FileDuring the backup, BARS sends the data to a staging directory, and, by default, one file that is called Backupmm-dd-yy#hh-mm.tar (where mm specifies the month, dd specifies the day, yy specifies the year, hh specifies the hour, and mm specifies the minute) archives all data that is backed up from the data source servers listed in the BARS configuration windows.

For more information about the backup file, see Chapter 3, “Backing Up the Data.”

About the SchedulerUsing the Scheduler tab (click Backup -> Scheduler on the BARS main window), you configure the day and time that you want the backup to run.

Cisco sets a default schedule for when the backup is to run. You can change the schedule at any time, restore the default schedule, and enable/disable the configured schedule.

The utility backs up all data at the same time. You cannot configure a separate schedule for each application.

You must enable the schedule, even if you choose to use the default schedule that Cisco automatically configures. See the “Enabling the Scheduler” section on page 3-5.

After you configure the backup settings, you can initiate a backup at any time. See the “Performing a Backup Now” section on page 3-8.


78-16853-01

Chapter 1 Backup and Restore System (BARS) Overview What Data Does the BARS Utility Back Up?

About the Backup Storage DestinationBARS stores all data from all applications in the same backup location.

For the backup destination, Cisco strongly recommends that you specify a tape drive or a network directory, not a local directory.

For more information about backup storage location, see the “Configuring the Backup Storage Location” section on page 3-7.

About the Created Backup Log FileThe backup process creates a backup log file with the following format:

Backupmm-dd-yy.txt

where mm specifies the month, specifies the day and yy specifies the year

BARS puts this file in the following location on the backup server:

C:\Program Files\Common Files\Cisco\Logs\BARS\Backup

On the Configure Scheduler window, you can specify the number of days for which you want to retain log files. Log files exist for each day that you perform a backup.

For more information, see the “Accessing the Backup Log File After the Backup Completes” section on page 3-9.

What Data Does the BARS Utility Back Up?If you configure the backup settings as instructed in this document, Cisco BARS automatically backs up the information that the following sections list for each supported application:

• Cisco CallManager Version 3.3(x) and 4.0(x), page 1-7

• Call Detail Records Administrative Reporting, page 1-8

• Cisco Customer Response Solutions, page 1-9

• Cisco Emergency Responder, page 1-11

Caution The Cisco IP Telephony BARS utility does not back up any operating system files except Host/LMhost, if these files exist on the server.

Cisco CallManager Version 3.3(x) and 4.0(x)

Cisco CallManager Publisher Database

The following list shows the data that is backed up and restored for the Cisco CallManager publisher database:

• LmHosts/Hosts files

• Latest Cisco CallManager publisher database

• DC Directory LDAP directory

• For Cisco CallManager 3.3.x—DirectoryConfiguration.ini from C:\dcdsrvr.


78-16853-01


For Cisco CallManager 4.0(x) or later—UMDirectoryConfiguration.ini.

• Directory schema files—avvid_schemaV*.txt

• Publisher and subscriber configuration information to replication.ini file.

• Cisco CallManager version to version.ini file.

• If the option to backup CDR is chosen, CDR database and CDR/CMR flat files from Local CDR Path

• TFTP files from C:\Program Files\Cisco\TFTPPath (the default path)

• TFTP files on subscriber servers that are configured as backup data source servers (targets)

• TFTP files from alternate file locations

• Cisco Bulk Administration Tool (BAT) files–templates from C:\CiscoWebs\BAT, CSV files from C:\BAT and the BATversion.asp file.

• HKLM\Software\Cisco Systems, Inc. (registry keys)

• Cisco CallManager DSN

• Security files (certificates) from under C:\Program Files\Cisco\Certificates. This applies only to Cisco CallManager 4.x or later.

• LDAPConfig.ini for IPMA configuration.

Cisco CallManager Subscriber Database

The following list shows the data that is backed up and restored for the Cisco CallManager subscriber database:

• LmHosts/Hosts files

• Publisher and subscriber configuration information to replication.ini file.

• Cisco CallManager version to version.ini file.

• If the option to backup CDR is chosen, CDR database and CDR/CMR flat files from Local CDR Path

• TFTP files

• Cisco CallManager DSN

Note The BARS utility does not back up the Microsoft Active Directory or Netscape Directory Server database. This utility does not back up Cisco Multilevel Administration (MLA). Refer to the Cisco MLA documentation for information on how to back up that data.

Call Detail Records Administrative Reporting

The following list shows the data that is backed up and restored for Call Detail Records (CDR) Administrative Reporting (CAR):

• CAR (ART) database

• C:\Ciscowebs\ART\reports\Pregenerated

• HKLM\Software\Cisco Systems Inc.\ART (registry key)


78-16853-01


Cisco Customer Response Solutions

The following list shows the data that is backed up and restored for Cisco Customer Response Solutions (CRS):

All Versions of Cisco CRS (with CRS server)

• LMHosts file and Hosts file

• $winsysdir$\Ccn\Ccndir.ini (backed up for CRS 3.5 and earlier)

• If present, C:\Program Files\Cisco\bin\SaEnvProperties.ini (backed up for CRS 3.5 and earlier)

• Files from C:\Program Files\Wfavvid, including Workflows (.aef), Java files(.java), Jar (.jar), Properties (.properties), and Audio (.wav) (backed up for CRS 3.5 and earlier)

Cisco CRS Release 3.0 and Later (with CRS server)


• $winsysdir$\Ccn\Ccndir.ini

• If present, C:\Program Files\Cisco\bin\SaEnvProperties.ini

• Files from C:\Program Files\Wfavvid, including Workflows (.aef), Java files(.java), Jar (.jar), Properties (.properties), and Audio (.wav)

• Files from C:\Program Files\Wfavvid, including XML (.xml), Class (.class), GSL (.gsl), and Digit (.digit), JobRunner.ini, Sch.ini

• War (.war) files from C:\Program Files\Wfavvid\tomcat_appadmin and below.

• Cfg files (.CFG) from C:\Program Files\Cisco\Common

• Cfg files (.CFG) from C:\Program Files\Cisco\Desktop

• AlarmService.ini from C:\program Files\Cisco\AlarmService

• GSL and .Digit from user and system grammar paths

• Databases DB_CRA, DB_CRA_CCDR, SCHEDULERDB.

• If Spanlink and ICD are installed:

– Database FCRASSVR (if ICD is installed)

– All files/folders under C:\Program Files\Cisco\Desktop_config\Config

– All files/folders under C:\Program Files\Cisco\Desktop_config\Icons

– All files/folders under C:\Program Files\Cisco\Desktop_config\Audio Files.

• Audio files(.wav) from user and system prompt paths

Cisco CRS Release 3.1 and Later (with CRS server)


• $winsysdir$\Ccn\Ccndir.ini

• If present, C:\Program Files\Cisco\bin\SaEnvProperties.ini

• Files from C:\Program Files\Wfavvid, including Workflows (.aef), Java files(.java), Jar (.jar), Properties (.properties), and Audio (.wav)

• Files from C:\Program Files\Wfavvid, including XML (.xml), Class (.class), GSL (.gsl), and Digit (.digit), JobRunner.ini, Sch.ini

• War (.war) files from C:\Program Files\Wfavvid\tomcat_appadmin and below.


78-16853-01


• Cfg files (.CFG) from C:\Program Files\Cisco\Common

• Cfg files (.CFG) from C:\Program Files\Cisco\Desktop

• AlarmService.ini from C:\program Files\Cisco\AlarmService

• GSL and .Digit from user and system grammar paths

• Databases DB_CRA, DB_CRA_CCDR, SCHEDULERDB.

• If Spanlink and ICD are installed:

– Database FCRASSVR (if ICD is installed)

– All files/folders under C:\Program Files\Cisco\Desktop_config\Config

– All files/folders under C:\Program Files\Cisco\Desktop_config\Icons

– All files/folders under C:\Program Files\Cisco\Desktop_config\Audio Files.

• Audio files(.wav) from user and system prompt paths

• System DSN dsn_cra_hrdb

• If ICD is installed, back up the following directory (including all files/folders), if it exists: C:\Program Files\Cisco\Desktop_AudioFiles

Cisco CRS Release 3.1 and Later (RDB server)


• Databases – db_cra, db_cra_ccdr

• SQL jobs belonging to category ‘CRS-RemoteDB Synchronization’

• If ICD is installed, backup the following directory (including all files/folders), if it exists: C:\Program Files\Cisco\Desktop_AudioFiles

Cisco CRS Release 3.1 and Later (VOIP and Record server)

• C:\Program Files\Cisco\Desktop_Audio Files

• CFG files (*.CFG) from C:\program Files\Cisco\Desktop

Cisco CRS Release 4.0 and Later (with CRS server) • Clusters, configurations, and applications profile in LDAP

• Workflow scripts that are already uploaded in LDAP

• Db_cra, db_cra_repository, FCRasSvr database in the cluster

• ICD configuration data (such as open LDAP and flat files)

• ICD recording files

• Windows hosts and lmhosts

• Cisco JTAPI configuration (jtapi.ini)

• User prompts, grammars, and documents under c:\Program Files\wfavvid\Prompts\user andc:\Program Files\wfavvid\Grammars\user andc:\Program Files\wfavvid\Documents\user.


78-16853-01

Chapter 1 Backup and Restore System (BARS) Overview Understanding How the Restore Utility Works

Cisco Emergency Responder

Cisco Emergency Responder Versions 1.2.1 and Above

The following list shows the data that is backed up and restored for Cisco Emergency Responder (CER):

• LmHosts and Hosts files from C:\Winnt\System32\Drivers\Etc

• Latest database CER12XX

• Registry key HKEY_LOCAL_MACHINE, “Software\Cisco Systems, Inc.\AVVID E911

• Replication information to Replication.ini

• Build Number and Minor Version to version.ini

• Folders—CallHistory, CERSysFiles, etc, export, import, nena_msag_records

• Files—JTapi.jar from %CERRoot%\lib and SAenvProperties.ini from %Program Files%\Cisco\bin

• CER NT Users

Understanding How the Restore Utility WorksThe BARS restore process allows you to recover all data that was compressed into the Backupmm-dd-yy.tar file.

BARS puts log files that were created during the restore process into the following folder:

C:\Program Files\Common Files\Cisco\Logs\BARS\Restore

For information on how the restore process works, what log files are created during the restore process, when to run a restore, and the procedures for running a restore, see Chapter 4, “Restoring the Data.”

Note For a CRS 4.0 restore, a separate restore process is described in Chapter 4, “Restoring the Data.” For CRS versions prior to 4.0, the restore process is the same as for other applications.

Location of Trace FilesBARS puts trace files that were created during the backup and restore processes into the following folder:

C:\Program Files\Cisco\Trace\BARS

These files will contain detailed information for each BARS operation. Refer to these files in case of a failed backup or restore process.


78-16853-01

Chapter 1 Backup and Restore System (BARS) Overview Setting the Trace Directory Path to Default C: Drive

Setting the Trace Directory Path to Default C: DriveIf you are replacing a server with four drives, set the trace directory path on the server to the default C: drive before you back up your server. After you install Cisco CallManager on the new server, you can configure the trace drive to collect trace files.

Use the following procedure to set the trace directory path to the default:

Procedure

Step 1 In Cisco CallManager Administration, choose Application > Cisco CallManager Serviceability.

The Cisco CallManager Serviceability window displays.

Step 2 Choose Trace > Configuration.

Step 3 From the Server pane on the left side of the Trace Configuration window, click the server name or IP address of the four-disk drive server.

Step 4 Click the Cisco CallManager service.

The Trace Configuration window for the service and server displays.

Step 5 In the upper-right corner of the window, click the SDL Configuration link.

Step 6 In the Trace Directory Path field under Trace Output Settings, change the drive letter to C:.

Step 7 Click Update.


78-16853-01


C H A P T E R 2
BARS Installation
This section contains the following topics, which include the step-by-step procedure for installing BARS:

• Restrictions When Installing or Upgrading BARS, page 2-1

• About Third-Party Applications and Services, page 2-2

• Installation Procedure, page 2-2

• Procedure to Uninstall BARS, page 2-4

• Determining Which Version of BARS Runs on Your System, page 2-4

Note BARS installation automatically removes any previously installed version of Cisco IP Telephony Applications (CIPTA) Backup Utility 3.5. BARS also migrates backup-server configurations from CIPTA Backup Utility 3.5 installation to BARS backup-server configuration. However, check all configurations after a migration is performed.

Restrictions When Installing or Upgrading BARSThis section contains the following topics that describe restrictions about the usage of various services and applications when you install or upgrade BARS:

• About Terminal Services, page 2-1

• About Third-Party Applications and Services, page 2-2

About Terminal ServicesDo not use Terminal Services to install/upgrade the utility.

To eliminate remote access to the server during the installation/upgrade, disable Terminal Services before the utility installation/upgrade and reboot the server. You must enable Terminal Services after the installation/upgrade.


Chapter 2 BARS Installation Installation Procedure

If you want to use Virtual Network Computing (VNC) to remotely install supported applications, see Table 2 on page -ix to obtain the latest version of the VNC document.

Caution If you have installed VNC but do not plan to use it to perform the installation, disable it to prevent remote access to the server. If you do not disable VNC and a user/administrator accesses the server during the installation, the utility installation will fail.

Do not use Integrated Lights Out (ILO) to install or upgrade the utility. Cisco supports ILO for remote management and remote configuration tasks only.

About Third-Party Applications and ServicesBe sure to stop and disable all non-Cisco CallManager applications and services before performing a BARS installation or upgrade. Failure to do so could interrupt the installation.

The following platform agents may interfere with the installation/upgrade: antivirus services, intrusion detection services, OEM server agents, server management agents, and VOIP monitoring/performance monitoring, or remote access/remote management agents. Disabling platform agents and services ensures that you do not encounter issues that are associated with these services.

If you installed Cisco IDS Sensor Host Agents on the server, locate the corresponding product documentation for procedures on disabling and stopping the services.

Caution Remember to manually enable all services after the installation/upgrade completes.

Installation ProcedureTo install BARS, perform the following steps:

Procedure

Step 1 There are two methods for obtaining BARS 4.0 (8):

a. Download BARS from the following URL:

http://cco/cgi-bin/tablebuild.pl/cmva-3des

b. Insert your BARS-installation CD.

Step 2 Run the BARS executable (.exe file) to launch the BARS installation process.

Step 3 Click Next.

Step 4 Accept the license agreement and click Next.


78-16853-01

http://cco/cgi-bin/tablebuild.pl/cmva-3des

Chapter 2 BARS Installation Installation Procedure

Step 5 You are now asked to specify the purpose of this server:

a. Backup server—This is the default. Use this choice if the server where you are performing the BARS installation will perform the actual backup operation when you back up data.

b. Backup target—Choose this option if you want the server where you are performing the BARS installation to have its data backed up when the BARS backup process runs.

You must choose this option if a backup server already exists.

If you choose this option, a field appears where you enter the name of the server.

Note You must configure all backup targets as data source servers on the BARS administration configuration window. For more information, see the “Configuring a Data Source Server” section on page 3-2.

Step 6 Click Next. The BackAdmin Password window appears.

Step 7 Enter the Backadmin Private Password Phrase for the BackAdmin account.

The installation uses the string that you enter to create a unique, encrypted password. You must enter the same phrase on the backup server and all backup targets.

If the passwords do not match or if BARS cannot verify the passwords, you receive a warning message that asks whether you want to proceed. If you proceed and the passwords do not match, an error message appears in the log file.

Note Administrator and BackAdmin passwords must match on the backup server and the backup target. BackAdmin passwords synchronize during BARS installation because servers have the same private phrase. Synchronizing the administrator passwords ensures a successful configuration, backup, or restoration, especially with the CER database.

Click Next.

Step 8 Follow the instructions on the screen and complete the installation process.

Step 9 When the process completes, reboot the server.

Note The installation log file, BARSInstall mm-dd-yyyy hh.mm.ss.log, is located in the folder: C:\Program Files\Common Files\Cisco\Logs.


78-16853-01

Chapter 2 BARS Installation Procedure to Uninstall BARS

Procedure to Uninstall BARSIf you need to uninstall BARS, perform the following procedure:

Procedure

Step 1 Choose Start > Settings > Control Panel.

Step 2 Double-click Add/Remove Programs.

Step 3 Click Cisco Backup And Restore System.

Step 4 Click Remove.

Step 5 Reboot the server and log in to the server by using the Administrator password.

Changing the Purpose of a ServerYou can change a backup server to a backup target, or vice versa, but you must uninstall and then reinstall BARS on the server; you can then specify the purpose by clicking the Backup Server or Backup Target radio button during the reinstallation of BARS. If you change a backup target to a backup server, you must configure the backup settings on the backup server. If you change the backup server to a backup target, be aware that you must choose and configure another backup server for BARS to run.

Determining Which Version of BARS Runs on Your SystemTo identify the version of BARS on your system, perform the following procedure:

Procedure

Step 1 Invoke the main Backup and Restore System configuration window. To invoke this window, go to Start -> Programs -> Cisco BARS -> BARS Admin.

Step 2 Click the About button on the main configuration screen, and the version of BARS is displayed.

You should upgrade BARS when later versions become available on the web; always verify that you have the latest utility installed on the backup server before you perform an application upgrade. Before the application upgrade, always back up the data to a network directory or tape device. If you store the data on the local directory, the application upgrade may overwrite the data.


78-16853-01


C H A P T E R 3
Backing Up the Data
This section contains information on topics that relate to using the backup portion of the BARS utility:

• Accessing BARS, page 3-2

• Configuring BARS for the First Time, page 3-2

• Configuring a Data Source Server, page 3-2

• Configuring the Schedule, page 3-4

• Configuring the Backup Storage Location, page 3-7

• Performing a Backup Now, page 3-8

• Canceling the BARS Backup Process, page 3-9

• Stopping the BARS Scheduler, page 3-9

• Accessing the Backup Log File After the Backup Completes, page 3-9

Figure 3-1 shows the BARS main window, with the choices of the Backup menu highlighted. The Backup menu items allow you to perform all necessary backup tasks.

Figure 3-1 Backup and Restore System Main Window


Chapter 3 Backing Up the Data Accessing BARS

Accessing BARSIf you have an administrative account on the BARS backup server, you can access the BARS administration web interface using the following URL from anywhere in the network:

http://BackupServerName/BARS/BARSmain.asp

where BackupServerName is the name of the BARS backup server.

To access the BARS administration web interface when you are physically located at the backup server, choose Start -> Programs -> Cisco BARS -> BARS Admin. The Backup and Restore System main window appears.

Configuring BARS for the First TimeTo configure BARS for the first time, you must perform the following tasks that are described in Table 3-1.

Configuring a Data Source ServerUsing the Backup and Restore System, you can add or delete a data source server, which houses the data that you want to back up. For more information on performing these tasks, see the following sections:

• Adding or Modifying a Data Source Server Configuration, page 3-3

• Deleting a Data Source Server, page 3-4

Table 3-1 Configuring the Backup Utility

Step Task Related Information

Step 1 Configure the data source server(s) where the data exists.

Configuring a Data Source Server, page 3-2

Step 2 Choose the applications on the data source server that you want to back up.

Configuring a Data Source Server, page 3-2

Step 3 Configure the backup storage location where the utility will store the data.

Configuring the Backup Storage Location, page 3-7

Step 4 Accept the default schedule in which the backup will run or modify the schedule.

You must enable the schedule before the backup utility will run.

Configuring the Schedule, page 3-4


78-16853-01

Chapter 3 Backing Up the Data Configuring a Data Source Server

Adding or Modifying a Data Source Server ConfigurationAdding or modifying a data source server configuration includes the following two-step process:

• Choosing the server where the data currently exists.

• Choosing the applications on the data source server that you want to back up.

For lists of all data that the BARS utility backs up, see Chapter 1, “Backup and Restore System (BARS) Overview.”

Tip You can configure more than one data source server.

Caution For Customer Response Solutions (CRS) 4.0, you need to specify only one data source server to back up. The server that you specify will back up the data for all nodes in the CRS cluster. If you specify more than one data source server, duplicate data will get backed up and the resultant .tar file will be much larger than necessary.

Procedure

Step 1 From the Backup and Restore System main window, choose Backup > Data Source Server.

Step 2 In the DNS/IP address field, enter the server name or server IP address where the data that you want to back up currently exists.

Note If you are modifying the data that you want to back up for a data source server that is already configured, click on the name of that data source server under the Configured Servers list.

Step 3 If you entered a remote server, enter a username and password with administrator access rights for the remote server and then click Next.

Note BARS attempts to connect to the remote server. If the remote server is not found, the authentication fails, and an error message appears.

Step 4 If no error message appears, choose the applications that you want to back up on the data source server configuration window.

Caution These applications must exist on the data source server you are configuring.

Step 5 Click Finish.

Step 6 The Data Source Server Summary window appears. Perform the following optional tasks:

a. If you want to add another Data Source Server, click Configure More Data Source Servers.

b. If you want to modify the default schedule, click Modify Schedule.

See the “Configuring the Schedule” section on page 3-4 for more information on how to update the schedule.


78-16853-01

Chapter 3 Backing Up the Data Configuring the Schedule

c. To configure the location where the utility will store the data, click Modify Backup Storage Location.

See the “Configuring the Backup Storage Location” section on page 3-7 for more information on how to add or modify the Backup Storage Location.

Related Topics


• Deleting a Data Source Server, page 3-4

Deleting a Data Source ServerThis section describes how to delete a data source server from BARS. If you delete the server, BARS does not back up the data that resides on the server.

Procedure

Step 1 From the Backup and Restore System main window, choose Backup > Data Source Server.

Step 2 The configured Data Source Servers list displays in the pane on the left side of the window. Click the server that you want to delete.

Step 3 Click the Delete button.

Related Topic

• Adding or Modifying a Data Source Server Configuration, page 3-3

Configuring the ScheduleAll data that you choose during the configuration is backed up on the day and time that you designate by using the Configure Scheduler screen.

Cisco sets a default schedule for the backup to run. You can change the schedule at any time, restore the default schedule, and enable/disable the configured schedule.

Tip You must enable the schedule, even if you choose to use the default schedule that Cisco automatically configures.



78-16853-01



• Enabling the Scheduler, page 3-5

• Disabling the Scheduler, page 3-5

• Updating the Schedule, page 3-6

• Restoring the Default Schedule, page 3-6

Enabling the SchedulerYou must enable the Scheduler to ensure that the scheduled backup occurs at the designated time.

Procedure

Step 1 Choose Backup > Scheduler.

Step 2 Click the Enable Scheduler button.

The message “Scheduler Status: Enabled” displays.

Related Topics




Disabling the SchedulerWhen you disable the Scheduler, scheduled backups do not occur. If you disable the Scheduler, Cisco recommends that you perform regular backups by using the information in “Performing a Backup Now” section on page 3-8.

Procedure

Step 1 Choose Backup > Scheduler.

Step 2 Click the Disable Scheduler button.

The message “Scheduler Status: Disabled” displays.

Related Topics

• Stopping the BARS Scheduler, page 3-9—This section describes how to stop and restart the BARS Scheduler from the Windows Start menu.





78-16853-01


Updating the ScheduleThis section describes how to change the defaults that Cisco automatically configures. When you click the Update Schedule button, BARS saves the frequency and log settings that you configured.

Procedure

Step 1 Cisco sets a default schedule for when the backup is to run. If you want to change the default, choose Backup > Scheduler from the main window.


Step 2 For the frequency, choose the time from the drop-down list boxes.

Step 3 Choose one of the following buttons, depending on your schedule preference:

a. Click the radio button On every and check the check boxes for the days when you want the backup to run.

b. Click the radio button After every and choose the number of days from the drop-down list box.

Step 4 If you want BARS to erase the log after a certain number of days, choose the number of days from the Erase logs after drop-down list box.

Step 5 If you want BARS to erase the backup file after a certain number of days, choose the number of days from the Erase logs after drop-down list box.

Step 6 Click Update Schedule.

Related Topics





Restoring the Default ScheduleIf you want to restore the default schedule that Cisco automatically provides, perform the following procedure:

Procedure

Step 1 From the main window, choose Backup > Scheduler.

Step 2 Click the Restore Defaults button.

The default schedule appears in the window.

Step 3 To ensure that backup runs as scheduled, click the Enable Scheduler button.

Step 4 To save the default settings, click the Update Schedule button.


78-16853-01

Chapter 3 Backing Up the Data Configuring the Backup Storage Location

When you restore the default schedule, all default settings including the frequency and the log settings appear in the Configure Scheduler window. Schedule status—enabled or disabled—does not change.

Related Topics




Configuring the Backup Storage LocationThis section describes the procedure for configuring the backup storage location, which is the location in which BARS stores the data.

Perform the following steps to configure the backup storage location.

Procedure

Step 1 Choose Backup > Storage Location.

Cisco allows you to choose only one Backup Storage Location for all data that is backed up. The utility compresses the data to a single file, the Backupmm-dd-yy#hh-mm.tar file, and stores the file in the location that you choose.

For the backup destination, Cisco strongly recommends that you specify a tape drive or a network directory, not a local directory.

Step 2 Click the Network Directory, Local Directory, or Tape Device radio button.

• You may click the Tape device radio button only if you have the Cisco CallManager server with tape drive (for example, the MCS 7835, MCS 7845-1400, IBM xSeries 340, or xSeries 342 server).

If you plan to restore data from one server to another server by using a tape drive, make sure that both servers use the same tape format.

• If you choose to use the Local Directory, make a copy of the Backupmm-dd-yy#hh-mm.tar file before you perform a restoration on the same server.

Note If the data is stored on the local directory and an unrecoverable error occurs on the server, the data is lost. There also exists the potential of consuming all available disk space if the destination location is the local directory on the system, thus causing the system to crash and become unrecoverable.

• If you choose a network directory as the destination for the backup server, the directory must be shared in Windows 2000. To share a directory, log in on that server, right-click the directory folder icon that you want to share, click Sharing..., click Share this folder, and then click OK.

If you choose to back up the data to a network directory, that server must have NETBIOS name resolution in place. (Use the computer name, the IP address or the fully qualified DNS name.)


78-16853-01

Chapter 3 Backing Up the Data Performing a Backup Now

Step 3 Perform the following step, depending on the radio button that you chose in Step 2:

a. Network Directory—In the Path Name field, enter the name of the server where you want BARS to store the data.

You must enter a user name and password with administrative access rights to the server; then, click Verify.

b. Local Directory—In the Path Name field, enter the directory path where you want BARS to store the data.

c. Tape Device—From the Device Name drop-down list box, choose the device where you want to store the data.

Step 4 Click the Update button near the top of the Backup Storage Location window.

Caution Choosing the local drive could consume all available disk space and cause the system to crash and become unrecoverable.

Related Topics

• Configuring a Data Source Server, page 3-2

• Performing a Backup Now, page 3-8

Performing a Backup NowIf you want to perform a backup now, you can either back up all configured data source servers, or you can choose the data source servers that you want to back up immediately.

Procedure

Step 1 Choose Backup > Backup Now. The Backup Data Source Server window appears.

Step 2 Perform one of the following tasks, depending on the outcome that you want:

a. If you want to back up all configured data source servers, click the All configured servers radio button.

b. If you want to choose the data source servers that the utility will back up, click the Selected servers radio button; then, check the server check boxes.

Step 3 Click Start Backup Now. A window gives status of the backup process as it runs.

Related Topics

• Configuring the Backup Storage Location, page 3-7



78-16853-01

Chapter 3 Backing Up the Data Canceling the BARS Backup Process

Canceling the BARS Backup ProcessTo cancel the backup process after it has begun, perform the following procedure:

Procedure

Step 1 Choose Start > Programs > Cisco BARS>

Step 2 You now have two options. Choose Cancel Backup.

Stopping the BARS SchedulerTo stop the BARS Scheduler, perform the following procedure:

Procedure

Step 1 Choose Start > Programs > Administrative Tools > Services.

Step 2 Locate the service named Cisco BARS Scheduler.

Step 3 Right-click Stop to immediately stop the Scheduler.

Step 4 To restart the Scheduler, you can navigate to the Cisco BARS Scheduler service again and right-click Restart.

Accessing the Backup Log File After the Backup CompletesThe backup process creates a backup log file with the following format:

Backupmm-dd-yy.txt

where mm specifies the month, dd specifies the day and specifies the year.

BARS puts this file in the following location on the backup server:

C:\Program Files\Common Files\Cisco\Logs\BARS\Backup

BARS writes all errors that occur during configuration or while the utility is running to the Backupmm-dd-yy.txt file. If you receive the following error messages or other error messages in the log file, the process did not successfully backup up the data:

• Cisco CallManager database could not be found on <Server Name>.

• Could not determine APPS version

• Could not find a CCM/ART/CDR SQL database on <Server Name>


78-16853-01

Chapter 3 Backing Up the Data Accessing the Backup Log File After the Backup Completes

• Error finding SQL database

• Error enumerating registry keys on <Server Name>

• Open file request returned Not Enough Space

Caution During the backup, heed warnings about the amount of temporary space that is available on the staging directory. The staging directory serves as a temporary directory where the backup utility places all files until it builds the single Backupmm-dd-yy#hh-mm.tar file. If you do not have enough temporary space), the backup will fail. Do not run a backup if you receive these warnings.

Always verify that the backup completed successfully.

Related Topics

• Appendix A, “BARS Error Messages”



78-16853-01


C H A P T E R 4
Restoring the Data
This section provides information on the following topics that relate to the restore process:

• Understanding How the Restore Process Works, page 4-1

• Important Information About the Restore Process, page 4-2

• Restoring the Data, page 4-3

• Restoring the Cisco CallManager Cluster, page 4-4

• Restoring Subscriber Servers, page 4-5

• Guidelines on Restoring a CRS Server or CER Server, page 4-6

• Tasks to Perform After Restoration, page 4-9

Understanding How the Restore Process WorksThe BARS restore process allows you to recover all data that was compressed into the Backupmm-dd-yy.tar file. The BARS Restore Wizard prompts you for the following information:

• The backup storage location of the archived Backupmm-dd-yy.tar file.

• The data destination server where you want the restore utility to send the restored data.

• The application that you want restored.

The BARS restore process stops system services, copies the data that you want restored to a staging directory, notifies the data destination server that the data is ready for restoration, and then sends the data to the data destination server.

Caution During the restoration, services stop, which causes call-processing interruptions. Cisco recommends that you use the restore utility during off-peak hours to minimize call-processing interruptions.

Caution All-third party applications, including Cisco-provided and approved applications that are co-resident on the Cisco CallManager server, must be stopped and disabled before you use the Restore process.

Also, be sure to stop and disable all intrusion-detection applications, such as Cisco Security Agent and any virus-protection software, before using the restore process.


Chapter 4 Restoring the Data Important Information About the Restore Process

Tip Before using BARS to perform a restore, reinstall any service releases; otherwise BARS throws a version-mismatch error.

After using BARS to perform a restore, be sure to reinstall Cisco IP telephony applications/products/plugins/locales/add-on devices to versions that are compatible with the restored version of Cisco CallManager. If this is not done, you might lose data during the next upgrade of Cisco CallManager as well as losing all locales and add-on devices.

The restore process creates log files, which are text files that are saved by date, in the following folder:

C:\Program Files\Common Files\Cisco\Logs\BARS\Restore.

If the following error messages or other error messages appear in the log file, the process did not successfully restore the data:

• Failed to drop CCM/ART/CDR database from <Server Name>

• Failed to restore DC Directory

• Failed to stop DC Directory service

• Failed to restart DC Directory service

Related Topics


• Restoring the Data, page 4-1

• Appendix A, “BARS Error Messages”


Important Information About the Restore ProcessBe aware of the following items relating to the restore process:

• While restoring a server, you should not change passwords for SQL and LDAP directory. These passwords will be the same as they were when the backup was performed.

• The restore process cannot selectively restore user-level components, such as mailboxes or device settings.

• The restore process does not reinstall locale settings that were installed with Locale Installer.

• The restore process does not reinstall bootstrap files.

• The restore process does not reinstall custom configurations.


78-16853-01

Chapter 4 Restoring the Data Restoring the Data

Restoring the DataThis section describes how to restore data that the backup process stored in the Backup Storage Location.

Procedure

Step 1 Choose Restore > Restore Wizard.

The Restore Wizard guides you through the restoration.

Step 2 On the “Restore Wizard: Step 1 of 4” screen, complete the information required to identify the backup storage location and the name of the archive, which contains the date and timestamp of the backup. Click Next.

Step 3 From the drop-down list boxes on the “Restore Wizard: Step 2 of 4” screen, first choose the data destination server, then choose the application to restore. Click Next.

Note If you are restoring the data on a Cisco Customer Response Solutions (CRS) (4.x release) cluster, specify one data destination server that belongs to the CRS cluster, and that server will restore the entire cluster.

If the archive you chose on the previous screen was a .tar file that was created from a manual backup as opposed to an archive that was created by using BARS, you are instructed to: “Enter CRS data destination server to restore” in the Data Destination Server field. Enter the name of any active CRS server in the CRS cluster and click Next.

Refer to the “Restoring a CRS Release 4.x Cluster” section on page 4-6 for information about a CRS 4.x restore.

Also, if CRS Node Manager in your targeted server is down or it has no CRS installed yet, you need to perform the steps shown in the “Restoring a CRS Release 4.x Cluster” section on page 4-6.

To restore CRS versions prior to CRS 4.0, follow the restore procedure for other applications described in “Restoring the Data” section on page 4-3.

You can only choose a single application to restore. If you want to restore additional applications, you must repeat the process.

Step 4 In the Authentication Information portion of the “Restore Wizard: Step 3 of 4” screen, enter a user name and a password that has administrative access privileges on the data destination server. Click Next.

Step 5 The restoration process overwrites all data on the data destination server that you chose in Step 3. To complete the restoration process, click the Restore button on the “Restore Wizard: Step 4 of 4” screen.

Step 6 When the restore process finishes, reboot the restored server for the process to take effect.

Step 7 Verify that the restored data is on the server.

Step 8 Repeat this procedure to restore any other servers in the system.


78-16853-01

Chapter 4 Restoring the Data Restoring the Cisco CallManager Cluster

Related Topics




Restoring the Cisco CallManager Cluster

Caution All pre-installation and post-installation tasks that are noted in the Cisco CallManager installation and upgrade documents apply to restoring the cluster. Review the guidelines before you begin any restoration procedures.

You need to reinstall Cisco CallManager on every server in the cluster only if all of the following conditions exist:

• Every machine in the Cisco CallManager cluster crashes

• You do not have a current backup of Cisco CallManager

• The Publisher database server crashes and the backup-up version of Cisco CallManager does not match the version currently running within the cluster. For example, a backup was taken of Cisco CallManager 3.3(2) but the cluster is currently running Cisco CallManager 3.3(3).

If the above conditions exist, follow the procedure below to install and restore the Cisco CallManager cluster.

Caution Do not change any passwords when you are restoring/replacing the server or cluster. The restoration process restores the previously backed up passwords, does not acknowledge the new passwords, and causes the system to malfunction.

If you change the Directory Manager password when you are restoring/replacing the server or cluster, the server cannot access the directory.

Tip Before using BARS to perform a restore, reinstall any service releases; otherwise BARS throws a version-mismatch error.

After using BARS to perform a restore, be sure to reinstall Cisco IP telephony applications/products/plugins/locales/add-on devices to versions that are compatible with the restored version of Cisco CallManager. If this is not done, you might lose data during the next upgrade of Cisco CallManager as well as losing all locales and add-on devices.


78-16853-01

Chapter 4 Restoring the Data Restoring Subscriber Servers

Procedure to Restore the Cisco CallManager Cluster

Use the following procedure to restore the cluster:

Step 1 Reinstall the operating system on the publisher database server.

Choose the Same Server Recovery option during the operating system installation to ensure that the original information you entered during the initial operating system installation displays in the appropriate fields.

Note If you will be reinstalling Cisco CallManager 3.3(2), manually remove the D:\stiRecover.flg file before proceeding with Cisco CallManager reinstallation.

Step 2 Reinstall Cisco CallManager on the publisher database server.

Make sure that the Cisco CallManager version that is installed on this server matches the version of the latest successful publisher database server backup.

Step 3 Restore the data to the publisher database server.

Step 4 Install the operating system and Cisco CallManager on all applicable subscribers in the cluster. Make sure that the Cisco CallManager version that is installed on each subscriber server matches the version of Cisco CallManager that is installed on the publisher database server.

This process re-sycnchronizes the replications between the publisher and subscribers.

Step 5 Restore subscribers on which CDR/TFTP data was backed up; refer to the “Restoring Subscriber Servers” section on page 4-5. Always restore one server at a time.

Step 6 After you restore the Cisco CallManager servers, you can restore other application servers.

Restoring Subscriber ServersCisco no longer requires that you remove the subscriber server from the Cisco CallManager database before recovering the server. When the subscriber server authenticates to the publisher database server and pulls a duplicate of the database from the server, the subscriber server automatically adds itself to the database.

Use the following guidelines to restore the subscriber server(s):

• Perform a new installation of both Cisco CallManager and the Cisco-provided operating system:

– For Cisco CallManager 3.3(3), the minimum required operating system is version 2000.2.3 with and upgrade to 2000.2.4, or a fresh install to operating system version 2000.2.4.

– For Cisco CallManager 4.0(1), the minimum required operating system is version 2000.2.3 with an upgrade to version 2000.2.5. The operating system must also be SR2 or later.

Note The version of Cisco CallManager must match the version that is running on the publisher database server.

• Restore the subscriber if its CDR and TFTP data was backed up.


78-16853-01

Chapter 4 Restoring the Data Guidelines on Restoring a CRS Server or CER Server

Guidelines on Restoring a CRS Server or CER ServerUse the following guidelines to restore these application servers:

• Make sure that you have restored the Cisco CallManager servers/data before you restore these application servers.

• After restoring Cisco CallManager data, restore data that was backed up from the CRS server(s) at the same time as the Cisco CallManager data. This is to avoid discrepancy between the CRS and Cisco CallManager databases.

• Install the operating system on the server, if it is not already installed.

• Co-resident servers (Cisco CallManager and CRS installed on the same server) may already have the operating system installed.

• Install the application as if it were a new installation (for CRS versions prior to 4.0).

• Upgrade the application to the version of the backup that you want to restore, if necessary (for CRS versions prior to 4.0).

• Restore the backup data to the new server.

• To restore the data, Cisco recommends that you have backup data stored on tape device or on a network directory, not on the local directory of the failed server.

• Verify that the data was restored to the new server.

Restoring a CRS Release 4.x ClusterThis section describes how to restore data on your CRS cluster that the backup process stored in the backup storage location.

Note This procedure includes some information about when the CRS Installer has to be invoked as part of the BARS restore process. For complete information about the CRS Installer, refer to the CRS installation guide.

Also refer to the CRS administration guide for information on patching and upgrades.

Procedure

Step 1 This step is necessary only if the CRS Node Manager in the data destination server you chose is down or does not yet have CRS installed. In either of these cases, do the following:

a. Launch the CRS installer on the targeted server.

b. Select or fill in the existing cluster profile and LDAP directory information.

c. Choose Repair Option.

d. Choose Restore Option in the next window.

e. Wait until the next window prompts you to initiate a restore with the BARS Restore Wizard.

Step 2 Choose Restore > Restore Wizard.

The Restore Wizard guides you through the restoration.


78-16853-01

Chapter 4 Restoring the Data Restoring a CRS Release 4.x Cluster

Step 3 On the “Restore Wizard: Step 1 of 4” screen, complete the information required to identify the backup storage location and the name of the archive, which contains the date and timestamp of the backup. Click Next.

Step 4 The “Restore Wizard: Step 2 of 4” screen appears in one of the following two versions:

• If the archive you chose on the previous screen was a .tar file that was created from a manual backup as opposed to an archive that was created by using BARS, you are now instructed to: “Enter CRS data destination server to restore” in the Data Destination Server field. Enter the name of any active CRS server in the CRS cluster and click Next.

The server you choose restores the data for the entire CRS cluster on which it resides. This data destination server does not need to be the same server that you chose as the data source server when this CRS cluster was backed up.

• If the archive you chose on the previous screen was a .tar file that was created by using BARS, you are now instructed to: “Select data destination server and application to restore.”

From the drop-down lists on the “Restore Wizard: Step 2 of 4” screen, first choose any active CRS server in the CRS cluster, then choose the application (CRS) to restore. Click Next.

Note If you are restoring the data on a Cisco Customer Response Solutions (CRS) cluster, the CRS data destination server you choose restores the data for the entire CRS cluster on which it resides. This data destination server does not need to be the same server that you chose as the data source server when this CRS cluster was backed up.

Step 5 In the Authentication Information portion of the “Restore Wizard: Step 3 of 4” screen, enter a user name and a password that has administrative access privileges on the data destination server. Click Next.

Step 6 The restoration process overwrites all data on the cluster where the data destination server resides. To complete the restoration process, click the Restore button on the “Restore Wizard: Step 4 of 4” screen. BARS now begins extracting the archive.

Step 7 The CRS Restore Wizard asks you to confirm that the correct archive is being restored. Click Next to continue.

Step 8 The BARS Restore Wizard next does the following:

a. BARS compares the cluster data in archive with all nodes in the cluster. (Cluster data refers to CRS version, JTAPI version, database type and version, components, languages, and codec types.)

b. If BARS determines that nodes with matched data exist, you will be prompted to choose any or all such nodes to repair if you know that a missing or corrupted binary file exits on a node.

c. BARS also determines if there are nodes with mismatched data. If there are nodes with mismatched data, these nodes are preselected (check-marked in their corresponding boxes on the screen) for repair.

Select any nodes that you want repaired in addition to any preselected nodes with mismatched data, and click Next.


78-16853-01

Chapter 4 Restoring the Data Replacing an Existing or a Failed Server

Step 9 Continue to follow the instructions on the BARS Restore Wizard:

If you have selected nodes to repair or if there are nodes in the cluster with mismatched data, repair each such node. The repair process invokes the CRS Installer, which must be run separately for each node. The BARS Restore Wizard refreshes each time the CRS Installer completes the recovery of a CRS node.

Also, if you ran the Restore option from the CRS Installer as described in Step 1, you must now return to the CRS Installer to complete that operation. To repair a node, run the CRS Installer on that node; the Restore Wizard displays a list of nodes that need to be repaired/recovered.

When you finish running the CRS Installer for all necessary nodes, the BARS Restore Wizard continues.

Step 10 Follow the instructions on the remaining screens of the BARS Restore Wizard.

When the restore process completes, all CRS services are automatically restarted, and a BARS summary page appears. Make sure that the word “Success” appears on the summary page.

Related Topics



Replacing an Existing or a Failed ServerWhen one server is configured to replace an existing or failed server, the new server uses the IP information and computer name of the original server. To replace an existing or failed server, perform the following tasks:

• Install the operating system and the software as if it were a new installation.

• Upgrade the application to the version of the backup that you want to restore.

• Restore the backup data to the new server.

You must have backup data stored on tape or on a network directory, not on the local directory of the existing or failed server, to replace the server.

Tip When you replace a server that has Cisco CallManager installed, choose the Server Replacement/Same Server Recovery option during the operating system installation to ensure that the original information that you entered during the initial operating system installation displays in the appropriate fields.

When you perform a server replacement, you must always manually enter the IP information, computer name, and other configuration data exactly as it was entered on the original server.

Make sure that you locate the configuration information for this server before you begin.

Related Documents

• Installing Operating System Version 2000.2.2 (or later)

• Installing Cisco CallManager Release 3.3 (or later)


78-16853-01

Chapter 4 Restoring the Data Tasks to Perform After Restoration

Tasks to Perform After RestorationWhenever you run a restoration process, perform the following post-restoration tasks:

• For the restoration to take effect, make sure that you reboot the server after you restore the data.

• Verify that no errors occurred during the restoration.

• If necessary, reinstall the Cisco IP telephony applications/products/plugins/service releases to versions that are compatible with the restored version of Cisco CallManager. Refer to the Cisco CallManager Compatibility Matrix for more information. To obtain the most recent version of the matrix document, see Table 2 on page -ix.

• To obtain the locales that were used prior to the restoration, reinstall the Cisco IP Telephony Locale Installer. To obtain locale installer documentation, see Table 2 on page -ix.


78-16853-01

Chapter 4 Restoring the Data Tasks to Perform After Restoration


78-16853-01


C H A P T E R 5
Backing Up and Restoring Security for Cisco CallManager
If you configured security in your Cisco CallManager 4.0 or 4.1 cluster, the following information applies for backups and restorations:

• Use the latest version of the Cisco IP Telephony Backup and Restore System (BARS) utility to back up data.

• BARS 4.0(7) and later backs up the CTL file and security-related configuration that exists in the database.

• Unless stated in this release note, all guidelines in this manual apply.

• All CTL operations depend on the Cisco CTL Provider service in Cisco CallManager Serviceability. Ensure that the service is activated and running when you use the CTL client after restorations complete.

• Any time that you update the CTL file, always run BARS, as described in this manual.


• Backing Up and Restoring Security for Cisco CallManager 4.0, page 5-1

• Backing Up and Restoring Security for Cisco CallManager 4.1, page 5-6

Backing Up and Restoring Security for Cisco CallManager 4.0If you implemented the CTL client and CAPF functionality in Cisco CallManager 4.0, use the following procedures for backups and restorations:

• Backing Up CAPF 1.0(1) Files For Cisco CallManager 4.0, page 5-2

• Restoring Data Only When Security Exists in the Cisco CallManager 4.0 Cluster, page 5-2

• Replacing a Secure 4.0 Publisher Database Server Where CAPF Utility 1.0(1) Was Installed, page 5-2

• Replacing a Secure 4.0 Subscriber Server Where CAPF Utility 1.0 (1) Was Installed, page 5-3

• Replacing a Secure 4.0 Publisher Database Server Where CAPF Was Not Installed, page 5-4

• Replacing a Secure 4.0 Subscriber Server Where CAPF Was Not Installed, page 5-5


Chapter 5 Backing Up and Restoring Security for Cisco CallManager

Backing Up CAPF 1.0(1) Files For Cisco CallManager 4.0

If you use CAPF utility 1.0(1) with Cisco CallManager 4.0, perform the following procedure to back up the CAPF files.

Procedure

Step 1 Use the latest version of BARS to back up the Cisco CallManager data on the publisher database server.

Step 2 Locate the server in the cluster where you installed CAPF utility 1.0(1). Copy capf.phone and all .0 files from the CAPF installation directory to a directory on a remote computer.

The default location for the CAPF installation specifies C:\Program Files\Cisco\capf.

Restoring Data Only When Security Exists in the Cisco CallManager 4.0 Cluster

To restore 4.0 data when security exists in your Cisco CallManager 4.0 cluster, perform the following procedure:

Procedure

Step 1 Restore the data, as described in this manual.

Step 2 Update the CTL file; sign the CTL file with a token that exists in the file and that the phone trusts.

Step 3 In Cisco CallManager Serviceability, restart the Cisco CallManager and Cisco TFTP services.

Step 4 Reset the devices.

Replacing a Secure 4.0 Publisher Database Server Where CAPF Utility 1.0(1) Was Installed

To replace a secure Cisco CallManager 4.0 publisher database server where CAPF Utility 1.0(1) was installed, perform the following procedure:

Procedure

Step 1 Obtain at least one token that exists in the current CTL file and that the phone trusts. You must use the token later in this procedure.

Step 2 On the new or rebuilt server, perform the following operating system tasks:

a. Use the Cisco-provided disks to install the Windows 2000 operating system.

b. Upgrade the operating system to match the version that currently runs in the cluster.

c. Apply operating system service releases to match the version that runs in the cluster.


78-16853-01


Step 3 On the new or rebuilt server, perform the following Cisco CallManager installation tasks:

a. Use Cisco-provided disks to install Cisco CallManager.

b. Upgrade Cisco CallManager to match the version that runs in the cluster.

c. Apply Cisco CallManager service releases and engineering specials to match the version that runs in the cluster.

d. Identify the location where you previously installed CAPF on the publisher database server. Reinstall CAPF utility 1.0(1) to the same location on the new or rebuilt server, as described in Cisco IP Phone Authentication and Encryption for Cisco CallManager 4.0.

e. If the CTL client previously existed on the publisher database server, go to Cisco CallManager Administration and install the CTL client.

f. On the new or rebuilt server, install the version of BARS that created the BARS backup file in the “Backing Up CAPF 1.0(1) Files For Cisco CallManager 4.0” section on page 5-2.

Step 4 Use BARS to restore the data on the new or rebuilt publisher database server; verify that the restored data exists on the publisher database server.

Step 5 Copy the files that were backed up in Step 2 in the “Backing Up CAPF 1.0(1) Files For Cisco CallManager 4.0” section on page 5-2 to the CAPF installation directory on the new or rebuilt publisher database server.

Step 6 Run the CTL client to update the CTL file; make sure that you click the Update CTL file radio button and sign the file with a token that exists in the file and that the phone trusts.

Tip Because the CTL file gets restored, do not choose the Mixed Mode or Non-Secure Mode options after you launch and run the CTL client.

Step 7 In Cisco CallManager Serviceability, restart the Cisco TFTP and Cisco CallManager services.

Step 8 Reset all devices.

Replacing a Secure 4.0 Subscriber Server Where CAPF Utility 1.0 (1) Was Installed

To replace a secure Cisco CallManager 4.0 subscriber server where CAPF utility 1.0(1) was installed, performed the following procedure:

Procedure


Step 2 Verify that you performed the tasks in the “Backing Up CAPF 1.0(1) Files For Cisco CallManager 4.0” section on page 5-2.






78-16853-01






d. Identify the location where you previously installed CAPF on the subscriber server. Reinstall CAPF utility 1.0(1) to the same location on the new or rebuilt server, as described in Cisco IP Phone Authentication and Encryption for Cisco CallManager 4.0.

e. If the CTL client previously existed on the subscriber server, go to Cisco CallManager Administration and install the CTL client.

Step 5 Copy all .0 files from C:\Program Files\Cisco\Certificates on the publisher database server to the C:\Program Files\Cisco\Certificates on the new or rebuilt subscriber server.

Step 6 Copy the files that were backed up in Step 2 in the “Backing Up CAPF 1.0(1) Files For Cisco CallManager 4.0” section on page 5-2 to the CAPF installation directory on the new or rebuilt subscriber server.



Step 8 In Cisco CallManager Serviceability, restart the Cisco CallManager and Cisco TFTP services.


Replacing a Secure 4.0 Publisher Database Server Where CAPF Was Not Installed

To replace a secure Cisco CallManager 4.0 publisher database where CAPF utility 1.0(1) was not installed, perform the following procedure:

Procedure











78-16853-01


Step 4 If the CTL client previously existed on the publisher database server, go to Cisco CallManager Administration and install the CTL client on the new or rebuilt server.

Step 5 On the new or rebuilt server, install the version of BARS that created the BARS backup file in the “Backing Up CAPF 1.0(1) Files For Cisco CallManager 4.0” section on page 5-2.

Step 6 Use BARS to restore the data on the new or rebuilt publisher database server; verify that the restored data exists on the publisher database server.



Step 8 In Cisco CallManager Serviceability, restart the Cisco TFTP and Cisco CallManager services.


Replacing a Secure 4.0 Subscriber Server Where CAPF Was Not Installed

To replace a secure Cisco CallManager 4.0 subscriber server where CAPF utility 1.0(1) was not installed, perform the following procedure:

Procedure









c. If the CTL client previously existed on the subscriber server, go to Cisco CallManager Administration and install the CTL client on the new or rebuilt server.

d. Apply Cisco CallManager service releases and engineering specials to match the version that runs in the cluster.

Step 4 Copy all .0 files from C:\Program Files\Cisco\Certificates on the publisher database server to C:\Program Files\Cisco\Certificates on the new or rebuilt subscriber server.


78-16853-01




Step 6 In Cisco CallManager Serviceability, restart the Cisco CallManager and Cisco TFTP services on the subscriber server.


Backing Up and Restoring Security for Cisco CallManager 4.1If you implemented the CTL client and CAPF functionality in Cisco CallManager 4.1, use the following procedures for backups and restorations:

• Restoring Data Only, page 5-6

• Replacing an Existing or Failed Secure 4.1 Publisher Database Server, page 5-6

• Replacing an Existing/Failed Secure 4.1 Subscriber Server, page 5-7

• Restoring the 4.1 Cisco CallManager Cluster That Uses Security, page 5-8

Restoring Data Only

If you implemented security, you must update the CTL file after you restore the data; sign the CTL file with a token that exists in the file and that the phone trusts.

For data restorations, you do not need to re-create the Cisco CallManager self-signed certificate/keys or the CAPF certificate/keys. If you copied the Cisco Unity certificate to all servers in the cluster prior to the data restoration, you do not need to copy the certificate again.

Replacing an Existing or Failed Secure 4.1 Publisher Database Server

When you replace an existing/failed publisher database server, the Cisco CallManager installation automatically installs the Cisco CallManager self-signed certificate/keys and the CAPF certificate/keys on the server.

If you need to replace or rebuild an existing/failed publisher database server and you configured security prior to the replacement/rebuild, perform the following procedure:

Procedure

Step 1 Obtain at least one token that exists in the current CTL file and that the phone trusts. You must use the token in Step 9.

Step 2 Use the latest version of BARS to back up the Cisco CallManager data on the existing publisher database server.


78-16853-01










Step 5 On the new or rebuilt server, install the version of BARS that created the backup file in Step 2.

Step 6 Use BARS to restore the data on the new or rebuilt publisher database server.

Step 7 Verify that the restored data exists on the publisher database server.

Step 8 If the CTL client exists on a subscriber server or a PC/workstation, go to Step 9. If the CTL client existed on the failed publisher database server, go to Cisco CallManager Administration and install the CTL client.

Tip Because the CTL file gets restored, do not choose the Mixed Mode or Non-secure cluster security option after you launch and run the CTL client.


Step 10 Restart the Cisco TFTP and Cisco CallManager services.


Replacing an Existing/Failed Secure 4.1 Subscriber Server

If you are replacing an existing/failed secure subscriber server and you configured security prior to the replacement/rebuild, perform the following tasks:

Procedure

Step 1 Obtain at least one token that exists in the current CTL file and that the phone trusts. You must use the token in Step 5.

Step 2 On the new or rebuilt subscriber server, perform the following operating system tasks:



c. Apply operating system service releases to match the version that currently runs in the cluster.


78-16853-01


Step 3 On the new or rebuilt subscriber server, perform the following Cisco CallManager installation tasks:




Step 4 If the CTL client exists on the publisher database server or a PC/workstation, go to Step 5. If the CTL client existed on the failed subscriber server, browse to Cisco CallManager Administration and install the CTL client.


Step 5 Run the CTL client to update the CTL file; click the Update CTL File radio button and sign the file with a token that existed in the file and is trusted by the phones.

Step 6 Restart the Cisco CallManager and Cisco TFTP services.


Restoring the 4.1 Cisco CallManager Cluster That Uses Security

Before you restore a secure cluster, ensure that your situation meets all of the following criteria:

• Every server in the cluster crashed.

• You configured security prior to the restoration.

• The phones and the backup file contain a valid CTL file.

If your situation meets the preceding criteria, perform the following tasks:

1. Obtain at least one token that exists in the current CTL file and that the phone trusts.

2. Restore the entire cluster, as described in the BARS documentation. Start with the publisher database server. After you complete the restoration on the publisher database server, restore the subscriber servers one at a time.

3. If the CTL client existed on a failed server in the cluster, reinstall the CTL client on the new or rebuilt server.

4. Run the CTL client. Click the Update CTL file radio button and make sure that you sign the file with a token that exists in the CTL file and that the phone trusts.


5. Restart the Cisco TFTP and Cisco CallManager services.

6. Reset all devices.


78-16853-01


A P P E N D I X A
BARS Error Messages
This section provides tables that list error messages and corrective actions for errors that may appear in the BARS log file or in dialog boxes. These messages can occur during either the backup or restore process for applications that BARS supports:

• BARS Backup Error Messages for Cisco CallManager

• BARS Backup Error Messages for Cisco Emergency Responder

• BARS Backup Error Messages for Cisco CDR Administrative Reporting (CAR)

• BARS Backup Error Messages for Cisco Customer Response Solutions

• BARS Restore Error Messages for Cisco CallManager

• BARS Restore Error Messages for Cisco Emergency Responder

• BARS Restore Error Messages for Cisco CDR Administrative Reporting (CAR)

• BARS Restore Error Messages for Cisco Customer Response Solutions

Table A-1 BARS Backup Error Messages for Cisco CallManager

Error Message Reason Corrective Action

You must enter a phrase from one to 15 characters in length. This phrase may contain English lower-case letters, English upper-case letters, Westernized Arabic Numerals, and the following non-alphanumeric special characters {} . <>:?/|\`~!@$^&*()_-+

You entered invalid characters for the private password phrase.

Enter valid characters.

Could not determine Cisco CallManager version.

The server could not be connected or the registry entry for Cisco CallManager does not exist.

Verify that the backup target is installed with same backadmin password phrase as that of the backup server, and that the registry entry for Cisco CallManager is not empty.

A-1S) Administration Guide, Version 4.0 (8)

Appendix A BARS Error Messages

Cisco CallManager versions prior to 3.3 are not supported.

Earlier versions of Cisco CallManager are not supported. Only 3.3(3) or later is supported.

Only Cisco CallManager 3.3(3) or later will be backed up. Use the latest version of the Cisco IP Telephony Applications Backup Utility to back up earlier versions of Cisco CallManager.

Could not extract publication information. Replication will not be restored.

The server replication is broken. The server is not in cluster.

Recreate the replication for the cluster and do the backup again.

Could not find CCM03XX database on server_name.

Database CCM03XX does not exist, or the Backadmin user is unable to connect to the database.

Backadmin passwords are different on backup server and backup target where server_name is the remote server.

Verify if the database exits on the system.

Only if the data source server to be backed up is remote server, install the backup target with the same backadmin private phrase as that of backup server.

Cannot continue with backup. Not enough space on server_name.

The staging directory lacks sufficient disk space.

Make sure the staging directory has enough disk space when you are planning to backup large files.

Could not find SQL service on this server. Database could not be backed up.

SQL service is stopped in the data source server.

Start the SQL service and then start the backup again.

Could not backup CDR & CMR files successfully.

The files or folder either do not have administrator permissions or may be in use.

Verify that the files and folder have full administrator permissions. Verify that the files are not in use.

Failed to backup Cisco CallManager Registry.

Cisco CallManager registry does not exist, or the Backadmin user is unable to connect to the registry. Backadmin passwords are different on the backup server and backup target.

Verify that the Cisco CallManager registry exists and that the remote targets have the same backadmin private phrase as that of the backup server.

Could not backup DC Directory completely.

The DC Directory backup failed. Verify that DC Directory is installed and that the service DC Directory server currently runs on the backup target. Restart the service and repeat the backup.

Could not back up TFTP files. The files or folder do not have administrator permissions or they may be in use.

Verify that the files and folders have full administrator permissions. Verify that the files are not in use.

Table A-1 BARS Backup Error Messages for Cisco CallManager (continued)


A-2Cisco IP Telephony Backup and Restore System (BARS) Administration Guide, Version 4.0 (8)

78-16853-01


Could not back up files from alternate file location path.

The files or folder do not have administrator permissions or they may be in use.


Could not back up BAT CSV files successfully.



Could not back up BAT Template files successfully.



Could not backup BAT Version file successfully.



Could not backup Cisco CallManager successfully on server_name.

Some of the Cisco CallManager components were not backed up successfully.

Verify that each Cisco CallManager component is backed up successfully.

Table A-2 BARS Backup Error Messages for Cisco Emergency Responder


The publication status of the CER database in SQL does not match the file E911Bootstrap.properties. Please verify configuration. Skipping database backup.

The replication of the cluster is broken. The server is not in the cluster.

Recreate the replication for the cluster and do the backup again.

Could not find the CER SQL database on server_name.

Database CER12XX does not exist, or the Backadmin user is unable to connect to the database.

Backadmin passwords are different on the backup server and backup target where server_name is the remote server.

Verify if the database exits on the system.

Only if the data source server to be backed up is remote server, install the backup target with the same backadmin private phrase as that of the backup server.

SQL Server does not appear to be installed on server_name. Skipping backup of SQL Server.

SQL Service is not running on the server.

Start the SQL service and then perform the backup.

Table A-1 BARS Backup Error Messages for Cisco CallManager (continued)



78-16853-01


Could not found Reg.dmp in the staging directory.

CER registry does not exist, or Backadmin user is unable to connect to the server.


Verify that CER registry exists.

For remote target machines, the target should be installed with the same backadmin private phrase as that of the backup server.

Could not found Version.ini in the staging directory.

Version information does not exist in registry.

Verify the registry contains the version information.

Could not determine CER version.

Version information does not exist in registry.

Verify the registry contains the version information.

Failed to backup CallHistory folder.



Failed to backup CERSysFiles folder.



Failed to backup Etc folder. The files or folder do not have administrator permissions or they may be in use.


Failed to backup Export folder. The files or folder do not have administrator permissions or they may be in use.


Failed to backup Import folder. The files or folder do not have administrator permissions or they may be in use.


Failed to backup Nena_msag_records folder.



File JTapi.jar not found in source folder.

The file does not have administrator permissions or the file may be in use.

Verify that the file has full administrator permissions and that it is not in use.

File SAenvProperties.ini not found in source folder.

The file does not have administrator permissions or the file may be in use.

Verify that the file has full administrator permissions and that it is not in use.

Table A-2 BARS Backup Error Messages for Cisco Emergency Responder (continued)



78-16853-01


CER versions prior to 1.2(1) are not supported.

Prior versions of CER are not supported for backup

CER 1.2(1) or later will not be backed up.

Could not backup Cisco Emergency Responder successfully on server_name

Some of the CER components were not backed up successfully.

Verify that all the CER components are backed up successfully.

Table A-3 BARS Backup Error Messages for Cisco CDR Administrative Reporting (CAR)


Could not find CAR database on server_name. Skipping database backup.

Database Art does not exist, or the Backadmin user is unable to connect to the database.

Backadmin passwords are different on the backup server and the backup target where server_name is the remote server.

Verify that the database exits on the system.


Failed to backup CAR Registry.

CAR registry does not exist, or the Backadmin user is unable to connect to the server.


Verify that CAR registry exists.

For remote target machines, the target should be installed with same backadmin private phrase as that of the backup server.

Failed to backup CAR Reports. The files or folder do not have administrator permissions or they may be in use.


Could not backup CAR successfully on server_name.

Some of the CAR components are not backed up successfully

Verify that all CAR components are backed up successfully.

Table A-2 BARS Backup Error Messages for Cisco Emergency Responder (continued)



78-16853-01


Table A-4 BARS Backup Error Messages for Cisco Customer Response Solutions


Could not backup database DB_Name successfully.

DB_Name can be db_cra, db_cra_ccdr, schedulerdb, fcRasSvr

Database DB_name does not exist, or the Backadmin user is unable to connect to the database.


Verify that the database exits on the system.


SQL Server does not appear to be installed on server_name. Skipping backup of SQL Server.

SQL Service is not running. Start the SQL service and do the backup.

The folder CRS_Root folder does not exist. Files *.aef, *.wav, *.java, *.jar, *.properties cannot be backed up.

Check that the CRS_Root folder exists.

Verify that CRS is properly configured on the system.

The folder CRS_Root does not exist. Files *.xml, *.class, *.gsl, *.digit, *.ini cannot be backed up.

Check that the CRS_Root folder exists.

Verify that CRS is properly configured on the system.

Failed to backup Desktop_Config\Config folder.



Failed to backup Desktop_Config\Icons folder.



Failed to backup Desktop_Config\AudioFiles folder.



Failed to backup Desktop_AudioFiles folder.



Unable to determine the setup of the server.

The setup (CRS or RDB) of the server cannot be determined from the registry.

Verify the registry entries for CRS or RDB.

Could not back up CRS successfully on server_name.

Some of the CRS components were not backed up successfully.

Verify that all CRS components are backed up successfully.


78-16853-01


Table A-5 BARS Restore Error Messages for Cisco CallManager


Could not find Cisco CallManager data in the archive.

The archive was not properly extracted.

Verify that BARS is properly installed.

Not enough space on the specified path to restore database CCM03XX. Skipping database restore.

The database dump is very large and there is not enough space in the system.

Verify you have enough space when you are restoring large files or databases.

Failed to drop database CCM03XX from “Server_Name”.

Database CCM03XX is in use and cannot be dropped, or the Backadmin user is unable to connect to the database.


Verify that the database is not in use.

Only if the data source server to be restored is the remote server, install the backup target with the same backadmin private phrase as that of the backup server.

Database CCM03XX on server “Server_Name” was not restored.

Restore of the database failed, or the Backadmin user is unable to connect to the database.


Verify that you have a good backup of the Cisco CallManager and check the logs for a successful backup of the system.


Could not find Cisco CallManager database dump in archive.

At the time of creating the archive the database dump was not present in the staging directory.

Verify that the backup of the database was successful by checking the backup logs.

Failed to restore registry keys. Check if Reg.dmp exists in the archive.

At the time of creating the archive, the registry dump was not present in the staging directory, or the Backadmin user is unable to connect to the server.


Verify that registry backup was successful by checking the backup logs.


Could not restore DC Directory successfully.

DC directory restore failed. Verify that the backup of DC directory was successful by checking the backup logs.


78-16853-01


Could not restore files to alternate path locations.

Files were not restored to alternate path locations. The files or folders may not have administrator permissionsor they may be in use.

Verify that the backup of the alternate path locations was successful by checkng the backup logs.Verify that these folders have full administrator permissions. Make sure that the files are not in use.

Could not restore DSN Cisco CallManager.

DSN information was not restored by BARS.

Verify that backup of DSN was successful by checking the backup logs.

Table A-6 BARS Restore Error Messages for Cisco Emergency Responder


The Cisco Emergency Responder archive is not extracted properly.


Verify that BARS is installed properly.

CER versions prior to 1.2(1) are not supported.

Restore of CER 1.2(1) or earlier is not allowed.

Restore of CER 1.2(1) or later is allowed.

Could not find Reg.dmp in the staging directory.

At the time of creating the archive, the registry dump was not present in the staging directory.

Verify that the registry backup was successful bychecking the backup logs.

Could not find Replication.ini in the staging directory.

Replication information could not be found from the archive

Verify that backup was successful from by checking the logs.

Failed to drop database CER12XX from “Server_Name” before restoring CER12XX.

Restore of the database failed, or the Backadmin user is unable to connect to the database.


Verify that you have a good backup of the CER.


Could not recreate publication on “Server_Name”.

CER publication is not created by BARS, or the Backadmin user is unable to connect to the database.


Recreate the replication manually or by running CERAdmin utility.


Table A-5 BARS Restore Error Messages for Cisco CallManager (continued)



78-16853-01


Could not recreate subscriptions.

CER subscriptions were not created by BARS, or the Backadmin user is unable to connect to the database. Administrator passwords are different on the backup server and backup target where server_name is the remote server.

Recreate the replications manually or by running the CERAdmin utility.

DatabaseCER12XX on server “Server_Name" was not restored.

BARS restore is unable to restore the database, or the Backadmin user is unable to connect to the database.


Verify that the SQL services are running.


Could not find CER.dmp in the staging directory.

At the time of creating the archive, the database dump was not present in staging directory.

Verify that the backup of the database was successful by checking the backup logs.

Could not find callHistory directory in the staging directory.

The archive does not contain these folders or files.

Verify that callHistory locations backup was successful by checking the backup logs.

Could not find CERSysFiles directory in the staging directory.


Verify that CERSysFiles locations backup was successful by checking the backup logs.

Could not find etc directory in the staging directory.


Verify that etc locations backup was successful by checking the backup logs.

Could not find export directory in the staging directory.


Verify that export locations backup was successful by checking the backup logs.

Could not find import directory in the staging directory.


Verify that import locations backup was successful by checking the backup logs.

Could not find nena_msag_records directory in the staging directory.


Verify that nena_msag_records locations backup was successful by checking the backup logs.

Table A-6 BARS Restore Error Messages for Cisco Emergency Responder (continued)



78-16853-01


Could not find jtapi.jar file in the staging directory.


Verify that jtapi.jar locations backup was successful by checking the backup logs.

Could not find SAenvProperties.ini file in the staging directory.


Verify that SAenvProperties.ini locations backup was successful by checking the backup logs.

Table A-7 BARS Restore Error Messages for Cisco CDR Administrative Reporting (CAR)


Could not find CAR data in the archive.


Verify that BARS was installed properly.

Failed to find ART.dmp in the archive. ART database will not be restored.

At the time of creating the archive, the database dump was not present in staging directory.

Verify that backup of the database was successful by checking the backup logs.

Database art on server “Server_Name" was not restored.

BARS restore is unable to restore the database, or the Backadmin user is unable to connect to the database.


Verify the SQL service are running.


Could not find Registry dump in the staging directory.

At the time of creating the archive, the registry dump was not present in staging directory.

Verify that backup of the registry was successful by checking the backup logs.

Failed to restore CAR reports. The archive does not contain these folders or files. The files or folders where the archive will be restored must have full administrator permissions.

Verify that export locations backup was successful by checking the backup logs.

Table A-6 BARS Restore Error Messages for Cisco Emergency Responder (continued)



78-16853-01


Table A-8 BARS Restore Error Messages for Cisco Customer Response Solutions


The Cisco Response Solutions archive is not extracted properly.


Verify that BARS was properly installed.

Failed to restore the db_name users. Db_name can be db_cra, db_cra_ccdr, schedulerdb, fcRasSvr

The database users were not restored properly, or the Backadmin user is unable to connect to the database.


Verify that the database is properly restored .


Failed to restore db_name on “Server_Name". Db_name can be db_cra, db_cra_ccdr, schedulerdb, fcRasSvr.

The database was not properly restored, or the Backadmin user is unable to connect to the database.


Verify that the database is backed up properly by checking the backup logs.


Could not find db_name dump in staging directory. Db_name can be db_cra, db_cra_ccdr, schedulerdb, fcRasSvr.

The database dump was not archived at the time of backup.

Verify that database dump backup was successfully created by checking the logs.

Failed to restore linked server information.

The linked server information was not backed up properly.

Verify that the databases were restored properly before restoring the linked server information.

Failed to restore the SQL Jobs properly.

SQL jobs were not restored successfully.

Verify that the SQL jobs were successfully created at the time backup by checking the backup log.

Could not find the SQL jobs dump file in the staging directory. Failed to restore SQL jobs.

SQL Jobs information did not exist in the archive.

Verify that SQL jobs backup was successful.

Could not find Wfavvid folder in staging directory.

The archive was unable to extract the folder.

Verify that the backup of this folder was successful.

Could not find Ccndir.ini file in the staging directory.

The archive was unable to extract the file.

Verify that the backup of this file was successful.

Could not find Common folder in staging directory.



Could not find Desktop folder in staging directory.




78-16853-01


Could not restore user and system grammar/prompts files.

The archive was unable to extract the file.

Verify that the backup of this file was successful.

Could not restore DSN dsn_cra_hrbd.

The DSN information could not be restored.

Verify that DSN was successfully backed up from the logs.

Table A-8 BARS Restore Error Messages for Cisco Customer Response Solutions (continued)



78-16853-01

Cisco IP Telephony Backup and Restore System (BARS) 78-16853-01

I N D E X

A

accessing BARS 3-2

accessing the backup file 3-9

adding a data source server 1-6

applications supported 1-3

application versions that BARS supports 1-4

B

BackAdmin account 2-3

Backadmin Private Password Phrase 2-3

backing up now 3-8

backup

data 1-6

destination 3-7

file 1-6, 3-7

file location 3-9

location 1-7

now 3-8

server 1-5, 2-3

storage location 3-4, 3-7, 4-1

tar file 3-7

target 2-3

backup target 1-6

BARS

backup process components 1-4

installation 2-2

restore process 4-1

version 2-4

C

Call Detail Records Administrative Reporting 1-8

CDR/CMR files 1-5

changing the purpose of a server 2-4

Cisco CallManager cluster 1-6

Cisco CallManager Publisher Database 1-7

Cisco CallManager Subscriber Database 1-8

Cisco Customer Response Solutions 1-9

Cisco Emergency Responder 1-11

components of BARS backup process 1-4

Configured Servers list 3-3

Configure Scheduler screen 1-7

configuring BARS for the first time 3-2

CRS cluster restoration 4-7

D

data backed up by BARS 1-7

data source server 1-6

data source server configuration 3-3

data source server deletion 3-4

default schedule 1-6, 3-6

disabling the Scheduler 3-5

DNS/IP address field 3-3

E

enabling the Scheduler 3-5

erasing the log 3-6

error messages from restore process 4-2

IN-1Administration Guide, Version 4.0 (8)

Index

I

installation log file 2-3

installation procedure 2-2

L

Local Directory 3-8

location of log file 1-7

location of trace files 1-11

log file 1-7

log file location 1-7

N

Network Directory 3-8

network directory 1-7

O

obtaining BARS release notes 1-4

P

publisher database 1-5

R

recovering data 4-1

replacement

secure publisher database server 5-6

secure subscriber server 5-7

replacing a failed server 4-8

replacing an existing server 4-8

restoration

secure cluster 5-8

secure data 5-6

secure publisher database server 5-6

IN-2Cisco IP Telephony Backup and Restore System (BARS) Administ

secure subscriber server 5-7

restore

data 4-3, 4-7

process 4-3, 4-7

wizard 4-3, 4-6

restore process 4-1

restore process error messages 4-2

restore utility 1-11

restoring

CiscoCallManager cluster 4-4

restoring CRS clusters 4-7

S

Scheduler 1-6

Scheduler configuration 3-4

Scheduler tab 1-6

security

replacement

publisher database server 5-6

subscriber server 5-7

restoration

data 5-6

replacing cluster 5-8

replacing publisher database server 5-6

replacing subscriber server 5-7

server

replacement

secure publisher database 5-6

secure subscriber 5-7

subscriber databases 1-5

supported applications 1-3

T

Tape Device 3-8

tape drive 1-7

Terminal Services restriction 2-1

ration Guide, Version 4.0 (8)78-16853-01

Index

TFTP files 1-5

trace files location 1-11

U

uninstalling BARS 2-4

updating the schedule 3-6

V

version of BARS 2-4

versions of applications that BARS supports 1-4

Virtual Network Computing (VNC) 2-2

Cisco IP Telephony Backup and 78-16853-01
IN-3
Restore System (BARS) Administration Guide, Version 4.0 (8)

Index

IN-4Cisco IP Telephony Backup and Restore System (BARS) Administ
ration Guide, Version 4.0 (8)
78-16853-01

Date post:	06-May-2023
Category:	Documents
Upload:	khangminh22
View:	0 times
Download:	0 times