Article ID: 811217 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
This article describes changes to the File Replication service (FRS) in a Windows 2000 post-Service Pack 3 (SP3) hotfix that improves the robustness of the service. You must install Windows 2000 SP3 before you install this hotfix. This hotfix includes multiple fixes.
Fixes in This Release
Glossary of Terms Used in This Article
Change Order (CO)When a change is made to a file or folder on a replica member, the information about that change (such as the name of the file or the ID of the member) is used to construct a message that is called a "change order." The change order is sent to the member's outbound partners. If they decide to accept the change, the partners request the associated staging file. After installing the change on their individual replica tree, the partners propagate the change order to their outbound partners.
File GUIDThe file GUID identifies the file or folder. It is created and managed by the replication service. It, with the replication version number and event time, is stored in the File ID table in the FRS database. Corresponding files and folders across all replica-set members have the same file GUID.
File ID TableThis is a table in the FRS database that contains an entry with version and identity information for each file and folder in the replica tree.
File Replication ServiceFRS is a multiple-threaded, multiple-master replication engine. Windows 2000-based domain controllers and servers use FRS to replicate system policies and logon scripts for client computers that are running Windows 2000 and earlier versions of Microsoft Windows. FRS can also replicate content between Windows 2000-based servers that host the same fault-tolerant Distributed File System (DFS) root or link replicas.
Identity-Based ReplicationAll objects in a replica tree have a unique ID assigned to them. In FRS, the NTFS file system Object ID attribute that contains a 16-byte GUID is used. The same object on all replica members has the same object ID. This permits unambiguous location information for the object by using the object's GUID and the corresponding parent GUID.
Replica PartnerThe immediate upstream and downstream partners of a replica member are referred to as its replication partners. Upstream partners are also referred to as inbound partners. Downstream partners are also referred to as outbound partners.
Replica SetIn FRS, two or more computers that are configured to replicate the contents of a file folder. The individual computers are referred to as replica members.
Update Sequence NumberThe NTFS file system maintains a monotonically increasing sequence number for each volume that is called an update sequence number (USN). The USN is incremented every time a modification is made to a file on the volume.
Version VectorThis is a vector of USNs, with one entry per replica set member. All change orders carry the originator GUID of the originating member and the associated USN. As each replica-set member receives the update, it tracks the USN in a vector slot that is assigned to the originating member. This vector describes whether the replica tree is current with each member. The version vector is then used to filter updates from inbound partners that may have already been applied. The version vector is also delivered to the inbound partner when the two members join. When a new connection is created, the version vector is used to scan the File ID table for more recent updates that are not seen by the new outbound partner.
For information about how to obtain this post-SP3 Ntfrs.exe release, see the following Microsoft Knowledge Base article:
(http://support.microsoft.com/kb/811370/EN-US/ )Issues That Are Fixed in the Post-Service Pack 3 Release of Ntfrs.exe
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.