The nonauthoritative restore (D2) is used to bring the local FRS replica set back up to date with its partners. Nonauthoritative restores are often necessary to resolve the following issues:
The nonauthoritative restore process brings a replica member up to date by comparing all the local files in a replica set with the ones of the upstream partners. After you set the Burflag to D2 and restart the service, FRS will move all the data into a "pre-existing" directory and then start to compare the file IDs and the files’ MD5 checksums from the upstream partner with the local ones. If the file ID and the MD5 checksum match, FRS copies this file from the pre-existing directory into its original location. If they don’t match, then FRS copies the new file from the partner. Before Windows 2000 SP3, this work is performed with each of upstream partner at once; with Windows 2000 SP3 and later and Windows Server 2003, this process is performed sequentially — one partner at a time.
To perform a nonauthoritative restore, use the following procedure:
To perform a nonauthoritative restore
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\ Backup/Restore\Process at Startup
When the FRS service restarts, the following actions occur:
The placement of files in the NtFrs_PreExisting_See_EventLog folder on reinitialized members is a safeguard in FRS designed to prevent accidental data loss. Any files destined for the replica that exist only in the local PreExisting folder and did not replicate in after the initial replication can then be copied to the appropriate folder. When outbound replication has occurred, delete files in the PreExisting folder to free up additional disk space.
For more information about performing a nonauthoritative restore, see article 290762, "FRS: Using the BurFlags Registry Key to Reinitialize File Replication Service Replica Sets" at http://support.microsoft.com/?id=290762.