I will turn an Unity Standalone server into a Primary Failover Server and I would like to get some guidelines on how is the best way with less impact to my customer.
Do I have to reinstall the server from scratch?
Could I have only the DC, exchange and Unity removed so I don't have to reinstall W2K and SQL?
My off box Exchange is running and has a lot of subscribers and so is my Unity Exchange, What will happen to the Unity subcribers after the migration?
Are subscribers in Unity Exchange compatible to those in the off box Exchange?
This should get you through it.
Hope this helps!
Let me add my 0.02 cents on top of PATRICK's good post.
It depends the Unity is Voice Messaging only or Unified Messaging. I assume you are running 4.0 Verison.
First, if it is Unified Messaging:
1. Since exchange box is separated already, it is easy just add a failover (secondary).
Here is the link:
Second, if it is Voice Messaging (unity and exchange, AD are in one box) only, remember for failover voice messaging only, the message store(exchange) have to seperated.
1. You need to seperate Unity from exchange first which mean uninstall Unity.
2. Then you need to install fresh Unity at the new BOX.
3. Point your new Unity to old unity box(it is exchange, AD, SQL now after uninstall unity)
4. After test throughly, then you can add secondary unity for failover. Actually, we can install primary and secondary first, then point to exchange. It is up to you... It is just my suggestion to finish primary first (test throughly), then secondary.
Third: if it is voice messaging only with seperated message store (exchange).
1. Then it is same step as unified messaging.
For conculsion, it is a long step (I miss a lot of step at this post, include restore unity data e.g. user greeting) and customer will have downtime. There is some pre-work you need to do, for example, backup unity first.
Here is good link... you should able to get all info you need:
Please rate the helpful post.
Also a few things to note.
a. if you have MSDE installed right now, you have to use SQL 2000 for failover.
b. The installation of failover server is mostly similar to the primary server, except that you use the default 10 user license that comes standard with Unity.
c. You run the failover config executable on the primary and then failover server to complete the failover setup.
The issue here is that the link below says that I have to reinstall all software since my standalone unity server with AD, EXCHANGE and SQL is going to become my primary server in the failover configuration. The partner Exchange and the DC server are up and running.
Let me understand what you try to do.
1. your current standalone unity have unity, exchange, SQL, AD all in one box, right??
2. You already have partner exchange and DC running, right??
If that is the case...I suggest call Cisco tac to get confirm when I put my 0.02 cents here.
1. your user alais in standalone have to match your partner exchange now. For instance: John Smith, alais is "jsmith" at standalone, but "johns" at partner exchange now. It will cause problem during migrate.
Basically, you need to use Unity backup tools to backup the user info, include greeting, and their existing voice mail at exchange box.
Then restore the data after install Untiy, it will match their alais to do restore to the right user.
Second, I dont think Cisco has documentation remove or unistall exchange from unity, Cisco only have docucmentation remove unity.
Take a look
" Moving Cisco Unity 4.x onto a Separate Server
For a Cisco Unity 4.x system that has Exchange 2000 or Exchange 5.5 on the Cisco Unity server, this section explains how to get Cisco Unity and Exchange onto separate servers by removing Cisco Unity from the current server and installing it on a separate server.
Some customers have successfully removed Exchange from the current server instead of removing Cisco Unity. However, removing Cisco Unity from the server has, on average, been more successful."
Please rate the helpful post.
> if you have MSDE installed right now, you have to use SQL 2000 for failover.
I'm running MSDE on the primary, so looks like I have to upgrade. Can someone point me to the procedure for this?