Note

You can download this article as a PDF

MongoDB Plugin

Enterprise

Bacula Enterprise Only

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

This document describes the Bacula Enterprise MongoDB Plugin, a dedicated Bacula Enterprise File Daemon plugin that protects MongoDB deployments using MongoDB-supported logical backup and restore tools integrated with Bacula Enterprise scheduling, cataloging, retention, storage, and restore workflows.

MongoDB is a distributed document database commonly used for application data, event records, service metadata, analytics pipelines, and high-volume operational workloads. Production MongoDB environments may be deployed as standalone servers, replica sets, or sharded clusters. They may also use authentication, TLS, client certificate authentication, and different recovery expectations depending on the business criticality of each database.

Traditional filesystem backups are not sufficient for many MongoDB deployments because live database files can change while they are being copied. The MongoDB Plugin addresses this by coordinating logical backups through mongodump and logical restores through mongorestore while adding Bacula-specific safety metadata, checksum validation, recovery-chain metadata, and operator guardrails.

Why Use Bacula Enterprise with MongoDB

Bacula Enterprise provides centralized policy control, cataloged recovery, long-term retention, encryption, deduplication-compatible storage targets, tape, object storage, and off-site or air-gapped protection. The MongoDB Plugin adds MongoDB-aware backup and restore behavior so backup administrators can protect MongoDB data without writing ad-hoc scripts around Bacula jobs.

The plugin is especially useful when organizations need:

  • Consistent logical backups of MongoDB application databases

  • Replica-set incremental and differential backup chains based on oplog capture

  • Point-in-time recovery within the available oplog window for replica-set chains

  • Controlled sharded-cluster backup and restore through mongos

  • Explicit isolated disaster-recovery workflows for sensitive admin database data

  • Authentication, TLS, and client certificate support in Bacula-managed jobs

  • Clear dry-run reporting before backup or restore changes are made.

The next sections explain supported topologies, installation, Fileset configuration, operational workflows, limitations, and troubleshooting guidance.

Read more:

See also

Previous articles:

Go back to: Databases.