About six months ago my C: drives on my domain controllers (DCs) simultaneously started filling up. I found the culprit -- the C:WINNTSYSVOLstagingdomain directory was filling up and not deleting files.
For whatever reason, only two DCs have that problem know. This appears to me to be an AD replication problem -- am I correct? I started to activate DFS for some directories about the same time period -- could that play into this? My temporary solution has been to schedule a script to run every so often that looks like this:
del /F /S /Q /A:H *.*
This way, if the folders get too full, the script will run before they start to consume several gigabytes of disk space, or worse yet fill the entire disk and create registry corruption.
What do you recommend?
The FRS staging folder is a temporary store for files that replicate to downstream partners of SYSVOL or DFS replica sets. Files in the FRS staging folder may consume disk space up to the limit assigned in the "Staging Space Limit in KB" option ([REG_DWORD] registry entry ["Default = 660 MB"]), or up to the amount of free disk space on the hosting drive, whichever is less.
For FRS replica sets that host gigabytes of content, it may be necessary to relocate the File Replication Service (FRS) staging folder to a different logical or physical drive to prevent the FRS staging folder from consuming all available disk space on the hosting drive, which can potentially affect the stability of other components, including the base operating system.
Consult MS KB article How to reset the File Replication Service staging folder to a different logical drive for instructions on how to modify the Staging Space Limit registry entry and/or move the Staging/Domain files to a different volume.
This was first published in March 2003