Migrating from Bacula
NGBackup is wire-, config-, catalog- and volume-compatible with Bacula Community 15. You can adopt it incrementally — even run mixed deployments — without a forklift migration.
What stays the same
Section titled “What stays the same”- Configuration syntax — your
Director{},Storage{},Client{},Job{},FileSet{}resources work as-is. - Catalog & volumes — point NGBackup at an existing catalog and storage and resume.
- Concepts — jobs, levels, pools, schedules, retention all behave the same.
What changed (names only)
Section titled “What changed (names only)”| Bacula | NGBackup |
|---|---|
bacula-dir | backup-dir |
bacula-sd | backup-sd |
bacula-fd | backup-fd |
bconsole | backup-console |
bcopy / bextract / bls / bscan | backup-copy / backup-extract / backup-ls / backup-scan |
/opt/bacula/{bin,etc} | /opt/backup/{bin,etc} |
Suggested path
Section titled “Suggested path”- Stand up a NGBackup Director/SD alongside Bacula.
- Point it at a copy of the catalog; validate configs with
backup-dir -t. - Move clients over as you go; add the NGBackup plugins (dedup, ransomware, replication) for capabilities Bacula Community doesn’t have.