General discussion


DFS Implementation Issues.

By kuroikazex ·
I run a Win2000 domain with AD and two replicating domain controllers (Directory 1 and Directory 2). I wish to have a fault-tolerant dfs link to my two data vaults (Vault 1 and Vault 2). So I jump into the DFS manager on Directory 1 and I create a new DFS root with some empy DFS share on Directory one. Since I don't want any files under the root I move on to make a DFS link. So I make a 25GB folder called Apps1 on vault 1 a dfs link. I then tried to make an empty folder on vault2 named apps and then setup automatic replication with vault1 as the primary. This resulted in the staging directory being made but only about 2 folders ever were moved out of it. Sometimes none are moved out. So I tried starting with two folders exactly the same, and that didn't work out correctly either as replication never began. I'm not sure what I'm doing wrong, but is it possible to make a fault-tolerant DFS link with one big folder and one empty one and sit back and watch the magic happen? Also if that's true could I do the same with 100GB? Any help on the specifics of dfs limits and implementation would be handy.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by d.walker5 In reply to DFS Implementation Issues ...

DFS root needs to be domain based, and the tragets need to be hosted on Windows servers running "file replication service." The "file replication service" is started automatically on DC's, but can be started manually on member servers, just go to the Services console. DFS can link to a maximium of 32 idential folders (aka targets or relicas)

I hope this helps.

Collapse -

by kuroikazex In reply to

The "vault 1" mentioned is a member server on a RAID array.
When you mean 32 identical folders do you mean that's the maximum that FRS can handle?

Is size a factor?

Related Discussions

Related Forums