Re: Server 2003 recovery
Leonard,
system state backup is not the same as the complete system backup.
Microsoft's solution for the backup of the Win 2003 system (without data
partitions) is called ASR (automated system restore).
Unless you are able to restore system state backup to the same machine then
you're in trouble.
System state includes files that are covered by the system file protection
(files in the %Windir%).
System state on DC also covers AD database (files in NTDS folder) and SYSVOL
folder.
What you're trying to do is reinstall OS then run restore system backup.
This is not supported scenario. This scenario is covered by ASR.
I'm not sure how this will work. I would:
0. Try to do everything off line, i.e. isolated from your production
network. (Note. Isolated, but not disconnect from the LAN. Use a loopback
plug or some LAN switch that nobody else is connected to).
1. save all that can be saved.
2. try to install OS to a brand new disk (leaving the old one aside as a
backup and/or evidence).
3. I would install just the bare OS with drivers and Service pack that was
present on the original config. I wouldn't worry about updates for now.
4. I would then restore from system backup and see what happens.
5. If you are lucky, your AD may start.
6. If DNS service didn't start, I would add DNS role either to this server
or another one on the network. Your DNS must have your domain zone
configured.
FSMO
Install support tools from Win2003 CD. They are in \Tools folder.
Run replmon.
You should see a list of FSMO roles.
If you have just one DC then obviously all FSMO roles are on this only one
DC.
If you had more than one DC then you are lucky.
On the surviving DC install DNS.
In the DNS create an AD integrated zone for your domain.
run
net stop netlogon
net start netlogon
(This should populate records in your DNS zone).
On the surviving DC open AD Sites and services. Turn the GC on.
Open AD Users and computers. Open properties for your domain and Open tabs
for PDC, RID and Infrastructure master. You can then transfer these three
roles to this (surviving) computer.
Now you need to transfer Schema master and Domain Naming master. You can do
it with ntdsutil or from mmc.
Schema Master
open cmd
Regsvr32 schmmgmt.dll
Open mmc and add "AD schema" snap-in.
From this snap-in you can transfer or seize Schema master role
Domain Naming master
Open AD Domains and trusts.
You will find option to transfer or seize Domain naming master role.
Caution
FSMO roles can be transfered or seized.
Transfer is with cooperation of your old DC (i.e. it is still responsive)
Seize is without cooperation from your old DC (i.e. it is unresponsive).
If you seize the role, than the old DC should not be reintroduced in your
network. It may cause serious trouble.
Questions
1. Was your failed DC only DC in your domain?
2. How many domains have you?
3. How many users are in your domain?
4. How many computers are in your domain?
5. How many OU's?
6. How many security groups?
7. How many AD aware applications?
These questions are here just to help you decide if perhaps it's easier to
rebuild the domain then to restore.
Good luck
"Leonard" <Leonard@discussions.microsoft.com> wrote in message
news:12B72578-F60C-4875-8D24-D34CFC075D99@microsoft.com...
> 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@discussions.microsoft.com> wrote in message
>> news:6A144EEF-ACB6-42F4-B266-24673B6028EB@microsoft.com...
>> > 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
>>
>>