Article ID: 290762 - View products that this article applies to.
This article was previously published under Q290762
OverviewFRS is a multi-threaded, multi-master replication engine that Windows Server 2003 and Windows 2000 domain controllers use to replicate system policies and logon scripts for Windows Server 2003, Windows 2000, and earlier-version clients. In Microsoft Windows NT, the LanMan Replication (LMREP) service handled replication. FRS replaced LMREP in Windows 2000. You can also use FRS to replicate content between Windows 2000 servers that host the same fault-tolerant Distributed File System (DFS) roots or child node replicas.
When you deploy Windows-based domain controllers or member servers that use FRS to replicate files in SYSVOL or DFS shares, you may have to restore or reinitialize individual members of a replica set if replication has stopped or is inconsistent. In some scenarios, you may have to rebuild the whole replica set from scratch.
FRS BurFlagsregistry key is used to perform authoritative or nonauthoritative restores on FRS members of DFS or SYSVOL replica sets.
Note System state backups of Windows member servers and domain controllers do not include the FRS database that maintains a mapping of files that are held in local FRS trees and a master list of FRS files. For more information about exclusions for Ntbackup.exe, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/233427/ )Files and folders that are not backed up when the Ntbackup.exe tool is used in Windows Server 2003, Windows XP, and Windows 2000
Restoring FRS replicasThe global
BurFlagsregistry key contains REG_DWORD values, and is located in the following location in the registry:
The most common values for the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
BurFlagsregistry key are:
BurFlagsrestores at the same time as you restore data from backup or from any other known good source, and then restart the service.
Nonauthoritative restoreNonauthoritative restores are the most common way to reinitialize individual members of FRS replica sets that are having difficulty. These difficulties may include:
Members who are nonauthoritatively restored must have inbound connections from operational upstream partners where you are performing Active Directory and FRS replication. In a large replica set that has at least one known good replica member, you can recover all the remaining replica members by using a nonauthoritative mode restore if you reinitialize the computers in direct replication partner order.
If you determine that you must complete a nonauthoritative restore to return a member back into service, save as much state from that member and from the direct replication partner in the direction that replication is not working. This permits you to review the problem later. You can obtain state information from the FRS and System logs in the Event Viewer.
Note You can configure the FRS logs to record detailed debugging entries. For more information about how to configure FRS logging, click the following article number to view the article in the Microsoft Knowledge Base:
221111To perform a nonauthoritative restore, stop the FRS service, configure the
(https://support.microsoft.com/kb/221111/ )Description of FRS entries in the registry
BurFlagsregistry key, and then restart the FRS service. To do so:
Authoritative FRS restoreUse authoritative restores only as a final option, such as in the case of directory collisions.
For example, you may require an authoritative restore if you must recover an FRS replica set where replication has completely stopped and requires a rebuild from scratch.
The following list of requirements must be met when before you perform an authoritative FRS restore:
BurFlagsregistry key, and then restart the FRS service. To do so:
Global vs. replica set specific reinitializationThere are both global- and replica set-specific
BurFlagsregistry keys. Setting the global
BurFlagsregistry key reinitializes all replica sets that the member holds. Do this only when the computer holds only one replica set, or when the replica sets that it holds are relatively small.
In contrast to configuring the global
BurFlagskey, the replica set
BurFlagskey permits you to reinitializes discrete, individual replica sets, allowing healthy replication sets to be left intact.
BurFlagsregistry key is found in the following location in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup / Restore\Process At Startup
This key can contain the same values as those that are discussed earlier in this article for authoritative and nonauthoritative restores.
You can locate the replica set specific
BurFlagsregistry key by determining the GUID for the replica set that you want to configure. To determine which GUID corresponds to which replica set and configure a restore, follow these steps:
Considerations before you configure authoritative or nonauthoritative restores of FRS membersIf you configure an FRS member to complete an authoritative or nonauthoritative restore by using the
BurFlagsregistry subkey, you do not resolve the issues that initially caused the replication problem. If you cannot determine the cause of the replication difficulties, the members will typically revert back to the problematic situation as replication continues.
A detailed breakdown on FRS interdependencies is beyond the scope of this article, but your troubleshooting should include the following actions:
(https://support.microsoft.com/kb/249256/ )How to troubleshoot intra-site replication failures
This article discusses the
FRS BurFlagsregistry key that the Microsoft Windows 2000 File Replication service (FRS) uses.
For more information about how to use System Start Restoration to retrieve files that are unavailable on any FRS replication partner, click the following article number to view the article in the Microsoft Knowledge Base:
811219For more information about FRS, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/811219/ )FRS: Recovering FRS objects and files by using system state restores
(https://support.microsoft.com/kb/266679/ )Pre-staging the File Replication service replicated files on SYSVOL and Distributed file system shares for optimal synchronization
(https://support.microsoft.com/kb/315457/ )How to rebuild the SYSVOL tree and its content in a domain
Article ID: 290762 - Last Review: February 28, 2007 - Revision: 5.2