VPS or managed hosting: who takes care of what?
Compare maintenance, backups, recovery and total cost before choosing a VPS or a managed hosting service.
Check what a copy protects, how independent it is and whether you can actually restore the service.
THE USEFUL ANSWER
A snapshot can be part of a backup strategy, but its name does not guarantee an independent copy or successful recovery. Check what is copied, where it is stored and how you would restore it.
DigitalOcean describes snapshots as on-demand disk images and backups as an automatic mechanism for Droplets. These are definitions for its products, not definitions to assume across every provider. Read the documentation for the offer you are considering.
The practical question is what you will get after restoration: a disk, an entire machine, a consistent database or selected files. A reassuring backup dashboard cannot answer that question for you.
Use these scenarios as preparation, not as a complete security audit.
Keep a short record of scope, frequency, retention, access, location and the restoration procedure. Add the date of the latest exercise and what was actually recovered.
| Item | What to record |
|---|---|
| Scope | Files, databases, configuration and secrets required for recovery |
| Version | Available recovery point and retained history |
| Independence | Dependencies on the original account, machine or storage |
| Restoration | Steps, permissions, keys and functional checks |
Restore a copy to an isolated destination. Check the data, then open the application or essential files. Compare known items and document discrepancies. The objective is not a “restore completed” message; it is a usable service.
Do not automatically copy secrets or personal information into a less protected environment. Define access and clean up according to your policy afterwards. For a critical service, have the responsible person approve the exercise.
How much work could you afford to lose? How long could you be without the service? Who holds the necessary access? What happens if the same incident affects the primary system and its copy? Answer in ordinary language before browsing supplier options.
These answers set objectives, not achieved results. Having a copy does not prove your application will restart within the desired time. The exercise provides an observation, together with its conditions and limitations.
For a small website, list the essentials, copy locations, procedure and final checks. Do not put passwords or keys in a shared worksheet. Record how authorised people access the secrets manager instead.
Use our recovery worksheet to record the copy used and the observed result. A “success” entry needs evidence: files opened, expected recent data present, or the application accessible.
Did finding credentials take longer than restoration? Were files missing from the inventory? Did the application rely on a forgotten external service? Capture these discoveries while testing, then address a specific weakness and repeat the relevant check.
A snapshot is not useless because of its name, and a product called “backup” is not sufficient by definition. Judge the incidents covered and your demonstrated ability to recover. Our VPS and managed hosting comparison helps clarify who is responsible for each step.