We are in process of upgrading the Windows Operating System from 2000 to 2003 on our Unity 4.0.5 due to security requirements.
I understand the process is to backup Unity with DiRT and rebuild the server on 2003 and restore.
I would like to call on to your experiences in dealing with this kind of upgrade and discuss any particular issues to look out for.
Our setup is single VM only Unity server with 2000 subscribers and 11 call handlers.
Id do the following:
DIRT backup unity 4.05.
also print out your Unity information dump that has your ESs installed. These will need be reinstalled.
If you have a spare drive, use it.
- Dirt backup, copy all off the server
- Shut down the server
- Pull the primary drive
- insert a new drive
- load the 2003 OS (either windows or Cisco platform disc)
- Load 2003 SP2 (no other updates)
- Load Unity 4.05
- Load ES updates from old system.
- DIRT restore
You should be good to go. Its going to be a long long process if you have 2000 mailboxes. DIRT can take a long time to back this info up and also restore it.
A better way to do this.... especially if you are doing all this work, is to buy a new server. Most likely, you have an old H1 server. So if you reload to 2003, next year, you will have to replace the server because it will EOL.
Purchase new server
Load Unity 7x, Exchange 2003
Use Cobras to export from 4.05
Use Cobras to import to 7.0.
The great thing with this, is that you minimize downtime, **AND** and have a rollback plan, the 4.05 server is still running!