Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

Non-Authoritive Restore taking too long - how to find out why/track initial replication?

$
0
0

I have had a server that despite not logging anything obvious like USN rollback has been acting strange - kept replicating back to other servers overwriting changes that had been made on them and such. Decided easiest thing is a quick D2 restore on the problem server.

After performing this though it initially sat there, created 2 files in the Netlogon (of the fair few that it should) and then appeared to just stop. No Policies being created, just the scripts with the 2 files and stalled for at least 30 mins.

As a test I copied and pasted the entire SYSVOL contents from it's partner DC to it in about 2 minutes... So I can't make any sense of this delay.

As another test I stopped the FRS, manually populated the scripts and policies folders and started it, leaving another 30 minutes with no change.

So now again I have cleared the folders, reput in Non-Authoritive restore mode and restarted FRS and exact same result of 2 files created and nothing further...

How can I find out a status or such of the copy process? I cannot see any open files or connections on the source DC from the restoring one.

Anything further I can do to simply find out what is going wrong? Another log I am missing or something? I have checked and been watching FRS logs during the process and nothing out of the ordinary here. Both servers are 2008 R2.


Viewing all articles
Browse latest Browse all 31638

Trending Articles