Manually Export a QCBM Backup Set Off-Site

A manual export copies a completed QCBM Backup Set's canonical Recovery Package to an enabled/configured Export Destination without changing the local backup into a different backup type. The local Backup Set and the off-site export remain separate results.

Off-site export requires Pro, Max, or All Access, the global export actions setting must be enabled, and your Joomla account must have permission to export backups.

Before You Export

Make sure at least one Export Destination is enabled and configured. Test the destination first and keep the local Backup Set until the remote transfer is confirmed.

QCBM shows manual export actions for completed Backup Sets. When export starts, QCBM acquires a per-Backup-Set operation lock and rechecks the stored package/part health before transferring anything.

Export to the Default Destination

  1. Open Backups > Backup History.
  2. Locate the completed Backup Set you want to copy.
  3. Choose Export to Default.
  4. Allow the export to finish and review the export result.

The action uses the current usable default destination. On Pro, backup export is limited to that default destination.

Export to Another Destination

Max and All Access can use Export to Other when multiple storage destinations are available:

  1. Choose Export to Other for the Backup Set.
  2. Select an enabled/configured destination from the modal.
  3. Choose Export Now.
  4. Review the result for that destination.

If your plan does not include multiple storage destinations, QCBM disables this action and directs exports to the default destination.

What QCBM Sends

QCBM exports the canonical Recovery Package produced for the Backup Set. Before transfer, the export path verifies that the Backup Set is complete and that its stored package/part health is acceptable.

The destination connector then creates or selects the appropriate target location and transfers the package using the provider-specific workflow.

The Local Backup and Remote Export Are Separate

An off-site export can fail even though the local Backup Set remains complete and usable. QCBM records export attempts separately so you can fix a provider problem without discarding a good local recovery point.

Likewise, a successful local backup is not proof that the remote copy exists. Check the export result before treating it as your second copy.

If QCBM Blocks the Export

Use the returned message to identify the reason. Common blocks include:

  • off-site export disabled in Settings;
  • no usable destination;
  • the Backup Set is not complete;
  • the Backup Set is already being exported, deleted, or processed by retention;
  • the package/part health check fails;
  • the selected destination is disabled, incomplete, disconnected, or not allowed by the current plan.

Verify the Result

Confirm that QCBM records the export as successful for the intended destination. For important recovery points, periodically verify that the provider account and folder remain accessible; destination credentials, authorization, quota, and permissions can change after a successful transfer.

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.