Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 5654

Problem with Clustered DFS Namespace

$
0
0

We have a Microsoft cluster running on 2 Server Enterprise 2008R2 Servers with the FileServices Roles (including DFS roles).  We have 3 Standalone DFS namespaces (roots) which have been up and running for a couple of months.  Users were complaining about performance so we added the DfsDnsConfig registry entry to force the FQDN format in the namespace (KB244380). 

Although it doesn't say to do so in the KB Article, I found several threads that said you also need to delete and recreate the namespaces afterwards.  This is where I got into the problem.

I deleted one of my namespaces from the Failover Cluster Manager utility.  I then recreated the namespace.  While it works, the share was empty.  This is because by default it placed the namespace in DFSRoots and we have our namespaces in DFSroot (no trailing "s").

So I am trying to delete the new namespace in DFSRoots and create it in the DFSRoot folder, but I get the error listed in the title.  This is what I've tried so far to resolve this:

1. dfsutil to remove the namespace and it fails saying the command is not supported in a cluster environment.  Fair enough.

2. I tried to delete the share (using "Share and "), but it fails saying the shared folder is a DFS namespace root.

3. I tried to find an option to add the namespace to the resource group (using "Failover Cluster Manager") but I can't find the appropriate option.  Maybe it cant be done from the "Failover Cluster Manager" unless you are created a new one, I think.

4. Of course I tried to delete the namespace (using the "DFS Management" utility) and that's where I get the error in the Title of this post.

5. I deleted the registry entry for the namespace under hklm\software\Microsoft\dfs\roots\standalone.  I did this on both Fileserver nodes in the cluster.  However then all the utilities complained that they couldn't find the namespace and I couldn't do anything with the specific namespace.  So I put the registry key back in.

At this point I don't know what else to try to delete this namespace properly.  Any assistance is appreciated.


Viewing all articles
Browse latest Browse all 5654

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>