Distributed File System Replication (DFSR) has come a long way from the time it was launched in Windows 2003 R2. With every new release of the operating system (Windows 2003 R2, Windows 2008 and then Windows 2008 R2), we have seen a lot of good changes being incorporated in the DFSR
In this post I will discuss the Health Report option available in Windows 2008 R2. Health Report option was available in Windows 2003 R2 and in Windows 2008 as well
In this example, we have configured three Replication Groups (RGs). We will create a Health Report for the Replication Group named "Data1"
To create a Health Report, Right Click on the RG for which you want to generate the health report and choose the option "Create Diagnostic Report"
On the first screen, we get three options
1. Health Report
2. Propagation Test
3. Propagation Report
Propagation Test & Propagation Report options were not available in Windows 2003 R2 or in Windows 2008 R2 through the "Health Report" Snap-In. It was a command line option. This is a new addition in Windows 2008 R2 DFSR. We will talk about Propagation Test & Propagation Report in a separate post.
For now, Lets choose the option "Health Report"
On this screen , you can change the path where this report will be saved when completed and the name of the health report. By default, the location of the health report is in C:\DFSReports and the Name of the Health Report will be Name of the RG><Date of Report><Time of Report>
A replication group can have multiple servers involved in replication. Here you can choose for which all servers involved in replication for this particular RG the report should run.
This gives the you following options:
1. Count Backlogged Files
2. Count the Replicated Files and their size on each member
Count Backlogged Files: Backlogged files are those files which have not yet replicated. Suppose you have configured two servers (Server1 and Server2) to replicate their data by creating a RG and added these two servers in that RG. Now lets assume that we had 1000 files on Server1. Once we enable replication between these two servers, and run the health report and assuming that no replication has taken place then the number of backlogged files will be 1000 on Server1 which are yest to be replicated on the Server2
When you choose this option, you have to choose a "Reference Member". Reference Member will be that server with which you want to do the comparison of this server for the backlog files.
Count the Replicated Files and their size on each member: This option will count the number of files that has been replicated for this Replication Group and the total size of the files on each server. This is a good option to do data comparisonn but do remember the fact that if you choose this option, DFSr will calculate the total data that has been replicated and doing so will take time. So if you choose this option, it will take time to generate the Report.
In case the report hangs, then make sure that the IE Enhanced Security is not checked.
The IE Enhanced Security can be disabled from Server Manager
Once generated, the Report will have two parts - Error/Warning and the Server Details
In this post I will discuss the Health Report option available in Windows 2008 R2. Health Report option was available in Windows 2003 R2 and in Windows 2008 as well
In this example, we have configured three Replication Groups (RGs). We will create a Health Report for the Replication Group named "Data1"
To create a Health Report, Right Click on the RG for which you want to generate the health report and choose the option "Create Diagnostic Report"
On the first screen, we get three options
1. Health Report
2. Propagation Test
3. Propagation Report
Propagation Test & Propagation Report options were not available in Windows 2003 R2 or in Windows 2008 R2 through the "Health Report" Snap-In. It was a command line option. This is a new addition in Windows 2008 R2 DFSR. We will talk about Propagation Test & Propagation Report in a separate post.
For now, Lets choose the option "Health Report"
On this screen , you can change the path where this report will be saved when completed and the name of the health report. By default, the location of the health report is in C:\DFSReports and the Name of the Health Report will be Name of the RG><Date of Report><Time of Report>
A replication group can have multiple servers involved in replication. Here you can choose for which all servers involved in replication for this particular RG the report should run.
This gives the you following options:
1. Count Backlogged Files
2. Count the Replicated Files and their size on each member
Count Backlogged Files: Backlogged files are those files which have not yet replicated. Suppose you have configured two servers (Server1 and Server2) to replicate their data by creating a RG and added these two servers in that RG. Now lets assume that we had 1000 files on Server1. Once we enable replication between these two servers, and run the health report and assuming that no replication has taken place then the number of backlogged files will be 1000 on Server1 which are yest to be replicated on the Server2
When you choose this option, you have to choose a "Reference Member". Reference Member will be that server with which you want to do the comparison of this server for the backlog files.
Count the Replicated Files and their size on each member: This option will count the number of files that has been replicated for this Replication Group and the total size of the files on each server. This is a good option to do data comparisonn but do remember the fact that if you choose this option, DFSr will calculate the total data that has been replicated and doing so will take time. So if you choose this option, it will take time to generate the Report.
In case the report hangs, then make sure that the IE Enhanced Security is not checked.
The IE Enhanced Security can be disabled from Server Manager
Once generated, the Report will have two parts - Error/Warning and the Server Details
