I am copying a large amount of files from one server to another via robocopy to a UNC share.
I notice that after robocopy completes that there is a large amount of disk activity that lasts for a while afterwards, the server is very sluggish at this time. I suspect this is the Windows' file system caching that is causing the large amount of disk activity after robocopy completes.
For debugging purposes, I would like to see how much data still needs to be written to disk (a performance counter would be best, to see a graph I can cross reference).
I am copying ~110k files that total ~1.3gb from and to Windows Server 2012 R2 instances.