The Storage Team Blog about file services and storage features in Windows and Windows Server.
My previous blog post explained how to configure the DFS Replication management pack. The backlog monitoring feature of the management pack is disabled by default and requires some additional configuration. This blog post explains how to enable backlog monitoring using the DFS Replication management pack and also describes how to override some of the default configuration settings in the management pack.
Configure the DFS Replication monitoring profile
In Operations Manager 2007, Run As Profiles and Run As Accounts are used to select users with privileges that are needed to run rules, tasks, and monitors. The backlog monitoring discovery script included in this management pack queries the DFS Replication WMI provider on all monitored computers. To do this, it needs to run in the context of a privileged monitoring account. This management pack includes a privileged monitoring profile called DFS Replication Monitoring Account. You need to add a Run As account to this profile to monitor the replication backlogs.
The first step is to create a Run As account that has the requisite privileges to connect to the DFS Replication WMI provider on all monitored computers. The WMI provider does not allow non-administrative access and therefore, you need to ensure that the Run As account has at the very least local administrator privileges for each of the monitored computers.
After the Run As account has been created, right click on the Run As Account in the Accounts pane and select its properties. In the Run As Account Properties – DFS Replication Monitoring Users dialog, select the computers to which these credentials are to be distributed.
The next step is to associate this Run As account with the privileged monitoring profile included in the DFS Replication management pack. This configuration step ensures that the replication backlog discovery script has the required privileges to connect to the WMI provider for DFS Replication on monitored computers and retrieve replication backlogs. To add the Run As account you just created to the DFS Replication Monitoring Account Run As Profile on System Center Operations Manager 2007 R2, perform the following steps:
Enable backlog monitoring
This feature enables administrators to keep track of replication backlogs on monitored computers. Backlog tracking is performed by a discovery script that queries the WMI provider for the DFS Replication service on monitored computers. This discovery script is disabled by default, thereby disabling the monitoring of replication backlogs by default. This section provides instructions for enabling backlog monitoring. After backlog monitoring is enabled, the Backlog Monitoring dashboard view will be populated with replication backlogs that are retrieved from all monitored computers.
To enable backlog monitoring for the DFS Replication Management Pack, perform the following steps:
Note: We highly recommend that you store all override settings in a separate management pack. By default, if you do not choose to store settings in a separate management pack, all overrides and custom configuration settings are stored in the Default Management Pack.
Note that it will take some time before the Backlog Monitoring view is populated with replication backlogs that are retrieved from the monitored computers.
Configure how often discovery rules are run
The following table lists the default frequency with which various discovery rules that are included in the DFS Replication Management Pack are run. Evaluate these default settings to determine whether the configured default frequencies are appropriate for your environment. If a configured default frequency is not appropriate for your environment, consider overriding the corresponding discovery rule and tuning the frequency as appropriate.
Discover replication backlogs on monitored computer.
Discover replication groups on monitored computer.
Discover DFS Replication settings on monitored computer.
Discover volumes hosting replicated folders on monitored computer.
Discover replicated folders on monitored computer.
To tune the configured default frequency for discovery rules that are included in the DFS Replication Management Pack, perform the following steps:
I have done everything here and see all data except for the actual Backlog Monitor. I did this in the morning and it's now past 5:00 p.m. and still nothing... Is there something else that needs to be configured?
Adam, have you:
a) created an override and enabled the backlog monitoring feature?
b) Created the run as account and added a user with administrative privileges?
One of the reasons for the backlog monitoring discovery script not working is if the user does not have the right privileges to make WMI queries.
You can also check the eventlogs on the SCOM server or on the monitored computer to see if the backlog discovery script is failing.
Is it possible to identify specifically chronic 4302 and 4304 errors and identify specific files using SCOM? For example identifying files where DFS-R is to be used as part of a share backup solution but files have persistent locks because the application or user retains a lock and the file never gets replicated or gets replicated too infrequently. I haven't tried yet... just hoping for guidance. Thanks
Monitoring DFS-R BackLogs with OpsMgr