[cisco-voip] Unity 4.0 Messaging Failover

[Jason Aarons (US)]

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.

 

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ed Leatherman
Sent: Thursday, June 21, 2007 4:08 PM
To: Kenny Marus
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Unity 4.0 Messaging Failover

 

Kenny,

First of all, i guess you know that you'll only have UMR service while your exchange is down right?

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. 

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. 

I agree with Justin, its a lot of reconfiguring just to move once. Are you going to leave failover in place afterwards?

On 6/21/07, Kenny Marus <kbrain at gmail.com> wrote:

Here is the scenario. 


 

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.  


 

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? 


 

 

Data Center


 

-CallManager Pub/Sub

-Unity 4.0

-Exchange Cluster

-Domain Controller (Global Catalog Server)


 

 

Corp Office


 

-CallManager Pub (To be moved from Data Center)

-Unity 4.0 (Remote Failover)


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




-- 
Ed Leatherman
Senior Voice Engineer
West Virginia University
Telecommunications and Network Operations 



-----------------------------------------
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070621/c5c27fc5/attachment.html