File Replication service does not replicate a file in a Distributed File System topology if the file is moved between folders (839605)



The information in this article applies to:

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server

SYMPTOMS

When you use File Replication service (FRS) to replicate information that is in a Microsoft Distributed File System (DFS) topology, a file is not replicated if the file is moved from one replicated DFS link to another replicated DFS link. This behavior occurs if both of the replicated DFS links are on the same server.

For example, Server1 has the following two replicated DFS links:
  • \\Server1\Link1
  • \\Server1\Link2
When you move a file from \\Server1\Link1 to \\Server1\Link2, the file is not replicated.

CAUSE

This issue occurs because the DFS link folders reside on the same volume. If the DFS link folders reside on the same volume, FRS does not recognize an update sequence number (USN) change. Therefore, the file is not replicated. FRS requires a USN entry to stage a file for replication.

RESOLUTION

To resolve this issue, configure the DFS link folders on different volumes.

MORE INFORMATION

The USN change journal provides a persistent log of all the changes that are made to the files that are on a volume. As files, folders, and other NTFS file system objects are added, modified, or deleted, NTFS records the change to the USN change journal. There is one USN change journal for each volume on a computer.

For additional information about FRS, click the following article number to view the article in the Microsoft Knowledge Base:

840675 Configuration and operational recommendations for the File Replication service in Windows Server 2003 and Windows 2000 Server

Also, see the "FRS Technical Reference." To do this, visit the following Microsoft Web site:

Modification Type:MajorLast Reviewed:8/21/2004
Keywords:kbtshoot kbprb KB839605 kbAudITPRO