Monitoring Performance
The two performance objects associated with File Replication service are listed in Table 18.1. The counters for these objects are available for each replica set managed by FRS while the service is running.
Table 18.1 FRS Performance Objects
Object |
Description |
|---|---|
FileReplicaConn |
Performance statistics for the Replicaconn object that defines replica connections to Dfs roots. |
FileReplicaSet |
Performance statistics for the Replicaset object that defines a replica set. |
Important FileReplicaSet counters that you can monitor to verify FRS performance are listed in Table 18.2.
Table 18.2 Key FileReplicaSet Counters
Counter |
Description |
|---|---|
Change Orders Received |
Number of change notifications received from inbound partners. |
Change Orders Sent |
Number of change notifications sent out to outbound partners. |
File Installed |
Number of replicated files installed locally. |
KB of Staging Space Free |
Amount of free space in the staging directory used by FRS to temporarily store files before they are replicated. The default staging space is 660 megabytes (MB). |
KB of Staging Space In Use |
Amount of space in the staging directory currently in use. If the staging directory runs out of space, replication stops. |
Packets Received |
Amount of data received locally. These packets can be change notifications, file data, or other command packets. |
Packets Sent |
Similar to packets received. |
USN Records Accepted |
Number of records that are accepted for replication. Replication is triggered by entries written to the NTFS change journal. FRS reads each file close record from the journal and determines whether to replicate the file. |
You can also observe FRS activity using Event Viewer. Select File Replication service , and then filter events by time and date or by type of event such as information, warnings, or errors. Right-click the individual message, and then click Properties to display details about an event.