Fileset Common Parameters

These parameters control the generic characteristics of the behavior of the Amazon RDS Plugin. You may also encounter these parameters in other Bacula Enterprise Plugins that produce similar effects, so you might already be acquainted with them.

Option	Required	Default	Values	Example	Description
abort_on_error	No	No	No, Yes	Yes	If set to Yes: Abort job as soon as any error is found with any element. If set to No: Jobs can continue even if it they found a problem with some elements. They will try to backup or restore the other and only show a warning
config_file	No		The path pointing to a file containing any combination of plugin parameters	/opt/bacula/etc/amazon-rds.settings	Allows to define a config file where configure any parameter of the plugin. Therefore you don’t need to put them directly in the Plugin line of the fileset
log	No	/opt/bacula/working/amazon-rds/amazon-rds-debug.log	An existing path with enough permissions for File Daemon to create a file with the provided name	/tmp/amazon-rds.log	Generates additional log in addition to what is shown in job log. This parameter is included in the backend file, so, in general, by default the log is going to be stored in the working directory.
debug	No	0	0, 1, 2, 3, 4, 5, 6, 7, 8, 9	Debug level. Greater values generate more debug information	Generates the working/amazon-rds/amazon-rds-debug.log* files containing debut information which is more complete with a greater debug number
path	No	/opt/bacula/working	An existing path with enough permissions for File Daemon to create any internal (and usually temporary) plugin file	/mnt/my-vol/	Uses this path to store metadata and temporary files

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

# cat /opt/bacula/etc/amazon-rds.settings
region=us-east-1
access_key=AKIAQTESTKEY12134g
secret_key=m23480ahpqwre894qwrffsfdSecretExample