Getting backups running is step one. Getting them running correctly is what actually matters.
A lot of WordPress sites have some form of backup in place — but the details of how it is set up determine whether it will actually save you when something goes wrong. Configuration is where most setups fall short.
What to configure when setting up WordPress backups
- What to back up — A complete backup includes both the database (content, settings, users) and the files (themes, plugins, uploads). Many setups only cover one. Both are required for a full restore
- Frequency — Daily for most business sites. More frequent for sites with high transaction volume or frequent content updates
- Storage location — Never store backups only on the same server as your site. Configure an external destination: cloud storage, a remote location, or a dedicated backup service
- Retention period — Define how many restore points to keep. Seven to thirty days gives you room to go back further if a problem is discovered late
- Notifications — Set up alerts for backup failures. A backup that silently stops running is worse than no backup at all — it creates false confidence
- Exclusions — Cache files and temporary data do not need to be backed up. Excluding them keeps backup files smaller and faster to create
Managed hosting vs doing it yourself
Quality managed WordPress hosting includes automated backups as standard. But “included” does not always mean “correctly configured.” It is always worth verifying what is actually being backed up, how often, and where it is stored.
If you are not certain your backup setup meets these criteria, a website checkup will tell you exactly where the gaps are. See also our backups best practices guide and the full backups knowledge base.
Want us to handle all WordPress maintenance for you? See our maintenance plans →