Chat now with support
Chat with Support

Active Administrator 8.6.3 - Web Console User Guide

Active Administrator Web Console Overview Active Directory Health Alerts Notifications Active Directory Health Check
Using the Health Check landing page Creating a Health Check Setting options for Health Check tests Purging Health Check History Health check tests
Forest tests Domain tests Domain controller tests Site tests
Active Directory Topology Reports Network Operations Center

DFSRS % processor time

Indicates that the CPU for the Distributed File System Replication (DFSR) service is too busy.

Category
•
Performance Counters
Data collector
•
Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
•
Required permissions: When monitored locally and remotely, only domain user privilege is required and the user must be a part of the Performance Logs user group.
Description

Tests the CPU utilization by the DFSR service to see if the utilization is above the configured threshold.

Resolution

Wait for a while to see if the error clears itself. For example, a high CPU utilization that occurs during an initial replication is transitory in nature.

Review the system configuration and tune the environment to optimize DFSRS performance as described in these references:

•
Common DFSR Configuration Mistakes and Oversights

DFSRS conflict area disk space

Detects that the amount of disk space allocated for conflict files during replication is less than or equal to the specified threshold.

Category
•
General
Requirement
•
Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
•
Required permissions: When monitored locally and remotely, only domain user privilege is required and the user must be a part of the Performance Logs user group.
Description

If the ConflictandDeleted folder runs out of space, DFS Replication removes older conflicting or deleted files to free up disk space, which might temporarily decrease replication performance.

If a staging folder quota is configured to be too small, DFS Replication might consume additional CPU and disk resources to regenerate the staged files. Replication might also slow down because the lack of staging space can limit the number of concurrent transfers with partners. Increasing the size of the staging folder and the ConflictandDeleted folder can increase replication performance and the number of recoverable conflicting and deleted files.

Resolution

Delete files from the ConflictandDeleted folder, or increase the quota of the ConflictandDeleted folder for the appropriate replicated folder(s).

DFSRS conflict files generated

Indicates that there are conflicted files in ConflictAndDeleted folder assigned to the replicated folder.

Category
•
General
Requirements
•
Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
•
Required permissions: When monitored locally and remotely, only domain user privilege is required and the user must be a part of the Performance Logs user group.
Description

This test enables administrators to keep track of the number of replication conflicts generated for replicated folders on the monitored computer. Monitoring the space utilization of the Conflict and Deleted area helps ensure that there is enough space to store replication conflicts and files deleted from replicated folders on the monitored computer. You can view a log of conflict files and their original file names by viewing the ConflictandDeletedManifest.xml file in the DfsrPrivate folder.

Frequent conflicts indicate that files in a replicated folder are frequently being modified on multiple servers in a short period.

Resolution

In general, resolution of this condition involves deciding whether a conflict object contains useful information, moving that information into a different directory object, and then deleting the object.

DFSRS private bytes

Indicates that the virtual memory allocated to the Distributed File System Replication (DFSR) service is too high.

Category
•
Performance Counters
Requirements
•
Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
•
Required permissions: When monitored locally and remotely, only domain user privilege is required and the user must be a part of the Performance Logs user group.
Description

Tests the DFSRS private bytes performance counter on the domain controller for the DFSR service to see if the value in the performance counter goes above the configured threshold for a period exceeding the configured duration.

Resolution

Review the system configuration and tune the environment to optimize DFSRS performance as described in these references:

•
Common DFSR Configuration Mistakes and Oversights
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating