none
DFSR resync all files in replication group.

    Question

  • I was migrating from using robocopy for replication of some files to using DFS.  What I thought would use the pre-seeded data ended up moving all of the pre-seeded files to conflict-and-deleted, but did not move the "source" version of the file to the replicated folder.   for whatever reason it decided to toast the pre-seeded data is fine by me.  I just need to get the sync part working.

    I see that dfsrdiag is able to initiate a sync process using syncnow.  What I have not been able to find is how to specify the "authoritative source" for the sync process.  I would hate to have it delete all of my production data on me.   The option /partner:<systemname>  is that referring to the source system or the system to replicate to?
    Tuesday, March 16, 2010 4:34 PM

Answers

  • Hi,

    You can choose the primary server during DFSR setup. And from

    DFS Replication: Frequently Asked Questions
    http://technet.microsoft.com/en-us/library/cc773238(WS.10).aspx

    We can find"
    Can I seed a replication group member with data prior to the initial replication?

    Yes. DFS Replication supports copying files to a replication group member before the initial replication. This "prestaging" can dramatically reduce the amount of data replicated during the initial replication.

    The initial replication does not need to replicate contents when files differ only by real attributes or time stamps. A real attribute is an attribute that can be set by the Win32 function SetFileAttributes. For more information, see SetFileAttributes Function in the MSDN library (http://go.microsoft.com/fwlink/?LinkId=182269). If two files differ by other attributes, such as compression, then the contents of the file are replicated.

    To prestage a replication group member, copy the files to the appropriate folder on the destination server(s), create the replication group, and then choose a primary member. Choose the member that has the most up-to-date files that you want to replicate because the primary member's content is considered "authoritative." This means that during initial replication, the primary member's files will always overwrite other versions of the files on other members of the replication group.

    For more information about the initial replication, see Create a Replication Group."

    Thanks.


    This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, March 18, 2010 12:14 PM