Is a BARS backup of the Publisher sufficient to effect a recovery, or is it preferable to have an OS backup, using the likes of Ghost or something similar?
I'm just trying to clarify some CallManager recovery procedures. If the box fails and at least on HDD of the RAID 1 mirror is OK, this can be moved to a cold standby server. owever, if the database is corrupt, or both HDDs fail then a full system recovery would be required. At the moment, this would require a complete rebuild of the system, followed by a BARS recovery. In this scenario will any existing Subscribers synchronise seamlessly, or will they need to be removed/re-added.
In terms of recovering Subscribers, is a BARS backup necessary?
Hopefully this will answer some of your questions;
Ghost and other third party backup packages are not Tac supported (doesn't mean they don't work but....)
We recently did a complete rebuild and restore from BARS in our lab setup. It really worked well!You will not need to remove/re-add the subs after this.
You can identify the Sub as a backup target but its not a must unless you have different files in the TFTP folder that are not in the Pub database. The Backup Target designation is usually for CRA,CER Servers etc. Have a look;
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.
**For subscriber databases that are configured for backup, BARS backs up only TFTP files and CDR/CMR files.**
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.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...