rsp_it
asked on
Using domain-based namespace in Windows 2008 Failover Cluster
Hi,
I am working on migrating my current DFS server to a Windows server 2008 cluster, when I tried to configure the domain-based namespace I got the below message:
"A domain-based namespace cannot be created on a cluster"
It seems that we can only use stand-alone namespace on a windows cluster, but we really need to keep the old domain-based namespace, if not we will have to change a bunch of things.
Now we plan to install another member server to host the domain-based namespace, link folders to the clustered DFS server, but this will waste another server and lost the failover function on the member server.
I am wondering whether I could use the domain-based namespace in a cluster by changing something in windows registry, or I could have some other better plans to keep both the cluster and domain-based namespace work.
Otherwise, due to some network issues, I can't enable DFS replication in my production.
Thanks
I am working on migrating my current DFS server to a Windows server 2008 cluster, when I tried to configure the domain-based namespace I got the below message:
"A domain-based namespace cannot be created on a cluster"
It seems that we can only use stand-alone namespace on a windows cluster, but we really need to keep the old domain-based namespace, if not we will have to change a bunch of things.
Now we plan to install another member server to host the domain-based namespace, link folders to the clustered DFS server, but this will waste another server and lost the failover function on the member server.
I am wondering whether I could use the domain-based namespace in a cluster by changing something in windows registry, or I could have some other better plans to keep both the cluster and domain-based namespace work.
Otherwise, due to some network issues, I can't enable DFS replication in my production.
Thanks
ASKER
We install the DFS servers in different buildings and enable replication will consume most of the bandwidth, that's why we disable the DFS replication. I am not looking for a way to use it, sorry for confusion.
The old domain-based namespace is very hard to change, so we have to think other plans to keep it. Here is another plan we have, let's see whether I can make it clear:
Build a two node file server cluster, publish shared folders from the cluster. At the same time, on each cluster node, configure DFS with domain-root (the DFS service is not running on the cluster, just running on the node), add shared folders (published from the cluster) into the domain-root DFS. Now, we will have two namespace servers that publish shared folders from the cluster. If we shutdown one node, another node will take over all tasks as DFS domain-root and file sharing.
We are not sure whether this could work, but any suggestions would be very thankful.
The old domain-based namespace is very hard to change, so we have to think other plans to keep it. Here is another plan we have, let's see whether I can make it clear:
Build a two node file server cluster, publish shared folders from the cluster. At the same time, on each cluster node, configure DFS with domain-root (the DFS service is not running on the cluster, just running on the node), add shared folders (published from the cluster) into the domain-root DFS. Now, we will have two namespace servers that publish shared folders from the cluster. If we shutdown one node, another node will take over all tasks as DFS domain-root and file sharing.
We are not sure whether this could work, but any suggestions would be very thankful.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can just setup DFS namespace on your domain controllers, which is where i feel they should live IMHO. You can have a failover cluster serve up the actual files.
http://support.microsoft.com/kb/301588
http://technet.microsoft.com/en-us/library/cc732863(v=ws.10).aspx