Connect Google Drive to QC Backup Manager

QCBM connects to Google Drive through your own Google OAuth application. You provide the OAuth Client ID and Client Secret, register the exact Authorized redirect URI shown by QCBM, authorize the Google account, and then test the destination before using it for backup exports.

Google Drive export requires Pro, Max, or All Access. PHP cURL and OpenSSL must be available on the Joomla server.

Create the Google OAuth Application

In the Google Cloud project you intend to use for QCBM, configure an OAuth client for the site and enable the Google Drive API. QCBM requests narrowly scoped access for files it creates plus the account email used to identify the connected account.

Keep the OAuth client secret private. It is a credential, not a value to publish in documentation, notes, or screenshots.

Copy QCBM's Exact Redirect URI

  1. Open Settings > Export Destinations in QCBM.
  2. Add a destination and choose Google Drive.
  3. QCBM displays a read-only Authorized redirect URI.
  4. Copy that URI exactly into the Google OAuth client configuration.

Google compares redirect URIs exactly. A different scheme, hostname, path, port, or trailing character can cause OAuth authorization to fail.

Save the Google Drive Destination

  1. Enter a clear destination name.
  2. Enter the Google OAuth Client ID.
  3. Enter the Google OAuth Client Secret.
  4. Choose the Google Drive folder name. The default is QC Backup Manager.
  5. Enable the destination if it should be available after authorization.
  6. Optionally mark it as the default export destination.
  7. Save the destination.

QCBM encrypts saved OAuth secrets and tokens before storing them. Saving the application settings does not by itself authorize the Google account.

Connect the Google Account

Reopen the saved destination and choose Connect Google Drive. Complete Google's consent flow using the account that should own or access the QCBM backup folder.

After authorization returns to Joomla, the destination should show a connected state. Use Reconnect after changing OAuth application credentials or provider permissions. Use Disconnect when QCBM should no longer retain the Google authorization.

Test the Destination

Click Test. QCBM obtains a valid access token, ensures the configured root folder exists, uploads a temporary test file, verifies the returned Google Drive object, deletes it, and records the result under Last Test.

A successful message states that the connection, folder access, test upload, verification, and cleanup passed.

Verify with a Recovery Package

After the provider test passes, manually export one completed QCBM Backup Set to Google Drive. Confirm the export succeeds and that the remote account/folder is the one you intended to use.

Automatic Profile export uses the current default destination. Do not enable automation until the OAuth connection, Test, and a real manual export have all behaved as expected.

Common Google Drive Connection Problems

  • Redirect URI in Google does not exactly match QCBM.
  • Google Drive API is not enabled for the project.
  • The OAuth client ID or secret was changed or revoked.
  • The connected Google account no longer has expected access.
  • PHP cURL or OpenSSL is unavailable on the Joomla server.

Correct the specific problem, reconnect when authorization changed, then run Test again.

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.