Automatically Export Verified QCBM Backups Off-Site

QCBM can automatically export a Backup Set after the local backup has completed and passed verification. Automatic export is deliberately a later stage: QCBM first creates the local Recovery Package, marks the Backup Set complete/verified, and only then attempts the optional off-site transfer.

An automatic-export failure does not automatically invalidate the verified local Backup Set. QCBM reports the export problem separately so you can preserve the local recovery point while fixing the destination.

Requirements for Automatic Export

All of the following must be true:

  • Your plan includes off-site export (Pro, Max, or All Access).
  • Off-site export actions are enabled in Settings.
  • The installation has a usable default Export Destination.
  • The Backup Profile has Auto-export after a successful verified backup enabled.
  • The global export-after-backup setting is enabled.

The automatic path uses QCBM's primary/default destination; the Profile does not select a separate destination for each run.

Enable Auto-Export on the Profile

  1. Create and test the destination that should receive automatic backups.
  2. Make that destination the default.
  3. Open the Backup Profile you want to automate.
  4. In Retention and Profile Options, enable Auto-export after a successful verified backup.
  5. Save the Profile.

Before relying on automation, manually export one completed Backup Set to the same default destination.

What Happens After a Successful Backup

During the backup workflow, QCBM creates and verifies the canonical Recovery Package and records the Backup Set as complete with verification state verified. The persistent job then moves to the optional auto-export phase.

If the Profile and global settings allow automatic export, QCBM starts a normal export using the default destination. The export path performs its own operation-lock and package-health checks before transfer.

What Happens When Auto-Export Fails

QCBM keeps the local Recovery Package complete and records that automatic export needs review. Provider failure, expired OAuth authorization, wrong credentials, quota exhaustion, network problems, or a destination configuration change can therefore produce a good local backup and a failed remote copy at the same time.

Do not delete the local Backup Set while troubleshooting the provider. Re-test the destination and manually retry an export after correcting the problem.

Changing the Default Changes Future Auto-Exports

Profile auto-export follows the current usable default destination. If you change the default, future automatic exports use the new default; historical packages are not automatically moved between providers.

After changing the default, test it and perform one manual export before the next scheduled Profile run.

Verify the Automation

  1. Run the Profile once under controlled conditions or allow its next scheduled occurrence.
  2. Confirm the Backup Set reaches complete/verified state.
  3. Confirm the automatic export result is successful.
  4. Confirm the destination/account/folder is the intended one.
  5. Review future failures as export problems unless QCBM also reports a local backup/verification failure.

Operational Practice

Periodically test the default destination even when automation has been healthy. Cloud tokens, remote-server passwords, SSH host keys, mounted storage, quotas, and permissions can change independently of the Backup Profile.

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.