DFSR Namespace Structure Choices

Fred Marshall 1 Reputation point

I've set up DFSR and, in doing that, set up 4 namespaces. I was asked: "Why more than one?" Well, I had a reason for doing it but I'm not sure it was a good reason.
Let's say that my reasoning didn't have a good technical foundation. OK - so be it.
This raises the question:
What are the pros and cons of having 1 vs N namespaces?

  • Harder to maintain?
  • Separate databases?
  • etc.
    Examples of using multiple namespaces and benefits?
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
10,638 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Fan Fan 15,231 Reputation points


    DFS-N makes it possible to give users a virtual view of shared folders, where a single path leads to files located on multiple servers.
    So, users don't have to remember the multiple server names to access resource. They just need to remember DFS-N name, they can access all the files configured under the DFS-Namespace.

    Based on my understanding, If we have 3 or 4 file servers, and we create 3 or 4 DFS-Namespaces, users must remember all the root names to access the resource.
    Each namespace appears to users as a single shared folder with a series of subfolders.
    In a sense, more Namespaces makes it more inconvenient for users to access.
    Of course, it takes a little more time to maintain if you have multiple DFS-Namespace.

    Just from the convenience of use, we can reduce the number of Namespaces,
    Instead, If you have a lot of shared folders, and you clearly distinguish their types, we can create different links under the same Namespace。

    But may not be so difficult to remember two or three Namespaces.