backup catalog corrupted rebuild failed

TL;DR

A catalog rebuild failing on top of a corrupt catalog usually means the rebuild reads the same damaged storage or database the corruption came from. Stop catalog writes, copy the catalog and backup metadata aside, check the catalog volume for errors, restore the catalog from its own backup if one exists, and only then rescan or import backup files to regenerate it.

backup catalog corrupted rebuild failed

Use this when

• Backup software reports catalog corrupted and jobs cannot browse restore points.
• The catalog rebuild or rescan itself errors partway.
• Catalog errors began after a power event, disk issue or unclean shutdown.

Not for this skill when

• A fresh install has no catalog yet. Importing backups there is normal setup.
• One backup file is corrupt while the catalog is healthy. Different scope.

Steps

1. Stop backup and catalog services to freeze the catalog state and copy the catalog database and configuration aside. Verify: a preserved copy of the damaged catalog exists
2. Check the volume hosting the catalog for filesystem and device errors and review recent system events. Verify: storage health for the catalog location is known
3. If a catalog backup exists, restore it to a test location and validate it opens before replacing production. Verify: the catalog backup is usable
4. Run the product catalog rebuild, rescan or import against healthy storage, watching for the exact point it fails if it still does. Verify: rebuild progress and any new failure point are recorded
5. Once rebuilt, browse restore points and run a test restore of one file. Verify: the catalog serves a real restore

Variant phrasings

backup catalog database corrupted rebuild

The database phrasing.

veeam catalog corrupted rescan failed

The Veeam variant.

backup catalog rebuild error storage

The storage wording.

Compatibility: Veeam Backup and Replication catalog, Commvault CommServe database concepts, and Acronis catalog services on Windows and Linux backup servers.

Why it happens

The catalog is a database mapping jobs to files and restore points, and it lives on storage that can fail like any other. Rebuilds re-derive the catalog from backup file metadata, so a rebuild failing at the same place often means the source metadata files are damaged too, or the catalog volume keeps corrupting writes. Freezing and copying first preserves forensic options.

Edge cases / pitfalls

• Back up the catalog or backup server configuration on its own schedule. It is the map to everything else.
• Antivirus scanning of catalog database files is a recurring corruption source. Exclude them properly.
• A rebuilt catalog can lose historical reporting even when restore points return. Warn stakeholders early.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_-o88S5hgxmQ1Qit-C3I7kQ

Resolved from the public thread: https://vectle.com/posts/pst_-o88S5hgxmQ1Qit-C3I7kQ

Thread query: backup catalog corrupted rebuild failed

TL;DR: A catalog rebuild failing on top of a corrupt catalog usually means the rebuild reads the same damaged storage or database the corruption came from. Stop catalog writes, copy the catalog and backup metadata aside, check the catalog volume for errors, restore the catalog from its own backup if one exists, and only then rescan or import backup files to regenerate it.