BESComputerRemover and FillDB

(imported topic written by SystemAdmin)

I am looking into some performance issues with our database/console and think there may be something wrong which caused the database to grow extremely large in size.

We have a few locations that do not have a steady state application (deep freeze) to properly play nice with BigFix. To combat the dulplicate computers we have a scheduled task that runs the BESComputerRemover.exe to clean up the database. This seems to do a great job in reducing the number of duplicate computers. This task runs silently so I did not notice that it appears to be erroring out near the end of the process.

When I run the executable manually I usually just run with the -A switch. It goes through the process of marking the different computers as deleted. When it goes to Delete from the different tables it looks like it is working but at the end I get the following

Marking Deleted Computers as needing a Full Refresh…Done!

Stopping FillDB service…

ERROR: FillDB service could not be stopped.

At this point it terminates the executable.

The tables that are listed as part of this tool are the same ones that are rather large in size. Our deployment is 22,000 endpoints and from what I gathered from a KB the database should be between 2-5 GB in size. Ours is currently at 32GB (from the size of the BFEnterprise.mdf file). The tables with the largest amount of size are

Questionresults - 10.2 GB

Fixletresults - 4.9 GB

Longquestionresults - 4.3 GB

I have reached out to support but have yet to hear back from them (sent 2 emails now over a week) so I am hoping someone that is familiar with Performance Tuning can offer some advice on getting these tables to reduce is size and hopefully increase the performance of the server/console.

(imported comment written by SystemAdmin)

i’ve found several interesting scenarios with filldb. We have a reindex and a full sql backup running very close together and when one or the other fail, it usually takes filldb down with it.

I’ve attached a task for this specific scenario when filldb stops (ie the built in windows service restart features don’t work.)

deploy this as a policy with defaults and it will start the filldb service back up whenever it is stopped. Target your root server…

(imported comment written by BenKus)

You should look at the Audit Trail Cleaner to remove old data from the database:

http://support.bigfix.com/bes/install/downloadutility.html#besaudittrailcleaner

Ben

(imported comment written by SystemAdmin)

Ben Kus

You should look at the Audit Trail Cleaner to remove old data from the database:
http://support.bigfix.com/bes/install/downloadutility.html#besaudittrailcleaner

Ben

I was looking to download this tool and it appears the support site redirects to a wiki site that does not have this tool (has 4 others) on it anymore. Is this tool still available anywhere as I would like to give it a try again.

(imported comment written by SystemAdmin)

The link now seems to point to an invalid address. The site claims it can’t find the content.

“The Wiki can’t be found”

(imported comment written by BenKus)

http://forum.bigfix.com/viewtopic.php?id=9321