This object monitors the creation and updating of replicated folder cluster resources, and creates a Critical alert if DFS Replication cannot create or update the cluster resource for a replicated folder. It does so by looking for the presence of DFS Replication Event 9001.
An unhealthy state of this monitor indicates that DFS Replication couldn’t create or update a cluster resource for a replicated folder. This can occur if the clustered file server instance isn’t online or if storage resources are unavailable.
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 confirm that a cluster resource is online using the Windows interface
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 confirm that a cluster resource is online 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.
Confirm that the storage resource is online
Confirm that the appropriate storage resource is online. To do so, open Failover Cluster Manager on the affected server and confirm that the status of the appropriate disk is Online. If it isn’t, select the disk and then click Bring this resource online.
This monitor automatically resets to the healthy state after this issue is resolved.