a partner induced version vector scan that have been sent to the outbound partners of this replica set member.4661The number of remotely originated file updates initiated on this replica set member.4663The number of remotely originated file updates retired on this replica set member.4665The number of remotely originated file updates that were aborted. Most likely because of an attempt to fetch a staging file from an inbound partner and the partner no longer has the file because it has been deleted.4667The number of remotely originated file updates that were retried for any reason on this replica set member.4669The number of remotely originated file updates that were retried due to a stage file generation problem on this replica set member.4671The number of remotely originated file updates that were retried due to a stage file fetch problem on this replica set member.4673The number of remotely originated file updates that were retried due to a stage file install problem on this replica set member. Most likely caused by a sharing conflict trying to access the target file or directory.4675The number of remotely originated file updates that were retried due to a problem during the final target file rename or delete operation on this replica set member. Most likely caused by a sharing conflict trying to access the target file or directory.4677The number of remotely originated file updates that encountered a name space collision on this replica set member. Most likely caused by simultaneous create of a file or directory with the same name on more than one replica set member.4679The number of remotely originated file updates that were propagated to the outbound log of this replica set member. The update remains pending in the outbound log until it has been delivered to all outbound partners.4681The number of remotely originated file updates that have been sent to the outbound partners of this replica set member.4683The number of remotely originated file updates that have been received by this replica set member. Note that depending on the replication topology it is possible for the same file update to be sent from multiple inbound partners. However, only one will send the actual file data.4685The number of remotely originated file updates that were dampened because the update was already delivered by another member.4687The number of pending outbound file updates that were dampened because the outbound partner has already received it from another source.4689The number of times FRS has initiated a read on the NTFRS change log. Each volume has its own change log.4691The number of NTFS change log records examined by FRS.4693The number of NTFS change log records accepted by FRS for further processing.4695The number of NTFS change log records skipped by FRS. Most likely because the cha