Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.dbdock.xyz/llms.txt

Use this file to discover all available pages before exploring further.

DBdock supports four storage backends, all exposed through the same config shape and all swappable without re-configuring backups.

Local disk

Filesystem storage — fastest, no network, no cost.

AWS S3

Industry standard, mature ecosystem. Any S3-compatible service works.

Cloudflare R2

Zero egress fees — if you restore frequently, this is the cheapest cloud option.

Cloudinary

Generous free tier, fastest to get started, no AWS/Cloudflare account needed.

​
Picking a provider

You want…Use
Fastest possible backup/restoreLocal (if single server)
Standard cloud backup with wide tool supportS3
Cheap cloud storage with no egress feesR2
Free tier, no cloud accountCloudinary
Multi-region backup destinationS3 or R2 with cross-region replication
Compliance (HIPAA, SOC 2)S3 with KMS + bucket policies

​
How DBdock uses storage

Regardless of provider:
  1. Backup is streamed (never buffered to disk) to the provider
  2. Files live under a dbdock_backups/ prefix with standardized naming
  3. Metadata is stored alongside each backup for list and restore
  4. Deletion is always soft — you’ll confirm before anything is removed

​
File layout

<bucket-or-root>/
  dbdock_backups/
    backup-2026-04-16-08-00-00-abc123.sql
    backup-2026-04-16-08-00-00-abc123.meta.json
    backup-2026-04-15-08-00-00-def456.sql
    backup-2026-04-15-08-00-00-def456.meta.json
    ...
The metadata file tracks size, compression, encryption, duration, and origin.

​
Switching providers

You can switch anytime. Existing backups stay in the old provider; new backups go to the new one. To consolidate, manually move old files or do a dbdock list on each provider and track both.

​
See also

Configuration

How storage is configured.

Security

Storage security best practices.