Monday, November 30, 2015

Create a Diagnostic Report

  1. In the console tree of the DFS Management snap-in, under the Replication node, right-click the \\domain\Public\Software\Tools replication group, and then clickCreate Diagnostic Report.
  2. Follow the steps in the Diagnostic Report Wizard
1-Type of Diagnostic Report or Test:

Accept the defaults.

2-Path and Name:

Accept the defaults.

3-Members to Include:

Accept the defaults.

4-Options:

Ensure that Yes, count backlogged files in this report is selected, select the server that has the most up-to-date files from Reference Member, and then select the Count the replicated files and their sizes on each member check box.

5-Review Settings and Create Report:

Click Create to create the diagnostic report.

6-Confirmation:

The wizard closes automatically, and the diagnostic report appears.

Review the health report created for the Tools replication group. In particular, take a look at the following sections:
  • Note the DFS Replication bandwidth savings. This savings will change over time as files are added and changed.
  • Review any errors or warnings, if any, for the members. These are typically event log errors that appear in the member's respective DFS Replication event log.
  • In the informational section for each member, review the replicated folder status (the status will be "Normal" after initial replication is complete) and other information. Notice that the primary member will show different statistics from the non-primary member; this is because data originated from the primary member and replicated to the non-primary member during initial replication.
The Diagnostic Report Wizard creates the health report by default. Note that you can set the wizard to perform the following operations as well:
  • Run a propagation test.
  • Create a propagation report.
A propagation test measures replication progress by creating a test file in a replicated folder. A propagation report provides information about the replication progress for the test file created during a propagation test.

No comments:

Post a Comment