Off-site, versioned backups of files, databases and mail, with retention that fits your business and a restore drill so you know it works before you need it. Set-up from €290.
Restore the daily backup from 1 day ago. Work done in the 1 day before the problem started has to be redone, plus anything since.
Set up this rule on my serverThe tool runs in your browser and checks nothing on any server. Pikselipolku is an independent studio and is not affiliated with cPanel, LiteSpeed or any other product named here.
Usually two to four working days from access to the first timed restore. The date is in the written quote.
Sites, databases, mailboxes, server configuration and what already backs up, if anything.
Schedule and retention agreed in writing, from your answers to the two questions above.
Encrypted, versioned copies to storage in your name, with a different provider from the server.
A full restore to a separate test server, timed and written up before the job is called done.
A failed or missing backup sends an email the same day, to you and to me.
Three quarterly drills on one sample store. The second one failed, which is exactly why drills exist.
Each drill restores a real backup to a separate test server, never over the live site, and the clock runs from "fetch the backup" to "the shop takes a test order".
The record goes into your monthly report, so you can see restores working instead of trusting that they would.
| Step | Detail | Time | Result |
|---|---|---|---|
| Fetch | Download from off-site storage, 4.6 GB | 19 min | pass |
| Files | Unpack site files and uploads | 10 min | pass |
| Database | Import 1.2 GB dump | 7 min | pass |
| Point | Hosts-file entry to the test server | 2 min | pass |
| Smoke test | Product images from 2026 missing | 14 min | fail |
| Fix and re-run | Exclude rule too wide; fixed, re-backed up, restored | 48 min | pass |
$ ls wp-content/uploads/
2023 2024 2025
Fixed prices in euros, excluding VAT 25.5%. The storage account is in your name, so the backups stay yours whoever runs the server.
If the first restore drill does not work, I fix the set-up and run the drill again at no extra cost. owner to confirm
When did you last restore one of your backups?
Plan my backupsGood backups are boring. If yours already are, keep them that way.
A backup on the same server as the site is a convenience, not a backup. The copy that matters lives somewhere else. If the site was hacked, read hardening and malware cleanup before you restore.
Site files, uploads and media, with cache folders excluded so backups stay small and fast.
Consistent dumps taken with --single-transaction, so a busy store backs up without locking checkout.
Mailboxes and forwarders, so a lost server does not mean lost inboxes.
Web server, PHP, cron and panel settings, so a rebuild takes hours, not days of guessing.
A second provider or data centre, in storage you own; deleted or encrypted files cannot overwrite older versions.
Encrypted on the server before upload, with the key stored in your password manager as well as mine.
As often as the data you can afford to lose. For a brochure site that changes monthly, nightly is plenty. For a store taking orders all day, back up the database every hour or more often, and files nightly. The tool above turns your answer into a schedule and retention you can check.
Off the server, with a different provider or data centre, in storage you own and can log in to. Copies are encrypted before they leave the server and versioned, so a deleted or encrypted file cannot overwrite older restore points. A local copy can stay on the server too, for fast restores.
Yes, that is the point. Every set-up ends with a full restore to a separate test server, timed and written down. After that, drills run quarterly or monthly depending on how long you can be down, and each one produces a short record like the sample above.
Tell me what runs on the server and your answers to the two questions in the tool. You get a written rule and a fixed price within one working day.
Prefer email? Write to [email protected]
Pikselipolku is an independent studio and is not affiliated with cPanel, LiteSpeed or any other product named here.