Restoring Files on a Member Server

Restoration on a member server is always authoritative because it is not FRS-aware. In other words, it assumes that there are no other copies of the restored files on other servers. As a result, the replica being restored replicates its data to other members of the replica set.

Note that an authoritative restore is simply the restoration of a file onto a member that is actively replicating files. It does not produce a mirror image of the backup tape content in the replica share. As an example, any new files that were created in the replica share after the backup tape was created are not deleted from the replica share. To perform a true authoritative restore of a replica share so that it mirrors the content from the backup tape, the user must first delete all files in the replica share and then restore the data from the backup tape.

To perform a nonauthoritative restore of a Dfs replica

1. Remove the failed member from the replica set.
2. Disable replication on the host server.
3. Repair the faulty member. For example, replace a disk drive that has failed.
4. Add the member back as a new replica. Do not specify it as initial master when you enable replication unless you want to do an authoritative restore.

   Note that initial master is only relevant when this member is the only member (that is, the first member) in the replica set. In this case, FRS enumerates the replica share and preloads its database with information about each file and folder. In addition, FRS assigns file object IDs to every file and folder in the replica share. If this member is not the only member in the replica share, FRS always treats the addition of a new member as nonauthoritative as described previously.

© 1985-2000 Microsoft Corporation. All rights reserved.