Understand QCBM Backup History and Backup Health

QCBM uses Backup History for individual Backup Sets and the Status page's Backup Health card for installation-wide totals. They answer different questions: Backup History tells you what happened to a specific recovery point; Backup Health tells you how much backup material and active work QCBM currently sees.

A separate Download Backup Log CSV provides the deeper permanent run ledger when you need schedule, source, timing, failure, receiver, or version evidence that is not all displayed on the Backup History card.

Read an Individual Backup History Record

Open Components > QC Backup Manager > Backups. Each current Backup History record shows the most important operational information for that Backup Set, including:

  • backup type;
  • current Backup Set status;
  • Recovery PIN status/value when your permissions allow it;
  • Backup Set title;
  • recorded total size;
  • created time;
  • Profile name;
  • Managed Private Storage location;
  • available download, export, cleanup, or delete actions.

Do not expect every run-ledger field to appear in this compact card.

Pay Attention to Findings

Backup History surfaces a findings area when QCBM detects something that requires review. Depending on the record, that can include:

  • a saved failure message and failed phase;
  • missing or unreadable stored package material;
  • unexpected working files left in the Backup Set folder;
  • partial-delete state;
  • failed or partial export state.

For failed runs, QCBM can also expose stored failure context so you can diagnose the phase rather than guessing from a generic “backup failed” description.

Understand Status Versus Verification

Backup completion and verification are related but distinct. A complete Backup Set can be re-verified later; a failed or cancelled set should not be treated as a recovery point merely because a Backup History row exists.

For recovery, prefer a Backup Set that is complete and verified and whose Recovery Package is still present and healthy.

What the Backup Health Card Counts

Open Status and find Backup Health. Current QCBM reports:

  • Backup sets — total Backup Set rows currently recorded;
  • Verified sets — Backup Sets whose current verification state is verified;
  • Profiles — configured Backup Profiles;
  • Parked files — files QCBM has placed in its parked-file handling area;
  • Active backup jobs — shown when queued or running backup jobs currently exist.

The Active backup jobs count is specifically based on queued/running job state; paused or postponed jobs are not included in that particular Status-card total.

Use Backup Health as a Summary, Not Proof of One Backup

A high verified-set count does not prove that the particular Backup Set you plan to use is healthy. Likewise, a healthy storage/scheduler summary does not replace checking the individual Backup History record and verification state.

Use Backup Health to spot broad changes, then drill into the specific Backup Set that matters.

Download the Permanent Backup Log for Deeper Evidence

When permitted, the Backup History toolbar includes Download Backup Log. The CSV comes from QCBM's permanent backup-run history table and includes fields that go beyond the compact Backup History card, including:

  • Backup ID and UID;
  • Profile ID/title and backup title/type;
  • run source;
  • schedule rule and schedule description;
  • scheduled occurrence in UTC and local time;
  • site timezone;
  • started and completed UTC timestamps;
  • status and verification state;
  • failure phase and message;
  • size and part count;
  • receiver evidence and server-copy deletion fields;
  • QCBM version and ledger timestamps.

This is where you should look for source, schedule, timing, and historical evidence that is not all rendered directly on the Backup History card.

Understand What Retention Can Remove

Profile retention can remove old eligible local Backup Sets and their recovery material. Separately, QCBM Settings define age limits for operational logs/jobs, export history, and audit history. The dedicated backup-run ledger used by Download Backup Log is different from those age-limited operational tables.

Do not assume that every historical screen and every artifact has the same retention lifecycle.

A Practical Review Sequence

  1. Use Status > Backup Health to see the installation-wide counts.
  2. Open Backups > Backup History and locate the specific Backup Set.
  3. Read its status, Profile, size, storage location, available actions, and any findings.
  4. Re-verify an important older Backup Set when appropriate.
  5. Use Download Backup Log when you need exact schedule/source/timing/failure evidence.
  6. Do not rely on a Backup Set for recovery until its current recovery material is complete and verified.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCBM feature? Visit the QC Backup Manager Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.