Understand QCBM Off-Site Backup Export

Off-site export copies QCBM's canonical Recovery Package to a second configured storage destination after the local Backup Set is complete and its package health is acceptable for export. The local backup and the remote export are tracked as separate outcomes so a provider failure does not erase a valid local recovery point.

Off-site export requires Pro, Max, or All Access. Pro supports one active destination; Max and All Access can manage multiple destinations and choose a non-default destination for manual export.

Supported Export Providers in QCBM 1.5.13

Current active connectors are:

  • Local / server path
  • SFTP / SSH
  • FTP
  • FTPS
  • Google Drive
  • OneDrive

Dropbox appears in the destination type list as a staged future connector, but QCBM 1.5.13 does not treat it as an active export provider. Do not rely on Dropbox for production exports in this build.

Plan Limits for Destinations

Pro can maintain one active off-site destination. Max and All Access enable multiple storage destinations. QCBM keeps one destination marked as the default; Pro exports to that default destination, while Max/All Access can also use Export to Other to select another usable destination.

Enable Off-Site Export Before Using It

The global off-site export setting must be enabled. A saved destination by itself does not cause QCBM to transfer Backup Sets. The destination must also be published, use an active provider, and contain the required configuration/authorization.

Manual Export

For a complete Backup Set, Backup History can offer Export to Default. Max/All Access can additionally use Export to Other when multiple usable destinations exist.

QCBM obtains a per-Backup-Set operation lock, rechecks the local package/part health, confirms the destination is usable, and then transfers the canonical Recovery Package. A Backup Set that is incomplete or has failed package health is blocked from export.

Automatic Export

A Profile can enable Auto-export after a successful verified backup. Automatic export also requires the global export-after-backup setting to be enabled.

Current Profile saving does not choose a separate destination ID for each Profile. Automatic export uses QCBM's primary/default active destination. If you need a different destination for a particular Backup Set and your entitlement allows it, use the manual Export to Other workflow.

Destination Testing and Export Verification Are Separate

The destination Test action proves the saved provider configuration can perform a small controlled write/verification/cleanup operation. It is an important setup check, but it is not the same as a real Backup Set export.

A real export records its own export run and file result. For the canonical package, QCBM transfers the file and records the export as complete only after its provider-specific verification succeeds.

Local Backup Health and Remote Export Health Are Separate

If a remote destination rejects credentials, loses quota, times out, or fails a provider operation, QCBM can mark the export failed/partial while preserving the already-valid local Recovery Package.

This separation is useful during troubleshooting: protect the good local recovery point first, then repair the remote destination and retry export.

Test Before Relying on Automatic Export

  1. Create/save the destination with the correct provider settings.
  2. Enable/connect it as required.
  3. Run the destination Test.
  4. Create or select a complete verified Backup Set.
  5. Run one manual export to the intended destination.
  6. Confirm the export result and the provider-side copy.
  7. Only then rely on Profile auto-export.

Security Considerations

Prefer encrypted transports/providers. SFTP is preferable to plain FTP when available; QCBM requires an explicit acknowledgement before plain FTP can be used because credentials and backup data are transmitted without transport encryption.

Protect OAuth application secrets, remote passwords, and provider accounts because an off-site Recovery Package contains sensitive site/database material.

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.