Common Parameters

Bacula Enterprise Only

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

These parameters control the general behavior of the IRIS Plugin. You may also encounter these parameters in other Bacula Enterprise Plugins that produce similar effects, so you may already be familiar with them.

Option	Required	Default	Values	Example	Description
abort_on_error	No	No	No, Yes	Yes	If set to Yes, abort the job as soon as any error is found. If set to No, jobs can continue even if some elements fail; the job attempts to back up or restore the remaining elements and only reports a warning
config_file	No		The path pointing to a file containing any combination of plugin parameters	/opt/bacula/etc/iris.settings	Allows you to define a config file to configure any plugin parameter, so you don’t need to put them directly in the Plugin line of the Fileset
log	No	/tmp/iris/iris-debug.log	An existing path with enough permissions for File Daemon to create a file with the provided name	/tmp/iris.log	Generates an additional log besides the job log. This parameter is included in the backend file, so by default the log is stored in the working directory
debug	No	0	0, 1, 2, 3, 4, 5, 6, 7, 8, 9	6	Generates `iris-debug.log*` files containing debug information. Greater values generate more verbose logs
path	No	/tmp	An existing path with enough permissions for File Daemon to create any internal (and usually temporary) plugin file	/opt/bacula/working	Uses this path to store metadata and temporary files

This is an example of a config_file with the Connection Parameters options:

# cat /opt/bacula/etc/iris.settings
instance=IRIS
namespace=%SYS
iris_owner_user=irisowner
iris_session_bin=/home/irisowner/bin/irissession
iris_bin=/usr/bin/iris