Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 278
  • Last Modified:

Recovering a failed Dc and Exchange on same computer after RAID failure with system state and exchange file backups

I have a single server that had a hardware RAID failure. I have workign system state and exchange backups on regular ntbackup disks. the machine was running the following before the crash: win2003R2 sp2, Exchange 2003 std sp2, Sharepoint Team Services (bad idea becuase it broke OWA oringally).
I fixed the hardware, reinstalled windows from sratch, reapplied service pack 2, went to MS update site and installed all critical hotfixes incl ie7 - so the server was at the right 'patch level'. I also ensured that all services were installed before restoring system state backup, eg: NNTP, SMTP, IIS, ASP, .net 2.0, and confirmed all were working on the new installation (server name is the same as well).

restored system state, marked the restore as primary, rebooted, and domain was back up.
Problem: IIS is corrupt (from system state restore). Therefore SMTP, WWW, IIS admin services wont start. I have removed IIS and associated components, so I can reinstall them, in order to rerun exchange disasterrecoery option, and ex2k3 is dependent on NNTP SMTP, IIS WWW etc in order to run.
First, removing IIS is incredibly slow (about 20 mins, dual xeon 2GB ram, SATAII drive) possibly becuase its looking for nonexistent registry entries. then reinstalling IIS, still doesn't allow smtp service, IIS admin service etc, to start up. I have a working system state, and exchange information store (per NT backup) - I don't want to rebuild the domain, but searchign the MS site is tedious, and find answers in bits and pieces. does ayone have a point form what should be done to get this functional.

Thanks
SK
0
sckruger
Asked:
sckruger
2 Solutions
 
Vishal BreedProgram ManagerCommented:
Removing & adding IIS is always pain when you have Exchange!!

Try this;

1> Remove IIS - reboot the server - after the server is on make sure IIS services are removed.

2> Remove Inetpub (from C:\) & Inetsrv (from C:\Windows\System32).

3> Then reinstall IIS.

4> Apply SP & patches again (since you have install W2K3 SP2 all files must match the SP2 level).

5> Then install Exchange with /disasterrecovery switch. While installing Exchange it may give warning that OS files have newer version than recommend - but ignore it.

-- Because when Exchange 2K3 was released W2K3 SP was not available. Hence it considers W2K3 SP1 or SP2 as newer version.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now