Excessive Replication and High CPU and Disk Usage by
FRS event ID 13567 occurs when FRS
detects and suppresses excessive replication. Excessive replication
is typically caused by applications that change all or most of the
files in a replica tree on a regular basis without actually
altering the file content — in other words, these applications
perform writes that do not change the file. Because FRS monitors
the USN journal for changes, if FRS finds a change, then it
replicates the file. Excessive replication can cause FRS to use
excessive amounts of disk I/O or CPU as it tracks this activity.
Common cases of applications that cause extensive replication are
those that rewrite the existing ACL (file security policy,
antivirus software) or rewrite the existing file (defragmentation
The effect of excessive replication depends on the version of
FRS being used:
From Windows 2000 Service Pack 3 and later and Windows
Server 2003, FRS event ID 13567 records that this kind of
non-change was suppressed to prevent unnecessary replication.
However, the underlying cause should still be investigated, because
it is causing unnecessarily high disk and CPU usage on that replica
For Windows 2000 versions prior to SP3, excessive
replication generators were the most common cause of replication
backlogs and for staging directories to fill up. On these versions
of FRS, administrators should investigate this problem
High CPU usage without event ID 13567 can be caused in the
The number of connections is not balanced between hub
There are more than 50 incoming connections to the server.
The KCC chose a server that was not intended to be a hub
Other applications, such as Exchange or SQL Server, are running
on the server.
The staging directory is too small, which causes staging files
to be regenerated and increases CPU and disk usage.
Identify the cause of excessive replication and high CPU and
disk usage by doing the following:
If the connections aren’t balanced or the server has too many
simultaneous incoming connections, adjust the schedule by using the
guidelines in Optimizing FRS
If high CPU usage is caused by other applications, upgrade the
hardware or move the application to another server.