Backups
VPS snapshot limitations: what snapshots protect and what they do not
A VPS snapshot captures storage state at a point in time, often on the same provider platform. It can be excellent for a short rollback before a risky change, but its convenience does not make it a complete independent backup strategy.
Understand what the snapshot actually captures
Provider snapshots may capture one disk or VM state, but attached volumes, external databases, object storage, DNS, secrets, and SaaS dependencies can remain outside it. Read the product semantics and verify exactly which disks and dependencies the snapshot includes.
Crash-consistent storage is not always application-consistent for a busy database.
Account for shared failure domains
If production and snapshots depend on the same account, provider, control plane, or storage system, one credential compromise or provider incident may affect both. Independent backup storage reduces that shared risk.
Keep backup credentials separate enough that a compromised VPS cannot automatically erase every copy.
Use snapshots for the rollback window they fit
Before package upgrades or configuration changes, a snapshot can shorten recovery when reverting the whole machine is acceptable. Document what data might be lost if production continues writing after the snapshot.
Do not roll back an active transactional system without considering newer database or user writes.
Pair snapshots with data-aware backups
Maintain database dumps, file backups, configuration exports, or other application-consistent copies according to recovery objectives, then test them independently.
- Read snapshot scope.
- Identify shared provider/account risk.
- Use snapshots for short rollback.
- Keep independent application-aware backups.