How to extend scan file retention during ILMT downtime?

1

Hello,

We have a client running an "All-in-One" ILMT and BigFix setup. In a disaster recovery scenario where the ILMT server is offline for an extended period, how long do scan results (Capacity and Software scans) stay cached before being purged?

Specifically, I am looking for the parameters to adjust the retention period for these files while they wait to be imported. Is this managed on the endpoint/scanner side or via the BigFix Server’s Upload Manager? We want to ensure no data is lost during server downtime without overfilling the server's disk space.

2

The scan results are stored as files on the BigFix Server under the UploadManagerData folder. These files are not purged automatically unless some custom maintenance job is scheduled to purge the files from these folders to manage disk space. If so, this would be specific to your implementation.

BigFix Administration settings are available to delete the files/folders from the UploadManagerData for only computers that are deleted from BigFix.

3

Thank you for the reply. To ensure no data loss during an ILMT outage, I am looking to configure these two specific settings on the BigFix Server:

  1. _BESRelay_UploadManager_RetentionPeriodPeriods: Does this parameter define the maximum time a file stays in the UploadManagerData folder before being purged, regardless of whether ILMT has imported it?

  2. _BESRelay_UploadManager_BufferDirectoryMaxSize: If this size limit is reached, will the BigFix server stop accepting new scan results from the endpoints?

I want to make sure I have enough "buffer" (both in time and disk space) to store 14 days of scans if the ILMT server is down. Any advice on the best values for these would be appreciated.

4

I am not sure where the first setting came from. I don’t find any reference to it. The 2nd setting _BESRelay_UploadManager_BufferDirectoryMaxSize and it’s corresponding _BESRelay_UploadManager_BufferDirectoryMaxCount are not set by default and have avery high values. If they are set manually to limit the UploadManagerData folder usage size, then check your Root Server client settings and increase it. Usually, these 2 don’t need to be changed

1 Like