Test a QCBM Export Destination

The Test action checks whether a saved Export Destination can perform the provider-specific operations QCBM needs right now. It is an important pre-production check, but it is not the same as exporting a full Recovery Package and it does not permanently guarantee future credentials, quota, network access, or permissions.

Use the Test after creating a destination and again after changing credentials, OAuth authorization, remote folders, firewall rules, or storage-provider settings.

Where to Run the Test

Open Settings > Export Destinations. The list shows each destination's status and Last Test. The Test button is available when the destination is enabled, uses an active connector, and has the required configuration or cloud authorization.

Google Drive and OneDrive must be connected before QCBM can test them.

What QCBM Tests by Provider

  • Local / Server Path: prepares/validates the path, writes a small temporary text file, reads it, and removes it.
  • SFTP / SSH: verifies the saved SSH host-key fingerprint, authenticates, prepares the remote folder, uploads a temporary file, checks its remote size, and deletes it.
  • FTP / FTPS: connects/authenticates, applies passive mode when configured, prepares the folder, uploads a temporary file, checks its size, and deletes it.
  • Google Drive: verifies authorization/folder access, uploads a temporary file, verifies the returned object, and deletes it.
  • OneDrive: verifies authorization/folder access, performs a resumable test upload, verifies it, and deletes it.

Read the Exact Failure

QCBM stores the test result, message, and time on the destination. Use the message to narrow the problem instead of changing several settings at once.

  • Authentication errors point to credentials or OAuth authorization.
  • SFTP fingerprint errors require independent host-key verification.
  • Folder/path errors point to the configured location or permissions.
  • FTP/FTPS connection failures may involve passive mode, firewall ports, TLS support, or PHP FTP functions.
  • Cloud failures may involve the app registration, redirect URI, provider permissions, or revoked authorization.

A Passed Test Is Not a Permanent Gate

A passed Test records that the destination worked at that time. QCBM still validates the destination and backup package when a real export starts. Conversely, the export engine does not treat an old green Test result as proof that the provider is still healthy.

Credentials can expire, tokens can be revoked, quotas can fill, folders can be removed, and network rules can change after a successful test.

Follow the Test with a Real Manual Export

  1. Choose a completed Backup Set in Backups > Backup History.
  2. Export it to the tested destination.
  3. Confirm the export result is successful.
  4. Verify the destination/account/folder is the one you intended to use.
  5. Only then enable automatic Profile export if that is part of your backup policy.

This controlled export is a stronger production check because it moves QCBM's real Recovery Package rather than a tiny temporary object.

When to Re-Test

Re-test after changing a password, OAuth secret, provider authorization, host fingerprint, remote folder, account type, firewall configuration, mounted path, or destination status. Also re-test when a previously healthy export begins failing.

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.