SCCM Secondary Site drive filling up RRS feed

  • Question

  • I am having an issue on my secondary site. SCCM is installed on the C:\ drive, and the drive is constantly filling up. I have expanded the drive numerous times and it continues to fill.

    SCCM Content Library is not growing
    IIS Logs - I believe aren't the cause
    SQL Logs - .ldf file is relativeily small

    Any ideas where to look?

    Monday, June 15, 2015 7:12 PM


All replies

  • Hi,

    Use WinDirStats (freeware) to see what is taking up disk space:

    Check out this guide for SCCM 2012 disk space:

    Best regards, Kjetil :) Please remember to click “Mark as Answer” on the post that helps you. This can be beneficial to other community members reading the thread.

    Monday, June 15, 2015 7:22 PM
  • Thanks windirstat showed me the location that seems to be sucking up the space.

    Program Files\Microsoft Configuration Manager\inboxes\\receive

    despool.log just shows content coming in and extracting. Packages that already exist on the server. I believe these are the software update deployment packages. There are some .TRY files that are a few months old. Are these safe to remove?

    Monday, June 15, 2015 9:11 PM
  • despoolr is where the server stores files it needs to unpack that it received from other sites--whether a parent or a child, or a secondary site.  Once unpacked, replmgr will place the files into the appropriate inboxes for local processing (state messages, dataldr, package content, software metering files, whatever happened to be inside that replicated file).

    That said, it is supposed to be for mostly 'current' things.  Anything older than a few weeks, unless you are in an EXTREMELY low bandwidth replication scenario (you'd definitely know if you are trying to communicate to sites in in the Outer Banks via satellite or something and you expect data to take weeks to transfer from your Secondary to your Primary or vice versa), is generally safe to cleanup/delete from that folder.

    It has been known to happen that if your server had to hard reboot, or somehow else communications were interrupted, the automatic movement of files didn't happen as designed; so you can usually delete older files or folders in there.

    Also, you've said you've 'expanded multiple times and it continues to fill'.  In general, I wouldn't recommend using the C: drive for your inboxes location.  Also, how big is "big"?  Inboxes can have a LOT of file transfers, and yes, sometimes they can be huge, at least temporarily, like when you are sending patches to your DPs.

    Standardize. Simplify. Automate.

    Monday, June 15, 2015 11:22 PM
  • Yesterday The despoolr receive was about 55GB. I removed about 22GB yesterday (files older than 3 weeks), the large files were the exact same size ~9GB. There are 4 .TRY files of the exact same size, dating back about 2 weeks. Reading more closely at the despool log file revealed that it was having issues decompressing our Win8 OS image. I believe these files are the image files it failed to decompress.

    My sites are fairly well connected, I don't recall exactly, but I think it will take about 3-4 days to replicate 50+GB content library.

    Reading more into this issue now, I am getting Error 1295 - Despooler failed to merge delta to the compressed package "US00015E". The operating system reported error 1295: The requested file operation failed because the storage quota was exceeded. To free up disk space, move files to a different location or delete unnecessary files. For more information, contact your system administrator.

    This is unusual as I have 25GB of free space on that drive currently.

    C:\ was a bad place to install to. This was one of the early site installs, all newer sites install on a separate drive.

    Tuesday, June 16, 2015 4:13 PM
  • I just rebooted and it appears the packaged decompressed successfully.

    Thanks for all the help!

    Tuesday, June 16, 2015 4:39 PM