Good Morning,
We recently had an issue with DFS where older files from our DR servers were overwriting newer files in our production server.
Too immediately resolve this issue, we severed the DFS links in our topology.
Now I am at the point where I am trying to rebuild two replicated folders within a DFS group. Here are the steps I have taken:
1) found out which DC's each file server were talking to.
2) Deleted the replicated folder ("Finance") from DFS Management
3) ran a DFSRDIAG POLLAD for AD to pickup the change
4) on each DC ran a repadmin syncall to replicate the changes
5) confirmed that all the File servers recieved the changes
6) Stopped DFS replication service on all File servers
7) Deleted the DFSRPrivate Directory from all the "Finance" folders on the file servers.
8) restart DFS replication service on all file servers
9) created a new replicated folder called Finance that points to the original replicated folder shares
I am now waiting for initial replication to kick off. the changes above were made approximately 14 hours ago. Since then, the status in the DFS health report remains at "waiting for initial replication". I have done some investigation and have found that it is currently going through and generating hashes for all the files.
It originally reported a backlog of 180000 transactions to send and recieve. After 14 hours, this number has dropped to 170000 transactions to send and recieve.
My question is:
Is it possible to speed up the process of cataloging and comparing the files for replication?
Over the past 14 hours, there have been no spikes in CPU, Memory or IO. As well, only 65 MB has been transferred between the file servers. Based on my calculations, it will take 4 days for DFS to go through and synchronize the file shares. Is there any way to dedicate more resources to DFS to speed this up? Or am I doing something wrong in my process to resync/pre-seed these files.
Any assistance would be greatly appreciated.
Kind Regards,
Jacob Estrin
Jacob Estrin