Recovery runbook · Beginner · 30 minutes of setup
How to back up WordPress — Time the Restore, Not the Backup Schedule
You have a backup schedule running and no idea how many minutes a restore would actually take — this page fixes the second half.
The short answer
Back up the two artefacts separately, then measure the restore: a WordPress site is a file tree plus a MySQL database, and the only figure that matters on the bad day is how many minutes it takes to bring both back. Our hosting already takes a daily backup you can restore from the panel, which sets your baseline — everything you add on top exists either to shorten that number or to survive the platform itself being unavailable.
What follows is how to size both artefacts, how to time a restore on a staging clone with WP-CLI, where the second copy has to live before it counts as a second copy, and why the cadence question is really a question about how much work you are willing to redo.
By the HostingFast team · Reviewed 24 August 2026
Beginner
Assumed skill
Quick
Time at the keyboard
5
Stages in the runbook
24/7
Engineers on shift
This runbook assumes you can open a terminal but never requires it — every step has a panel equivalent. What it will not do is treat 'backups are enabled' as the finish line, because that sentence contains no measurement.
Two numbers run through the whole guide: your recovery point, meaning how much work you lose, and your recovery time, meaning how long the site is down while you get it back. Write both down before you choose any tool.
Two artefacts, and only one of them grows quietly
wp-content is the file half: themes, plugins, uploads. The database is the other half, holding your content, the options table and every setting a plugin has ever written. Restore one without the other and you get a site that boots and shows nothing anybody recognises.
Check both sizes before planning anything. `du -sh wp-content` for the files and the database size from phpMyAdmin tell you whether you are moving 200 MB or 20 GB, and that single figure decides whether a nightly full copy is sensible or whether uploads want handling separately from the database.
Time a restore and you have a backup
Restore into a staging clone with a stopwatch running. `wp db import backup.sql`, then a click through the homepage, one deep page and wp-admin, is a fifteen-minute drill — and it converts 'we have backups' into a number you can quote, which is the recovery time you are implicitly promising everyone.
Do it quarterly. The failures that bite are never the missing file: they are the dump truncated part-way, the plugin that stored absolute paths in serialised options, and the mailbox nobody remembered sat outside the archive entirely.
A copy on the same disk is not a copy
An archive stored inside the account it protects shares a failure domain with the thing it insures. The panel backup already lives apart from your files, which covers most scenarios; a plugin shipping a weekly archive to Drive, Dropbox or S3 covers the one it cannot — the account itself being gone.
Two locations, two schedules, two retention windows. A month of dailies plus a handful of monthlies handles slow-burning problems: a compromise you notice in week three needs a copy from week two, and a seven-day window will not have one.
What runs unattended on this platform
Daily backups fire on every plan and restore from your panel — files, databases or both — with no ticket in the way. Free SSL issues and renews itself, and the one-click installer covers WordPress and 400+ other applications, so none of that belongs in your own backup plan.
What is left is genuinely yours: the off-platform copy, the retention policy, and the drill. If a restore misbehaves, support answers at any hour of any day and will run it through with you rather than posting a link.
The stack these steps were measured on
Every runbook here was exercised on the platform we actually operate — cPanel, LiteSpeed, NVMe storage, one-click installs — so the commands and the panel screens match what is in front of you rather than a generic host.
Order an annual plan and the first year of your domain registration costs you nothing.
- Restores you run yourself, straight from the panel
- Daily backups on every tier, not only the top one
- Staging clones to rehearse the restore on first
- Engineers on shift whatever hour it goes wrong
Why HostingFast
Standard on every plan
A number, not a reassurance
You finish this page able to state your restore time in minutes, because you will have held a stopwatch on one.
Both halves accounted for
Files and database are treated as separate artefacts with separate sizes, because that is precisely how restores fail.
Commands and click-paths together
Every step gives the WP-CLI or shell version alongside the panel route, so it works over SSH or in File Manager.
Failure domains named
Where a copy lives matters more than how often it is taken, and each step says which location survives what.
Scoped honestly
Timing a restore and adding an off-platform copy is a beginner-level job — about 30 minutes of setup, plus a fifteen-minute drill each quarter.
No cargo cult
Nothing here recommends a plugin for work the platform already does daily, and better, without you watching.
Quick Start
From order to online
- 1
Size both artefacts first
`du -sh wp-content` for the files, and the database size from phpMyAdmin for the rest. A 400 MB site and a 40 GB site need different plans, and the dashboard will never tell you which one you are running.
- 2
Read the baseline you already have
Our hosting takes an automatic daily backup, restorable straight from the panel. Confirm the schedule and retention on your plan first — that is your floor, and half the plugins people install merely duplicate it.
- 3
Write down a recovery target
Decide how much work you can stand to lose and how long the site may be down. Those two numbers choose your cadence and your tooling; without them every backup plugin looks equally good.
- 4
Put one copy off the platform
A backup plugin shipping a weekly archive to Drive, Dropbox or S3 covers the failure the panel copy cannot: the account itself being unreachable. Separate failure domains are the entire point of copy number two.
- 5
Drill the restore quarterly
Clone to staging, `wp db import` the dump, click the homepage, a deep page and wp-admin. Twenty minutes, four times a year, and that drill is what turns an archive into a backup.
Built In
Loaded onto every plan
- Daily backups on every plan, with restores you run yourself from the panel
- Staging environments for rehearsing a restore before you ever need one
- NVMe SSD storage on every tier, not just the expensive ones
- LiteSpeed caching compiled into the server rather than bolted on by plugin
- SSH, Git and Composer on the developer-focused plans
- Per-site PHP version switching from the control panel
- cPanel — the control panel most of the industry already runs
- In-place account upgrades, with no migration when you change plan
- Money-back cover: 30 days on hosting plans, 7 on reseller
- 99.9% uptime as the target, monitored around the clock
Frequently Asked
What people ask us most often
How long should a restore take, and how do I find out?
Time one. Clone to staging, import the dump, click through the site: that wall-clock figure is your recovery time, and it is the only honest answer available. A small site comes back from the panel in minutes; a 20 GB uploads directory does not, which is exactly the sort of thing worth discovering on a quiet Tuesday rather than mid-incident.
Which half causes more restore trouble, the files or the database?
The database, almost every time. Files are inert. The database carries absolute URLs, serialised options and an autoload table that a careless search-and-replace will corrupt silently. Restore the database first, check the siteurl and home values, then lay the files back over the top.
How is billing handled, and does the price move at renewal?
Card payment through a secure checkout, and renewals bill at the rate you originally ordered at — there is no introductory price waiting to expire. Invoices sit in your client area and auto-renewal is a toggle in your account, so stopping it never involves a phone call.
How many sites can share a single account?
From the Turbo tier upwards, several — each with its own domain, mailboxes and certificate inside one account. They do share that account's PHP workers and disk I/O, so if the extra sites belong to clients rather than you, reseller hosting keeps them properly isolated instead.
Keep reading
How to Understand Website Firewalls
What a web application firewall actually inspects, where it sits in the request path, and the rules worth touching — intermediate, roughly 20 minutes of reading.
How to Take Payments Online
Take card payments without card data ever reaching your server, and without the checkout adding a second to the page — beginner, roughly an hour.
Best Hosting With WordPress Toolkit
The same decision as a buying guide: which specifications move the numbers, which are marketing, and the plan we would sign.
Domain Names
Search, register and transfer names — year one free when you order annual hosting.
WordPress Hosting
WordPress on LiteSpeed and NVMe, with staging clones and daily backups included.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Host it where the restore is one click.
Daily backups, free SSL and free migration on NVMe behind LiteSpeed, with engineers on shift at any hour — at a rate that does not move at renewal.
View WordPress Hosting plans