<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.gmailquote
{mso-style-name:gmail_quote;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Good point, 4.2(1) uses the LANMAN browser service to find the
partner Unity box. Failover partnership doesn’t even look at LMHOSTS. Sometimes
Microsoft browsing works, sometimes it doesn’t. Developed in early 90s when
Thinet prevailed it wasn’t very robust. I opened a tac case and got nowhere,
the SE wasn’t very knowledgeable despite my sending him sniffer traces, etc.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Ed Leatherman<br>
<b>Sent:</b> Thursday, June 21, 2007 4:08 PM<br>
<b>To:</b> Kenny Marus<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] Unity 4.0 Messaging Failover<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Kenny,<br>
<br>
First of all, i guess you know that you'll only have UMR service while your
exchange is down right?<br>
<br>
In my limited experience with Unity failover... you may run into some problems
getting it setup and running over the WAN. I tried to set it up with the failover
server across our network core on the other side of town at our backup site.
Gig all the way through, but on a different IP Subnet/broadcast domain. We
could not get the failover wizard to even see the other server. <br>
<br>
TAC's suggestion was to pull the server out of the rack and bring it to the
main office, put it on the same network and Unity, set up failover, and move it
back across town again. Might be worth thinking about in your case. We still
haven't done it yet ourselves. <br>
<br>
I agree with Justin, its a lot of reconfiguring just to move once. Are you
going to leave failover in place afterwards?<o:p></o:p></p>
<div>
<p class=MsoNormal><span class=gmailquote>On 6/21/07, <b>Kenny Marus</b> <<a
href="mailto:kbrain@gmail.com">kbrain@gmail.com</a>> wrote:</span><o:p></o:p></p>
<p class=MsoNormal>Here is the scenario. <o:p></o:p></p>
<div>
<p class=MsoNormal><br>
<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>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. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><br>
<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>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? <o:p></o:p></p>
<div>
<p class=MsoNormal><br>
<o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Data Center<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><br>
<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>-CallManager Pub/Sub<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>-Unity 4.0<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>-Exchange Cluster<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>-Domain Controller (Global Catalog Server)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><br>
<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Corp Office<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><br>
<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>-CallManager Pub (To be moved from Data Center)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>-Unity 4.0 (Remote Failover)<o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br clear=all>
<br>
-- <br>
Ed Leatherman<br>
Senior Voice Engineer<br>
West Virginia University<br>
Telecommunications and Network Operations <o:p></o:p></p>
</div>
</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>