{
  "slug": "backup-catalog",
  "term": "Backup catalog",
  "aliases": [
    "backup catalogue"
  ],
  "definition": "A backup catalog is a metadata repository that records backup jobs, saved objects and their media or locations to support restore selection.",
  "note": "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. [bareos-catalog]\n\nReconstruction: 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. [bareos-bscan]\n\nHistory: 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. [rman-catalog]\n\nRecovery 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. [bareos-catalog] [bareos-bscan] [rman-catalog]\n\nAfter 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. [bareos-bscan]",
  "status": "shipping",
  "advantages": [],
  "limitations": [
    {
      "text": "Catalog protection must include its own recovery dependencies; storing it with the database and disks it protects exposes both to the same failure.",
      "citationIds": [
        "rman-catalog"
      ]
    }
  ],
  "related": [
    "backup",
    "backup-manifest",
    "restore-test",
    "backup-verification"
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-16",
  "citations": [
    {
      "id": "bareos-catalog",
      "title": "Bareos 25: catalog indexes and the separate storage daemon",
      "url": "https://docs.bareos.org/bareos-25/IntroductionAndTutorial/WhatIsBareos.html#catalog",
      "accessed": "2026-11-16"
    },
    {
      "id": "bareos-bscan",
      "title": "Bareos 25: bscan reconstruction, missing metadata and multi-volume ordering",
      "url": "https://docs.bareos.org/bareos-25/Appendix/BareosPrograms.html#bscan",
      "accessed": "2026-11-16"
    },
    {
      "id": "rman-catalog",
      "title": "Oracle Database 19: recovery-catalog history, protection and partial reconstruction",
      "url": "https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/managing-recovery-catalog.html",
      "accessed": "2026-11-16"
    },
    {
      "id": "hesela-recovery",
      "title": "Hesela: Snapshots and backups: which failures can you recover from?",
      "url": "https://hesela.com/analyses/snapshot-backup-recovery-boundaries/",
      "accessed": "2026-11-16"
    }
  ],
  "provenance": [
    "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."
  ]
}
