The Dockstash alternative to Provider volume snapshots
Provider volume snapshots is a solid choice for what it does — whole-disk cloud snapshots. Where Dockstash differs is Docker-project awareness: it auto-detects your Compose stack, dumps each database the correct way from the running container, and drill-tests the restore. You need database-consistent, restorable, per-project backups that live off the production provider and are proven by a restore drill.
Provider volume snapshots — Whole-disk cloud snapshots. Cheap add-on billed per GB by your provider.
How Dockstash compares to Provider volume snapshots
| Capability | Dockstash | Provider volume snapshots |
|---|---|---|
| Database consistency | Consistent per-engine dumps (pg_dumpall, --single-transaction, --oplog) | Disk-level snapshot; can capture a torn DB mid-write |
| Granular restore | Restore a single project, volume, or database snapshot | Whole-disk only — all or nothing |
| Off-provider isolation | Stored on your separate storage VPS over SSH | Usually in the same provider account as the server |
| Restore verification | Automated restore-drill diff against source | None — you assume the snapshot boots |
| Setup effort | Install agent, auto-scan, confirm | One click in the provider console |
| Cost | Free self-host tier; you pay for your own storage | Cheap per-GB provider fee |
| Encryption / ownership | Restic-encrypted with your key on your storage | Managed by the provider |
Where Provider volume snapshots is strong
- One-click and fully managed by your cloud provider
- Fast whole-server rollback to a point in time
- No agent to install and almost no configuration
- Cheap per-GB pricing at most providers
Where Dockstash pulls ahead
- Not application- or database-consistent — a mid-write snapshot can be a torn, unrestorable DB
- All-or-nothing: you cannot restore a single project, volume, or table
- Lives in the same provider account as the server it protects (weaker isolation)
- No dump adapters, no restore-drill diff, no per-project reporting
Who should switch to Dockstash
You need database-consistent, restorable, per-project backups that live off the production provider and are proven by a restore drill.
Provider volume snapshots is the right choice when: Fast full-machine rollback and a coarse safety net — best used alongside real application backups, not instead of them.
Migrating from Provider volume snapshots
Snapshots and Dockstash are complementary rather than mutually exclusive. Keep provider snapshots for fast whole-machine rollback, and add Dockstash for consistent, granular, off-provider, verified application backups. Install the agent, auto-scan the Compose projects, point at a storage VPS in a different account or region, and rely on the restore drill for the recovery guarantee snapshots cannot give.
Last updated: July 2026
Frequently asked questions
Are provider snapshots a real backup?
They are a coarse safety net, not an application backup. A whole-disk snapshot taken while Postgres is writing can capture a torn page that will not restore. Use them for fast rollback, and use Dockstash for consistent, restorable data backups.
Can I restore just one database from a snapshot?
No. Volume snapshots are all-or-nothing at the disk level. Dockstash restores a single project, volume, or database dump so you are not forced into a full-server rollback.
Should I stop taking snapshots if I use Dockstash?
No need. They are cheap and good for fast machine-level rollback. Run both: snapshots for the whole box, Dockstash for consistent, off-provider, verified application data.
Why does off-provider storage matter?
Snapshots usually live in the same provider account as the server. If that account or region is compromised or lost, so are the snapshots. Dockstash stores to a separate storage VPS you control.