Unity 3.1(5) VM upgrade to 4.0 VM on a new server

[Leonlei]

Current Unity status

- Member server of a small NT domain

- English and VM only 3.1(5)

- Exchange 5.5

- CallManager 4.1(3) integration

- AMIS enabled

Upgrade goal

- Move Unity to new server

- Remove from NT domain and to be the controller of AD

- English and VM only 4.0(4 or 5)

- Exchange 2000

- Keep current callmanager integration and AMIS networking

Upgrade option 1

1. DiRT back the current Unity server

2. Build Unity 3.1(5) on new server with Exchange 5.5 in new AD

3. DiRT restore the Unity data and mailboxes on new server

4. Upgrade Unity 3.1 to 4.0 and Exchange 5.5 to 2000 on new server in one shot

5. Take existing Unity server offline

6. Put the new Unity server to production

Q: 1. Do I need dongle to build Unity 3.1(5) on the new server and what license I should use

to DiRT backup(the number of port and subscribers, etc)?

2. Is there any problem to DiRT restore if the Unity has been moved to new AD while the DiRT backup on the previous NT domain?

3. How to backup Unity 3.1 on new server before I start upgrade to 4.0?

Upgrade option 2

1. Build Unity 4.0 and Exchange 2000 on new server in AD, just like a fresh installation, but different IP and hostname than the existing Unity?

2. Manually configure Unity(Call routing, call handlers, etc)

3. Import subscriber using bulk tool and create Exchange mainbox and AD user account on new Unity server

4. Put Unity 4.0 to production

5. Move Mailboxes from Exchange 5.5 to Exchange 2000

6. Take existing Unity offline and change new Unity server to the same one as existing Unity

We want migrate all users mailboxes to the new server, which option would be the better one?

[lindborg]

option 1 is your better bet.

1. you don't need a dongle to build your 3.1(5) system - you can install without a key and it'll run for a while (certainly long enough to do the install/upgrade).

2. DiRT is fine with changing domains - it's one of the reasons it's around. Check the help for the DiRT utility and/or the Reconfiguration and Upgrade Guide for more detail. You'll find the reconfiguration guide for Exchange here: http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_upgrade_guides_book09186a0080222fdf.html

just make sure you you have the latest versions of DiRt backup and restore apps before begining - you can get them on its home page here:

http://www.ciscounitytools.com/App_DisasterRecoveryTools.htm

[Leonlei]

Thanks Jeff. If the loosing of message is an acceptable potential impact, do you think option 2 would be more straight forward,it almost likes fresh Unity 4.0 installation.

In option 1, after we migrated mailbox to new Unity 3.1.5 on new server, we still face the risk of loosing message during Exchange and Unity upgrade. If the upgrade doesn't go well for any reason, we have back out to Unity 3.1(5) on new server. Am I right?

[Leonlei]

We decide to go with option 1. Can DiRT restore work on the new server with exact version, but different hostname? Thanks,

[cfortanb]

Yes...you can restore to a server with a different hostname. It must be the same release though. Also, instead of building a new 5.5 system, you can go ahead and build the new server using Exchange 2000 as the backend.