Update of SQLBackupAndFTP integration with Google Drive

What will change?

Currently, SQLBackupAndFTP has access to all files and folders on Google Drive. Soon, SQLBackupAndFTP will request access only to the files and folders on Google Drive created by SQLBackupAndFTP.

What needs to be done?

Upgrade to version 12.7.22 and reconnect to Google Drive

The list of Google Drive connections that need to be reconnected will be displayed in SQLBackupAndFTP in the “Select backups in selected destinations” section. Integrations that have not been reconnected will stop working after April 14, 2024. To reconnect do the following:

  1. Run SQLBackupAndFTP 
  2. Make sure to use SQLBackupAndFTP version 12.7.22. If you have an active Full-Service subscription, navigate to “Help” > “Check for updates.” If your subscription has expired, you can always renew it by clicking the “Renew subscription” link in the “Actions” column on the “My Account” page.
  3. Click the destination in the list
  4. In the opened dialog click the Change link

  5. Go through the authorization process for the SQLBackupAndFTP application
  6. Click the Save & Close button


In most cases, reconnecting is sufficient. SQLBackupAndFTP will still be able to correctly delete previously created backups and restore from these backups. This is possible since SQLBackupAndFTP works with backup files using the internal identifier of Google Drive. 

But there are a few exceptions:

  1. SQLBackupAndFTP will lose access to backups created by SQLBackupAndFTP versions older than 12.7.22 if they are stored in Google Drive folders that haven’t been created by SQLBackupAndFTP.
  2. SQLBackupAndFTP will lose the ability to work with a user’s folder if the folder path is specified as a URL. In this case, replacing the URL with a relative path to the folder is sufficient.
  3. Additionally, SQLBackupAndFTP will completely lose the ability to work with folders and files shared with you by other users (shared folders).

Potential anomalies

If a folder (or folder hierarchy) specified in the Google Drive destination settings was not created by the SQLBackupAndFTP application, then after reconnecting to Google Drive, a folder with the same name may appear. Newly created backups will be stored in this folder. Note that this is not an error, but rather a feature of Google Drive.

If this confuses you, navigate to the Google Drive destination settings within the backup job settings and specify a new, non-existent folder (path). It will be created automatically on your Google Drive.

Leave a Reply

Your email address will not be published. Required fields are marked *