Hi,
I’m really annoyed with the current behavior of my BigFix environment. We do only have BigFix installed in our environment and Every time I free up disk space,it automatically fills up. 2 days ago I’ve created a space of 10 GB and took less than 10 actions but right now I do only have space of 70 MB.
I’ve cleared the the Download/Upload folders. Audit Cleaner tool is not so effective as it is immediately quits Every time I run it.
Can anyone please help?
The space consumed is directly related to how much content you are pushing with the platform – 10GB isn’t a lot so I would start by expanding it by significantly more than that.
Then I would use a tool like Windirstat to verify what is actually using the space.
When you delete the download cache if you are pushing actions it will just redownload that information. You’ll want to figure out what is actually using that space and address that issue. I typically allow downloads/uploads to grow to over a couple hundred gigabytes before I worry about significant cleanup.
Are you talking about running out of space on a client or on the root server itself?
It sounds like you are talking about the root server.
There are settings that can be adjusted to limit the maximum size of the root server cache, but as @strawgate mentions, 10gb is very small. I would recommend a 2TB volume just for the cache if you plan to do a lot of software installs and patching just to prevent the cache from rolling over. The volume storing the cache can be slower than the other storage involved with the root server.
@strawgate
@jgstew
Thanks guys for your response. Yes I’m talking about root server. We’ve a very small environment of like 50 endpoints. What my concern is the space is automatically fills up. I only took less than 10 actions which doesn’t includes any download. I’m still curious why it is happening.
The files in uploads and the BES Cache are named after their hashes. If you use a tool like Windirstat to identify what is taking the space you can identify what fixlet or task the download is coming from.
Every KB of space that BigFix takes up can be accounted for this way – just use a tool to figure out where the space is being taken up, find out what files they are, and then investigate where those files are coming from.
Without knowing where the files are, what they are called, and their size, we can’t really help you.
As @strawgate mentions, if we know where the space is being taken up, then we can tell you how to limit the space in some areas.
There are settings to limit the maximum cache on the root server, but if that isn’t where your issue is, then that won’t fix the issue.
Hi there,
As per suggestion of @strawgate I’ve installed Windirstat and figure out the space is consuming by both MS SQL and Bigfix server as well. @jgstew yes the root server and the SQL db both on same machine. and my total volume size is 150 GB. Below is the screenshot of Windirstat result.
Only about 70GB is being used by BigFix which is well within the size I would expect an environment to be.
You could move the SQL backups to another share but…
The cost for you trying to reduce it further is probably higher than the cost of just expanding the storage (Or adding a disk and moving it to that storage).
Your DB is bigger than I would have expected, but I agree with @strawgate , I would recommend throwing storage at the problem if you can.
Dear @strawgate and dear @jgstew
My hard disk was 100 GB and I recently expand it to 150 GB but I’m quite confused why I’m getting low storage issues.
Where are you seeing low storage issues?
Can you show us a screenshot of, “My Computer” that shows us the volumes themselves?
Yeah I would happy to show you the screenshot but I don’t have it because I’ve already expand it. I’m sorry
No worries, I’m glad you were able to resolve the space issues!
