Cloud Sync

Sync backups to the cloud for true 3-2-1 data protection

Local backups protect against accidental deletes and bad edits, but not against drive failure or theft. Syncing backups to the cloud completes the 3-2-1 rule. Ginkgo supports BYOS (Bring Your Own Storage) — use cloud drives or NAS you already own, with no capacity limits and no extra fees.

Supported Storage Backends

Covers major cloud providers and NAS. All backends support encrypted transfer and encrypted storage.

Type	Protocol	Compatible With
`S3`	AWS SDK v2	Amazon S3, MinIO, Cloudflare R2, Wasabi, Alibaba OSS, Backblaze B2
`WebDAV`	HTTP	Synology, QNAP, Feichu Cloud, Nextcloud, ownCloud, any WebDAV server
`SFTP`	SSH + SFTP	Any SSH server with SFTP support
`OneDrive`	Microsoft Graph	Microsoft personal and business accounts
`Dropbox`	Dropbox API	Dropbox
`Google Drive`	Google Drive API	Google Drive
`peer://`	Mesh Backup (P2P)	Other devices running Ginkgo Backup, no central server needed. See the Mesh Backup docs.

Add a Cloud Backend

On the Cloud Storage page, add a backend and click "Test Connection" to verify it works before saving.

S3 Configuration Fields

字段	必填	说明
`endpoint`	Required	S3 endpoint URL
`bucket`	Required	Bucket name
`region`	Required	Region
`access_key_id`	Required	Access key
`secret_access_key`	Required	Secret key
`prefix`	Optional	Path prefix within the bucket

WebDAV Configuration Fields

字段	必填	说明
`url`	Required	WebDAV server URL
`username`	Required	Username
`password`	Required	Password

SFTP Configuration Fields

字段	必填	说明
`host`	Required	SSH server address
`port`	Optional	SSH port (default 22)
`username`	Required	SSH username
`password`	One of two	SSH password
`private_key`	One of two	SSH private key (PEM format)

OneDrive / Dropbox / Google Drive

These cloud drives use the OAuth2 authorization flow:

When creating a backend of these types, the API returns an authorization URL

Open the URL in a browser, sign in and authorize

Paste the callback URL back into Ginkgo

Tokens auto-refresh and persist — no re-auth needed

💡 Google Drive uses the full drive scope (not drive.file) so it can list existing folders and avoid duplicate creation.

Create a Sync Job

After adding a cloud backend, create a sync job to copy local backups to the cloud:

Sync is asynchronous — after a backup completes, blobs upload in the background. Failed syncs are retried automatically by the Patrol service.

Use 3-2-1 to Protect Your Data

Ginkgo natively supports "one source, multiple storage targets." Configure a local repo + cloud repo for the same source, and each backup writes to both — making 3-2-1 effortless.

Security Notes

Cloud credentials are encrypted with the repository key and stored in the local database
If repository encryption is enabled, blobs are encrypted before upload
OAuth2 tokens auto-refresh and persist
All cloud backends use TLS for encrypted transfer