Remove Local and Verified Off-Site Copies of a QCBM Backup Set

QCBM can optionally delete recorded completed off-site exports at the same time you permanently delete the local Backup Set. This is intentionally more destructive than ordinary local deletion and should be used only when the local package and the known off-site copies are all no longer required.

Remote cleanup is based on QCBM's recorded completed export rows and applies provider-specific ownership checks before it removes files or Backup Set folders.

Confirm You Have Another Recovery Path First

Before deleting every known copy of a Backup Set, identify another complete and verified recovery point that you are prepared to use. If this Backup Set is the last known good package, do not combine local and off-site deletion merely to reduce storage use.

Select Remote Cleanup in the Delete Dialog

  1. Open Components > QC Backup Manager > Backups.
  2. Locate the Backup Set and click Delete.
  3. Review the Recorded off-site destinations list. QCBM shows destinations with completed export records and the number of recorded files.
  4. Select Also delete verified copies and their Backup Set folders on the destinations listed above.
  5. Reconfirm that no listed copy is still needed.
  6. Click Permanently Delete Backup Set.

Which Remote Copies QCBM Tries to Delete

QCBM builds remote cleanup from completed export records for the selected Backup Set. It does not scan an entire provider account looking for similarly named files.

For each recorded destination, QCBM uses the saved provider configuration and verifies that the remote/local export path belongs to the selected Backup Set before deleting it.

Provider-Specific Ownership Checks

The deletion safeguards vary by connector:

  • Google Drive and OneDrive use recorded file/folder identifiers and verify the Backup Set folder name and expected parent relationship before removing the folder.
  • Local/server-path exports must remain inside the configured destination root and must match the expected Recovery Package/Backup Set path pattern.
  • SFTP, FTP, and FTPS cleanup verifies the recorded remote folder corresponds to the selected Backup Set under the configured destination root.

If an ownership check fails, QCBM reports the remote cleanup failure instead of broadening the delete target.

What Happens if Remote Cleanup Partly Fails

QCBM may successfully remove the local Backup Set while one remote provider refuses or cannot complete deletion. In that case it does not pretend the whole operation succeeded.

The local files are cleared, the Backup Set is kept in a delete_partial/missing state, and the failure message identifies the remote destination that still needs attention. The Backup History record remains so you can review or retry safely.

What Happens After Full Success

When local deletion and all requested remote cleanup complete successfully, QCBM purges the local Backup History and related operational records. It reports how many verified remote files, Backup Set folders, and destinations were removed.

The permanent backup-run ledger is updated with the server-copy deletion time/source before the Backup Set row is purged.

Credentials Still Matter During Deletion

Deleting a remote copy requires QCBM to authenticate to that destination. A previously successful export does not guarantee deletion will work months later if OAuth authorization, passwords, provider permissions, network access, or the destination configuration has changed.

If credentials are no longer valid, restore access or remove the remote copy through the provider after carefully identifying the exact Backup Set.

Verify the Result

After the operation, confirm the Backup Set is gone from local Backup History only when the delete completed fully. If QCBM reports partial remote cleanup, preserve that record until every intended remote copy is accounted for.

Do not interpret removal from the local server as proof that Google Drive, OneDrive, SFTP, FTP, FTPS, or a local export path was also cleaned successfully.

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.