Few feelings compare to opening your website and finding a blank screen, a 500 error, or worse, a page you don't recognize because someone changed it without permission. The first reaction is usually panic, and panic is a terrible advisor: it pushes you to poke at things randomly, reinstall plugins without a plan, or delete files you'll need later. The good news is that if your hosting takes daily backups, almost any disaster can be fixed in minutes. The key is knowing how to restore properly: what to recover, from which date, and in what order. In this guide we walk you through it step by step, without the drama and without unnecessary jargon.
The four scenarios that come up again and again
After years of managing our own sites and client sites, disasters almost always fall into four categories. The first is the update that broke everything: you updated WordPress, a theme, or a plugin, and suddenly the site throws a fatal error or looks visually destroyed. It's the most common case and, paradoxically, the easiest to solve, because you know exactly when the problem started.
The second is a hack or malware infection: strange redirects appear, ads you never placed show up, or Google flags your site as dangerous. Here, restoring is only part of the solution — if you don't close the door the attackers came through, they'll be back.
The third is accidental deletion: you removed a folder over FTP thinking it was a different one, emptied a database table with a badly written query, or deleted a page that had spent months climbing Google's rankings. It has happened to all of us at least once.
And the fourth, a classic if you work with clients: someone touched what they shouldn't have. The client logged into the dashboard, "improved" something, deactivated a security plugin, or edited the wrong file, and now the site is down. Nobody will admit anything, so the practical move is to restore and move on.
Not everything restores together: files, database, email, and DNS
Here comes the concept most people overlook, and the one that prevents the most trouble: a backup is not a single monolithic block. A good backup system lets you restore separately the site files (the WordPress core, your theme, plugins, uploaded images), the database (your content, pages, orders, users), the email accounts with their messages, and even the domain's DNS zones.
Why does this matter so much? Because restoring everything is not always the best move. Imagine your online store broke yesterday because of an update, but three new orders came in this morning. If you restore the full backup from two days ago, you get the site working again... and you lose those three orders, because they live in the database and you just overwrote it with an old version. In that case, the smart move is to restore only the files (where the broken plugin lives) and leave the database untouched. The reverse also happens: if someone deleted content but the files are fine, you restore only the database and you're done. Restoring surgically instead of restoring everything is the difference between recovering your site and creating a brand-new problem.
Before you touch anything: two steps that will save you
The natural impulse is to restore right now, but pause for ten minutes and do two things first. One: identify the cause, even roughly. What changed right before things broke? An update, a new plugin, a suspicious login? The answer tells you what to restore and from which date. If it was a hack, you also need to know how they got in, because restoring without changing passwords and patching the vulnerability is an open invitation for them to return tomorrow.
Two: take a backup of the current state, even though it's broken. It sounds contradictory, but it's pure gold. If the restore goes wrong, or if you later discover you needed a file or a piece of data from the "broken" state (an order, an email, evidence of the hack for analysis), you'll be glad you kept that snapshot. Generating a manual backup before restoring takes two minutes and gives you an extra safety net.
The step-by-step with JetBackup from cPanel
On hosts that use JetBackup — like BanaHosting, which includes it in every plan with automatic daily backups — the process is surprisingly simple. You log into cPanel, find the JetBackup section, and you'll see the available restore types: files, databases, email, cron jobs, and DNS zones, each one separate.
The flow is always the same: first, choose the date of the backup you want to use. This is where your earlier detective work pays off: if the site broke on Tuesday afternoon, restore from Tuesday morning's backup, not from last week's. Then choose what to restore: you can select your entire home directory, a specific folder (for example, just wp-content/plugins if a plugin was the culprit), or a specific database. Finally, one click on restore. The system queues the job, runs it in the background, and notifies you when it's done. For small sites it takes minutes; for large sites, a bit longer, but without you having to do anything else.
One detail that adds real peace of mind: in a well-designed backup architecture, copies are stored on separate hardware from the server where your site lives. If the problem is the server itself (a failing disk, for instance), your backups are safe somewhere else. It's a point worth verifying before signing up with any host.
How to verify the restore actually worked
Restoring doesn't end when the progress bar hits one hundred percent. Before declaring victory, check with intention:
- Homepage and key pages: home, contact, and your highest-traffic pages. Open them in an incognito window to bypass browser cache.
- The admin area: log into your WordPress dashboard and confirm you can sign in and that your critical plugins are active.
- Forms and checkout: send yourself a test message through the contact form and, if you run a store, simulate a purchase.
- The original cause: if a plugin broke things, don't blindly update it again; if it was a hack, change every password and patch whatever was vulnerable.
- What happened after the backup: check whether you lost content, orders, or comments created after the restored date, and recover them manually if needed.
What to look for in a host's backup policy
A restore is only as good as the backup behind it. When evaluating a host, ask four concrete questions. Frequency: are backups daily and automatic, or weekly, or "on request"? A weekly backup means you can lose up to six days of work. Retention: how many days back can you go? If malware sat hidden for two weeks, a three-day retention window is useless. Self-service: can you restore on your own from the panel, right now, or do you have to open a ticket and wait (and sometimes pay)? When your site is down, every hour counts. And separate hardware: do the copies live on the same machine as your site, or on independent infrastructure? Only the second option is a real backup.
We came to appreciate these details the hard way, through a few scares of our own, and it's one of the reasons we've stayed with BanaHosting: daily JetBackup copies, one-click restores from cPanel, and storage on separate hardware turn what used to be a crisis into a ten-minute routine. And if anything gets complicated, their 24/7 support answers in under ten minutes by chat, ticket, or phone, with a 30-day money-back guarantee as a safety net while you try it out.