Upload Manager Settings

These settings apply to the Upload Manager component:

_BESClient_UploadManager_BufferDirectory

The Archive Manager always sets the Upload Manager input Buffer Directory to __BESData/__Global/Upload. This directory is on the client computer, in the BigFix Client folder.

_BESClient_UploadManager_ChunkSize

Uploads are done one chunk at a time. In a conflict between this computer and the upstream computer, the size of the chunk is set to the smaller of the two.

A value of 0 for the chunk size indicates that the upload is done in a single chunk. The local chunk size setting is specified in bytes. The default value is 131072 that corresponds to 128 KB.

This setting does not apply to Windows systems. There is no need of a restart to update the value of this setting.

_BESClient_UploadManager_ThrottleKBPS

After each chunk is uploaded, the Upload Manager calculates the amount of time to sleep to maintain the throttle speed in kilobytes per second (ThrottleKBPS). This allows you to compensate for network bottlenecks. For example, a BigFix client that is connected over a slow VPN to the relay might have a low upload throttle rate to minimize the bandwidth on that network segment.

In a conflict between this computer and the upstream relay (or server), the throttle KBPS is set to the smaller of the two.

The default value is 0, which disables throttling.

_BESRelay_UploadManager_BufferDirectory

Like the BigFix Client, the BigFix Relay also has an Upload Manager, and it also has a buffer directory, whose path is specified by this setting. The Upload Manager uploads the files in the sha1 subdirectory of the specified directory. It sorts the files by modification time and then, just like the BigFix Client, it uploads them in chunks to smooth out the bandwidth requirements.

_BESRelay_UploadManager_BufferDirectoryMaxSize

This setting denotes the maximum amount of space on disk that the server is allowed to take from the client using the Upload Manager. You can set the maximum file size to be as large as 2^64 – 1 bytes. Its default is 1 GB.

_BESRelay_Uploadmanager_BufferDirectoryMaxCount

This setting denotes the number of files that the buffer directory is allowed to hold. Its default is 10,000.

_BESRelay_UploadManager_CompressedFileMaxSize

This setting denotes the amount of space of the largest compressed file the Upload Manager is allowed to handle. You can set the maximum file size to be as large as 2^64 – 1 bytes. It applies only to the server and it is evaluated during the decompression of the uploaded archive.

_BESRelay_UploadManager_ChunkSize

Uploads are done one chunk at a time. In a conflict between this computer and the upstream computer, the size of the chunk is set to the smaller of the two.

A value of 0 for the chunk size indicates that the upload is done in a single chunk. The local chunk size setting is specified in bytes. The default value is 131072 that corresponds to 128 KB.

This setting does not apply to Windows systems. There is no need of a restart to update the value of this setting.

_BESRelay_UploadManager_ThrottleKBPS

After each chunk is uploaded, the Upload Manager calculates the amount of time to sleep to maintain the throttle speed in kilobytes per second (ThrottleKBPS). This allows you to compensate for network bottlenecks. For example, a BigFix relay that is connected over a slow VPN to the server might have a low upload throttle rate to minimize the bandwidth on that network segment.

In a conflict between this computer and the upstream server (or relay), the throttle KBPS is set to the smaller of the two.

The default value is 0, which disables throttling.

_BESRelay_UploadManager_CleanupHours

Sometimes archived files accumulate but do not get uploaded. This might happen with a network outage, a downed server or other communication problem. To avoid overloading the system, these old files are deleted or cleaned up. This setting determines how old a file can get before it is deleted.

The default value is 72 hours (three days).