- A useful backup has the database and the wp-content folder (media, plugins and themes) and has been tested in a restore.
- Match the frequency to the site: daily for stores and sites that change every day, weekly for most others.
- Keep at least one copy off the server: a backup that only lives on the server disappears with it.
A backup is your site’s insurance: nobody thinks about it until they need it. A faulty plugin, an update that breaks the theme, a hack or a host that vanishes, and what separates a scare from a loss is a recent, complete copy that is easy to restore. This guide shows how to build that routine.
What must be in the backup
- Database: all the content and settings. Without it, there is no site.
- Media (
wp-content/uploads): uploaded images and files. Usually the largest part. - Plugins and themes: you could reinstall them, but the backup keeps the exact versions and any custom files.
What can safely stay out: old post revisions, spam comments, transients (temporary data) and cache folders. Leaving them out makes the backup smaller and faster.
The 3-2-1 rule, applied to WordPress
The classic backup rule says: 3 copies of your data, in 2 different places, with 1 off-site. For WordPress, that means:
- The live site (the working copy).
- Recent backups on the server itself, for quick restores.
- A copy off the server: in your Google Drive or in cloud storage.
Your host’s backup helps, but it doesn’t replace yours: it stays with the same provider, its retention is not always what you need, and restoring it may depend on support.
How often to back up
| Type of site | Frequency | How many to keep |
|---|---|---|
| Online store, membership site, news portal | Daily | 7 to 14 |
| Blog or site with weekly posts | Weekly | 4 to 8 |
| Company site that rarely changes | Every two weeks or monthly | 3 to 6 |
And always a manual backup before updating WordPress, a theme or an important plugin, and before any big change.
How to automate backups with Migram
- Install Migram (free) and open Migram → Schedule.
- Turn on automatic backups and choose the frequency: daily, weekly, every two weeks or monthly, with the day and time.
- In How many to keep on this server, set how many recent backups to keep. Older ones are deleted on their own; manual backups are never deleted automatically.
- Choose what stays out of the automatic backups (in Export → Advanced options).
- Turn on e-mail notifications to know when a backup fails or has warnings.
For the off-server copy, Migram PRO sends each automatic backup to your Google Drive, and the Cloud plans also keep it in Migram Cloud, which can be restored even if the server is gone.
How to restore a backup
- Open Migram → Backups and pick the backup.
- Click Restore and confirm.
- The current site keeps working until the end: the new database is loaded separately and switched in at once.
If the whole server is lost, install a clean WordPress on any host, install Migram and import the file you kept off-site (or restore straight from Migram Cloud, in Migram → Import). It is the same process as a site migration.
Test your backup
A backup that has never been restored is a bet. Every few months, restore a backup on a test site (a local copy or a subdomain) and check that the content, images and login are all there. It takes a few minutes and shows whether the routine really works.
Frequently asked questions
Isn’t my host’s backup enough?
It is an extra layer, not the only one. It stays with the same provider as the site, with retention set by them, and restoring it may depend on support. Keep a copy of your own, off the server.
How much space do backups take?
Each backup is roughly the size of the database plus media, plugins and themes. Multiply by the number of backups kept on the server and make sure your hosting plan has that space.
Do backups slow down the site?
A good plugin works in short steps in the background. Schedule automatic backups for a quiet time, such as the middle of the night.
Where does Migram keep backups on the server?
In wp-content/migram-backups, protected from direct web access. To use another folder, define MIGRAM_STORAGE_DIR in wp-config.php.