Backups run but we've never tested a restore.
A backup you've never restored is a hope. UpdraftPlus, BlogVault or your host's snapshot is fine, provided you actually rehearse the restore.
Try this first
- 1Set RPO and RTO. How much data can you lose (one hour, one day) and how fast do you need to be back (four hours, one day). That sets frequency and approach.
- 2Pick off-host storage: BlogVault, UpdraftPlus to S3 or Google Drive, or your host's native off-site option. Backups on the same server don't count.
- 3Run at least daily files plus DB. A busy webshop wants hourly or incremental, otherwise you lose orders.
- 4Run a restore test on staging at least quarterly. Document steps and time. A six-hour restore is a wake-up call.
- 5Keep at least 30 days of history. Hacks often surface after weeks and your latest backup is already infected.
- 6Write a runbook with steps, contacts and credentials. In a crash you won't remember where to start.
When to bring us in
If you handle customer data, payments or medical records, you need a verified backup strategy with a separate audit trail (and a DR plan). Bring in an experienced WP engineer.
See also
- WordPress, plugins and theme have gone 6+ months without updatesOut-of-date WP is the number-one entry for malware. Don't just hit 'update all', back up first.
- Theme update broke the layout or threw a fatal errorThemes overwrite custom CSS on update unless you use a child theme.
- WordPress shows a blank screen after a plugin install or updateWSOD (white screen of death) is usually one crashing plugin. You isolate it.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.