This object monitors the resumption of replication following a backup or restore operation on a volume containing a replicated folder. It does so by looking for the presence of DFS Replication Event 1106. If the replication fails to resume, this monitor creates a Critical alert.
An unhealthy state of this monitor indicates that the replication failed to resume after a backup application used the Volume Shadow Copy Service (VSS) to back up or restore a volume containing a replicated folder. This can occur if the backup application is still accessing files used by DFS Replication.
Wait for the DFS Replication service to start
No action is required. DFS Replication will attempt to start the DFS Replication service 30 minutes after it stops.
To manually start the DFS Replication service from the Operations console, click Start DFS Replication Service.
To manually start the DFS Replication service from a command prompt, open an elevated command prompt window and then type the following command, where <servername>is the UNC path of the affected server:
Sc <servername> start dfsr
Note: To start a service, you must be a member of the local Administrators group on the affected server. You can also start services using the Services snap-in, the Windows PowerShell Start-Service cmdlet, or command-line tools such as net start.
This monitor automatically resets to a healthy state when the issue is resolved.
To verify that the DFS Replication service is running from the Operations console, Query DFS Replication Service Status.
To do so from a command prompt, open a command prompt window and then type the following command:
sc <servername> query dfsr
Note: To query the service state, you must be a member of the local Administrators group on the affected server.