Clean Up Temporary Working Files for a QCBM Backup Set

QCBM can remove a limited set of known working artifacts that are no longer needed after a completed Backup Set's canonical Recovery Package has passed full verification. This is a targeted cleanup tool, not a general-purpose file deleter.

The cleanup action appears only when QCBM detects recognized temporary/support files in a completed Backup Set folder. It verifies the recovery material before deleting anything.

When QCBM Offers Clean Up

In Backups > Backup History, a completed Backup Set can show a finding that unexpected working files remain in its managed folder. If QCBM recognizes one or more of those files as safe cleanup candidates and your account has integrity-management permission, the finding includes a Clean Up action.

QCBM does not offer this action for an incomplete Backup Set.

Verify Before Removing Working Files

Before cleanup proceeds, QCBM rechecks the completed Backup Set. The stored backup parts must pass size/checksum health checks, and the canonical Recovery Package must be ready and pass ZIP verification.

If either check fails, QCBM blocks cleanup with a message that the Recovery Package must pass full size, checksum, and ZIP verification first. This prevents cleanup from becoming an accidental substitute for fixing a damaged recovery point.

Run the Cleanup

  1. Open Components > QC Backup Manager > Backups.
  2. Find the completed Backup Set in Backup History.
  3. Review the finding that lists unexpected working files.
  4. If available, click Clean Up.
  5. Read the result message showing which known files were removed or which files could not be deleted.
  6. Re-verify the Backup Set if you want an additional post-cleanup integrity confirmation.

What QCBM Considers a Known Cleanup Candidate

QCBM restricts automatic cleanup to filenames it knows can be temporary working/support artifacts for that Backup Set. Current logic can recognize raw database/files/full archive artifacts tied to the Backup Set UID, including split working parts, plus specific support files such as the recovery runner/instructions and source-index/metadata support files when they are left outside the canonical package.

It does not iterate through arbitrary unknown files and delete them simply because they are unexpected.

The Backup Set Folder Must Be Proven to Belong to QCBM

QCBM also verifies the managed path before deleting candidates. The stored folder must exist, its basename must match the Backup Set UID, and the path must pass QCBM's managed Backup Set ownership check.

If that ownership check fails, cleanup stops and removes nothing.

What Cleanup Does Not Remove

This action is not the same as deleting a Backup Set. It does not intentionally remove the canonical verified Recovery Package, manifest, or the Backup History record. It also does not reach into unrelated folders or off-site destinations.

If the goal is to remove the entire Backup Set, use the dedicated permanent delete workflow after confirming the recovery point is no longer needed.

Understand Partial Cleanup Results

If QCBM deletes some candidates but cannot remove others because of file permissions or filesystem conditions, it reports a warning and names the files that remain. Fix the underlying filesystem issue before repeating cleanup rather than manually deleting broad portions of Managed Private Storage.

Verify the Result

After successful cleanup, the known temporary files should no longer appear as a finding for that Backup Set. The Backup Set should still have a usable canonical Recovery Package. For an important recovery point, run Verify and confirm the package, manifest, recorded size, and SHA-256 checksums still pass.

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.