[cisco-voip] CallManager DR scenario

Stu Packett SPackett at fenwick.com
Mon Jun 26 17:04:57 EDT 2006


I'm thinking about moving my Pub to our DR site as well.  I'm just
concerned about network traffic between the sites.  I know there's a
rule to not have phones registered to the Pub because it does many
roles.  Does anyone know what roles that might be?  I have a DS3 between
my HQ and DR site and I think I have enough bandwidth to handle the
traffic.

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Carter, Bill
Sent: Monday, June 26, 2006 10:56 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] CallManager DR scenario

 
I am implementing a CallManager cluster with servers located at both HQ
and a DR site.  The Publisher will be located at HQ, with 2 subscribers
at HQ and the 2 subscribers at the DR site.  

If HQ is offline for an extended period of time (building blows up), the
publisher will not be available.  In this situation, CallManager
configuration changes will probably have to be made, but the publisher
will be down.  

* Can changes be made to the system without an active publisher?

* I know subscriber won't replicated database to other subscribers.
What happens when the publisher comes back online?  Are changes
replicated from Subscriber to Publisher?

* With 2 subscribers located at the DR site, will I have to make
configuration on both subscriber CallManagers (see previous question)? 

* In a period of extended outage, I assume it would be best to restore
the Publisher to one of the Subscribers at DR, correct?

It seems like a Catch-22 for CallManager DR design.  Do you locate the
Publisher at HQ or DR?  I guess it depends on which site will go
down?!?!?  HaHaHa!!


This email may contain proprietary and confidential information for the
sole use of the intended recipient. 
Any review, retransmission, dissemination, or other use of this
information by persons or entities other than 
the intended recipient is prohibited. If you are not the intended
recipient, please contact the sender and 
delete all copies. To the extent that opinions are expressed in this
message, they are not necessarily the 
opinions of Sentinel Technologies or any of its affiliates, employees,
directors, officers or shareholders.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip



More information about the cisco-voip mailing list