Hi Everyone,
I have 2 Windows Server 2008 R2 servers (As Hyper-V VM's) with several DFS-N and DFS-R items between them.
One directory with about 1.6 million files required the NTFS permissions changed due to a new work process. I applied these changes on the folder on Server1, and expected them to propagate to Server2. I have a script that polls for the DFS-R
Backlogged files every few minutes, that suddenly spiked to 1.6M (In only the direction of Server1 sending, Server2 receiving), and slowly worked its way down. At about the time it would have gotten back down to 0, it shot back up to the full 1.6M, and
has stayed there as a perfect flat line. I tested replication by creating and deleting files on both servers, and replication is still occuring, but the backlog still shows 1.6M files.
As a side note (Not sure if related or not) Both servers have Volume Shadow Copies configured in identical ways (Same time, same mirrored folders). The server on which I applied all of the permission changes attempted to snapshot the entire 1.6M files,
which grew beyond the usage limit for snapshots, deleting all old snapshots in the process. This is apparently normal behavior, as changing permissions sets the archive bit on the files. Server2, however did not do this, and continued making snapshots
as normal. I checked several files and folders deep within the folder structure, and found the permissions did apply to both servers.
So, my question is: Is there a real problem with the DFS Replication, that just hasn't manifested yet, or is the counter broken?
In any case, does anybody have any ideas to fix?