Root UploadManagerData Management

Our UploadManagerData folder on our root server is very large (2m files, 300k folders) for 65k active clients. BFI Scans occur every 7 days.

In the BESAdminTool Cleanup tab, the settings are set to to 7,7,30. I’ve also set “_BESRelay_UploadManager_CleanupHours” on the Root to 168 but it hasn’t made a difference on the files being kept/deleted from UploadManagerData.

  1. Is _BESRelay_UploadManager_CleanupHours not working as expected, and is somewhat redundant from the “Remove Deleted Uploads” checkbox from the BESAdminTool?
  2. The BESAdminTool Cleanup setting of “Remove Deleted Computers” requires a value of >=30. Why is that? I want Uploads to be removed 7 days after deleted, but it is forcing >=30.
  3. If we were to write a script to delete UploadManagerData that is older then 7 days, Does anything need to be cleaned up in the BFEnterprise Uploads Table? Hopefully not.

What do others do to keep tihs

Well … the CleanupHours have nothing to do with admin tool … in fact it works in a different context respect the ‘Computer Remover’ tool that deletes data under the Upload Manager buffer dir, while this setting get rid of data for such a reason have been not elaborated on the relay and or the server and so have never reached that buffer …
In any case need to take care that a problem have been identified and fixed in the newer versions of the product with the following DA:
KB0084859 - Task to cleanup obsolete files uploaded in the Temp folder not working

The 30 days are to wait for a computer have been deleted ( accidentally or not ) from the deployment and request to register to the same server again … for these agents all their data is maintained in place until that time …

Once a file under the UploadManager bufferDir folder have been deleted, the FillDB first and the ‘Computer Remover’ then will manage the database … the first in general within an hour … the second with the limit of the 30 days …