A backup of your site is a saved snapshot of the files and database that lets you restore the site if it gets broken, hacked, or you make a bad update yourself. The direct answer to the main question: set up backups before anything goes wrong, not after — if you have no copies, there is nothing to restore from. Below I cover the essentials with no fluff: what a complete WordPress site backup consists of, why a copy at your hosting provider is not yet your backup, the 3-2-1 rule, how often to run backups, which plugins let you set everything up in an evening, and, most importantly, how to verify that you can actually restore from the backup.

What does a site backup consist of?

A full backup of a WordPress site always has two parts: files and database. Taken separately they are almost useless. If you save only the database you lose the design, theme settings, and all uploaded images. If you save only the files you lose all content, products, and orders because they live in the database. A real backup is the files and database captured at the exact same moment.

Backup part What it contains What you lose without it
Site files WordPress core, theme, plugins, uploads folder (uploads — all images and documents) Design, functionality, all media files
Database Posts, pages, products, orders, users, comments, site and plugin settings All content and orders — even if the files are intact the site will be empty

So when you choose a backup method, first check: does it save both? Many “quick” backups stop at the database, and when you need it you discover there is nowhere to restore the images and settings from.

How is a hosting provider backup different from your own?

Direct answer: a copy at your hosting provider is a nice bonus but not a replacement for your own backup. Many hosts do back up accounts, yet relying on them alone is risky for several reasons:

  • The copy lives on the same infrastructure. If the account is blocked, deleted for non-payment, or the provider restricts access, the copies become unavailable along with the site. This happens: I have a separate post about what to do when a hosting provider blocks your site.
  • Retention depth and frequency are limited by the plan. Often only the last few copies are kept, with older ones overwritten . If you notice the problem late, a “good” copy may no longer exist.
  • Restoring is not always fast or free. On some plans restoring a backup requires a support ticket and may be paid — while the site stays down.
  • You have no control over whether the copy is valid. Until you restore it at least once, you do not know if it works.

Simple conclusion: treat the host’s copy as extra insurance and keep your main backup under your own control and separate from the live site.

The 3-2-1 rule — how to store copies

This is the basic standard for backups and applies directly to websites:

  • 3 copies — the live site plus at least two backups.
  • 2 different media/locations — for example, cloud storage and a local drive, not two files in the same folder.
  • 1 copy off-site — at least one copy is stored somewhere other than the hosting account where the site runs.

The last point is the key. If your only backup lives on the same hosting as the site, one event — account suspension, ransomware, or server failure — destroys both the site and its copy. An off-site copy (cloud, another server, your computer) breaks that link: no matter what happens to the hosting, you still have a snapshot you can restore from.

How often should you run backups?

Frequency depends on how often the site changes. Use this guideline:

Site type Database Files
Brochure site, landing page (changes rarely) Once a week Once a month or when changes occur
Blog, content site Every other day to daily Once a week
Online store (orders every day) Daily, or more often Once a week + before updates

One extra rule on top of the table: create a backup before every change — updating WordPress or plugins, switching themes, editing code. If something breaks you can roll back to a copy made five minutes ago instead of yesterday’s. I covered how to update safely and why a backup is essential in the post how to update WordPress without breaking your site.

How to Set Up Backups: Plugins

For WordPress there are proven free plugins that handle the task without any coding. Here are three working options for different scenarios:

  • UpdraftPlus — probably the most popular backup plugin. It creates scheduled copies and uploads them to external storage (Google Drive, Dropbox and others), with restore launched from the dashboard in a couple of clicks. A solid main tool for most sites.
  • All-in-One WP Migration — packs the entire site (files and database) into a single snapshot file. Convenient for taking a full copy before a major edit or moving the site to another host. The free version has a limit on the size of the import file.
  • BackWPup — flexible scheduled jobs with uploads to FTP, cloud storage, or a separate folder. Good when you need to keep copies on your own external storage. Full restore from a backup is easier in the paid version.
!

Two common setup mistakes. The first is leaving copies on the same hosting as the site: that breaks the 3-2-1 rule, so configure uploads to the cloud or an external drive. The second is storing the database dump in an open folder on the site: that’s a direct leak because the database holds passwords and clients’ personal data. A site with forms and orders collects personal data.

How to Restore a Site from a Backup?

The method depends on how the copy was made and what happened to the site:

  • Through the plugin. If UpdraftPlus created the backup and the site is still basically working, restoration runs straight from the dashboard: the plugin restores the files and database from the chosen copy.
  • Manually. Files are uploaded to the host via FTP or the file manager, and the database is imported through phpMyAdmin. This method is universal and works even when the admin area is unreachable.
  • On a clean host. If the site is blocked or infected, the copy is deployed on a clean environment first, then the cause is investigated.

If the site was hacked, simply rolling back is not enough — it’s important not to bring the vulnerability back with the copy. I’ve put together a separate step-by-step guide for the first minutes after a hack: WordPress site hacked — what to do in the first 30 minutes. Finding and removing the infection is handled through hacked site cleanup ($249 flat, cleaned within 24 hours), and the backup is used to restore a clean version of the site.

Why Backups Often Fail to Save the Site

“We have backups” is the phrase that most often leads to losing the site. Here’s why backup in practice doesn’t work:

  • Copies stay on the same host. Account suspension or a hack takes out both the site and the backup at once.
  • Only the database or only the files are backed up. An incomplete copy won’t let you restore the whole site.
  • Copies have never been restored. “Backups exist somewhere” is not a backup until you’ve confirmed that a working site can be brought back from them.
  • Only one rotating copy is kept. If the hack or failure is noticed a week later, the single copy already contains the problem.
  • Copies are made too infrequently. For a store, even one backup per week can mean losing several days of orders.

Checklist: Working Site Backup

  • Copy is complete: files and database from the same moment in time.
  • Schedule matches how often content changes (store — daily).
  • At least one copy is stored off the site’s hosting.
  • History contains several copies, not a single rotating one.
  • A separate copy is taken before every update.
  • Restoration has been tested at least once in practice.
  • Database dump is not left openly accessible on the site.

How I Can Help

In short:

  • Set up backup for your site — from $99. Plugin, schedule matched to your update frequency, copies uploaded to the cloud, and a test that a working site can actually be restored from them.
  • Take the site on ongoing maintenance — Care $99/month. Regular backups, safe updates on a staging copy, monitoring. Cancel anytime.
  • If it’s already happened. I’ll restore the site from a backup; if it’s infected — hacked site cleanup for $249 flat, with a clean version returned from the backup.
I’ll set up backups so you can restore your site within an hour

I’ll connect backup with cloud uploads, configure the schedule, and test restoration in practice so the copy actually works when you need it. I can also take the site on regular maintenance. Care $99/month, one-time setup from $99.

Set up backup and maintenance

Common questions

Many hosts create copies of accounts, but this is not a replacement for your own backup. The copy stays on the same infrastructure, retention depth is limited by your plan, and restoration is sometimes handled only after a support ticket and may cost extra. Keep at least one copy of your own outside the hosting account.
It depends on how often the site changes: an online store — daily and always before any update; a content site — several times a week; a simple brochure site — once a week. On top of that, make a separate copy right before any change to the site so you can roll back to the state it was in five minutes ago.
At least one copy must be stored outside your hosting account — in the cloud, on another server, or on a local drive. If the copy lives on the same hosting as the site, a single event (account suspension, hack, or outage) can wipe out both the site and the backup. This is the point of the 3-2-1 rule.
Reliable free options: UpdraftPlus — scheduled backups with cloud upload and one-click restore from the dashboard; All-in-One WP Migration — a single snapshot file of the whole site, handy for moving it; BackWPup — flexible scheduled jobs that send copies to external storage. The right choice depends on your site and where you want the copies stored.
No, a backup does not prevent hacking, but it helps you recover afterward: you restore the site from a clean copy. That is why it is important to keep several copies in the backup history — if an infection went unnoticed for a while, the newest copy may already contain malicious code, so an earlier one becomes useful.
Yes. Even a simple brochure site is more painful and time-consuming to rebuild from scratch than to set up automated backups once. And if the site has forms or customer accounts, personal data is stored in the database, so keeping it safe is also a legal responsibility, not just a convenience.

Read also

  • WordPress site hacked: what to do in the first 30 minutes — the exact situation where a backup saves the day.
  • Site blocked by the hosting provider: what to do — why a backup stored on the same hosting can become unavailable together with the site.
  • Online store maintenance: what is included and how much it costs — regular backups as part of ongoing store support.