SQL Backup Master Help

Online Documentation

Google Drive SQL database backup destination

SQL Backup Master supports the use of Google Drive for database backup purposes.

To use Google Drive as a backup destination, you must have an account. If you don't already have a Google Drive account, you can visit https://www.google.com/drive/ to create one.

To create a Google Drive backup destination within SQL Backup Master, click the Add toolbar button in the Destinations section of the Database Backup Editor window. When prompted to choose a destination, select Google Drive and click the Select button.

Authorization

SQL Backup Master must be authorized to connect with your Google Drive. Doing so allows SQL Backup Master to upload database backup files to Google Drive on your behalf.

Click the Authorize Now button to proceed. Your default web browser will be launched and directed to a Google sign-in page where you can either allow or deny cooperation between SQL Backup Master and your Google Drive account. Sign in and click Allow if you wish to continue with authorization.

Once access is granted, authorization completes automatically – simply close the browser page and return to SQL Backup Master, which will then show the name of the associated Google Drive account.

Note: SQL Backup Master requests Google's limited drive.file access scope. This means it can only see and manage the folders and files it creates itself – it cannot access your other Google Drive content or files shared with you.

Congratulations, SQL Backup Master can now back up your SQL Server databases to your Google Drive.

Optional Settings

The following optional settings are also available:

  • Remote dir - By default, SQL Backup Master will upload database backup files into the root of your Google Drive. Here, you can specify a directory name (e.g. "SQL Backups" or something similar) to use instead. If the directory doesn't already exist, it will be created. You can also specify multiple sub-directories by separating them with a forward slash (e.g. "Apps/SQL Backups").
  • Emergency destination - When this option is enabled, the associated backup destination will be used only if all other backup destinations fail.
  • Enabled backup types - Controls which backup types (Full, Differential, Transaction Log) are sent to this destination. At least one type must remain enabled.

Cleanup

Each time SQL Backup Master successfully uploads a database backup to a destination, it executes a clean-up procedure.

This allows you to automatically remove database backup files that are older than a specified number of days and/or hours.

Important: Cleanup operations for a given destination will only affect the database backup files associated with that destination.