Freeing up space on the SASHome drive

[Nigel_Pain]

Windows 2012R2, SAS 9.4M7, mid-tier server

I'm trying to free up some space on the drive containing SASHome and the config directory. It has a capacity of 95Gb but we're down to less than 5Gb free. As far as I can make out most of the logs are being tidied up. But we have a policy of applying all relevant hotfixes on a monthly basis, and did an upgrade in place from M5 to M7 back in October last year so I reckon there must be quite a lot of redundant content, just can't quite work out how to find it. I'm also not sure whether I need to keep hotfix packages in installmisc\hotfixes after they've been applied? I always have done in the past.

Thanks

[gwootton · Accepted solution]

The Deployment Manager checks the hot fixes staged for installation against what is in the deployment registry and only installs those that have not already been installed, so there isn't a requirement to keep them in there. Most hot fixes are pretty small though so I'm not sure how much of a gain you'd get. Typically the things that consume space in the Config directory are log files (especially when trace logging is enabled) and if the Service Architecture Framework is enabled, those data sets (<SASConfig>\Lev1\Web\SASEnvironmentManager\emi-framework\Datamart). Settings can be adjusted to lower the history length for those to control their size.

[Sajid01]

Hello
In addition to what has been said above make sure you are not using TRACE or DEBUG log level.
If workspace logging is enabled that will also consume lot of space.

Therefore please review your logging configuration.

[Nigel_Pain]

Thanks @gwootton and @Sajid01 for your suggestions. There's no trace logging or workspace logging enabled, just the standard vanilla options, and we don't have the Service Architecture Framework enabled. However, I did subsequently find an article by @ScottMcCauley Reclaim Disk Space After a SAS 9.4 Upgrade-in-Place and this yielded around 14Gb of space for me, so the immediate panic is over and I'll monitor usage carefully to see what happens.

[Nigel_Pain]

Oops, marked the wrong post as the solution!