Thursday, June 07, 2012 3:02 PM
I am replicating my DFS file system to a new member. Whilst DFS has always been enable on this server and configured for the folders I am replicating, the service has been stopped for some time as it was not necessary. I believe this may be the cause of some of my issues.
Initial replication has taken an incredibly long time (a couple of weeks) for about 250GB of data and has still not completed. It seems to have came to a halt.
What settings or diagnostic info can I check to identify the cause of this? The event logs are not displaying any errors or warnings.
Friday, June 08, 2012 8:11 AM
Can you please check this useful link once http://blogs.technet.com/b/askds/archive/2007/10/05/top-10-common-causes-of-slow-replication-with-dfsr.aspx
Regards, Ravikumar P
Monday, June 11, 2012 8:40 AMModerator
As the replication is still not finished, I suggest to recreate it. Set staging folder with a larger size (steps could be found in the article provided by EXRAPUL).
Meanwhile, for large files, it is recommanded to manually migrate to target server with backup-restore or robocopy instead of waiting DFSR.
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact firstname.lastname@example.org.
Monday, June 11, 2012 11:43 AM
I have actually tried removing the member, doing a robocopy of the whole lot (merging into what was already copied), and then re-adding the member. There is now still a backlog which it is slowly working through. Am I right in assuming it is just comparing checksums?