VPS Snapshots: When to Take One and How to Restore Fast
You're about to run a major kernel update, migrate PHP versions, or let a junior dev SSH in and try something quick. Ten minutes later the server won't boot, or worse, boots into a broken state that half-works. This is exactly the moment a snapshot would have saved you - if you'd taken one first.
Snapshots are one of the most underused safety nets on a VPS. Not because they're hard to use, but because people don't think about them until after something breaks. Here's what a snapshot actually does, when to take one, how to restore fast on Getwebup, and where snapshots stop being enough.
What a snapshot actually is
A snapshot is a point-in-time copy of your entire virtual disk - the OS, installed packages, config files, databases, everything - frozen exactly as it was the moment you took it. Restoring one doesn't merge changes or selectively undo things. It rolls the whole disk back to that exact state, as if the time between the snapshot and now never happened.
That's the key thing people get wrong. A snapshot isn't a diff or a changelog. It's a full-disk time machine with one stop: the moment you clicked the button.
When you should take one
Take a snapshot immediately before any change that could leave the server in a broken or half-finished state:
- Before OS or kernel upgrades -
apt dist-upgrade,dnf upgrade, or a full distro version bump (e.g. Ubuntu 22.04 to 24.04) - Before major software version changes - PHP 7.4 to 8.3, MySQL to MariaDB, Node LTS jumps
- Before installing a control panel - cPanel, Plesk, CyberPanel installers touch a lot of system files and are hard to cleanly undo
- Before firewall or SSH config changes - a bad UFW rule or a typo in
sshd_configcan lock you out entirely - Before letting someone else access the server - a contractor, a plugin installer script, anything you haven't personally reviewed
- Before a risky manual database operation - bulk
UPDATEorDELETEqueries without aWHEREclause you're 100% sure about
Rule of thumb: if you'd feel nervous explaining the change to your manager beforehand, take a snapshot first. It costs you 60 seconds. Skipping it can cost you a full day of restoring from an off-site backup, if you even have one.
How to take a snapshot on a Getwebup VPS
- Log in to your Getwebup client portal and open VPS / Cloud Servers
- Select the server you want to snapshot
- Go to the Snapshots tab
- Click Create Snapshot and give it a name you'll actually recognize later - not "snapshot1", but something like
pre-php83-upgrade-2026-07-13 - Wait for the status to show Completed before you start your risky change - a snapshot still in progress is not a snapshot you can restore
On most Getwebup VPS plans, snapshot creation takes anywhere from 30 seconds to a few minutes depending on disk size and how much data has changed since the last one. The server stays online during the snapshot - you don't need to schedule downtime for this part.
How to restore fast when something breaks
If the update goes sideways:
- Go back to VPS / Cloud Servers > Snapshots
- Find the snapshot you took before the change
- Click Restore and confirm - this will overwrite the current disk state entirely
- Reboot the server once the restore finishes
A restore typically takes a few minutes. Once it's done, the server is exactly as it was before you touched anything - which also means anything you legitimately changed after that snapshot (new files uploaded, new orders in a database, new emails) is gone too. That's the tradeoff, and it's the single most important thing to understand before you rely on snapshots.
Where snapshots stop being enough
Snapshots are for undoing a specific bad change quickly. They are not a substitute for a real backup strategy, for a few reasons:
| Snapshot | Backup |
|---|---|
| Lives on the same storage infrastructure as the VPS | Should live somewhere else entirely (off-server, ideally off-provider) |
| Usually kept short-term (hours to a few days) | Kept on a schedule - daily, weekly, with retention policies |
| Captures the whole disk, all-or-nothing | Can be partial - just the database, just public_html, etc. |
| Not consistent for databases mid-write unless you pause writes first | Proper backup tools flush and lock the database for a clean copy |
If your only copy of the site lives in snapshots, one storage-level incident on the host side takes both the live server and every snapshot with it. Keep scheduled off-server backups running regardless - snapshots are the fast local undo button, not the disaster recovery plan.
A note on database consistency
If your VPS runs MySQL or PostgreSQL under active write load, a snapshot taken mid-transaction can capture the database files in an inconsistent state. For anything beyond a quick rollback of your last change, it's worth running mysqldump or your database's native backup tool separately, rather than relying on the snapshot alone to restore a clean database.
Prevention: build snapshots into your habits
- Snapshot before any change you can't easily reverse manually
- Name snapshots with the date and what you were about to do - future you will not remember what "test1" means
- Delete old snapshots once you've confirmed the change is stable - they take up storage and old ones just add noise
- Never treat a snapshot as your only copy of anything - pair it with scheduled off-server backups
Snapshots won't stop you from making a bad change. What they do is turn a bad change from a multi-hour recovery project into a two-minute rollback. That's worth building into your workflow as a default habit, not a special occasion.
Frequently asked questions
How long does a VPS snapshot take to create?
On most Getwebup VPS plans it's 30 seconds to a few minutes, depending on disk size and how much data has changed since the last snapshot. The server stays online while it's taken.
Does restoring a snapshot cause downtime?
Yes, briefly. The server needs to reboot after the restore completes, so expect a few minutes of downtime during the restore and reboot.
Can I keep multiple snapshots at once?
Yes, though most plans have a storage allowance or limit on how many you can retain. Delete old ones once you've confirmed a change is stable to avoid running into that limit.
Is a snapshot the same as a backup?
No. A snapshot lives on the same infrastructure as your VPS and is meant for fast, short-term rollback. A backup should be stored separately and follow a retention schedule. Use both - they solve different problems.
Will a snapshot save data created after it was taken?
No. Restoring a snapshot rolls the entire disk back to the exact moment it was captured. Anything added or changed after that point - new files, new database rows - is lost on restore.