Enable, Disable, Edit, and Delete QCBM Export Destinations

Export Destinations are reusable storage configurations. QCBM lets you edit their provider settings, enable or disable them without deleting the configuration, change the default destination, test them, and remove destinations that are no longer needed.

Treat destination deletion separately from deleting remote backup files. Removing a destination configuration does not mean QCBM has erased every Recovery Package previously exported through it.

Use the Export Destinations List

Open Settings > Export Destinations. Each row shows the destination name/type, current status, default state when applicable, last test information, and actions such as Edit, Connect/Reconnect for cloud providers, Test, Set Default, Enable/Disable, and Delete.

Edit a Destination

Choose Edit to change the provider configuration, path/folder, credentials, OAuth application settings, notes, enabled state, or default state. Provider-specific fields are shown for the selected destination type.

When an existing remote-server password or cloud secret is already stored, QCBM can preserve it when the password/secret field is left blank as indicated by the UI. After changing connection information, run the destination Test again.

Enable and Disable

Disable stops the destination from being selected as a usable target for new export work while preserving its saved configuration. This is usually the right temporary action during maintenance, credential rotation, quota problems, or a storage-provider incident.

Enable returns the destination to published use, subject to its current configuration and connection state. On a plan that permits only one off-site destination, QCBM prevents enabling another destination while a different one is already enabled.

Cloud Connection State

Google Drive and OneDrive require provider authorization in addition to saved app credentials. Use Connect after saving a new cloud destination, Reconnect after application or permission changes, and Disconnect when that destination should no longer retain authorization.

Run Test after connection-state changes before returning the destination to automatic use.

Delete a Destination Safely

Before deleting, confirm which backup/export procedures still depend on the destination and whether any remote packages must be retained or deliberately removed.

If the destination has no historical export references, QCBM can delete the destination row. If export history still refers to it, QCBM instead keeps a secret-free archived label row for historical records while clearing active credentials/path data and removing it from active/default use.

What Destination Deletion Does Not Do

Deleting the destination configuration does not mean that historical backup packages on that provider are automatically deleted. Remote Backup Set deletion is a separate operation performed from Backup History when you explicitly choose to remove recorded verified off-site copies.

Destination deletion also does not erase historical export records merely to make the list look clean. QCBM preserves those references where needed for operational evidence.

Check the Default After Lifecycle Changes

If you disable or remove the current default destination, review which remaining destination QCBM treats as default. Test the intended replacement and perform one controlled Export to Default before relying on Profile auto-export.

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.