Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Backups

VPS snapshot limitations: what snapshots protect and what they do not

Published August 2026 · 2 min read · Updated 2026-09-05

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.

Next step

Understand crash consistency, storage coupling, retention and application state before treating a VPS snapshot as a complete backup or recovery plan.

Plan independent backup storage

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Linux file permissions: ownership, modes, groups and ACLs explained

Understand Unix ownership and rwx modes, then use groups and ACLs where needed so services can access files without opening them to every user.

Read the guide

Moving a DreamHost VPS to Canadian hosting

Inventory the server, copy it safely, test it, and cut DNS over with a rollback plan.

Read the guide

More vps & linux guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move