This page contains affiliate links. If you make a purchase through one, we may earn a commission at no extra cost to you.
Unlike shared hosting, where backups are often handled entirely by the host, a VPS generally puts backup responsibility on you — which means it’s genuinely easy to skip until the day you actually need one. Here’s what’s actually available and how to set it up so it runs without you thinking about it.
Snapshots vs. Automated Backups: Not the Same Thing
These two terms get used loosely, but they solve different problems. A snapshot is a manual, on-demand save of your server’s exact current state — useful right before you install new software or make a risky change, so you can roll back instantly if something breaks. It’s not a substitute for ongoing protection, since it only captures a single moment you chose, not an evolving history. An automated backup runs on a schedule in the background, capturing your server’s state regularly (often daily) without you having to remember to trigger it, and is what actually protects you against slower-building problems like a corrupted database you don’t notice for a few days.
What Contabo Actually Offers
Contabo provides both, and they’re worth understanding as separate tools rather than one feature. Free snapshots are available on every VPS at any time, stored for a limited window and meant for that “about to make a risky change” use case above. Auto Backup is a separate, optional add-on: daily incremental backups (capturing just what changed since the last one, not a full copy every time) with roughly a week and a half of rolling history, stored off-server so a problem with your VPS itself doesn’t also take out your backups. Restoring from either is handled through Contabo’s own control panel rather than a manual process.
Why Off-Server Storage Is the Part That Actually Matters
This is the detail that makes a backup strategy actually work: a backup stored on the same physical server it’s protecting doesn’t help if that server has a hardware failure, since the backup goes down with it. Auto Backup’s off-server storage specifically avoids that failure mode, which a snapshot taken and left on the same VPS does not fully protect against. If your site’s data is genuinely important, this off-server distinction is worth paying the small add-on cost for rather than relying on snapshots alone.
Set It Up Once, Then Forget About It
The actual failure mode most people run into isn’t a bad backup tool — it’s never turning one on in the first place. Enable an automated, scheduled backup during your initial VPS setup, alongside the SSH key setup and other basics covered in our first VPS setup guide, rather than treating it as a someday task. A backup you set up after already losing data once is a lesson learned the hard way; one set up during initial setup costs a few minutes and is never thought about again until the day it actually saves you.
Is a snapshot the same thing as a backup?
Not really — a snapshot is a manual, one-time save of your server’s current state, typically used right before a risky change. An automated backup runs on a schedule and provides ongoing rolling protection, which a single snapshot doesn’t.
Why does it matter if a backup is stored off-server?
A backup stored on the same physical server it’s protecting doesn’t help if that server has a hardware failure — the backup goes down with it. Off-server storage avoids that specific failure mode.
When should I set up automated backups on a new VPS?
During initial setup, alongside SSH key configuration and other basics — not after something has already gone wrong. It takes a few minutes upfront versus being a hard lesson learned after real data loss.