DFSR Troubleshooting Tips:
1) Staging Quota - Ensure that you have a large enough size for staging. This is where files are isolated from the file system. If you have 8G worth of files trying to stage where the quota is 4G (Default), the staging folder will purge files until it reaches the 60% mark. If this keeps reaching the limit and you receive "High Watermark" warnings, increasing the staging quota will correct this.
2) Locked Files - Another issue you may encounter is "Locked Files". Locked files are files that are currently opened. This can mean that they are opened by a user or an application. If you have a database file such as .MDB (Access Database) in your replication path that is open or any other files that are open and locked, it will not replicate. Ensure the file is not locked or exclude that file from being replicated, if it is not needed.
3) Backlog - At times, you'll come across backlogged files. Backlogged files are files that are waiting to replicate across the network. Depending on how much traffic you have in replication, bandwidth settings or any other variable, this backlog can occur.
- Run a diagnostic report- This report will tell you if there are sharing violations (ex: locked files) or issues communicating to the other members. It will also allow you to see if the file count drops showing that replication is occurring. Having some backlog is common and is normally not an issue.
- Run the command line- "dfsrdiag backlog /rgname:'Group Name' /rfname:'folder name' /smem:servername /rmem:servername"
- Run a propagation test- This will create a test file and verify that it can replicate to the member servers. This can be done through the DFSR management utility or through the command line.
4) Files not replicating - This can be any number of things. You should first verify the topology in the DFSR Management GUI. This will tell you if the servers are able to replicate. You can also check that you can reach the Domain. The "Verify Topology" does not always show you that you have issues with contacting the Active Directory Domain. Try reaching the member servers through UNC or using the NameSpace, if you have one configured.
5) Delays - All of the above can cause delays in replication. Look at the following for main points of a delay in replication
- NIC drivers are not up-to-date
- Bandwidth Throttling is too aggressive
- Service Packs or other System Updates have not been applied
- Initial Synchronization is happening (This will most likely go away when completed)
6) Antivirus Interference - Antivirus programs can cause replication issues on files. If you are running into issues with replication, you can start by excluding known locations that reside in the replication path. This will allow replication and prevent your antivirus from deeming the file as a potential risk and removing it or locking it.
DFSR TIP: If you have to stop replication for any problems or maintenance, it is better to "Disable" it rather than "Delete" it. If files are not in synch and you create replication using an outdated primary, all those files will overwrite the up-to-date ones. Disabling will allow it to stop and then pick back up when you are ready to start the DFSR process again.
7) For Remote procedure call errors. - The RPC connection may fail because of a network problem. This problem prevents the DFS Replication service from obtaining files. For most RPC connection problems, the DFS Replication service will try to obtain the files again without logging a warning or an error in the DFS Replication log. You can capture the network trace to determine whether the cause of the problem is at the network layer. To examine the TCP ports that the DFS Replication service is using on replication partners, run the following command in a Command Prompt window: