Caching packages on the sha1 folder
You can use the CentOS Download Cacher R2 to cache packages directly on an internet-enabled BigFix server's sha1 folder to improve performance during the Fixlet deployment.
Before you begin
- Ensure you have access to the BigFix supported Alma Linux base repositories
and sub-repositories. To check, run the subcommand
check-allrepos. - Ensure you have enough space to download the repository metadata and packages. To check for the
required storage space, run the subcommand
check-storagereq. - Increase the BigFix server's sha1 folder size limit by doing the following steps:
- From the BigFix console, right-click the computer and select Edit Computer Setting.
- Increase the _BESGather_Download_CacheLimitMB
size.
The suggested size is the current BigFix server’s sha1 folder size plus the size of sha1_download_dir.
If the size of the sha1_download_dir cannot be determined beforehand the suggested size of the sha1_download_dir is a minimum of 20GB per repository. Note that the minimum size of 20GB might increase over time.
About this task
Procedure
-
Use the
buildReposubcommand with theCentOSR2DownloadCacher.exefile to download packages from a repository to the BigFix server's sha1 folder. For example:CentOSR2DownloadCacher.exe --download_dir C:\downloads --sha1_download_dir C:\Program Files (x86)\BigFix Enterprise\BES Server\wwwrootbes\bfmirror\downloads\sha1 buildRepo --key almalinux-9-x64In this example, the download cacher tool downloads the packages directly to the BigFix server's sha1 folder.
-
Open the configuration file of the CentOS Download Cacher R2 called
plugin.ini. Configure theplugin.inifile with the following settings to set the BigFix Server to retrieve the packages from its sha1 folder.localCache = localCacheOnly = noDo not specify a value for the
localCachesetting if the BigFix server is internet-enabled and the packages are saved directly in the BigFix server's sha1 folder.