AD Restore

  • Thread starter a3matrix@gmail.com
  • Start date
A

a3matrix@gmail.com

Greetings to the group:
I am looking at doing an AD restore from tape from last December not
for the purposes of rolling back the current environment, but because
we need data of some type that is no longer available.
Is it possible to perform an authoritative restore of the system state
to a DC then unplug that DC from the network so it can't replicate and
wind up with a DC with AD on it as it was last December?

Rather than squeeze the trigger and wind up finding out the (possibly)
really bad way, I thought I would read up and also ask others.
So far, the reading has not given me a warm fuzzy.

TIA
Drew
 
P

Pegasus \(MVP\)

<a3matrix@gmail.com> wrote in message
news:1186497418.597737.29350@q75g2000hsh.googlegroups.com...
> Greetings to the group:
> I am looking at doing an AD restore from tape from last December not
> for the purposes of rolling back the current environment, but because
> we need data of some type that is no longer available.
> Is it possible to perform an authoritative restore of the system state
> to a DC then unplug that DC from the network so it can't replicate and
> wind up with a DC with AD on it as it was last December?
>
> Rather than squeeze the trigger and wind up finding out the (possibly)
> really bad way, I thought I would read up and also ask others.
> So far, the reading has not given me a warm fuzzy.
>
> TIA
> Drew
>


You should restore your data only, not your system state.
If you restore it to a different location then this will have no
effect on your system state or on your current data.
 
A

a3matrix@gmail.com


> You should restore your data only, not your system state.
> If you restore it to a different location then this will have no
> effect on your system state or on your current data.


Apparently no one is sure what the exact data is. I am being kept
completely in the dark other than the order to "restore AD from last
December"
I get the feeling "they" think that it is right up there with making
hot broth using a bullion cube.
Either way, the restore is running. I am watching it and once it is
done I will yank the network cable and let the chips fall.
Thanks for your help.
Drew
 
P

Pegasus \(MVP\)

<a3matrix@gmail.com> wrote in message
news:1186499120.197576.179980@22g2000hsm.googlegroups.com...
>
>> You should restore your data only, not your system state.
>> If you restore it to a different location then this will have no
>> effect on your system state or on your current data.

>
> Apparently no one is sure what the exact data is. I am being kept
> completely in the dark other than the order to "restore AD from last
> December"
> I get the feeling "they" think that it is right up there with making
> hot broth using a bullion cube.
> Either way, the restore is running. I am watching it and once it is
> done I will yank the network cable and let the chips fall.
> Thanks for your help.
> Drew
>


Regardless of where the data is located, System Restore won't
restore it. BTW, it is good practice to store all server data on a
drive other than the system drive.
 
A

a3matrix@gmail.com

> Regardless of where the data is located, System Restore won't
> restore it. BTW, it is good practice to store all server data on a
> drive other than the system drive.


I should clarify. The data they are concerned about is contained
within AD user accounts. Not data in the sense of a file server.
I was able to restore the AD files to the box, but when I went into
Directory Services Restore Mode and ran ntdsutil and tried to restore
the database it fails due to Tombstone life. Not a big surprise. So
the question now is how to defeat teh Tombstone.
Drew
 

Similar threads

M
  • Article
Replies
0
Views
102
Microsoft Corporate Blogs
M
J
Replies
0
Views
95
Jack_813 i
J
M
Replies
0
Views
67
Matthew Bell1
M
Back
Top Bottom