Snapshots versus backups

A VPS snapshot is a point-in-time disk image kept on the same storage as your server. A backup is a separate copy you can restore after the node itself is gone. Snapshots are useful for quick rollback; backups are what protect you when hardware or a whole site fails.

The panel button is easy, so many people treat a snapshot as the whole plan. That works until a node dies or a project is removed and the only copy lived next to the original. If the array fails, the guest and the snapshot can disappear together. That is one copy on one medium in one building, not a 3-2-1 strategy.

What a VPS snapshot is good for

Use a snapshot before a panel upgrade, a major package change, or a short experiment you might undo in minutes. Rollback is fast because the data never left the hypervisor storage. Keep one around a risky change, then delete it once the change is stable so the array is not full of old images. A snapshot is a convenience tool, not an offsite archive.

Dump MySQL to a file you can move elsewhere. Copy public_html when the site files are the product. Mail in Maildir is a third set of data worth protecting on its own. A disk snapshot might include all three if the guest is quiet, but it still has not left the building.

Crash-consistent versus actually restorable

A crash-consistent snapshot often boots, and InnoDB often recovers on its own. “Often” is not enough when the shop depends on clean orders and options. If the snapshot is your only database copy, dump first or quiet the guest before you capture. A snapshot taken mid-checkout can return with a missing order or a half-written row, and then you spend a day fixing tables by hand.

Test a restore once onto another VPS or a local VM until you have seen the site answer. The first restore during a real outage should not be a rehearsal with customers waiting.

Build a plan that does not depend on memory

Keep offsite backups on a schedule that runs without you remembering to click. Same-array snapshots stay useful for short undo windows; they do not replace copies you can pull after the node is gone. Offsite backups for a VPS covers the rest of that setup in plain steps.