Back Up SQL Server to Google Drive Automatically

SQL Server can only write backups to a disk path, a network share or (in newer versions) Azure or S3-compatible storage. It cannot write to Google Drive directly. So the job is two steps: back up to a local folder, then get that folder into Drive automatically. Here are three ways to do the second step, with the trade-offs of each.

Start with a reliable local backup

Every option below copies files that already exist. Set up a scheduled local backup first, following how to schedule SQL Server backups, and confirm new .bak files appear every day.

Option 1: Google Drive for desktop

Google's desktop app syncs a folder on your PC to Drive. Point your backups at a folder inside the synced area, or add your backup folder to sync.

Setup: install Drive for desktop, sign in, open its settings, and add D:\SQLBackups as a folder to back up to Google Drive.
Good for: a single PC or small office server with small databases.

Watch out for

It runs in a signed-in user session, not as a Windows service. If nobody is logged in to the server, nothing uploads.

Deletions sync too. If ransomware encrypts or deletes the local folder, the damage can reach the Drive copy. Deleted files do go to Drive's trash, which Google empties after 30 days.

Large uploads compete with daytime bandwidth, and there is no clear signal when an upload fails.

Option 2: rclone with Task Scheduler

rclone is a free command-line tool that uploads to Google Drive and many other services. It runs without a logged-in user, which suits servers.

Download rclone for Windows and extract it, for example to C:\Tools\rclone.
Run rclone config, create a new remote named gdrive of type drive, and complete the browser sign-in.
Test an upload by hand.

Command prompt

C:\Tools\rclone\rclone.exe copy "D:\SQLBackups" gdrive:SQLBackups ^
  --include "*.bak" --max-age 48h ^
  --log-file "D:\SQLBackups\logs\rclone.log" --log-level INFO

Add that line to the end of your backup batch file, after the success check, so uploads only happen when the backup worked.

Use copy, not sync

rclone sync makes Drive match the local folder, including deleting files from Drive when they disappear locally. rclone copy only adds files, so a local wipe does not remove your off-site copies. Clean up old Drive files separately, for example with rclone delete gdrive:SQLBackups --min-age 60d.

rclone stores its Drive token in rclone.conf in the user profile of the account that ran rclone config. Run the scheduled task as that same account, and protect that file: anyone with it can access the Drive.

Option 3: a backup tool with a native Drive destination

Backup software that treats Google Drive as a destination does the backup and the upload in one job, with one schedule, one log and one alert. That removes the most common failure of the script approach: the backup works, the upload quietly stops, and nobody notices for weeks.

Storage space

Free Google accounts include 15 GB shared across Gmail, Drive and Photos, so daily full backups fill it quickly. Estimate what your schedule needs with the backup storage calculator, and keep fewer copies in Drive than locally: for example 14 local days and 8 weekly copies in Drive.

Security checklist

Use a dedicated Google account for backups. Don't use a person's day-to-day account.
Turn on 2-step verification for that account.
Encrypt backups before upload if they contain personal or financial data, for example a password-protected 7-Zip archive, or rclone's crypt remote.
Test a restore from a file downloaded from Drive, not just from the local copy.

Google Drive backup with Velocity

Velocity supports Google Drive as a backup destination alongside a local folder and FTP/FTPS. Save the destination once, reuse it across jobs, and send each SQL Server or folder backup to local and Drive in the same scheduled job, with automatic retries if the upload fails.

Start free trial See destinations