Manage Multiple QCBM Off-Site Destinations

Max and All Access can manage multiple QCBM Export Destinations at the same time. This lets you keep different providers or storage purposes available while still designating one destination as the default for normal backup exports.

Multiple destinations do not mean that every backup is copied to every provider automatically. QCBM keeps one default destination for Profile auto-export and Export to Default; administrators can choose another destination manually when the plan includes multiple storage destinations.

Plan Requirements

Multiple Export Destinations require Max or All Access. Pro includes one off-site destination and limits backup export to the default destination.

The global off-site export setting must also be enabled before backup export actions can run.

Create and Name Each Destination Clearly

Open Settings > Export Destinations and create each storage target independently. Use names that identify the provider and purpose, such as “Google Drive — Long-Term Backups” or “SFTP — Disaster Recovery NAS.”

Each destination keeps its own provider type, connection settings, enabled state, default flag, notes, and Last Test result. A problem with one destination does not automatically make the others unusable.

Choose One Default Destination

Use Set Default on the destination that should receive normal default-based backup exports. QCBM keeps only one destination marked as default at a time.

The default is used by Export to Default and by Profile automatic export. Changing the default affects future exports; it does not move packages that were already exported to the previous destination.

Use Export to Other for a Specific Manual Copy

On Max and All Access, a completed Backup Set can use Export to Other from Backup History. QCBM presents the enabled/configured destinations that are available for selection.

This is useful when you want a particular recovery point copied to a secondary provider without changing the site's normal default destination.

Enable Only Destinations That Are Ready

A destination must be enabled and correctly configured before QCBM treats it as usable. Cloud destinations also need a current OAuth connection; SFTP requires the trusted host-key fingerprint; plain FTP requires the explicit insecure-transport acknowledgement.

Use Disable to take a destination temporarily out of service without deleting its saved configuration or historical export references.

Test and Monitor Destinations Independently

Run the provider Test after creating or changing each destination. Then manually export a real completed Backup Set before relying on the destination for routine use.

Monitor provider quota, credentials, authorization, host keys, remote paths, and permissions separately. A successful Test on Destination A says nothing about Destination B.

Keep the Local and Remote Results Distinct

QCBM records the local Backup Set and each export attempt separately. A failure on one remote destination can occur while the local Recovery Package remains complete and while another destination remains healthy.

When troubleshooting a multi-destination setup, identify the exact destination and export run before changing credentials or provider settings.

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.