I dug out an unused HDD and experimented with restoring my SystemState and Exchange backups the past 3 days.
Whilst I'm pleased to say the system still "works" after a restore, there are a number of big, bright-red "ERROR!" events logged in the System and Application event log, but hopefully nothing not solvable. Active Directory was correctly restored and fully operational
afterwards.
But not Exchange.
Here are the steps I took:
- Made a SystemState backup from a Windows Server 2003 SP2 system
- Which is also a:
- Domain Controller
- IIS Box
- Exchange Server
- SQL Server 2000
- Terminal Server - Application Mode
- Fileserver NAS
- All on 512MB RAM (it worked fine with 256MB of RAM a year ago)
- Which is also a:
- Replaced the system's HDD with a spare one I had lying around
- Installed a new installation of Windows Server 2003 on said drive
- Patched it to SP2 and installed other patches and IE7
- Restored the SystemState backup
But then I wanted to test the state of my Exchange backups, so I attempted to reinstall Exchange. Exchange setup said it was already installed so I would need to reinstall. I went along with this.
But Exchange Setup threw a wobbly since IIS was corrupted. So I went to the Add/Remove Windows Components wizard and totally removed the Application Server checkbox, rebooted, then reinstalled IIS, NNTP, SMTP, W3SVC, and the rest that goes with it.
No dice. IIS Admin takes ages to boot up then doesn't display anything and Exchange Setup still complains.
This is nice to know, in the unlikely event of a real server meltdown my emails are screwed, despite having backups. (Although I could set up a virtualised server elsewhere, make it join the domain, then install Exchange on that and restore my emails there).
I'm going to see what happens if I restore earlier emails onto a cloned copy of my working Windows Server installation, but does anyone have any tips for a successful Windows Server brain transplant?
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.