How many namespace servers?

Discussion in 'File Systems' started by PoBoy, Jul 25, 2006.

  1. PoBoy

    PoBoy Guest

    I have 8 servers\sites to replicate data to. I though the server had to be a
    namespace server inorder to replicate, but that is not so - just need to have
    the folder targets and replicated folders setup on all the servers. So my
    question is, what is the point (if there is one) in having more than 1 or 2
    (for redunancy) namespace servers when the data can still replicate? I guess
    if the server is a namespace server, the root share will open faster if it is
    local, but once you get to the folder targets (that are local) - it wont
    really matter will it?

    My Current Setup:
    5 Servers = Namesapce Servers
    1 Server = just has folder target and replication setup.
    2 Servers = not setup just yet

    What does the site wtih the 1 server that isnt a namespace server lack?
     
    PoBoy, Jul 25, 2006
    #1
    1. Advertisements

  2. Redundancy and fast/local access are reasons to have multiple root targets
    (aka namespace servers) for a namespace. The downside to having many
    namespace servers is the potentially increased load on the PDC emulator when
    namespace servers poll the DC to obtain changes. We have something called
    root scalability mode, which we advise if you have more than 16 root servers.
    When this mode is enabled, W2K3 servers will poll their local PDC, not the
    PDC emulator, to obtain changes.

    You can find details on root scalability mode in the DFS technical reference
    at www.microsoft.com/dfs.
     
    Jill Zoeller [MSFT], Jul 25, 2006
    #2
    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.