I have restored CUCM publishers in a test lab before to be more familiar with the process, never had any problems. However, I would like to know more about the impact of a restore in a production environment. Currently, no call control or registration is being done on my production publisher - it's only purpose is to maintain the database. If the publisher goes down, I have nightly backups to restore it, but I'm wondering what the impact would be if I restore. For instance, if I use a previous evening's backup and I've already added phone since, what will happen to those phones after the restore? The subscribers are supposed to maintain a limited database of customer-facing features, I doubt the new phone information will be honored after the restore. Also, it's pretty standard that after a cluster is built out that, under System>Server each host is renamed to its IP address. When a new publisher is created, after it's brought up and before it's restored, it will still have its hostname. I'm assuming that the restore will change it's own hostname under System>Server so that the subscribers will be able to rejoin it and resume replication?
Can anyone recommend a good document on these implications?
3. When a new publisher is created, after it's brought up and before it's restored, it will still have its hostname. I'm assuming that the restore will change it's own hostname under System>Server so that the subscribers will be able to rejoin it and resume replication?
Ans) CM replication is not done based on the System > Server information. It is done based on the host files that are on indidual servers. It does not have any effect replication if you have IP address or hostname in the System > Server . To throw more light on it, I am attaching a PPT to this thread.
Thanks, Vajrender. This PowerPoint looks great, I'll check it out. It sounds like restoring a publisher is really a pretty straightforward affair. I just need to make sure that I configure the same administrative accounts, passwords, and network stack settings, then I can do the restore. I may lost some information if there are lots of changes between the backup cycles.
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...