Client/Server File Sync Provider RRS feed

  • Question

  • Hi,

       I am new to MSF and hoping to use MSF 2 (CTP2) for a project that I am working on . . . I need to perform a one-way file sync (NTFS) between two servers, but I want to use TCP sockets as the transport layer (as opposed to a mapped drive) . . . The reason we are hoping to use TCP sockets is that we want to split up the disk I/O so that most of the 'disk writes' are handled by the remote server (server A contains master copy of files; server B receives changes via TCP socket and maintains backup copy of files) . . . I assume that I need to create a custom sync provider, but I need a little help to get started (and confirmation that I do in fact need to do this) . . . Thanks in advance for your help . . .

    • Moved by Max Wang_1983 Thursday, April 21, 2011 12:38 AM forum consolidation (From:SyncFx - Technical Discussion [ReadOnly])
    Tuesday, September 15, 2009 8:52 PM


All replies

  • Hi,

       Any expert advice on this?  I would really appreciate some help . . .

    Thursday, September 17, 2009 5:45 PM
  • Hi -

    You do need to write a custom provider because our in-the-box File Sync Provider does not allow you to change the transport layer. You can find more information on how to write a provider here -


    Deepa ( Microsoft Sync Framework)
    Friday, September 18, 2009 9:51 PM
  • Deepa,

       Thanks for your reply . . . I may be thinking incorrectly, but would it be possible to simply inherit from the Microsoft.Synchronization.Files.FileSyncProvider class and then override the transport mechanism?  If this is possible, do you know where I can find documentation indicating which components will need to be overridden?

    Tuesday, September 22, 2009 3:15 PM