locked
Would peer-to-peer sync model also support network failover scenario? RRS feed

  • Question

  • I have three synchronisation peers, A, B and C.  A holds the knowledge of truth and it allows local insert/update/delete.  Peer A needs to synchronise its data to B or C as Upload only.

    B and C are set up being bidirectional sync peers.  No local update is allowed either on B or C.

    The intention is to use B and C as the redundent sync peers for A.  This means that there will be two exactly same WCF services, one for B and one for C.  A can invoke ServiceB to upload changes to peer B.  A can also invoke ServiceC to upload changes to peer C.  But A doesn't know which service to which it invokes at the design time.  A is only configured to call a virtual endpoint and it's up to the network device to forward the call to ServiceB or ServiceC at the run time.  But the network device will not forward calls within the same sync session to different physical endpoints.

    Would this setup be supported?  Any input from MS would be appreciated.

    Thanks.
    • Moved by Max Wang_1983 Thursday, April 21, 2011 1:07 AM forum consolidation (From:SyncFx - Technical Discussion [ReadOnly])
    Monday, August 10, 2009 8:12 AM

Answers

  • Michael,

    IN short, your topolgy is like the one below

    A (local changes) --> Upload only virtual end point --> {B or C}

    B <- Bidirectional-> C.

    To confirm, A never downloads changes from B or C, right ?
    If so, it should work. Since B/C are randomly chosen by the b/w device, do try to ensure that B and C do a bidirectional sync regularly so they don't get out of sync too much. This will help in keeping them "closer" to A in terms of changes they have seen from A.


    Hope this helps,
    Sameer

     

     

    Monday, August 17, 2009 11:51 PM