I have an existing Unity server, VM only with Exchange 2k local as Message Store, in an AD network, hosting 3 remote CCM's for voice-mail. I will be swapping out the hardware completely to a new server (an MCS 7837), and I want to ensure that the migration occurs with minimal downtime or hiccups. After much thought I decided to use the client's backup program (UltraBac ... I know, it's not on the list, but it works well with SQL) to do a full, system-state backup of the old server. In the meantime, I would apply the WinOS to the new server, give him an IP address and hook em up, but NOT bring him into the domain or install any software. Once I had a few successful backups, I would do a complete restore of Unity/Exchange on the new system, reboot after unplugging the old system from the network, then apply the dongle, double-check licensing, and then test.
The old server will stay available for a hot restore if there are lasting problems with the new one. This way, we will only lose maybe a few saved voice-mails, but nothing more.
What are the holes, if any, in this idea? What has anyone else done in this scenario? and what would you suggest? My goals for the client are typical:
- mimimize down-time
- limit off-hours work, reducing the charge on my eventual bill
- most importantly, work the first time!