Learn Bacula - Bacula 15.0.x & Latest Features

#Introduction

So far we've worked with one version: Bacula 15.0.4. But understanding where that version came from and where it's heading is part of professionalism — it determines when to upgrade, what changes, and what's risky. In episode 17 we examine the 15.0.x series and the history of previous versions.

Bacula is software that is 25 years old; every major release carries architectural decisions. Understanding 15.0.0 — and why 15.0.4 became the stable point we use — is the groundwork for planning upgrades in production.

#Bacula 15.0.4

#Release Status

Bacula 15.0.4 was released on 23 May 2026 as the latest stable release of the 15.0.x series. Its status: a bug fix and improvements release — not a major feature release, but consolidation. For the Community edition, the previous release was 15.0.3 (March 2026).

Verify the installed version

bacula-dir --version

The output shows the full version number along with the build date. Regularly checking against the latest release on bacula.org is a mandatory habit.

#What 15.0.4 Brings

A point release like 15.0.4 usually brings:

Bug fixes in the Director, Storage Daemon, and File Daemon.
Improvements in job handling, error handling, and catalog edge cases.
Updates to the bconsole tool and admin commands.

The operational lesson: for a stable system, point releases are low-risk upgrades that should be taken promptly — especially those containing fixes that touch your scenarios.

#15.0.0: The Big Leap

#Unified Catalog Improvements

The most substantial update is in 15.0.0: a major overhaul of the catalog. Its goal is one — performance at scale. In environments with hundreds of thousands of file records and thousands of volumes, old catalog queries could become a real backup bottleneck.

The 15.0.0 overhaul touched:

Catalog schema and indexes that are more efficient for common queries (list jobs, list files, restore lookups).
Metadata storage friendlier to bulk operations.
Faster volume handling with large pools.

The practical impact: jobs that used to slow down as the catalog grew now run more consistently. For new deployments (like ours), 15.0.x is the right starting point — you skip the schema-correction phase of early releases.

Note

"Unified catalog" means one single catalog handling all component metadata consistently. The consequence: migrating between Bacula versions requires a catalog upgrade — backing up the catalog before an upgrade is a mandatory step you must never skip.

#Version History

#The 13.x Series (2022-2023)

The 13.x series brought refinements to volume management, retention, and internal consistency — the foundation later overhauled in 15.x. Many online guides about Bacula still write syntax from the 13.x era; most of it remains valid, but always check your version's manual.

#The 11.x Series

The 11.x series was the modernization era — code structure updated and platform support expanded. This was when Bacula asserted its position as a serious suite for heterogeneous environments.

#Release Pattern

Bacula uses major (big features) + point (fixes) versioning. The safe upgrade practice:

Bacula upgrade pattern

1. Back up the catalog and configuration
2. Read the release notes between versions
3. Test in staging (restore drill!)
4. Upgrade components + migrate the catalog
5. Validate with bacula-dir -t and test a job

Never jump an upgrade without reading the migration notes — schema changes between major versions cannot be rolled back without a restore.

#Community vs Enterprise Feature Matrix

Mapping the features between editions matters before deciding to upgrade:

Bacula 15.0.x feature matrix

Feature                        Community   Enterprise
Core backup/restore                ✔           ✔
bconsole                          ✔           ✔
Tape & changer support            ✔           ✔
PostgreSQL/MySQL/SQLite           ✔           ✔
Console ACL                       ✔           ✔
Application/VM plugins             –           ✔
Deduplication                      –           ✔
Integrated media encryption        –           ✔
WORM / compliance                  –           ✔
BWeb dashboard                     –           ✔
Official vendor support            –           ✔

If you only need the left column, Community is complete — that's the edition we've used throughout the series. We dissect the right column in depth in episode 18.

Tip

Before upgrading, read the official release notes on bacula.org and the per-version change lists on GitHub bacula/bacula. Don't trust third-party blogs for migration details — use them as pointers, not as the source of truth.

#Closing

Key takeaways:

15.0.4 (23 May 2026) is the stable bug-fix release; 15.0.3 Community released March 2026.
15.0.0 brought unified catalog improvements and performance for large scale.
History: 13.x (2022-2023) foundation, 11.x modernization era.
Upgrades always start with a catalog backup + reading release notes + staging tests.
Community vs Enterprise: the feature columns differ clearly; choose per need.

In the next episode, episode 18, we'll compare Bacula Enterprise and Community thoroughly — application and VM plugins, deduplication, encryption, WORM, the BWeb dashboard, and when you should pay for a license versus going pure open source. This is the most important commercial decision in Bacula adoption.