Automatic one-way synchronized solution

Discussion in 'File Systems' started by Roger Down, Jun 21, 2004.

  1. Roger Down

    Roger Down Guest

    I have read up on some of the documentation regarding DFS/FRS, but I'm still not sure if I can get
    what I want from it... So I'll describe my plan here...:

    I have a server which contains many files and directories. All changes to these files/directories is
    done ONLY on this server (master server).
    To ensure maximum availability of these files and directories, I need to synchronize several
    web/file (client) servers from the master server.

    Other requirements:

    - Changes done on the client servers MUST NOT be synchronized/replicated back to the master server.
    Data can only be synchronized from the master server.
    - If one of the client servers fails in some way, the client server is taken out of the synchronized
    configuration. When added back to the synchronzied configuration, the master server must detect
    automatically that the data is old, and starts a synchronzing process to ensure that the correct
    that is available again.


    1. Is the above scenario possible using DFS/FRS ?
    2. From what I heard, DFS/FRS only works with master-master configuration, is this true ?

    If anyone have already implemented such a scenario, I'd be happy to receive tips/tricks and best
    practices... :)

    Best of regards...
     
    Roger Down, Jun 21, 2004
    #1
    1. Advertisements

  2. Roger,

    You can do this with DFS, but, you're going to need to disable the
    replication on teh root, because, as you said it's multimaster. Instead,
    grab a copy of the robocopy utility form teh srver res kit tools (free on
    download.microsoft.com), and use it with the /mir switch to sync the cleint
    servers.

    --
    --
    Brian Desmond
    Windows Server MVP
    12.il.us

    Http://www.briandesmond.com
     
    Brian Desmond [MVP], Jun 23, 2004
    #2
    1. Advertisements

  3. This scenario is possible using FRS, but it must be administered very
    carefully. In such a scenario, you want to set up a custom
    replication topology so that there are only connections outbound from
    the "master" machine that originates changes to the leaf machines that
    are supposed to just have copies of the data.

    With such a topology file changes on the clients will never flow back
    to the master. But this situation must be avoided. You need to set
    up share permissions so these files can't be changed, otherwise you
    will get "trapped" changes on these client machines should changes
    originate there.

    Depending on how a client server fails and is subsequently restored,
    FRS should be able to resync the current data from the master machine.

    You'll probably want to set up FRS monitoring such as with the
    Ultrasound tool.

    Be sure to patch your FRS to the latest QFE.
    WS2K3: Q823230
    W2K: SP4 or Q815473
    Call product support to get the QFEs. You won't be charged if you
    only ask for the patches.

    --Richard

    Please post FRS related questions to
    microsoft.public.windows.server.dfs_frs and prefix the subject line
    with "FRS:" to make it easier to spot. Note that FRS is used to
    replicate SYSVOL on domain controllers and DFS root and link targets.

    For additional FRS resources, please visit
    http://www.microsoft.com/frs.

    This posting is provided "AS IS" with no warranties, and confers no
    rights.
     
    Richard Chinn [MSFT], Jun 25, 2004
    #3
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.