Backup catalog
A backup catalog is a metadata repository that records backup jobs, saved objects and their media or locations to support restore selection.
Index and payload: File indexes and job-to-volume records locate recovery data; the stored file contents remain on backup media. A catalog can cover many jobs, unlike an inventory for one backup. [1]
Reconstruction: The documented bscan procedure rebuilds catalog entries from surviving volumes, but not Client records or changer-slot assignments. For records spanning volumes, include all necessary volumes in one scan; out-of-order scanning can leave a newly reconstructed catalog incomplete. Retain the matching client and device configuration. [2]
History: A recovery catalog can retain metadata longer than a database control file. Recreating it only from that control file cannot recover records that have aged out; available backups may need separate recataloging. [3]
Recovery scope: Catalog loss and payload loss are different failures. A surviving catalog does not recreate missing backup contents, and absent catalog entries do not establish that the media was erased. Verify recovered contents after locating the intended copy. [1] [2] [3]
After scanning: Retention rules can prune reconstructed records again. The scan cannot recover all original job timestamps, so CopyJob, MigrationJob and VirtualFull ordering can differ, affecting always-incremental chains. Check retention and chain order before treating the rebuilt catalog as ready. [2]
Relations
- related
- Backup, Backup manifest, Restore test, Backup verification
Limitations
- Catalog protection must include its own recovery dependencies; storing it with the database and disks it protects exposes both to the same failure. [3]
Citations
- Bareos 25: catalog indexes and the separate storage daemon
- Bareos 25: bscan reconstruction, missing metadata and multi-volume ordering
- Oracle Database 19: recovery-catalog history, protection and partial reconstruction
Further reading
Sources & caveats
- Bareos 25 and Oracle Database 19 describe different implementations, not a shared catalog schema or universal reconstruction guarantee.
- Documentation synthesis; no catalog rebuild or backup restore was executed.