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 have DFS setup using the DFS Management Administrator Tool. I turned on replication in the Distributed File System Administrator Tool as well and this morning we lost tons of files from that share. Please explain to me why this was wrong and if there is anything that can be done to repair it. (No, we don't have backups. We have some shadow copies, but those were deleted as well. We have been using DFS as its own backup)

share|improve this question
up vote 6 down vote accepted

Before I say anything else,

DFSR is not a backup! Don't use it this way, or you'll get burned again eventually.

So for clarification, you had Server1 with a set of files, and Server2 without that set of files. You added a folder target on Server2, and then created a replication group between the two servers?

In theory if it was done as above then Server2 would have been in an initial replication state, received the files from Server1, and then made active.

Most likely what happened is Server2 was taken as authoritative during the replication group setup, which wiped out the share on Server1.

I would check the DFSR event log on both servers, looking for this event:

Event ID 4412 - The DFS Replication service detected that a file was changed on multiple servers.

This event will describe which files were removed, and where they now exist. Your conflict and deleted folder is typically with the DFS share, in a hidden folder named DFSRPrivate. Note: By default this folder will only hold 660MB of files, and then rotate that space afterwards.

Also check the Pre-Existing folder within the DFSRPrivate folder, as your files may be there too.

share|improve this answer
+1 for "DFSR is not a backup!". +5 if I could. DFS-R is a nice way to aggregate data from multiple locations into a single location to perform backups, but it's not a backup itself. – Evan Anderson Mar 11 '11 at 16:33

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.