Create Support Procedures and Train the Operations Staff

All administrators who add or change content in FRS replica trees should understand the implications of multimaster replication, including the following points:

• FRS supports a multi-master file replication model in which any computer accepts and replicates changes to any other computer taking part in the replication configuration.
• Administrators should be aware of the bandwidth impacts of changes that they make in the replica tree.
• Any changes made to a file in a replica tree will occur on all other members of the replica set. Administrators must never attempt to help FRS by making the same change on other members of the replica set.
• If an administrator makes a change to a file, and it later seems the changes have been reversed, then it might be a case of "dueling administrators;" that is, another operator is making changes in the same file and has overwritten the earlier changes. In this case, administrators should try to contact other operators to see if this is the case.
• Any files that administrators delete on one member will also be deleted on all other members.
• If administrators rename a file or folder so that it is moved out of the replica tree, FRS treats that as a delete on the other replica members.
• If two operators create identically named folder at the same time (or even before the first created directory has reached the other computer) on the same server, then morphed folders occur. Morphed folders occur when two or more identically named folders on different servers are added to the replica tree. FRS identifies the conflict during replication, and the receiving member protects the original copy of the folder and renames (morphs) the later inbound copy of the folder. The morphed folder names have a suffix of "_NTFRS_xxxxxxxx," where "xxxxxxxx" represents eight random hexadecimal digits.