DFS Quesion

[brad310]

I have a question regarding DFS and its capabilities.

We are retiring a domain controller (2k3 x32) which was also a file server, loaded with shares and whatnot in its D:\, and our user's MyDocuments are redirected there as well.

We've got 2 new DC's online (2k3 x64) and want to replicate the data from the old DC to both of the new. I have no issue with creating the domain root...but if I create a new link pointed to a share on the old DC, when we take it offline, will uploads still be able to come into the "old" path? The "path to target" will obviously be different since that is what it is physically looking for on the network...so I'm wondering if I need to change EVERY link in DFS.

If you have done anything like this before or know of a better solution, feel free.

Thanks.

 

[mooseracing]

Our you going to try and replicate everything from teh old ones to the new ones with DFS-R? So you will have 3 servers that temp. have the data then down to 2 when finished?

If you take the namespace server out in the DFS Mgmt tool for the old one it won't use that path anymore. It will use whatever other namespace servers you have set up that point to the namespace. If you left that namespace server in there there will be errors about replication in the eventlogs, I don't think your users shoudl see anything though since that is the point of DFS, in case a target goes down it seamlessly covers it.

 

[brad310]

Originally posted by: mooseracing
Our you going to try and replicate everything from teh old ones to the new ones with DFS-R? So you will have 3 servers that temp. have the data then down to 2 when finished?

If you take the namespace server out in the DFS Mgmt tool for the old one it won't use that path anymore. It will use whatever other namespace servers you have set up that point to the namespace. If you left that namespace server in there there will be errors about replication in the eventlogs, I don't think your users shoudl see anything though since that is the point of DFS, in case a target goes down it seamlessly covers it.

Correct, we want to have 3 DC's online w/ all the data, then demote the old one to have the 2 new ones online...all while having the data replicated accross all 3 until we pull the old one offline. Some programs we have here send/pull data from a specific UNC that we obviously dont want any hiccups in.

 

[mooseracing]

Good luck with it, it should work that way without an issue once all the targets are replicated across the 3. Right now I am battling mysterious DFS communication problems, yet all my targets are replicating. And to limit the source we knocked it down to only one namespace server and the rest are replications targets.

I like how it works I just wish it would quit filling up my eventlog