Ask any business owner if their website is backed up and you'll hear "yes" almost every time. Ask when they last restored one and the room goes quiet.
That gap is where businesses lose weeks of work. A backup you've never restored isn't a backup, it's a hope. Here's how to close the gap in an afternoon.
Why Most Backup Setups Fail
They live on the same server. If a drive dies, ransomware runs, or the account gets suspended, the backup dies with the site. Same box, same fate.
They're incomplete. A files-only backup with no database restores a WordPress site with no posts, no orders, no users. A database-only backup restores content with no images. You need both, from the same moment in time.
They're too old. Weekly backups mean you can lose six days of orders. Match your backup frequency to how much data you're willing to re-enter by hand.
They've never been tested. Corrupted archives, partial dumps, and missing table prefixes are all invisible until the day you need them.
The 3-2-1 Rule
The standard that's survived every technology shift:
- 3 copies of your data
- on 2 different types of storage
- with 1 copy off-site
For a typical business site: the live server, an automated nightly backup on the host, and a copy pushed to off-site object storage. Three copies, two locations, one of them completely independent of your hosting account.
What to Actually Back Up
- Files: uploads, themes, plugins, custom code
- Database: content, users, orders, settings
- Configuration: web server config, PHP settings, cron jobs, TLS setup
- DNS records: export the zone; rebuilding it from memory during an outage is misery
- Credentials: where the domain is registered, who the DNS provider is, where mail is hosted. Store it in a password manager, not in someone's head.
That last two are the ones everybody forgets, and they're the ones that turn a two-hour recovery into a two-day one.
Retention: How Far Back Should You Go?
A practical schedule for most small businesses:
| Backup | Keep for |
|---|---|
| Nightly | 14 days |
| Weekly | 8 weeks |
| Monthly | 12 months |
Why so long? Because not every disaster is loud. Malware or a bad plugin update can sit quietly for weeks. If your only backups are seven days old, you restore the problem right along with the site.
Test the Restore Today
This is the step that separates real backups from theater. Once a quarter:
- Spin up a scratch server or a staging site.
- Restore your most recent full backup to it.
- Log in. Click through. Check images, check the database, check a recent order.
- Time it. How long did it take? That number is your actual recovery time, the one to quote when someone asks "how fast can we be back?"
If the restore fails, you just found out on a Tuesday afternoon instead of during an outage. That's a win.
Where Managed Hosting Fits
This is exactly the kind of work that quietly doesn't happen when everyone is busy. Managed hosting with Node Dog Cloud includes automated nightly backups, off-site retention, and monitoring that catches problems before they become restores, plus someone to run the restore for you if it ever comes to that.
The Bottom Line
Backups are cheap. Downtime and lost data are not. Take twenty minutes this week to answer three questions: Where are my backups? How old are they? When did I last restore one?
If any answer is "I'm not sure," we should talk.
Want Backups You Can Actually Restore?
Every Node Dog Cloud plan includes automated nightly backups, off-site retention, and tested restores, so you never have to find out the hard way. Ask us for a free backup and restore audit of your current setup.