<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1256">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style></head>
<body>
<style>
<!--
.EmailQuote
{margin-left:1pt;
padding-left:4pt;
border-left:#800000 2px solid}
-->
</style><body>Kind of like Active Directory has multiple master? Would be a PERS request via their Cisco AM.<br><br>Sent from my HTC ECO 4G.<br><br><div id="htc_header" style="">----- Reply message -----<br>From: "Ahmed Elnagar" <ahmed_elnagar@rayacorp.com><br>Date: Thu, Jul 1, 2010 9:10 am<br>Subject: [cisco-voip] Standby publisher<br>To: "Bill" <bill@hitechconnection.net><br>Cc: "cisco-voip@puck.nether.net" <cisco-voip@puck.nether.net><br><br></div></body>
<font size="2"><div class="PlainText">No the issue is some customers "especially call centers and service providers" almost have daily changes and add on...they cannot withstand the time that a Publisher is down...we need another server in the cluster that replicates that DB real time for CUCM Publisher and it can act as a Publisher in the event that the "primary" Publisher fail.<br>
<br>
Best Regards;<br>
Ahmed Elnagar<br>
Senior Network PS Engineer<br>
Mob: +2019-0016211<br>
CCIE#24697 (Voice)<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: Bill [<a href="mailto:bill@hitechconnection.net">mailto:bill@hitechconnection.net</a>] <br>
Sent: Thursday, July 01, 2010 5:18 PM<br>
To: Ahmed Elnagar; 'Ryan Ratliff'<br>
Cc: cisco-voip@puck.nether.net<br>
Subject: RE: [cisco-voip] Standby publisherpublisher. This changes a bit in6.x where the "user facing features" are written on each node,and replicated out to other nodes in realtime. This is what lets youset and clear CFA with the pub down in later versions.<br>
<br>
Yes it's called a subscriber. :)<br>
<br>
Like the other person that responded said you are adding another level of<br>
redundancy to an already redundant system.<br>
<br>
-----Original Message-----<br>
From: cisco-voip-bounces@puck.nether.net<br>
[<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Ahmed Elnagar<br>
Sent: Thursday, July 01, 2010 9:02 AM<br>
To: Ryan Ratliff<br>
Cc: cisco-voip@puck.nether.net<br>
Subject: Re: [cisco-voip] Standby publisherpublisher. This changes a bit<br>
in6.x where the "user facing features" are written on each node,and<br>
replicated out to other nodes in realtime. This is what lets youset and<br>
clear CFA with the pub down in later versions.<br>
<br>
Ryan;<br>
<br>
Do Cisco has any plans for a "Backup Publisher" I have this discussion with<br>
customers since the 4.x train till now.<br>
<br>
Best Regards;<br>
Ahmed Elnagar<br>
Senior Network PS Engineer<br>
Mob: +2019-0016211<br>
CCIE#24697 (Voice)<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: Ryan Ratliff [<a href="mailto:rratliff@cisco.com">mailto:rratliff@cisco.com</a>] <br>
Sent: Thursday, July 01, 2010 4:28 PM<br>
To: Bill<br>
Cc: Ahmed Elnagar; 'Andrius Kislas'; cisco-voip@puck.nether.net<br>
Subject: Re: [cisco-voip] Standby publisherpublisher. This changes a bit in<br>
6.x where the "user facing features" are written on each node, and<br>
replicated out to other nodes in realtime. This is what lets you set and<br>
clear CFA with the pub down in later versions.<br>
<br>
No you can't. All database changes can only be made to the publisher. This<br>
changes a bit in 6.x where the "user facing features" are written on each<br>
node, and replicated out to other nodes in realtime. This is what lets you<br>
set and clear CFA with the pub down in later versions.<br>
<br>
See<br>
<a href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/6_0_1/cucm-rel_">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/6_0_1/cucm-rel_</a><br>
note-601a.html#wp44437 for specfics.<br>
<br>
Having a standby publisher installed and ready for restore is not a bad idea<br>
but you will be restricted by licensing (P1 TAC SR with the licensing team<br>
should get you rehosted pretty quickly I hope). The only thing to worry<br>
about wrt to IP address is if the pub is specified in System->Server by IP<br>
address this would cause problems after the restore. This could be avoided<br>
simply by changing the IP address to match the failed publisher before<br>
starting the restore.<br>
<br>
-Ryan<br>
<br>
On Jul 1, 2010, at 9:18 AM, Bill wrote:<br>
<br>
Also, at least in the 4.x days, you can still make changes to the subscriber<br>
if the publisher is down. <br>
<br>
-----Original Message-----<br>
From: cisco-voip-bounces@puck.nether.net<br>
[<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Ahmed Elnagar<br>
Sent: Thursday, July 01, 2010 7:43 AM<br>
To: Andrius Kislas<br>
Cc: cisco-voip@puck.nether.net<br>
Subject: Re: [cisco-voip] Standby publisher<br>
<br>
What about the license? The license relates to the MAC address of the<br>
server??<br>
<br>
Best Regards;<br>
Ahmed Elnagar<br>
Senior Network PS Engineer<br>
Mob: +2019-0016211<br>
CCIE#24697 (Voice)<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: cisco-voip-bounces@puck.nether.net<br>
[<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Andrius Kislas<br>
Sent: Thursday, July 01, 2010 1:17 PM<br>
To: Cisco Voip<br>
Subject: [cisco-voip] Standby publisher<br>
<br>
Hi All.<br>
<br>
Correct me if I am wrong, but when the publisher fails the biggest impact we<br>
have is not being able to change configuration. In large environments this<br>
might be serious impact.<br>
<br>
My question is - does anybody use a standby/cold publisher that has the only<br>
task - sit and wait until the primary publisher fails? This standby<br>
published would ba standalone (not a member of existing cluster), would have<br>
different IP address (in the same subnet) and the same name as existing<br>
publisher, would have no licenses uploaded and would be kept in the same<br>
version as primary publisher. During primary publisher failure we would need<br>
to change IP address and perform disaster recovery. This would save us some<br>
time that we would typiacly need to get new server, install new publisher,<br>
upgrade it and finally perform recovery.<br>
<br>
Does it sound fine or are there any caveats for such approach?<br>
<br>
Regards,<br>
Andrius<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
Disclaimer: NOTICE The information contained in this message is confidential<br>
and is intended for the addressee(s) only. If you have received this message<br>
in error or there are any problems please notify the originator immediately.<br>
The unauthorized use, disclosure, copying or alteration of this message is<br>
strictly forbidden. Raya will not be liable for direct, special, indirect or<br>
consequential damages arising from alteration of the contents of this<br>
message by a third party or as a result of any malicious code or virus being<br>
passed on. Views expressed in this communication are not necessarily those<br>
of Raya.If you have received this message in error, please notify the sender<br>
immediately by email, facsimile or telephone and return and/or destroy the<br>
original message. <br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
Disclaimer: NOTICE The information contained in this message is confidential<br>
and is intended for the addressee(s) only. If you have received this message<br>
in error or there are any problems please notify the originator immediately.<br>
The unauthorized use, disclosure, copying or alteration of this message is<br>
strictly forbidden. Raya will not be liable for direct, special, indirect or<br>
consequential damages arising from alteration of the contents of this<br>
message by a third party or as a result of any malicious code or virus being<br>
passed on. Views expressed in this communication are not necessarily those<br>
of Raya.If you have received this message in error, please notify the sender<br>
immediately by email, facsimile or telephone and return and/or destroy the<br>
original message. <br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
Disclaimer: NOTICE The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Raya will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any malicious code or virus being passed on. Views expressed in this communication are not necessarily those of Raya.If you have received this message in error, please notify the sender immediately by email, facsimile or telephone and return and/or destroy the original message. <br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></font>
</body>
</html>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</STRONG></P></BODY></HTML>