Backup Parameters
EnterpriseBacula Enterprise Only
This solution is only available for Bacula Enterprise. For subscription inquiries, please reach out to sales@baculasystems.com.
The following parameters control backup scope and behavior.
Option |
Required |
Default |
Values |
Example |
Description |
|---|---|---|---|---|---|
|
No |
All application databases |
Database name |
|
Application database to include. Repeat or use comma-separated values where supported. |
|
No |
Database name |
|
Database to exclude after include selection. |
|
|
No |
All collections |
Collection name |
|
Collection name to include across selected databases. |
|
No |
Collection name |
|
Collection to exclude after include selection. |
|
|
No |
|
|
|
Include |
|
No |
|
|
|
Skip application users and custom roles. |
|
No |
|
|
|
Delete local artifact root after successful backup. Mainly for orchestrated runs. |
|
No |
|
|
|
Run backup preflight only. |
|
No |
|
|
|
Dry-run report format. |
Bacula Level Behavior
The plugin uses Bacula job metadata and local chain state to resolve the previous artifact for Incremental and Differential jobs.
For standalone and sharded deployments, Incremental and Differential jobs run as safe full-style fallback artifacts. For replica-set primaries, they capture oplog segments and participate in a point-in-time recovery chain.
Security Capture
By default, the plugin captures selected application database users and custom
roles when the MongoDB user has sufficient privileges. Use skip_security=yes
for lower-privilege data-only backups.
Use include_admin=yes only when the backup is intended for isolated disaster
recovery. Normal in-place restore of admin content is intentionally guarded
because it can overwrite administrative users and roles.
See also
Previous articles:
Next articles:
Go back to: Plugin Configuration.