What Is a Website Backup (and When Does It Save You)?

← All Hosting Guides

Imagine you spent months decorating your home — every photo on the wall in the right spot, everything exactly how you like it. Now imagine a fire, a flood, or a break-in, and everything is gone. Painful to think about, right? For your website, a backup is the equivalent of having a copy of everything packed safely somewhere else. And unlike a house, websites get “broken into” and “flooded” surprisingly often.

This guide explains in plain words what a website backup actually is, what it should include, which disasters it saves you from, what it doesn’t protect you from, and how a restore works when the worst happens.

What exactly is a website backup?

A website backup is a complete, restorable copy of your website, stored somewhere separate from the live site. A complete backup has two parts, and you need both:

Your files — WordPress itself, your theme (like Divi), your plugins, and every image, PDF and video you’ve uploaded. On a typical hosting account this lives in a folder called public_html.
Your database — a separate file that holds all your content: posts, pages, menus, user accounts, comments, and your settings. A WordPress site without its database is an empty shell; the files alone don’t contain your text.

A useful analogy: the files are the walls, plumbing and furniture of your house, and the database is everything written in your diary. Copying only one of them means the other is lost.

When does a backup actually save you?

Backups feel like a boring chore right up until the day they’re the only thing standing between you and starting over. Here are the real-world situations where a recent backup turns a catastrophe into a ten-minute inconvenience:

You get hacked. This is the big one. Malware gets injected into your site, Google flags it with a red “this site may be hacked” warning, and visitors vanish. Cleaning a hacked site by hand can take days and isn’t always possible. Restoring a clean backup from before the infection? Minutes.
A plugin update breaks everything. You click “update” on a plugin, and suddenly your homepage is a white screen (the famous WordPress “white screen of death”). If the plugin author never replies to your support ticket, a backup from before the update lets you roll back instantly.
You delete something by accident. You’re tidying up and delete a page — or an entire menu — that you actually needed. Maybe a whole client’s worth of content. There is no “undo” button on a live website. There is only a backup.
Your hosting company has a bad day. Servers fail. Disks die. A good host keeps backups of their own, but the gold-standard rule in the industry is that you should also have a copy you control, because no single copy is ever guaranteed.
A “developer” (or a well-meaning friend) makes a mess. Someone edits your theme files directly, breaks the site, and disappears. Backup → restore → back to business.
A compromised account locks you out. If an attacker changes your admin password and email, a backup plus your hosting credentials are how you take the site back.

What a backup does NOT cover

Backups are powerful, but they’re not magic. Know these limits:

A backup is a snapshot, not a time machine into the past. If your last backup was a week ago, a week of new posts, orders, and customer emails is gone when you restore. This is why backup frequency matters — daily backups mean you lose at most a day.
Restoring rolls everything back. Restoring to yesterday’s backup also undoes everything done today, including legitimate work. If you got hacked, find the oldest backup from before the hack.
Backups don’t prevent attacks. They’re your recovery plan, not your firewall. Security hardening (updates, strong passwords, SSL) and backups do different jobs — you need both.
Email and domain settings usually live elsewhere. Most website backups don’t include your mailboxes or your DNS records. Check what your host’s backup covers.
A backup stored on the same server isn’t fully safe. If the server itself dies — or is compromised — a “backup” sitting next to your site can die with it. Copies should exist in a second location.

How often should you back up?

A simple rule of thumb based on how often your site changes:

Changes weekly or less (a brochure site): weekly backups are fine.
Changes daily (a blog, a business site with contact forms): daily backups.
Takes orders or holds member data (an online shop): daily backups of the website, plus frequent backups of the shop database specifically — order data is the thing you least want to lose.

And remember the industry-standard 3-2-1 rule: 3 copies of your site, on 2 different types of storage, with 1 copy stored off-site (somewhere other than your main server). You don’t need to be obsessive about it — but at minimum, one copy should live somewhere other than the server running your site.

How a restore actually works

When something goes wrong, a restore is just running the process in reverse:

Stop and assess. Figure out what happened and when, so you pick a backup from before the problem started. Restoring onto a hacked site with the wrong backup just re-imports the hack.
Upload or select the backup. Depending on your host, you either pick a restore point in the control panel or upload the backup files and database dump yourself.
Restore the files and the database. Both parts, always. Files without the database gives you a broken site; database without files is just text with nowhere to live.
Update passwords and software. After a hack, change every password (hosting, WordPress admin, database) and update WordPress, your theme and plugins before you’re back online for long — otherwise you may get re-infected within hours.
Test. Click through your pages, send a test email through your contact form, place a test order if you run a shop. A restore isn’t finished when the files land; it’s finished when the site works.

If your host offers one-click restores, this whole process is usually minutes. Doing it manually from files is very doable too — it’s just slower.

Backups at AriHosting

We keep this simple: every hosting plan includes daily automatic backups of your files and database, retained on a rotating schedule, with restore available on request from support. You don’t have to configure anything — but if you’d like your own independent copy as well (per the 3-2-1 rule), you can download a full backup from cPanel at any time, and we’ll happily walk you through it.

Quick checklist

✅ Confirm backups are running (files and database)
✅ Match backup frequency to how often your site changes
✅ Keep at least one copy off the main server
✅ Do one test restore — a backup you’ve never restored is a plan you’ve never rehearsed