restoring data and active directory into a new server

[Guest]

We have a Windows 2000 domain controller that crashed completely, motherboard
and raid controller and one of the hard drive (we suspect electric shock).

We are going to restore the data, programs and active directory on a new
machine. So I need to create the same hard drive configuration (two
partitions) restore data folders, Program Files (we have some legacy programs
- the company that created them is out of business now) and System State.

THe way I am thinking to do this is to remove the metadata from the domain
for the old system, create a new installation of Windows 2000 Server in the
new server with the hard drive configured as the old system, (same or bigger
size, same letters), then restore the data folders, Program Files in normal
mode, then reboot the server into directory services mode and restore the
System State.

The new server will have the same name as the old one and the same IP address.

My question is, should I restore Winnt folder as well ? If so, should I do
that in directory services mode ? Someone suggested that to restore Winnt
folder I should install the new server in a folder other that Winnt ?

Or should I not restore Winnt folder at all ?

Also should I join the new machine in the domain before I do the restore or
not ?

Is this method going to work (if someone has tried it before) and is there
anything I need to change or be careful of ?

I read the following article and it gives some directions but it does not
answer all my concerns.

http://www.microsoft.com/technet/pr...irectory/maintain/opsguide/part1/adogd03.mspx

is there any other documentation that would help me more ?

We do have two other domain controllers in place but we are more interested
in recovering the data and programs. (one of them needs Visual Fox pro
installed).

I do have a full backup (Backup Exec) of the old server.

Please help.

Thank you.

 

[Chris Malone]

Since you have other functioning DCs, restore what data you need and do
not worry about restoring AD to the busted DC. Seize whatever FSMO
roles that the busted DC owned to other DCs and go from there. You can
then promote the new machine up to a DC if you want to.

 

[Ken Aldrich]

Why would you go to the trouble of doing a metadata cleanup and then running
a dcpromo? I think I must be missing some critical thing here.

What you would normally do is build up a new 2000 server with the similar
hardware (critical that you use the same number of CPU's - if not there is a
workaround where you can replace the HAL - I can show you how to do this).
Name it the same, put it in a workgroup - don't join to domain.
Set up the network information to be the same as the old.
You may or may not need to edit the hostfile to point to your backup server
(depends on your DNS and backup infrastructure)
Install any necessary backup software client.
Do a complete restore, all drives and system state.
Boot into AD Recovery mode, do an UNATHORITATIVE restore.
Reboot.
Let synchronization happen.
You should be good to go.

I don't understand why you would take the risk of siezing roles and doing
metadata cleanup. Perhaps I missed something in your post.

 

[Guest]

But I will need to restore the system state for the programs to run
(registry) which is going to restore the AD as well.

Right ?

Is there a way to install System State without installing AD ?

 

[Guest]

I am not worried about cleaning the metadata. Maybe I did not explained it
very well.
Sorry about that.

First of all I want to thank you for all the explanations.

I plan to have a new server which will have bigger partitions than the
original server, the same number of processors.
What I am worried about is overriding Winnt folder might create problems on
the new hardware.
Should I restore Winnt folder ? Can I restore System State without restoring
Winnt folder ?

There is also another point that I am not quite clear.
You say to restore everything data and system state to the new machine.
Should I do that on Windows normal mode ?

Now if I install the system state in Normal mode doesn't that install the
Active Directory as well or Active directory is installed only in AD Recovery
Mode ?

Thanks again.

Genti

 

[Herb Martin]

But I will need to restore the system state for the programs to run
(registry) which is going to restore the AD as well.

Right ?

No, that was the point of just re-installing and then (eventually)
just doing a promotion -- there is no point in a System State
install from an AD perspective if you use DCPromo. In this
case you get AD from the promotion.

Is there a way to install System State without installing AD ?

Sure. Were you to do a System State install from a DC onto
an (ordinary) server it would become a DC. (It's a way to
effectively fake a DC promotion.)

You could of course also restore a non-DC System State which
would have nothing to do with AD.

 

[Guest]

I don't think you really understood my point. Mr. Malone suggested to
reinstall data without reinstalling the DC (data was in DC) and then promote
it to a DC. But I want to run the programs that were there as well (and that
is more important as I have two other DCs).
To run the programs I have to restore system state and this is going to
restore the AD as well. So I cannot make the programs run without promoting
the server to DC. My question was, can I restore the system state of a DC
without promoting the new server into a DC ?

But I will need to restore the system state for the programs to run
(registry) which is going to restore the AD as well.

Right ?

No, that was the point of just re-installing and then (eventually)
just doing a promotion -- there is no point in a System State
install from an AD perspective if you use DCPromo. In this
case you get AD from the promotion.

Is there a way to install System State without installing AD ?

Sure. Were you to do a System State install from a DC onto
an (ordinary) server it would become a DC. (It's a way to
effectively fake a DC promotion.)

You could of course also restore a non-DC System State which
would have nothing to do with AD.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

 

[Herb Martin]

I don't think you really understood my point. Mr. Malone suggested to
reinstall data without reinstalling the DC (data was in DC) and then
promote
it to a DC. But I want to run the programs that were there as well (and
that
is more important as I have two other DCs).
To run the programs I have to restore system state and this is going to
restore the AD as well. So I cannot make the programs run without
promoting
the server to DC. My question was, can I restore the system state of a DC
without promoting the new server into a DC ?

Not to my knowledge. It will take you only a
few minutes to try it (offline) and tell us.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

But I will need to restore the system state for the programs to run
(registry) which is going to restore the AD as well.

Right ?

No, that was the point of just re-installing and then (eventually)
just doing a promotion -- there is no point in a System State
install from an AD perspective if you use DCPromo. In this
case you get AD from the promotion.

Is there a way to install System State without installing AD ?

Sure. Were you to do a System State install from a DC onto
an (ordinary) server it would become a DC. (It's a way to
effectively fake a DC promotion.)

You could of course also restore a non-DC System State which
would have nothing to do with AD.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

:

Since you have other functioning DCs, restore what data you need and
do
not worry about restoring AD to the busted DC. Seize whatever FSMO
roles that the busted DC owned to other DCs and go from there. You can
then promote the new machine up to a DC if you want to.