Option #1<\/h3>\n\n\n\nYou could use a PowerShell command line from Microsoft.
1. Get-DfsrBacklog: <\/strong><\/h4>\n\n\n\nThis command shows retrieves pending updates between two computers that participate in DFS-R file replication service. <\/p>\n\n\n\n
PS C:\\> Get-DfsrBacklog -SourceComputerName \"MyServer\" -GroupName \"G01\" -FolderName \"Folder\"\n\nIdentifier : {DCE7FC28-5584-4D5D-BC84-2BD9D53CC5FC}-v538\nFlags : 5\nAttributes : 32\nGlobalVersionSequenceNumber : {DCE7FC28-5584-4D5D-BC84-2BD9D53CC5FC}-v538\nUpdateSequenceNumber : 71575496\nParentId : {997D8F76-1207-49D7-85C9-DED015105A2F}-v1\nFileId : 562949953495210\nVolume : \\\\.\\C:\nFence : 3\nClock : 130078672846368199\nCreateTime : 3\/15\/2013 5:28:04 PM\nUpdateTime : 3\/15\/2013 5:28:04 PM\nFileHash : 173b51c11257a2eb 8c05884560fcfd1d\nFileName : file.exe\nFullPathName : c:\\folder\\file.exe\nIndex : 1\nReplicatedFolderName : folder\nReplicated Folder Id : 997d8f76-1207-49d7-85c9-ded015105a2f<\/code><\/pre>\n\n\n\n<\/p>\n\n\n\n
2. Get-DfsrState:<\/strong><\/h4>\n\n\n\nThis command shows you the current replication state of DFS-R in regard to its DFS replication group partners. <\/p>\n\n\n\n
PS C:\\> Get-DfsrState -ComputerName \"Server\" | Format-Table FileName,UpdateState,Inbound,Source* -Auto -Wrap\n\nFileName UpdateState Inbound SourceComputerName\n-------- ----------- ------- ------------------\nntfrs - Copy.exe Scheduled True SRV02\nntdsai - Copy.dll Scheduled True SRV02\nNlsLexicons0046 - Copy.dll Scheduled True SRV02\nNlsLexicons000a - Copy.dll Downloading True SRV02\noccache - Copy.dll Scheduled True SRV02\nNlsModels0011 - Copy.dll Scheduled True SRV02\nNlsLexicons0007 - Copy.dll Scheduled True SRV02\nNlsLexicons000f - Copy.dll Downloading True SRV02\nNlsLexicons003e - Copy.dll Scheduled True SRV02\nNlsLexicons0045 - Copy.dll Scheduled True SRV02\nNlsData001a - Copy.dll Downloading True SRV02\nntlanui2 - Copy.dll Scheduled True SRV02<\/code><\/pre>\n\n\n\n<\/p>\n\n\n\n
Option #2<\/h3>\n\n\n\n
Option two is to use the Dfsrdiag.exe tool that provides DFSR status. In the latest Windows Server builds, DFS Management Tools may not be installed. You should execute the following command from PowerShell to install it.<\/p>\n\n\n\n
Install-WindowsFeature RSAT-DFS-Mgmt-Con<\/code><\/pre>\n\n\n\n<\/p>\n\n\n\n
DFS-R Deficiencies<\/h2>\n\n\n\n
The DFS-R service is widely used and suffers from well-known deficiencies, foremost among these being a general lack of visibility into the replication process. DFS-R is effectively a \u201cblack box,\u201d indicating nothing about the current status of the service. When relying on DFS-R and its algorithms for mission-critical replication, this lack of visibility can be extremely frustrating for administrators tasked with keeping these critical services operational and users happy. <\/p>\n\n\n\n
For mission-critical data replication, customers require additional functionality from the service as follows:<\/p>\n\n\n\n
\n- A detailed status of the DFS-R replication process<\/li>\n\n\n\n
- DFS-R health check<\/li>\n\n\n\n
- DFS-R force replication <\/li>\n\n\n\n
- DFS-R performance tuning (making replication times predictable and consistent)<\/li>\n\n\n\n
- DFS-R real-time monitoring<\/li>\n\n\n\n
- DFS-R GUI\/Dashboard<\/li>\n<\/ul>\n\n\n\n
Many of these address basic visibility and control issues inherent in the service. For example, a common pain customers experience is when a file is sitting in a SCHEDULED state with no clear way to start the replication. Waiting for the service to \u201cget around to it\u201d is not a viable option. A simple \u201cforce replication\u201d feature would solve these problems. Another common complaint from customers is the performance of the service is often inconsistent. Replication times should be predictable and fast, especially for mission-critical workflows, regardless of the network topology (i.e. full mesh, hub\/spoke).
There are some basic resources available in Windows whereby users can gain limited status information on the DFS-R service. The most commonly used are the ones mentioned earlier.<\/p>\n\n\n\n
The Future of DFS Replication in Windows Server<\/h2>\n\n\n\n
Despite these configure tools, it\u2019s clear from the community that to make DFS-R an acceptable application for mission-critical work would require significant development from Microsoft. Unfortunately, the prospects of Microsoft fixing these deficiencies is not likely. With the release of Azure File Sync in 2017, the roadmap for DSF-R is not promising as Microsoft clearly views Azure and Azure File Sync as the migration path for DFS-R. Not only will DFS-R no longer see needed development to fix these issues, but it will also obviously face end-of-life at some point in the near future with dwindling support until then. The operational risks around continued DFS-R usage will further compound as more Microsoft resources are shifted to Azure.<\/p>\n\n\n\n
Better Options to Consider Instead of DFS Replication in Windows Server<\/h2>\n\n\n\n
For customers looking to address these risks and improve visibility into critical replication processes without migrating everything to Azure, Resilio Active Everywhere (formerly Resilio Connect) is a comprehensive solution. It addresses most or all of the deficiencies of DFS-R and it works with the file and storage services and servers you already have while offering a migration path to the cloud at any point in the future.<\/p>\n\n\n\n
![\"Performance](\"\/images\/sync1m-100kb.svg\")
1. Get-DfsrBacklog: <\/strong><\/h4>\n\n\n\n
This command shows retrieves pending updates between two computers that participate in DFS-R file replication service. <\/p>\n\n\n\n
PS C:\\> Get-DfsrBacklog -SourceComputerName \"MyServer\" -GroupName \"G01\" -FolderName \"Folder\"\n\nIdentifier : {DCE7FC28-5584-4D5D-BC84-2BD9D53CC5FC}-v538\nFlags : 5\nAttributes : 32\nGlobalVersionSequenceNumber : {DCE7FC28-5584-4D5D-BC84-2BD9D53CC5FC}-v538\nUpdateSequenceNumber : 71575496\nParentId : {997D8F76-1207-49D7-85C9-DED015105A2F}-v1\nFileId : 562949953495210\nVolume : \\\\.\\C:\nFence : 3\nClock : 130078672846368199\nCreateTime : 3\/15\/2013 5:28:04 PM\nUpdateTime : 3\/15\/2013 5:28:04 PM\nFileHash : 173b51c11257a2eb 8c05884560fcfd1d\nFileName : file.exe\nFullPathName : c:\\folder\\file.exe\nIndex : 1\nReplicatedFolderName : folder\nReplicated Folder Id : 997d8f76-1207-49d7-85c9-ded015105a2f<\/code><\/pre>\n\n\n\n<\/p>\n\n\n\n
2. Get-DfsrState:<\/strong><\/h4>\n\n\n\nThis command shows you the current replication state of DFS-R in regard to its DFS replication group partners. <\/p>\n\n\n\n
PS C:\\> Get-DfsrState -ComputerName \"Server\" | Format-Table FileName,UpdateState,Inbound,Source* -Auto -Wrap\n\nFileName UpdateState Inbound SourceComputerName\n-------- ----------- ------- ------------------\nntfrs - Copy.exe Scheduled True SRV02\nntdsai - Copy.dll Scheduled True SRV02\nNlsLexicons0046 - Copy.dll Scheduled True SRV02\nNlsLexicons000a - Copy.dll Downloading True SRV02\noccache - Copy.dll Scheduled True SRV02\nNlsModels0011 - Copy.dll Scheduled True SRV02\nNlsLexicons0007 - Copy.dll Scheduled True SRV02\nNlsLexicons000f - Copy.dll Downloading True SRV02\nNlsLexicons003e - Copy.dll Scheduled True SRV02\nNlsLexicons0045 - Copy.dll Scheduled True SRV02\nNlsData001a - Copy.dll Downloading True SRV02\nntlanui2 - Copy.dll Scheduled True SRV02<\/code><\/pre>\n\n\n\n<\/p>\n\n\n\n
Option #2<\/h3>\n\n\n\n
Option two is to use the Dfsrdiag.exe tool that provides DFSR status. In the latest Windows Server builds, DFS Management Tools may not be installed. You should execute the following command from PowerShell to install it.<\/p>\n\n\n\n
Install-WindowsFeature RSAT-DFS-Mgmt-Con<\/code><\/pre>\n\n\n\n<\/p>\n\n\n\n
DFS-R Deficiencies<\/h2>\n\n\n\n
The DFS-R service is widely used and suffers from well-known deficiencies, foremost among these being a general lack of visibility into the replication process. DFS-R is effectively a \u201cblack box,\u201d indicating nothing about the current status of the service. When relying on DFS-R and its algorithms for mission-critical replication, this lack of visibility can be extremely frustrating for administrators tasked with keeping these critical services operational and users happy. <\/p>\n\n\n\n
For mission-critical data replication, customers require additional functionality from the service as follows:<\/p>\n\n\n\n
\n- A detailed status of the DFS-R replication process<\/li>\n\n\n\n
- DFS-R health check<\/li>\n\n\n\n
- DFS-R force replication <\/li>\n\n\n\n
- DFS-R performance tuning (making replication times predictable and consistent)<\/li>\n\n\n\n
- DFS-R real-time monitoring<\/li>\n\n\n\n
- DFS-R GUI\/Dashboard<\/li>\n<\/ul>\n\n\n\n
Many of these address basic visibility and control issues inherent in the service. For example, a common pain customers experience is when a file is sitting in a SCHEDULED state with no clear way to start the replication. Waiting for the service to \u201cget around to it\u201d is not a viable option. A simple \u201cforce replication\u201d feature would solve these problems. Another common complaint from customers is the performance of the service is often inconsistent. Replication times should be predictable and fast, especially for mission-critical workflows, regardless of the network topology (i.e. full mesh, hub\/spoke).
There are some basic resources available in Windows whereby users can gain limited status information on the DFS-R service. The most commonly used are the ones mentioned earlier.<\/p>\n\n\n\n
The Future of DFS Replication in Windows Server<\/h2>\n\n\n\n
Despite these configure tools, it\u2019s clear from the community that to make DFS-R an acceptable application for mission-critical work would require significant development from Microsoft. Unfortunately, the prospects of Microsoft fixing these deficiencies is not likely. With the release of Azure File Sync in 2017, the roadmap for DSF-R is not promising as Microsoft clearly views Azure and Azure File Sync as the migration path for DFS-R. Not only will DFS-R no longer see needed development to fix these issues, but it will also obviously face end-of-life at some point in the near future with dwindling support until then. The operational risks around continued DFS-R usage will further compound as more Microsoft resources are shifted to Azure.<\/p>\n\n\n\n
Better Options to Consider Instead of DFS Replication in Windows Server<\/h2>\n\n\n\n
For customers looking to address these risks and improve visibility into critical replication processes without migrating everything to Azure, Resilio Active Everywhere (formerly Resilio Connect) is a comprehensive solution. It addresses most or all of the deficiencies of DFS-R and it works with the file and storage services and servers you already have while offering a migration path to the cloud at any point in the future.<\/p>\n\n\n\n