Advanced Parameters

Bacula Enterprise Only

This solution is only available for Bacula Enterprise. For subscription inquiries, please reach out to sales@baculasystems.com.

The following parameters are advanced and should not be modified in the vast majority of cases:

Option	Required	Default	Values	Example	Description
stream_sleep	No	1	Positive integer (1/10 seconds)	5	Time to sleep when reading header packets from FD and not having a full header available
stream_max_wait	No	0	Positive integer (seconds)	360	Max wait time for FD to answer packet requests
time_max_last_modify_log	No	86400	Positive integer (seconds)	43200	Maximum time to wait to overwrite a debug log that was marked as being used by another process
logging_max_file_size	No	50MB	String size	300MB	Maximum size of a single debug log file
logging_max_backup_index	No	25	Positive integer (number of files)	50	Maximum number of log files to keep
log_rolling_file_pattern	No	/tmp/iris/iris.%d{yyyy-MM-ddHHmm}.log.gz	String file name pattern	/tmp/iris/iris.%d{yyyy-MM-dd}.log.gz	Log pattern for rotated log files
split_config_file	No	=	Character	:	Character to be used in config_file parameter as separator for keys and values
opener_queue_timeout_secs	No	36000	Positive integer (seconds)	3600	Timeout when internal opener queue is full
publisher_queue_timeout_secs	No	36000	Positive integer (seconds)	3600	Timeout when internal publisher queue is full

The internal plugin logging framework has the following characteristics:

The .log files are rotated automatically. Currently, each file can be up to 50 MB and the plugin keeps 25 files.
- This behavior can be changed using the internal advanced parameters: logging_max_file_size and logging_max_backup_index.
The .err file can show contents even if no actual error has occurred during the jobs. It can also present contents even if debugging is disabled. This file is not rotated, but it is generally anticipated to remain small in size. If you still need to rotate it, you can include it in a general rotating tool such as logrotate.
Parallel backups and failed backups will generate several log files, for example: iris-debug-0.log, iris-debug-1.log, and so on.