<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I'm pretty sure the requirement to restore every node after you do the pub changed in 6.1. In 5.x this was the case.<div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div>-Ryan</div></span>
</div>
<br><div><div>On Jul 20, 2010, at 2:12 PM, STEVEN CASPER wrote:</div><br class="Apple-interchange-newline"><div style="MARGIN: 4px 4px 1px">
<div>No problem, I guess I am going to have to lab this unless someone else has. </div>
<div> </div>
<div>I am also looking at a Pub replacement at some point and if all subsequent nodes need to be restored I could be looking at a major outage to accomplish this.</div>
<div> </div>
<div>Steve <br><br>>>> Ed Leatherman <<a href="mailto:ealeatherman@gmail.com">ealeatherman@gmail.com</a>> 7/19/2010 4:19 PM >>><br>I had not seen that in the DRS Admin guide Steve, thanks for pointing<br>that out - I'm very curious as I have a publisher server I need to<br>replace soon.<br><br>I was planning based on the "Replacing a Single Server" guide. yikes...<br><br><br><br><br>On Mon, Jul 19, 2010 at 12:11 PM, STEVEN CASPER <<a href="mailto:SCASPER@mtb.com">SCASPER@mtb.com</a>> wrote:<br>> We upgraded to CUCM 7.1.5 and are re-writing our DR plan in the event we<br>> would need to rebuild a publisher (and to make the auditors happy!)<br>><br>> The Disaster Recovery System Administration Guide for Cisco Unified<br>> Communications Manager Release 7.1(2) indicates the need to restore<br>> subsequent nodes after the Publisher restore is complete (page 14 Step 14)<br>><br>> <a href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/drs/7_1_2/drsag712.html#wp41804">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/drs/7_1_2/drsag712.html#wp41804</a><br>><br>><br>> The Replacing a Single Server or Cluster for Cisco Unified Communications<br>> Manager Release 7.1(2) does not include this step. See page 30-31<br>><br>> <a href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/7_1_2/cluster/clstr712.html">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/7_1_2/cluster/clstr712.html</a><br>><br>> Is a subsequent node restore required after a publisher restore?<br>><br>> To make matters more confusing the DRS guide indicates that a restore of the<br>> first node includes a restore of subsequent nodes but the next step tells<br>> you to precede to the restoring subsequent node procedure!<br>><br>><br>> Thanks,<br>> Steve<br>><br>> ************************************<br>> This email may contain privileged and/or confidential information that is<br>> intended solely for the use of the addressee. If you are not the intended<br>> recipient or entity, you are strictly prohibited from disclosing, copying,<br>> distributing or using any of the information contained in the transmission.<br>> If you received this communication in error, please contact the sender<br>> immediately and destroy the material in its entirety, whether electronic or<br>> hard copy. This communication may contain nonpublic personal information<br>> about consumers subject to the restrictions of the Gramm-Leach-Bliley Act<br>> and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or<br>> disclose such information for any purpose other than to provide the services<br>> for which you are receiving the information.<br>> There are risks associated with the use of electronic transmission. The<br>> sender of this information does not control the method of transmittal or<br>> service providers and assumes no duty or obligation for the security,<br>> receipt, or third party interception of this transmission.<br>> ************************************<br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>><br>><br><br><br><br>-- <br>Ed Leatherman<br><br></div><pre>************************************
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.
There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.
************************************
</pre></div>
_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div><br></div></body></html>