[cisco-voip] Unity 4.0(4) failover bundle with Exchange 2000

[Jason Aarons (US)]

Funny, I'm about to do my first failover setup this Thursday and Friday,
and putting in production on Saturday pm.

>From reading the guides;
Cisco Unity Faillover Configuration and Administration Guide.pdf
Cisco Unity Reconfiguration and Upgrade.pdf


I assume the below;

1) Just building another server, the 3 Unity service accounts need same
username/password are Primary Server
2) Voicemail Ports Secondary Server are different then Primary Server
3) new Server has different ip address, different hostname
4) Make sure they have recent DiRT backup of Primary Server 
5) Make sure they have recent Veritas backup of Primary Server
6) Need to upgrade Primary from MSDE to SQL 2000 before building new
Secondary.

Do you know if the license key (*.lic) of the Primary Server needs to
change?

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Simon, Bill
Sent: Wednesday, August 09, 2006 10:47 AM
To: Cisco Voip
Subject: [cisco-voip] Unity 4.0(4) failover

Looking for any special install notes/gotchas from people who have setup

Unity 4 in a failover situation.  We're preparing to do it this weekend.

  Engineering group tested it but I just want to see if any of you 
encountered anything that strayed from Cisco's docs or your common-sense

expectations.

Thanks
Bill

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

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