MongoDB Plugin: Limitations

Bacula Enterprise Only

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

The MongoDB Plugin is designed for Bacula-managed logical backup and restore workflows. The following operating boundaries help keep backup artifacts consistent and restore behavior predictable.

The plugin runs from a Bacula File Daemon host and is currently focused on Linux deployments.
MongoDB Database Tools must be installed and executable by the File Daemon environment, as described in MongoDBToolsInstallation.
Replica set operations should connect through a replica set URI or directly to the writable primary. Direct secondary backup is rejected.
Sharded cluster operations should connect through mongos. The plugin does not back up shard members or config servers directly, and config database recovery remains a manual administrative operation.
Sharded Incremental and Differential jobs are stored as full-style logical artifacts, not oplog deltas. Sharded oplog point-in-time replay is not currently exposed.
Sharded admin replay is intentionally blocked by automated restore guardrails; recover sharded users and roles manually when required.
Standalone Incremental and Differential jobs are also stored as full-style logical artifacts because standalone servers do not provide an oplog chain.
Restore to an older MongoDB major version is rejected. Restore to the same or a newer compatible major version is the expected path.
MONGODB-X509 requires TLS, a client certificate/key file, and authentication_database=$external.
tls_allow_invalid_hostnames=yes reduces TLS identity validation and should be limited to controlled test or migration scenarios.