DFS-R: Replication Error Status Monitor

  • ID:  Microsoft.Windows.FileServer.DFSR.ReplicationStoppedOnErrorMonitor
  • Description:  This object monitors replication and creates a Warning alert if replication stops due to an error.
  • Target:  Replicated Folder
  • Enabled:  Yes

Operational States

Name State Description
FirstEventRaised Warning  
SecondEventRaised Success  

Alert Details

Monitor State Message Priority Severity Auto Resolution
FirstEventRaised (Warning) DFS-R: Replication Stopped Due to an Error Medium Warning Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

This object monitors replication and creates a Warning alert if replication stops due to an error. It does so by checking for the presence of DFS Replication Event 4004 in the DFS Replication event log.

Causes

An unhealthy state of this monitor indicates that replication has stopped on a replicated folder due to an error. This can occur for a number of reasons, including the following:

  • The volume hosting the staging folder doesn’t have sufficient available disk space, or the staging folder exceeds a folder quota.

  • The local path of the replicated folder on a particular member has changed or the volume storing the replicated folder is offline.

  • DFS Replication doesn’t have the appropriate permissions on the replicated folder.

  • The DFS Replication resource on a failover cluster is offline or in a Failed state.

More information about the specific reason which caused this event to be triggered can be found in the event text itself.

Resolutions

Increase available disk space

To resolve this issue, use the following procedure:

1. Check the error listed in the alert description in the Operations console. The following error is listed when there is not enough available disk space: Error 112 (There is not enough space on the disk.)

2. Increase the available disk space on the volume, increase the size of the volume, or increase the folder quota set on the folder containing the staging folder.

To manually check the amount of available disk space, open a command prompt window and type the following command, where <servername> is the name of the server hosting the affected folder and <domain\user> is your user name:

WMIC /node: "<servername>" /user: <domain\user> volume list status.

After freeing up space, restart the DFS Replication service.

Adjust DFS Replication quotas

You can edit the quota size of the staging folder and the Conflict and Deleted folder to reduce the disk space requirements of DFS Replication. To do so, see Edit the Quota Size of the Staging Folder and Conflict and Deleted Folder (http://go.microsoft.com/fwlink/?LinkId=186944).

Important: 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 effectively limit the number of concurrent transfers with partners. Increasing the size of the staging folder and the Conflict and Deleted folder can increase replication performance and the number of recoverable conflicting and deleted files.

Correct the replicated folder permissions

If the DFS Replication service doesn’t have Full Control permissions to the replicated folder and staging folder, replication will fail. To resolve this issue, grant the local System account Full Controlpermissions to the replicated folder and subfolders as well as the staging folder (if located outside of the replicated folder).

Fix the path of the replicated folder

To resolve this issue, confirm that the local path of the replicated folder is available, and bring the volume online if necessary.

If the path has changed, you must remove the server’s membership in the replication group and recreate it. Doing so requires membership in the Domain Admins group or delegated permissions.

Confirm that the failover cluster resource is online

If the server is a member of a failover cluster, confirm that the DFS Replication resource is online. To do so, open Failover Cluster Manager on the affected server and confirm that the status of the appropriate clustered file server instance is Online. If it isn’t, select the appropriate resource and then click Bring this service or application online.

To do so by using Windows PowerShell™, open a Windows PowerShell command prompt window while logged on with an account that is a member of the local Administrators group on the failover cluster, and then type the following command, where <replicatedfolder_rootpath> is the root path of the replicated folder hosted by the clustered file server instance:

get-wmiobject -namespace root\mscluster -class MSCluster_Resource -Filter "name='DFSR <replicatedfolder_rootpath>'"

If the resource is online, the value of the State field should be 2.

Important: Add a second backslash (\) before any backslashes in the replicated folder root path. For example d:\shares\public would be written as d:\\shares\\public.

Verification

After replication completes, this monitor automatically resets to a healthy state.

To manually confirm that replication is healthy, run a propagation test on the affected folder by using DFS Management or the following commands, where <ReplicationGroup>is the name of the replication group and <ReplicatedFolder>is the name of the replicated folder:

dfsrdiag propagationtest /rgname:"<ReplicationGroup>" /rfname:"<ReplicatedFolder>" /testfilename:DFS-RTestFile.xml

dfsrdiag propagationreport /rgname:"<ReplicationGroup>" /rfname:"<ReplicatedFolder>" /testfilename:DFS-RTestFile.xml /reportfilename:c:\DFS-R_Report.xml

External References
This monitor does not contain any external references.

See Also for Windows Server File & iSCSI Services Management Pack


Downloads for Windows Server File & iSCSI Services Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED