I'm new to setting up a DFS Namespace and I'm looking for some guidance. My goal is to create redundancy in my namespace servers so that if one becomes unavailable, clients can still access the namespace. I've been finding a lot of information on DFS-R for file replication but that's not what I'm after. Should I just set up multiple namespace servers and forget about DFS-R for this?
I'm also using my Domain Controllers (DCs) as namespace servers, but I've heard mixed opinions on that. Some say it's a good idea while others warn against it—what are the potential issues with using DCs this way? I appreciate any tips or good resources you can recommend!
4 Answers
While you can use DCs, I recommend setting up dedicated namespace servers. Keeping roles separate can help maintain system stability. It’s straightforward to add additional namespace servers through the MMC, so you might want to consider that option.
If you’re not managing a huge environment, then making every DC a DFS-N namespace server should work just fine! It simplifies things. Just keep an eye on performance if your setup grows.
For redundancy, it's totally fine to use DCs as namespace servers. Just make sure to add several DCs as namespace servers so that if one goes down, others can handle the requests. A multi-DC setup can ensure your namespace remains available to clients without any hiccups.
Be cautious about using DFS-R—it can get a bit complicated and was originally designed to be phased out in favor of Storage Replica. Make sure you really need it for your setup. Are you planning to host everything on-premises?
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures