<div>I have a 10 Mbps between the sites.</div><div><br class="webkit-block-placeholder"></div><div>The following information is what i am basing my "Remote Failover" comment on. (45Mbps or 40ms round trip delay.) "Local failover" does require both Unity servers to be in the same physical location as you stated.
</div><div><br class="webkit-block-placeholder"></div><div><div>Messaging Failover </div><div>There are two types of failover available with Cisco Unity. Both types require access to the same messaging systems and messaging infrastructure components. There is local failover, in which both the primary and secondary failover servers are co-located in the same physical site as the messaging system they service. There is also remote failover, where the primary and secondary failover servers are located in separate physical sites. In a remote failover configuration, the network connectivity should be no less than 45 Mbps between the sites, and the messaging systems and messaging infrastructure components must be accessible by both Cisco Unity servers. (Note that messaging infrastructure components include domain controllers and/or directory servers, global catalog servers, and name resolution hosts.) Regardless of your network connectivity bandwidth, the response time between the Cisco Unity server and the Exchange servers it is connected to should be no more than a 40-millisecond round trip delay in order for Cisco Unity to service subscriber TUI requests normally.
</div><br><br><div><span class="gmail_quote">On 6/21/07, <b class="gmail_sendername">Jason Aarons (US)</b> <<a href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p><span style="font-size:11.0pt;color:#1F497D">The Failover guide for Unity states same Physical Location, not
45Mbps, however I've seen it work with Metro Ethernet. How much bandwidth do
you have? I would think any latency would make controls sluggish, but may work
for temporary solution.</span></p>
<p><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt">
<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
cisco-voip-bounces@puck.nether</a><a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">.net</a>] <b>On
Behalf Of </b>Kenny Marus<br>
<b>Sent:</b> Thursday, June 21, 2007 3:34 PM<br>
<b>To:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> [cisco-voip] Unity 4.0 Messaging Failover</span></p>
</div><div><span class="e" id="q_1134fd780b8baad6_1">
<p> </p>
<p>Here is the scenario.</p>
<div>
<p><br>
</p>
</div>
<div>
<p>Moving CallManager and Unity from a Data Center to Corporate
Office. We are looking to plan this correctly with the least amount of downtime
possible. The plan is to first move the CM Pub from the Data Center to the Corp
Office. Then build a 2nd Unity box at the Corp office and set it to run in
"Remote Failover" mode with the Primary Unity accross the WAN in the
Data Center. This will be a temporary solution while the Exchage Cluster is
shut down and moved from the Data Center to the Corp office. One thing to note
regarding the "Remote Failover" mode is that we will not have the
Cisco recommended 45 Mbps between sites however all we are trying to accomplish
with this is a short term access to Unity while the Primary Unity and message
store (Exchange Cluster) are being moved. </p>
</div>
<div>
<p><br>
</p>
</div>
<div>
<p>What will be the user expierence for the users when the
Unity and Exchange Cluster are shut down at the Data Center? Will they be able
to access VM through the TUI? </p>
<div>
<p><br>
</p>
</div>
<div>
<div>
<p> </p>
</div>
<div>
<p>Data Center</p>
</div>
<div>
<p><br>
</p>
</div>
<div>
<p>-CallManager Pub/Sub</p>
</div>
<div>
<p>-Unity 4.0</p>
</div>
<div>
<p>-Exchange Cluster</p>
</div>
<div>
<p>-Domain Controller (Global Catalog Server)</p>
</div>
<div>
<p><br>
</p>
</div>
<div>
<p> </p>
</div>
<div>
<p>Corp Office</p>
</div>
<div>
<p><br>
</p>
</div>
<div>
<p>-CallManager Pub (To be moved from Data Center)</p>
</div>
<div>
<p>-Unity 4.0 (Remote Failover)</p>
</div>
</div>
</div>
</span></div></div>
</div>
<div><p></p><hr size="1"><p></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></div></blockquote></div><br> </div>