Enable Automatic Off-Site Export for a QCBM Backup Profile

On Pro, Max, and All Access, a QCBM Profile can automatically export its verified Recovery Package after the local Backup Set finishes successfully. Automatic export is deliberately a second step: QCBM first creates and verifies the local recovery point, then attempts the configured export.

That separation matters during troubleshooting. A remote-provider failure can leave you with a valid local Backup Set that should be preserved while the destination is repaired.

Prepare the Export Destination First

  1. Open QCBM's off-site/export destination management.
  2. Create or review the destination you intend to use.
  3. Make sure the destination is published and fully configured.
  4. Run its destination test and correct any connection, credential, path, or provider problem before relying on automation.
  5. Set the intended destination as the default if the Profile should use the normal default target.

QCBM supports active configured destinations for Local, SFTP, FTP, FTPS, Google Drive, and OneDrive when the provider is available in the current build.

Enable Auto-Export on the Profile

  1. Go to Components > QC Backup Manager > Profiles.
  2. Edit the Profile.
  3. In Retention and Profile Options, enable Auto-export after a successful verified backup.
  4. Save the Profile.

QCBM also has global export settings. Automatic Profile export runs only when the Profile option is enabled and the global export after backup behavior is enabled.

Which Destination Does Automatic Export Use?

A Profile does not store a separate destination ID in the current 1.5.13 Profile save workflow. Automatic export uses QCBM's primary/default export destination. QCBM enforces a single default and selects that destination for default-based export operations.

Changing the default destination affects future default-based operations. It does not rewrite the destination recorded for export attempts that already happened.

Local Backup Success Comes First

QCBM reaches automatic export only after the Backup Set has completed database/archive/part/manifest verification and received its canonical Recovery Package. The local Backup Set is therefore established before the remote copy is attempted.

During automatic export, QCBM verifies that the Backup Set is complete, checks the saved backup parts, confirms the destination is active/configured, and copies the canonical Recovery Package to the destination. Successful export records its own run and marks the backup export state accordingly.

What If Automatic Export Fails?

If the remote export throws an error after the local Recovery Package is complete, the persistent backup job can still finish with a message explaining that the local package is complete but automatic export needs review.

Do not delete a healthy local Backup Set just because the remote copy failed. Instead:

  1. Open Backup History and confirm the local set is complete and verified.
  2. Review the export state and export-run message.
  3. Test the destination again.
  4. Correct credentials, provider access, remote path, quota, network, or configuration issues.
  5. Retry/export the verified Backup Set after the destination is healthy.

Why Destination Testing Still Matters

QCBM can attempt an export to an active configured destination even if an earlier test is old, so the destination test should be treated as an operational readiness check rather than a one-time checkbox. The test performs provider-appropriate connection/upload work and records the latest pass or failure message.

Run a fresh test after credential changes, provider changes, remote-folder changes, firewall changes, or a failed automatic export.

Verify the First Automatic Export

Create a controlled backup with the Profile. Confirm the local Backup Set becomes complete and verified, then confirm the export run reports completion and the Recovery Package exists at the intended destination.

Only after both results are proven should you rely on the Profile for unattended off-site protection.

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.