[cisco-voip] Unity 4.0 Messaging Failover

[Kenny Marus]

I have a 10 Mbps between the sites.

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.

Messaging Failover
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.


On 6/21/07, Jason Aarons (US) <jason.aarons at us.didata.com> wrote:
>
>  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.
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether <cisco-voip-bounces at puck.nether.net>.net<cisco-voip-bounces at puck.nether.net>]
> *On Behalf Of *Kenny Marus
> *Sent:* Thursday, June 21, 2007 3:34 PM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] Unity 4.0 Messaging Failover
>
>
>
> 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)
>
> ------------------------------
>
> * 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/e50481b6/attachment.html