Caching packages on the sha1 folder
You can use the SCC Download Cacher 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 SUSE 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 50GB per repository. Note that the minimum size of 50GB might increase over time.
About this task
Procedure
-
Use the
buildRepo
subcommand with theSCCDownloadCacher.exe
file to download packages from a repository to the BigFix server's sha1 folder. For example:SCCDownloadCacher.exe --mirrorUser username --mirrorPass base64_encoded_password --download_dir C:\downloads --sha1_download_dir C:\Program Files (x86)\BigFix Enterprise\BES Server\wwwrootbes\bfmirror\downloads\sha1 buildRepo --key sles-12-x86_64-sp0, sles-11-x86-sp4
In this example, the download cacher tool downloads the packages directly to the BigFix server's sha1 folder.
-
Open the configuration file of the SCC Download Cacher called
plugin.ini
. Configure theplugin.ini
file with the following settings to set the BigFix Server to retrieve the packages from its sha1 folder.localCache = localCacheOnly = no
Do not specify a value for the
localCache
setting if the BigFix server is internet-enabled and the packages are saved directly in the BigFix server's sha1 folder.