A solid WordPress backup strategy follows the 3-2-1 rule: three copies of your data (the live site plus two backups), on two different types of storage, with one copy off-site. In practice, combine your host’s automatic backups with an external copy, for example on Google Drive using the free UpdraftPlus plugin, and test a restore every now and then.
Guide current as of 10 November 2026. UpdraftPlus steps refer to the free version of the plugin (1.26.x); WP-CLI commands assume SSH access.
Key takeaways
- A complete WordPress backup is the database plus the
wp-contentfolder, along withwp-config.phpand.htaccess. - 3-2-1 rule: 3 copies, 2 types of storage, 1 off-site. Your host’s backups only count as one copy.
- Free UpdraftPlus can send backups to Google Drive, Dropbox, Amazon S3 or FTP on an automatic schedule.
- Back up the database more often than the files: it changes with every order, comment and post.
- Keep several versions over time: a hack discovered late may already be in your most recent backups.
- An untested backup is just a hope: restore it on a staging copy.
What do you need to back up in WordPress?
Two things: the database, which holds your content, settings, users and orders, and the wp-content folder, which holds your media, themes and plugins. Add wp-config.php and .htaccess, which carry the site’s configuration. WordPress core itself can be downloaded again at any time.
| Component | Contents | Changes | Essential? |
|---|---|---|---|
| Database | Posts, pages, settings, accounts, WooCommerce orders | With every action on the site | Yes |
wp-content/uploads | Images, PDFs, media | With every upload | Yes |
wp-content/themes and plugins | Themes and plugins, including customised ones | With every update | Yes |
wp-config.php, .htaccess | Database credentials, keys, rewrite rules | Rarely | Yes |
Core (wp-admin, wp-includes) | WordPress files | Each release | No, re-downloadable |
The official WordPress Backups page covers each part. Leave out cache folders (wp-content/cache, wp-content/litespeed) and old backup archives stored on the server: they bloat every copy for no benefit.
What is the 3-2-1 backup rule?
A simple rule so you never depend on a single copy: keep 3 copies of your data (the original and two backups), on 2 different types of storage, with 1 copy off-site. It is set out, among others, by the US Cybersecurity and Infrastructure Security Agency in its Data Backup Options paper.
Each number addresses a specific risk. Three copies protect you if one backup fails. Two types of storage stop a single incident (a disk failure, a mistake, a compromised account) from hitting every copy. The off-site copy covers a disaster or a problem at the provider that hosts the original. Two sensible additions: keep one backup disconnected when it isn’t in use, out of reach of ransomware, and check regularly that backups actually restore.
| Copy | Where | Who handles it | Purpose |
|---|---|---|---|
| 1. The live site | Your host’s server | You | Original |
| 2. Host backups | Your host’s infrastructure | The host, automatically | Fast restore after a mistake |
| 3. External copy | Google Drive, Dropbox, S3, local disk | You, via a plugin or script | Full independence from your host |
How often should you back up WordPress?
As often as the amount of data you could live with losing. A brochure site updated once a month can get by with weekly backups; an active blog deserves a daily database backup; an online store needs the database backed up at least daily, plus a copy right before any major update.
| Type of site | Database | Files | Versions to keep |
|---|---|---|---|
| Brochure site | Weekly | Weekly | 4 to 8 weeks |
| Active blog or publication | Daily | Weekly | 2 to 4 weeks |
| WooCommerce store | Daily, or several times a day | Daily | 2 to 4 weeks, plus a monthly copy |
| All | Before every major update | Before every major update | Until validated |
Retention matters as much as frequency. If you only keep the last three daily backups and a hack is discovered after two weeks, every copy is infected. Keep a few older restore points too.
How do you back up WordPress to Google Drive with UpdraftPlus?
Install the free UpdraftPlus plugin, pick Google Drive as remote storage, authorise access to your Google account, then schedule file and database backups separately. Archives are then uploaded automatically to an “UpdraftPlus” folder in your Drive.
The official UpdraftPlus listing confirms that the free version supports Google Drive, Dropbox, Amazon S3, FTP and other destinations. The steps:
- Install and activate UpdraftPlus from Plugins > Add New.
- Go to Settings > UpdraftPlus Backups and open the Settings tab.
- Set the schedules: choose the “Files backup schedule” and the “Database backup schedule” separately, and how many backups to retain (older ones are deleted automatically).
- Under Choose your remote storage, click Google Drive, then click Save Changes at the bottom of the page.
- Authorise access: UpdraftPlus sends you to Google, you sign in to the account you want, grant the permissions and complete the setup back in WordPress.
- Review “Include in files backup” (plugins, themes, uploads, other folders) and leave cache folders out.
- Run a first manual backup from the Backup / Restore tab with Backup Now, then check the archives appear in Google Drive.
The connection process is walked through step by step in the vendor’s guide How to use the UpdraftPlus Google Drive app. Three things to watch:
- Storage space: a free Google account has 15 GB shared between Gmail, Google Drive and Google Photos. Multiply the size of one backup by the number of versions you keep.
- Encryption: in the free version, the database is uploaded unencrypted (database encryption is a premium feature). If it holds customer data, protect the Google account with 2FA and check this storage against your data protection obligations.
- A dedicated account: ideally use a Google account reserved for backups, with a unique password, so a compromise of your personal account doesn’t reach your backups.
How do you back up WordPress from the command line?
If your hosting gives you SSH access, two commands produce a complete backup: a database export with WP-CLI and an archive of the files. A tool like rclone can then copy those archives to Google Drive or other storage, with no WordPress plugin involved.
cd /path/to/wordpress
DATE=$(date +%F)
# 1. Database
wp db export ~/backups/db-$DATE.sql
# 2. Files (without caches)
tar -czf ~/backups/files-$DATE.tar.gz \
--exclude='wp-content/cache' --exclude='wp-content/litespeed' \
wp-content wp-config.php .htaccess
# 3. Off-site copy (rclone set up beforehand with "rclone config")
rclone copy ~/backups gdrive:site-backupswp db export produces a standard SQL file that wp db import can load back. Setting up Google Drive in rclone is documented on rclone.org. Schedule the script with a cron job and prune old local archives so you don’t fill your disk.
At Hosterwise there is no SSH access: it is a security choice that reduces the servers’ attack surface. You get the same result without the command line: UpdraftPlus, covered above, automates the copy to Google Drive, and CyberPanel lets you export the database with phpMyAdmin, generate a site archive under Backups and fetch files with the File Manager or an FTP account.
Are your host’s backups enough?
They are essential but not sufficient. They make quick restores possible after a mistake or a failed update, but they depend on the same provider as your site: in a billing dispute, an account suspension or a major incident on their side, you are left without a copy. Always add one you control.
Ask your host three questions: how often do backups run, how long are they kept, and who can restore them, how quickly? At Hosterwise, your sites are backed up automatically every day, on every plan. Those backups are stored off the server that hosts your sites, each one is kept for 30 days and, if something goes wrong, our support team restores an earlier version. They are copy number two in your 3-2-1 setup; copy number three, on Google Drive or elsewhere, stays in your hands.
How do you test a backup restore?
Restore to a test copy (a staging subdomain or a local install), never straight onto the live site. Check pages, media and the admin login: you then know the backup works and how long a restore actually takes.
- Create a test environment: a subdomain such as
staging.example.comwith a fresh WordPress, or a local development tool. - Install UpdraftPlus there, connect the same remote storage and rescan it, or upload the archives manually.
- Restore the database, plugins, themes and uploads.
- Check the home page, a few posts, images and a form. Discourage indexing on the test copy (Settings > Reading).
- Delete the test copy when you are done, or password-protect it.
With WP-CLI, if your host gives you SSH access, restoring the database on the test copy takes two lines, followed by a URL replacement:
wp db import db-2026-11-10.sql
wp search-replace 'https://example.com' 'https://staging.example.com' --skip-columns=guidAt Hosterwise, import the database with phpMyAdmin from CyberPanel, then ask our 24/7 support to run that wp search-replace for you.
Time the whole operation: that is your real recovery time. Test at least once a quarter, and whenever you change your backup method.
What are the most common backup mistakes?
- Keeping backups only on the site’s own server: if the server or the account is lost, so are they.
- Backing up files but not the database: you lose all your content.
- Never checking uploads: an expired Google authorisation or a full Drive can silently stop backups for weeks. Turn on the plugin’s email reports.
- Keeping too few versions: you may only find copies that are already infected or broken.
- Skipping a backup before big changes: a major update, a new theme, a move to a new host.
- Running several backup plugins: they fire at the same time and slow the site down. One is enough.
A second automatic copy with Hosterwise
Backups are also a pillar of our WordPress security checklist: they are your safety net when every other defence has failed. Hosterwise plans include daily automatic backups of your sites, stored off the server that hosts them and kept for 30 days, with restores handled by our 24/7 support team. For online stores, our WooCommerce hosting guide explains why daily backups make a difference.
Everything included is listed on our hosting features page; to pick the plan your site needs, compare the Starter, Premium and Boost plans, which host up to 3, 10 or 20 sites, with resources dedicated to each site. All include free migration and a 30-day money-back guarantee.
WordPress backup FAQ
Can the free version of UpdraftPlus back up to Google Drive?
Yes. Free UpdraftPlus supports Google Drive, Dropbox, Amazon S3, FTP and more. Backups go to an “UpdraftPlus” folder in your Drive; choosing a custom subfolder, encrypting the database and incremental backups are premium features.
What is the difference between full and incremental backups?
A full backup copies the whole site every time. An incremental backup only copies what changed since the previous one: it is faster and smaller, but restoring it depends on the chain of earlier backups.
How much space does a WordPress backup take?
Roughly the size of your compressed wp-content folder plus the database, with media usually taking the lion’s share. Multiply that by the number of versions you keep to size your external storage.
Should I back up before every update?
Before every major update (a new version of WordPress, WooCommerce or a page builder), yes. For small automatic updates, a recent daily or weekly backup is usually enough.
Can I restore an UpdraftPlus backup on another host?
Yes. Install a fresh WordPress on the new host, add UpdraftPlus, upload or fetch the archives and restore them. It is one of the migration methods in our migration guide.
Does Hosterwise back up my sites automatically?
Yes, with nothing to set up: daily on every plan, with each backup kept for 30 days. They are stored off the server that hosts your sites, and our support team can restore an earlier version when needed. We still recommend an external copy to complete the 3-2-1 rule.



