VPS Snaps

Backing up to Google Drive

Keep backups in a folder of your own Google Drive, connected by signing in with Google.

3 min readStorage

Google Drive works as a storage destination for every kind of backup: SSH servers, the agent, WordPress sites, Railway and Render databases, Kubernetes and DNS zones. Backups go to a folder in your own Drive; nothing is kept by VPS Snaps.

Step 1 — Sign in with Google

In Storage → Add destination, choose Google Drive, name the destination and the folder to make in your Drive, and select Sign in with Google. Leave Google Drive ticked on Google's consent screen.

VPS Snaps asks only for the files it creates (drive.file). It cannot see or change anything else in your Drive.

Step 2 — Choose it on a backup job

Pick the destination on any backup job. Each job gets its own folder inside the one you named. Your servers upload straight to your Drive through a link that can write that one file; restores download straight from it with a token that lasts under an hour.

What to know about Drive

Backups count against your Google account's storage (15 GB free). Google limits uploads to 750 GB a day per account. Retention deletes old backups permanently rather than to the bin, so the space comes back. Agents need version 1.2.7 or newer, and WordPress restores need the plugin's version 1.0.0 or newer.

If Google stops accepting the sign-in

Revoking access, changing some account settings, or an app still in Google's testing phase can end the sign-in. The destination then says so under Storage, with Sign in with Google again. Sign in with the same Google account: only it can see the backups already stored.

Still stuck?

Open the failed run under Backup History and copy the error text out of the log — pasting that into your first message is usually the difference between one reply and four.