Download and Use the Permanent QCBM Backup Log

QCBM maintains a permanent backup-run ledger separately from the retained Backup Set artifacts and ordinary age-limited operational logs. The Download Backup Log action exports that ledger as CSV so you can review manual and scheduled backup history even after a Recovery Package has been removed by retention or manual deletion.

The Backup Log is evidence of what QCBM recorded about a run; it is not proof that a deleted package still exists or is recoverable.

Download the CSV

  1. Open Components > QC Backup Manager > Backups.
  2. Find the Backup History toolbar.
  3. Click Download Backup Log.
  4. Save the CSV and open it in a spreadsheet, database tool, or text editor that preserves timestamps and long identifiers.

The action requires permission to download QCBM backup material/history.

What the Permanent Ledger Contains

QCBM 1.5.13 exports one row per recorded backup run with these current fields:

  • Backup ID and Backup UID;
  • Profile ID and Profile title;
  • Backup title and backup type;
  • run source;
  • schedule rule and human-readable schedule;
  • scheduled occurrence in UTC and in the site-local representation;
  • site timezone;
  • started and completed UTC timestamps;
  • status and verification state;
  • failure phase and failure message;
  • size in bytes and part count;
  • creator user ID;
  • Receiver verification/device/delete-request/delete-status evidence;
  • server-copy deletion time and source;
  • QCBM build version;
  • ledger created and updated timestamps.

Distinguish Run Source

The run-source field helps separate a normal manual backup from scheduler-driven activity and other QCBM-created recovery points. This is useful when a customer reports “a backup appeared” or “the scheduled backup did not run” because you can identify how the recorded run was initiated instead of relying on its title alone.

Use Schedule Fields to Audit Automation

For scheduled runs, compare the schedule rule/description, scheduled occurrence, site timezone, and actual start/completion timestamps. This can show whether a Profile became due correctly but started on a later task poll, or whether the recorded run belonged to a different scheduled occurrence.

Use Failure and Verification Fields Together

Status alone does not tell the whole story. Review the verification state and any failure phase/message alongside the run status. A failed verification is different from a preflight failure, a cancellation, or a remote export problem.

When troubleshooting a current Backup Set, pair the CSV record with the live Backup History findings and current storage/package verification.

Receiver and Server-Copy Evidence

For QCBM Receiver workflows, the ledger can retain Receiver verification, device, deletion-request, and deletion-status fields. It also records when the server copy was deleted and the source of that deletion event.

These fields are useful when the local server no longer retains the Recovery Package but you need to understand the historical movement/deletion lifecycle.

Why the Ledger Survives Normal Backup Set Deletion

When QCBM permanently deletes a Backup Set, it purges the live Backup History row and related operational records but updates the separate backup-run ledger before doing so. Profile retention can likewise remove old retained Backup Sets without deleting this dedicated ledger.

This is different from QCBM's configurable operational, export, and audit-history retention settings. Those settings age out their own tables; they are not the permanent backup-run ledger.

What the Backup Log Cannot Prove

A historical row does not prove that the Recovery Package still exists, that an off-site destination is currently reachable, or that the package still passes its checksum. Use Backup History/Verify for retained local packages and provider-side checks for remote copies.

Practical Uses

  • Confirm whether a backup was manual or scheduled.
  • Compare scheduled occurrence with actual execution.
  • Review historical failures after short-lived operational logs have expired.
  • Track Receiver acknowledgement and server-copy deletion evidence.
  • Preserve a long-term run audit trail for maintenance records.

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.