Every host says they backup daily. The question that actually matters is whether anyone on your team has restored from one lately, and whether that restore worked on the first try.
We have walked into migrations where the client assumed backups were fine because the control panel showed green checkmarks. Then someone deleted the wrong folder, or ransomware hit, or a plugin update turned the database into soup. That is when you find out if "daily backups" meant tested recovery or just a zip file sitting on the same disk.
What a real backup plan includes
A backup you can trust has a few boring parts that are easy to skip when you are busy:
- Files and database, separately. WordPress without the database is a pile of PHP. A database dump without uploads is a site full of broken images.
- Off-server copies. If backup and production live on the same machine, a disk failure or compromise takes both.
- Retention that matches your risk. One nightly snapshot is not enough if you only notice corruption a week later.
- A documented restore path. Who does it, how long it takes, and what gets rolled back (email, DNS, app state).
- Periodic test restores. Not "we should test someday." Actually spin up a copy and verify login, checkout, or whatever keeps the business running.
Managed hosting should include most of this by default. Unmanaged means you own every line of that list.
Where backups usually fail in practice
These are the patterns we see when someone calls in a panic:
- Backups ran, but nothing critical was in scope. Custom upload paths, cron output, or a second database never made it into the job.
- Restore was never practiced. The first real restore happens under pressure at 11 p.m.
- Incremental chains broke silently. A full backup aged out and dailies stopped chaining correctly months ago.
- Ransomware or bad actor had time to encrypt backups too. Same credentials, same network, no immutable copy.
- Provider "backup" was really a snapshot you pay extra to access. Read the fine print on retention and restore fees.
None of this is exotic. It is what happens when backups are treated as a checkbox instead of a recovery plan.
Questions to ask your host (or your own team)
- Where do backups live geographically? (Canadian clients often care about this for compliance and peace of mind.)
- How far back can we restore, and at what granularity?
- When did you last complete a successful test restore for a site like ours?
- What is the expected recovery time for files only vs full database rollback?
- Are backups encrypted at rest and in transit?
- If we get hacked Tuesday afternoon, can we roll back to Monday night without rebuilding from scratch?
If the answers are hand-wavy, tighten the plan before you need it.
What we do on managed Swift Host environments
Our default posture is daily backups with off-server retention, monitoring on backup job success, and restore runbooks documented per environment. When something goes wrong, we are not inventing the process during the incident. We pull the right snapshot, validate, and cut over with you on the line.
That is the difference between "we have backups" and "we can get you back online." For WordPress shops, WooCommerce stores, and custom apps, the second sentence is the one that saves the quarter.
DIY backup hygiene if you are still on shared hosting
Not ready to move yet? At minimum:
- Export the database on a schedule you actually run (plugin cron is fine if you verify the files land somewhere else).
- Sync uploads to external storage, not just a folder on the same account.
- Store credentials for restore separately from the server.
- Once a quarter, restore to a staging URL and click through the site like a user would.
It is tedious. It is also cheaper than explaining to customers why orders from last week vanished.
Bottom line
Backups are not insurance paperwork. They are a rehearsal for a bad day. If nobody has restored lately, you do not have backups. You have hope.
Want us to review what your current host is actually keeping? Talk with Swift Host. We will tell you what looks solid and what is a gap, even if you are not moving today.
