Bacula backup catalog recovery

A lost Bacula catalog does not necessarily erase backup volumes, but it removes the index that makes restores efficient and reliable.

The Bacula catalog tracks jobs, clients, files, volumes and media positions. Backup data can remain on disk or tape after the catalog database is lost, but recovery must reconstruct enough metadata to identify and restore the required sessions.

Understand the symptom

Catalog recovery connects Bacula volume records and job streams to a consistent database schema.

WHY

What is happening

A database backup is the preferred source when it matches the Bacula version and volume set. When it is unavailable, tools such as bscan can read volume records back into a prepared catalog, but incomplete media, wrong schemas or duplicate records can produce an incomplete index. Bootstrap files can narrow recovery to known jobs or file positions.

What you may see

Symptoms that change the recovery path.

01

Director starts with an empty catalog

Jobs and volumes exist physically but no longer appear in restore selection.

02

Catalog database will not start

Database corruption, missing files or storage failure blocks Bacula metadata access.

03

Volumes show unknown or purged

Catalog state no longer matches labels and data on media.

04

Restore tree is incomplete

Some job or file records were not imported or the required volume is absent.

Protect the source

Actions that can make the situation worse.

01

Recycling can overwrite the only backup

A volume judged expired by a new catalog may still hold required data.

02

Broad bscan imports can duplicate state

Repeated scans into a changing catalog complicate job and file relationships.

03

Relabeling erases original identity

Media labels connect physical volumes to job streams and should be preserved.

Do this now

Safe steps before evaluation.

01

Disable backup schedules

Stop new jobs, pruning, retention, recycling and volume initialization.

02

Inventory all media

Record labels, barcodes, pools, sizes, tape locations, disk paths and last-write times.

03

Preserve configuration and metadata

Keep Director, Storage Daemon and File Daemon configs, logs, bootstrap files and catalog dumps.

04

Clone disk volumes when possible

Work from protected copies so scans do not change or compete with backup storage.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Version and media mapping

NEPFOSYS correlates Bacula release, catalog schema, volume labels, jobs and available dumps.

02

Protected catalog reconstruction

Catalog restore or targeted volume scanning is tested in an isolated database.

03

Restore validation

Priority clients, dates and file selections are restored to separate storage and checked for completeness.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Can bscan rebuild the Bacula catalog?

It can repopulate records by scanning Bacula volumes, but results depend on complete readable media, compatible schema and careful handling of duplicates.

Are bootstrap files useful without the catalog?

Yes. They can identify jobs and media positions for targeted restores, though they are not a complete replacement for the catalog.

Should I create a new empty catalog and resume backups?

Not on the same media pools. First preserve and reconstruct the old backup inventory so existing volumes are not recycled or overwritten.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case