A reliable website backup strategy is more than switching on an automated task. This guide provides a practical schedule for WordPress and small-business websites, explains what to back up, shows how to test a restore, and gives you a repeatable recovery checklist for routine updates and unexpected incidents.
Overview
Your backup schedule should reflect how often your website changes and how much recent data you can afford to lose. A brochure-style site that changes once a month has different requirements from an online store, membership site, or active blog that receives new orders, comments, or form submissions every day.
Two recovery objectives make the decision clearer:
- Recovery point objective (RPO): the maximum amount of recent data you are prepared to recreate after a failure. An RPO of 24 hours suggests that a daily backup may be acceptable; an RPO of one hour requires more frequent copies.
- Recovery time objective (RTO): the target time for getting the website usable again. A short RTO requires documented restore steps, accessible credentials, and a tested backup rather than an unverified archive.
A complete website backup normally includes both files and the database. WordPress files contain the core installation, themes, plugins, media uploads, and configuration files. The database contains posts, pages, users, settings, menus, comments, and other structured content. Backing up only one of these parts may leave you with an incomplete recovery.
| Backup component | What it usually contains | Why it matters |
|---|---|---|
| WordPress files | Core files, themes, plugins, uploads, and configuration | Restores the application and uploaded assets |
| Database | Content, accounts, settings, menus, and comments | Restores the site’s changing information |
| Hosting configuration | Redirects, scheduled tasks, PHP settings, and service configuration where applicable | Helps reproduce the hosting environment |
| Email and DNS records | MX, SPF, DKIM, DMARC, A, CNAME, and TXT records | Supports continuity for email and domain connections |
Keep a copy of important DNS and email settings separately from the website backup. A website restore does not necessarily restore DNS records or mailboxes. For reference, see the DNS records guide and the business email DNS checklist.
Checklist by scenario
For a low-change brochure website
- Schedule at least a regular full backup, with the interval chosen according to how often content changes.
- Create an additional backup before publishing a major redesign, changing the theme, or installing a significant plugin.
- Retain several recent versions so you can recover from a problem discovered after the latest backup.
- Perform a restore test on a planned schedule instead of assuming that a successful backup job guarantees a usable restore.
For an active blog or small-business website
- Use more frequent database backups if the site receives regular form submissions, comments, bookings, or content updates.
- Run a complete files-and-database backup before WordPress core, plugin, or theme updates.
- Save a copy outside the production hosting account. An account-level problem should not remove every copy of the backup.
- Record the backup location, encryption details, retention period, and person responsible for checking failures.
For an online store, membership site, or other high-change website
- Define the maximum order, account, or submission data that could be lost and choose the backup interval accordingly.
- Consider separate schedules for the database and large static files, provided the backup system can restore them consistently.
- Protect backups from unauthorised access because they may contain customer information, user accounts, or confidential business data.
- Document a recovery owner and an escalation path. During an incident, uncertainty about who acts first can delay restoration.
- Test the recovery process with a copy of the site or another isolated environment before an emergency occurs.
Before a website migration or hosting change
- Create a fresh backup immediately before the migration and verify that the archive can be opened.
- Export or document DNS records, email settings, SSL requirements, cron jobs, redirects, and third-party integrations.
- Keep the original hosting account available until the new site has been checked and the rollback decision period has passed.
- Compare pages, media, forms, user access, search visibility settings, and transactional functions after the move.
The WordPress migration checklist can be used alongside this backup plan when changing hosts.
What to double-check
Storage and retention
Use a storage arrangement that separates at least one backup from the live hosting environment. This may be a provider-supported remote destination, a controlled cloud storage location, or another appropriately protected repository. Avoid treating a backup folder on the same server as your only recovery option.
Choose retention deliberately. A practical policy might keep several recent daily copies, a smaller set of weekly copies, and selected monthly copies, but the right pattern depends on storage capacity, site activity, compliance needs, and how far back problems may go unnoticed. State the policy in writing rather than allowing old files to be deleted unpredictably.
Backup integrity
- Check that scheduled jobs report success and that failures generate an alert.
- Confirm that the archive contains both the database and required files.
- Check the backup date, size, destination, and access permissions.
- Protect backup access with strong credentials and appropriate multi-factor authentication where available.
- Keep backup software, WordPress, plugins, and hosting components maintained according to your normal security process.
Restore testing
A restore test should answer a simple question: can this backup produce a working website? Use a staging site or isolated environment where possible. Record the test date, backup version, restoration steps, errors, and result.
- Select a specific backup rather than an unspecified “latest” copy.
- Restore the files and database into the test environment.
- Confirm that WordPress loads and that the correct site URL is used for the test.
- Open representative pages, images, menus, and posts.
- Test administrator login, forms, search, ecommerce or membership functions, and important integrations.
- Check links, redirects, scheduled tasks, and media paths.
- Document any manual steps required to complete the restore.
Do not send test emails or process real transactions from a restored staging copy unless those functions have been safely isolated. Afterward, remove or protect the test environment so it cannot expose content or become an overlooked security risk.
Common mistakes
- Backing up only the database: content may be present, but themes, plugins, uploads, and configuration may be missing.
- Backing up only before major changes: this does not protect content created between changes or data lost through an account or server failure.
- Keeping every copy on the live server: a storage, access, or hosting incident could affect both the site and its backups.
- Never testing a restore: an archive can be incomplete, corrupted, incompatible, or difficult to use without the correct credentials.
- Ignoring plugin compatibility: two backup tools or a backup tool and a security or caching plugin may interact unexpectedly. Test changes on staging where practical.
- Forgetting non-WordPress dependencies: DNS, email, SSL certificates, payment services, analytics, and external integrations may require separate recovery steps.
- Overlooking security: backups can contain passwords, personal information, and private content. Restrict access and use protected storage.
- Assuming a host backup meets every requirement: hosting backups can be useful, but confirm their scope, retention, access method, and restore process before relying on them as your only copy.
If a restore changes HTTPS behaviour, review the SSL certificate setup guide and the HTTPS troubleshooting guide.
When to revisit
Review this website disaster recovery plan before seasonal planning cycles, a major campaign, a redesign, a WordPress or plugin update, a hosting change, or a new data-collection workflow. Revisit it whenever the site becomes more active, adds ecommerce or membership features, changes owners, or moves to a different backup tool.
Use this recurring checklist:
- Each backup cycle: check that the job completed and the expected files and database are present.
- Before material changes: create and label a fresh restore point.
- Monthly or on a schedule suited to your risk: perform a restore test and record the result.
- Quarterly or after major workflow changes: review retention, off-site storage, access permissions, contacts, and RPO/RTO targets.
- After an incident: update the runbook with what failed, what worked, and which manual steps should be automated or documented.
Start by writing down your site’s update frequency, acceptable data loss, recovery target, backup locations, retention period, and restore owner. Then run one controlled restore test. A documented backup that can be recovered is a practical foundation for safer WordPress hosting and ongoing website operations.