windows DFS 文件服务，目前发现大量文件从文件夹下被系统删除

Question

您好，环境为4台server 2019 DFS 集群。目前发现大量文件从 DFS 文件夹目录下被系统删除（文件夹没有被删除的情况）。

问题发生前，替换过一台DFS主机。新旧设备通过 fastcopy 进行数据的快速拷贝。请问有可能是什么原因。如何排查

Answer 1

Hello,

Thank you for posting question on Microsoft Windows forum!

Based on your query of unexpected file deletions in your DFS cluster after replacing a host and using FastCopy for data migration. This situation could be caused by several factors:

Possible Causes:

1. DFS Replication Issues: The new server may not have properly synchronized with the existing DFS infrastructure, causing replication to misinterpret changes and trigger deletions.
2. File Permissions & Ownership Conflicts: If FastCopy altered file attributes (such as timestamps or ownership settings), DFS Replication might treat certain files as outdated and remove them.
3. Staging Folder or Conflict Resolution Behavior: DFS replication uses a staging folder; if it runs into conflicts, it may automatically clean files deemed unnecessary.
4. Accidental Synchronization with an Empty Folder: If the new DFS server had an empty folder during synchronization, older DFS versions might mistakenly remove files from the entire cluster.
5. FastCopy Settings: Some FastCopy configurations (like mirroring mode) could inadvertently delete files on the target system during the copying process.

Potential Troubleshooting steps:

1.Check Event Viewer Logs:

• Look for DFS Replication events in Event Viewer under Applications and Services Logs → DFS Replication.
• Search for warnings or errors related to file deletions. Like Event ID 4412, 4660, 4663.

2.Verify DFS Replication Status:

• Run following command to show any ongoing replication activities and conflicts.
• dfsrdiag.exe ReplicationState

3.Examine FastCopy Settings:

• Ensure FastCopy wasn't configured in mirror mode, which could have deleted files rather than syncing them.

4.Check for FastCopy Logs (if available):

• Did FastCopy generate any logs during the copy process? These might indicate errors or skipped files.
• Verify if FastCopy preserved all attributes (timestamps, permissions, ownership, alternate data streams). Tools like Robocopy with the /COPYALL flag are generally preferred for this type of data migration.

5.Review the Old Server:

• Do the files exist on the old server that was replaced? This is a critical piece of information. If they do, that indicates the copy process was the problem.

6**.DFSR Health Report**:

• Generate a health report for your replication group. This can provide valuable insights into replication status, backlogs, and errors.
• Open DFS Management, navigate to your replication group, right-click, and select Create Health Report.

7.Restore Files (if needed):

• If DFS Replication deleted files, check Previous Versions or backup solutions.

You can refer to the below article for more troubleshooting information.

• https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/troubleshoot-file-replication-service-ditributed-file-system

Hope the above information is helpful!