Fileset Tuning Parameters

These set of parameters can be used to fine-tune the behavior of the plugin to be more flexible in cases of bad network environments, or when significant job concurrency is happening, etc. It is not necessary to modify them for the great majority of the cases:

Option

Required

Default

Values

Example

Description

backup_queue_size

No

100

0-500

1

Number of maximum enqueued internal operations between service static internal threads (there are 3 communicating through queues with the set size: service fetcher, service opener and general publisher to bacula core). This could potentially affect api concurrent requests and consequently, throttling and cpu/memory consumption for both, the FileDaemon and the Exchange server. It is only needed to modify this parameter, in general, if you are need a ver precise control of your concurrency levels

concurrent_threads

No

10

0-100

1

Number of maximum concurrent backup threads running in parallel in order to open data for running download actions. If you want to have a precise control of your parallelization through different jobs, please set up this value to 1. Please be careful also with the memory requirements, multi-threaded increases very significantly memory consumption per job

concurrent_listing_threads

No

2

0-20

1

Number of maximum concurrent backup page listing threads running in parallel in order to fetch sets of data. This parameter will also affect api concurrent requests

api_list_page_size

No

100

10-500

1

Number of items got in each page for multi-page requests to EWS API

general_network_retries

No

5

Positive integer (number of retries)

10

Number of retries for failed requests to the EWS API

general_network_delay

No

50

Positive integer (seconds)

100

Delay between retries to the EWS API

Go back to the Fileset Configuration article.