How to Back Up a WordPress Site and Restore It

Back up WordPress properly: database and files on their own schedules, a snapshot before every update, an off-site copy, and a restore you can undo.

Here’s an uncomfortable question: if your WordPress site vanished tomorrow—database, uploads, everything—could you actually get it back? For a lot of owners the answer is “maybe, from a host backup that might be recent.” A real backup strategy is the single highest-value thing you can do for a site, because a bad update, a hack, or a hosting failure can erase months of work in seconds. And a backup you’ve never restored isn’t a backup—it’s a hope. Here’s how to do it properly.

The essentials

  • Back up separately: database, plugins, themes and uploads change at different rates—so archive them independently.
  • Automate it: schedule the database daily and files weekly (they don’t change at the same pace), each with its own retention.
  • Snapshot before updates: switch on the pre-update backup once and it turns a broken update into a one-click rollback.
  • Keep a copy off-site: push backups to S3, Google Drive, Dropbox, OneDrive, pCloud, SFTP or WebDAV (Google Drive, Dropbox and OneDrive in Beta)—a local-only backup dies with the server.
  • Restore safely: every restore first backs up what it is about to overwrite, so you can undo it in one click—and if that safety backup fails, nothing is restored until you say so.

What does a good backup strategy actually look like?

A good WordPress backup strategy rests on three principles: back up the database and the files as separate pieces, because they change at different speeds; let a schedule do the remembering for you; and protect the riskiest moment of a site’s life, the update, with an automatic snapshot taken just before it. Everything else is detail.

Separate your components. Your database, plugins, themes and uploads don’t change at the same rate—your database might change hourly while your uploads sit still for weeks. Backing them up (and restoring them) independently saves time and space: change a few posts and you don’t need to re-archive 5 GB of media.

Run on a schedule. Manual backups depend on you remembering, and you won’t. An automatic schedule means you’re covered on your worst day, not just your most diligent one. Because the database and files move at different speeds, the smart pattern is database daily, files weekly—each on its own cadence and retention.

Protect the risky moments. The single most dangerous instant for a site is right after an update. A pre-update backup, taken before any core, plugin or theme update once you’ve enabled it, means a broken update is a rollback instead of a rebuild—and if the update takes the whole site down, the Fatal Error Recovery module gets you back into the admin to run it.

Put together, that gives you a simple cadence—each piece on its own schedule for its own reason:

What to back upRecommended cadenceWhy
DatabaseDailyChanges constantly—posts, comments, orders, settings
Files (plugins, themes, uploads)WeeklyChange far less often than the database
Pre-update snapshotBefore every update, once switched onThe single riskiest moment for a site
Off-site copySent with every backupA local-only backup dies with the server

How do you set up backups with Blaminhor Essentials?

Enable the Backup & Restore module and it splits into a few clear jobs: create a backup from the components you pick, schedule the database and files on independent cadences, push copies off-site, and manage or restore existing ones. Before every restore it backs up what will be overwritten; switch on pre-update backups once and updates are covered too.

Activate the Backup & Restore module in Blaminhor Essentials. It’s organized around a few clear jobs.

The Backups tab of the Backup & Restore module: three archives listed with their name, type (pre-restore or database), the components they contain, size and date, each with Restore, Download and Delete buttons. The Backups tab: every archive with what it contains, when it was made and a Restore button—including the safety backups the module made before a restore.

  • Create a backup — pick components (database, plugins, themes, uploads; optionally all of wp-content or core), and a live progress bar shows each step. Large archives are automatically split so they don’t hit server limits.
  • Schedule backups — set independent frequencies for the database and files (daily, weekly, every two weeks or monthly), each with its own time and retention count. Turn on pre-update backups to snapshot automatically before core, plugin or theme updates, and get an email report when scheduled backups run (all runs, or failures only).
  • Send copies off-site — connect a remote destination and each backup is also uploaded there: S3-compatible storage, Google Drive, Dropbox, OneDrive, pCloud, SFTP or WebDAV (Google Drive, Dropbox and OneDrive in Beta). Local by default, off-site when you want real disaster recovery.
  • Manage and restore — browse existing backups, restore any of them, download archives to your computer, or bulk-delete old ones to reclaim space.

What happens when you restore?

Before any restore, the module backs up exactly what it is about to overwrite: the database for a database restore, plugins, themes and uploads for a files restore. If the restore goes wrong, you undo it in one click. If that safety backup cannot be created, the module stops, touches nothing, and asks whether to restore anyway, without undo.

Two limits are worth knowing before you lean on that undo. First, undoing a restore replays the safety backup, so anything created or changed between the restore and the undo—an order, a comment, an upload—goes with it. Second, the safety backup covers the database, plugins, themes and uploads; restoring the whole of wp-content or WordPress core goes beyond what it holds, so keep a full backup for those.

The restore engine also handles the details that quietly wreck naive restores: it processes serialized data correctly (so Elementor and Divi layouts survive), manages table-prefix differences when restoring to a different install, and guards against two restores running at once. Restoring a backup to a new domain? It detects the difference and offers to update references during the restore—the same problem the Domain Changer solves, built into the restore path. And a database backup is the right first step before a database cleanup, which cannot be undone any other way.

How often should you back up?

Back up as often as you would hate to lose work: daily for a WordPress site that changes every day (an active blog, a WooCommerce store, anything with user-generated content), weekly for most business sites and portfolios, every two weeks or monthly for near-static sites. The module offers all four cadences, separately for the database and the files.

  • Daily — active blogs, WooCommerce stores, anything with user-generated content.
  • Weekly — most business sites and portfolios.
  • Every two weeks or monthly — near-static sites that rarely change.

And let the pre-update backup cover the gaps: once it’s on, every time WordPress, a plugin or a theme updates, a snapshot is taken automatically, whatever your schedule.

What does a WordPress backup done right come down to?

You don’t need an enterprise, cloud-first system to be genuinely safe. You need components backed up separately, an automatic schedule, a snapshot before every update, one off-site copy, and a restore you can undo. That’s the whole job—and it’s exactly what the Backup & Restore module does.

Backup & Restore is one of the 26 modules in Blaminhor Essentials—free and open-source on WordPress.org.

Download Blaminhor Essentials

– blaminhor

FAQ

Should WordPress backups be stored off-site?

Yes. A backup sitting only on the same server dies with that server in a hosting failure or hack—which is exactly when you need it. The 3-2-1 rule says keep at least one copy off-site. The Backup & Restore module can start local (no account needed) and also push copies to S3, Google Drive, Dropbox, OneDrive (these three in Beta), pCloud, SFTP or WebDAV.

What is a pre-update backup?

It's an automatic snapshot taken right before WordPress, a plugin or a theme updates—the single riskiest moment for a site. If an update breaks something, you have an instant restore point from moments before, with no action required once you've switched it on. It turns 'I updated and the site broke' from a disaster into a one-click rollback.

Is it safe to restore a WordPress backup?

It is when the tool protects you. Before any restore, the Backup & Restore module backs up exactly what the restore will overwrite—the database, or the plugins, themes and uploads—so you can undo it in one click. If that safety backup cannot be created, nothing is restored until you explicitly choose to go on without an undo.

Do I still need backups if my host already backs up my site?

Yes. Host backups are a safety net you don't control: retention is often short, restores can be slow or come at a cost, and they may not cover the exact moment you need. Your own backups—on your schedule, kept off-site—mean you're never stuck waiting on a support queue to get your site back.

Can I use a backup to migrate my site to a new host?

Yes. Because the Backup module processes serialized data and adjusts table prefixes, you can restore an archive onto a fresh install elsewhere. Moving to a new domain in the process? It detects the change and offers to update the references during the restore, so your internal links and page-builder layouts land intact.

Are my off-site backups encrypted and secure?

The module does not encrypt the archives themselves: a backup is a plain ZIP (with the database as an SQL file inside), so anyone who can read the destination can read your site. What it does encrypt is the connection credentials it stores—API keys, tokens, SFTP keys. Pick a destination you trust and keep its access limited.

What happens if I undo a restore?

Undoing a restore replays the safety backup taken just before it, so the database or files go back to their state at that moment. Anything created or changed in between—an order, a comment, an upload—is lost with it. That is why a restore is best tested on a staging copy, or on the live site at a quiet moment.

blaminhor Building what's missing.

Comments