Common 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 control general behavior of the MongoDB Plugin. They are provided by the Bacula MetaPlugin layer and have the same purpose as in other Bacula Enterprise plugins that use this backend model.

Common parameters
Option	Required	Default	Values	Example	Description
`abort_on_error`	No	`no`	`yes` or `no`	`yes`	Abort the Bacula job as soon as the plugin detects a non-recoverable error. Keep this enabled for production jobs where partial artifacts must not be accepted silently.
`config_file`	No		Path to a readable file	`/opt/bacula/etc/mongodb.settings`	Read plugin parameters from a file. This is useful for keeping long connection settings, credentials, TLS paths, and database scope outside the FileSet definition.
`log`	No	Bacula job log only	Writable file path	`/var/log/bacula/mongodb-plugin.log`	Write additional plugin debug information to a local file. Use this for troubleshooting together with the Bacula job log.
`debug`	No	`0`	`0` to `9`	`2`	Enable increasing levels of plugin debug output. Higher values are intended for support investigations and may expose operational details in logs.
`path`	No	Bacula working path	Existing directory	`/opt/bacula/working`	Directory used for small local control files, temporary metadata, restore planning files, and staged oplog replay payloads. Current normal Bacula restores stream `dump/*.archive` directly to `mongorestore`; size this path for metadata and oplog replay, not for full dump archive staging.

Configuration File Example

The config_file parameter accepts the same key=value options that can be placed directly in the Fileset. Sensitive parameters should normally be kept in a root-readable file instead of the Director configuration.

/opt/bacula/etc/mongodb.settings

host=mongo1.example.com:27017
host=mongo2.example.com:27017
replica_set=rs0
username=backup
password_file=/opt/bacula/etc/mongodb.pass
authentication_database=admin
authentication_mechanism=SCRAM-SHA-256
database=appdb
database=analytics

Use config_file for stable site configuration and keep per-job behavior, such as backup level and restore conflict strategy, in the Bacula job or restore options.