Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We currently have a 2003 DFS server that has a backlog of several gigabytes. And that's for just a single DFS share. It was not set up during this administration, we have simply been dealing with it's effects.

We are currently running a script to attempt to recover some of the data, but DFS is still running and getting in the way. (link to script: And, any modifications made to files after the script has started will likely be ignored by the script and just put at the back of the queue (not a VBscript guy, so I don't know the implementation details of the script components)

First and foremost, if we stop and uninstall DFS, will the data remain in the folders DFS creates (dfsprivate, etc) for us to continue the recovery scripts? If this is possible, it would seem like the simplest approach (that I can think of) to recover as much data, as quickly as possible.

Do any of you have any other suggestions for recovering the data in a faster way if the above method is not possible? We are completely okay with removing DFS if that helps the situation. Until we get a more reliable system (2008 perhaps), we have changed all of our users drive mappings to point directly to a file server instead. However, that is only a temporary solution as much of their data is still missing.

Let me know if anymore information is needed, and I can provide you with it.

share|improve this question
up vote 0 down vote accepted

Disabling all of DFS leaves the files in Dfsprivate intact so that the script can recover it without additional data being added to the backlog. It seems to be the only way to recover the data, and just about the fastest. The only way to do it faster might be to write my own script to copy multiple files simultaneously (assuming our disk I/O isn't maxed out, which I don't think it is because we are not copying that fast at all...), which the provided script does not do for fairly obvious reasons given the implementation (it would start copying files quicker than they could be completed as there is no scheduling, etc).

Another option might be to boot up in a liveCD environment on linux and write a script to parse the Preexisting.xml and then call dd for the file transfers because dd is just a beast. Yeah, I'm doing that next time, if possible.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.