Troubles Restoring System State from Back Up

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

In my network we have 3 DC's. A contractor blew away the sysvol\Domain\Policies and sysvol\Domain\scripts folders and all the lovely GP within.

I'm using Veritas 9 to back up the servers and the system state. After restoring the system state from the back up, I used ntdsutil to perform an authoritative restore from one DC.

After letting the network simmer for a while, the restored system state was overwritten by the bad system state

I've tried taking down all three servers and restoring the system state to each machine then letting AD work it's magic. However, the DC's didn't recognize each other and no replication was done.

Any suggestions?
 
If the sysvol was deleted and the Group Policies links in ad still exist.The
system state is not bad. It is restoring the sysvol with the policies. What
happens is that FRS replicates the deletion of the files from the other
servers. Stop FRS on all DCs. Restore the system state. Now you have two
choices. Me I would copy the sysvol\domainame\policies and scripts
directories to another location. So you will not have to redo the system
state. Next either wait for the deletion and the copy the files back. Which
should trigger the replication back out. Or mark the version of sysvol on
the restored dc as authoritative by setting burflags to D4. start frs on
this server and then use the burflags of D2 on the remaining servers.

--
Richard McCall [MSFT]

"This posting is provided "AS IS" with no warranties, and confers no
rights."
Paulie D said:
In my network we have 3 DC's. A contractor blew away the
Click to expand...
sysvol\Domain\Policies and sysvol\Domain\scripts folders and all the lovely
GP within.
I'm using Veritas 9 to back up the servers and the system state. After
Click to expand...
restoring the system state from the back up, I used ntdsutil to perform an
authoritative restore from one DC.
After letting the network simmer for a while, the restored system state
Click to expand...
was overwritten by the bad system state.
I've tried taking down all three servers and restoring the system state to
Click to expand...
each machine then letting AD work it's magic. However, the DC's didn't
recognize each other and no replication was done.
 
Back
Top