DFS Question . . . .

[jaksen112]

I have setup a DFS root/replica etc, that seemed easy enough. my question is, is it possible to setup site-A with a DFS folder, setup site-B with a replica of this folder, then configure DFS so that clients only hit the folder in their respective sites? (decreasing bandwith usage etc)


thanks
112

01110000

 

[antnic]

Yes, by doing what you have said will do that. I would suggest that you do it on a 2k3 DC box rather than 2k DC as the Site based DFS works alot better.

 

[ecunupe]

You also have to run dfsutil /sitecosting to enable this. When you run this switch it will give you information about adding registry entries on your domain controllers. This will enable your clients to connect to domain controllers in the closest site via the site link costs in active directory sites and services.

 

[ricpinto]

The purpose of DFS is to replicate to other servers and sites. So the solution there is the scheduling/timing/sitecosting of the replication. If you don't want that then don't include the share in the DFS root.

 

[Jpoandl]

I have setup a DFS root/replica etc, that seemed easy enough. my question is, is it possible to setup site-A with a DFS folder, setup site-B with a replica of this folder, then configure DFS so that clients only hit the folder in their respective sites? (decreasing bandwith usage etc)"

It seems like everyone is saying the same thing here...but to clarify this for you, please read the following.

DFS has two main functions. The first, is that you can create a logical heirarchy of folders so that your users can connect to one spot and gain access to all shares on the network. For example, imagine that your have 5 file servers with 5 shares on each folder. Your clients would have to remember which server contained what shares. DFS can help you organize your share points, so that the data can be view centrally through DFS. (Publishing share names in AD is another way to help centralize shares)

The other function of DFS is to replicate data. However, the data that you replicate should be READ ONLY. DFS is not meant to handle read/write data. After you setup AD DFS replication, the clients will automatically understand where the "LOCAL" DFS share exists. This happens by the client talking to Active Directory and DNS. The client compares its IP address with the IP subnets defined in Active Directory Sites and Services. The client can tell what site it is in. It then looks for a DFS replica within its site. If one is found, the client will be redirected to the local DFS replica. If the client does not find a local DFS replica, it will be randomely redirected to a WAN connected replica. The key here is to make sure that your AD Sites are defined properly in AD sites and services.

-later



Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)