We're running an application server with Windows Server 2008R2 installed, and currently have script that that runs overnight to copy a large (42 Gb) file from the database server back to the application server (the command is actually a robocopy command). normally this process runs well, but we ran into an instance this week where - after the file transfer was complete - the server memory usage showed appx 5Gb of 'modified' memory still in use, and the server was running terribly slow, not letting users login to the software they needed to that was running on the application server. After we ran a tool from SysInternals called RamMap, we were able to determine that the 5Gb of memory in 'modified' memory, was due to the last part of the copy process, and it showed that 5Gb of the large file was still loaded into memory long after the copy had completed. After reading into the issue some, we ran across others that have experienced the issue, http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2general/thread/74c2c9ca-f8c1-4c37-bc8c-cd074ce0c6cd/ but unfortunately the official fix that is posted here http://www.microsoft.com/en-us/download/details.aspx?id=9258, is not supported for our version of servers, and we haven't been able to find a supported patch yet. So we are needing to see if there is a supported patch, or recommendations for the issue on Windows Server 2008 R2? Also, we found a patch listed here as well from the bottom of the first forum thread, (http://support.microsoft.com/default.aspx?scid=kb;EN-US;979149) but it doesn't really mention caching issues, is this one relevent to our problem at all?

Hi, This can be a temporary issue, you may restart the computer to check the result. If it does not work, please try to install the hotfix KB979149 and also run Windows Update to install the new updates to check the result. Regards,Arthur Li TechNet Community Support

Hi, This can be a temporary issue, you may restart the computer to check the result. If it does not work, please try to install the hotfix KB979149 and also run Windows Update to install the new updates to check the result. Regards,Arthur Li TechNet Community Support

you can take a look here http://social.technet.microsoft.com/wiki/contents/articles/6925.how-to-prevent-filecache-to-eat-up-all-the-ram.aspx as for the cause of the cache still being in use, i think I saw a while back a thread in which case an outdated av client caused the cache to not being released properly

you can take a look here http://social.technet.microsoft.com/wiki/contents/articles/6925.how-to-prevent-filecache-to-eat-up-all-the-ram.aspx as for the cause of the cache still being in use, i think I saw a while back a thread in which case an outdated av client caused the cache to not being released properly

Good recommendations, I dont think it was a temporary issue, I found out actually this is the second time it's happened, the first being in June of this year. We checked the Antivirus, and that all looks well and up to date. For now, there was a decision made to kill the robocopy step on the server, so I'm not sure if we'll be able to completely follow up with the issue. Though I'd still like to go through with the patch / hotfix noted above, KB979149. That one seems to match our symptoms very well, and seems like it would be the correct solution. I'll try to follow up here to post on the results of the hotfix, if/ when we end up installing it to the server. Thank-you very much!