Re: Server 2003 recovery

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Leonard wrote:
WE have the system state backup so that should be ok

The other programs etc will need to be reinstalled etc iam aware of that

I presume to restore sysyem state I must have all the windows updates done or do I just need to go as far as the lates service pack

any advice on changing the DNS and FSMO rules

thanks

"Dusko Savatovic" wrote:

I suppose you have just one DC.
If it is your only DC in the domain, you're in trouble.
You must restore system state.
The additional content you might need to recreate depends on the way that system state backup was taken. If you backed up complete system drive, then you're OK. If you just backed up system files, then you'll have to reinstall any additional content that was not saved with a backup.

If you have more than one DC in your domain, then your domain should continue to function without interruption. You may need to adjust DNS and FSMO roles.

"Leonard" <Leonard@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:6A144EEF-ACB6-42F4-B266-24673B6028EB@xxxxxxxxxxxxxxxx
Its looking like out 2003 server (domain controller) has had a Hard Drive
failure, and its probably 2 of the 3 driver from the raid 5 array

WE need to reload the server, I just want to confirm a few points

I have another 2003 server running exchange 2003 which I ok I will need this
logging back on the domain when the server gets back up and running whic will
then let us get email up and running

Will the exchange server just logback on after a clean server 2003
installation or will I need to run system state recovery

If I need to run the system state recovery do I need ALL the windows updates
applying along with all the applications, sql etc reloaded?

We have backups of user data, which I have no problem in restoring

its just the issue of the exchange box I am not to sure of

look forward to your replys

Thanks


I would do the following:

1) Back up the system state. Always a good idea.
2) Create a second DC. It could be a decent workstation.
3)Make sure that DNS, DHCP, etc. are set up and configured on the new DC.
4) Move all the FSMO roles to the new DC
5) Take the first DC off line and make sure everything works. Resolve any issues.
6) Rebuild the original DC and DCPROMO it. I wouldn't bother with restoring the system state.
6) Repeat steps 2 - 4 for the DC

At this point, you could DCPROMO the temp DC back to a member server and remove it from he domain. However, I would suggest that you keep the "temp" DC, if possible, active. Remove DHCP (or look into splitting scopes) and make it a GC. Now your domain can continue to operate if one of the primary DC fails and disaster recovery becomes a relatively simple job...

--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
.



Relevant Pages

  • Re: SBS two adapter setup with Netopia Router. Help Save my weeked
    ... >> When you click OK on this message, the server restarts. ... >> are not able to start the server or restore the system state from backup. ...
    (microsoft.public.windows.server.sbs)
  • Re: Test lab: DC Promotion and removal process
    ... I now need to move this DC into the test lab and this is where I get lost. ... system state restore processes and have been able to successfully restore ... system state to another server, log in, and have full access to all AD ...
    (microsoft.public.windows.server.active_directory)
  • System State Restore to New Box Failure
    ... All DCs in the Forest have failed. ... I have system state backups of every DC in each Domain ... referenced in the registry from the system state restore can be found ... I have run DCDIAG on the DC and it says that "A Global Catalog Server ...
    (microsoft.public.windows.server.active_directory)
  • Re: disaster recovery
    ... The shortest sequence to restore the entire thing, ... [The assumption below is that you do not have another DC or Exchange server ... you may find that after doing the first restore of System State, ... The worst scenario would be if the older server was such old ...
    (microsoft.public.windows.server.sbs)
  • Re: Restore DC - Windows Server 2003 STD SP2
    ... The server is no where to be found, all they have is system state backup. ... Reinstall with same name/os/sp, stay in workgroup, and then just ... system state restore? ...
    (microsoft.public.windows.server.active_directory)