A dependable website backup strategy combines complete coverage, sensible retention, protected off-site copies, and regular restore tests. This checklist helps you decide what to back up, how often to capture it, how long to keep it, and how to prove that recovery will work when you need it.
Overview
A backup is useful only if it is both available and restorable. A hosting control panel may offer automated snapshots, but that does not automatically mean every important website component is covered or that the backup can be recovered to a working environment. Your plan should account for the website files, databases, uploaded media, configuration, email where applicable, and the domain and DNS details needed to reconnect the site.
Start by defining two recovery objectives:
- Recovery point objective (RPO): the maximum amount of recent data you are prepared to lose. If a site changes daily, a daily backup may be adequate; an ecommerce or membership site may require more frequent database protection.
- Recovery time objective (RTO): the target time for returning the website to an operational state. A brochure site may tolerate a longer manual recovery, while a business-critical application may require documented steps and a prepared staging environment.
These objectives should determine the schedule rather than the other way around. For a broader hosting security routine, compare this plan with the hosting backups and disaster recovery checklist.
Checklist by scenario
Standard business or brochure website
- Back up the complete web root, including themes, plugins, application code, media, and configuration files.
- Export the database on a schedule that matches how often content changes.
- Keep at least one copy outside the hosting account or hosting server.
- Use a retention pattern that includes recent daily or weekly copies and a longer-term monthly copy.
- Test a restoration at planned intervals rather than waiting for an outage.
WordPress website
- Confirm that the backup includes both the database and the
wp-contentdirectory, including uploads, themes, and plugins. - Record the WordPress version, active theme, important plugins, PHP version, and any custom configuration that may be needed during recovery.
- Check whether the backup tool can restore to a different directory, subdomain, or staging site.
- Before a major update, create a fresh backup and confirm that it completed successfully.
- Review the managed WordPress hosting setup and maintenance checklist for related maintenance tasks.
Database-driven or frequently changing website
- Separate database frequency from file frequency if transactions or user activity change more often than application files.
- Confirm that exports are complete, readable, and stored with timestamps.
- Document how to pause writes or place the site in maintenance mode during a final recovery cutover.
- Decide how uploaded files created after the last full file backup will be captured.
- Measure the time required to rebuild the application, import the database, clear caches, and verify core functions.
Email and DNS dependencies
- Determine whether mailbox data is covered by the web hosting backup. Website files and hosted email are often managed separately.
- Keep a current inventory of DNS records, including A, AAAA, CNAME, MX, TXT, and verification records used by external services.
- Record nameservers, DNS provider access, domain ownership details, and renewal contacts in a secure location.
- After restoration, verify that DNS points to the correct server and that email records have not been overwritten.
For a practical reference, use the DNS records guide when documenting the records required to reconnect a restored website.
Hosting migration or provider change
- Create an independent backup before changing nameservers, DNS records, application settings, or server configuration.
- Retain the original backup after the migration has been verified.
- Test the copy on the new host before changing production DNS where possible.
- Compare URLs, file permissions, scheduled tasks, SSL configuration, database credentials, and outbound email.
- Keep a rollback plan that states how to return traffic to the previous environment.
The choice of shared hosting, VPS hosting, or cloud hosting can affect access to snapshots, automation, storage, and recovery tooling. Review the hosting comparison guide before assuming that a new platform supports the same recovery workflow.
What to double-check
Use this table when reviewing a provider feature, backup plugin, script, or internal process.
| Area | Questions to answer |
|---|---|
| Files | Are application files, uploads, themes, plugins, and custom configuration included? |
| Database | Is the database captured separately, and can it be imported without corruption or missing tables? |
| Are mailboxes, aliases, filters, and mail data covered, or do they require a separate process? | |
| Location | Is at least one usable copy stored outside the primary hosting account? |
| Schedule | Does the frequency match the rate at which the website changes? |
| Retention | Can you recover from a recent mistake as well as an issue discovered weeks later? |
| Security | Are backup files access-controlled and encrypted during transfer and storage where appropriate? |
| Restoration | Can the backup be restored to staging or another host without affecting production? |
| Monitoring | Will someone know when a scheduled backup fails, runs out of storage, or produces an incomplete archive? |
Run a restore test
- Select a recent backup and record its date, size, source, and included components.
- Restore it to a staging site, isolated directory, or temporary server. Do not overwrite production for the first test.
- Confirm that the application loads and that the database connection works.
- Check representative pages, images, forms, user authentication, search, file downloads, and key transactions.
- Verify URLs, redirects, SSL, scheduled jobs, caching, and outbound email behavior.
- Record the elapsed time, errors, manual fixes, and any missing data.
- Update the procedure and repeat the test after changing hosting, backup software, the CMS, or major infrastructure.
A restore test is successful only when the result is usable, not merely when an archive extracts without an error.
Common mistakes
- Keeping every copy on one server: a server problem, compromised account, or accidental deletion may affect both the website and its backups.
- Backing up only the files: many CMS websites need the database to restore posts, settings, users, orders, and other dynamic data.
- Assuming a green status means a complete backup: inspect the backup contents and review failure notifications.
- Using a single retention point: the newest copy may preserve a damaged or compromised state. Keep multiple recovery points.
- Ignoring access credentials: a backup is difficult to use if the hosting panel, storage account, DNS provider, or encryption key is unavailable.
- Testing only the homepage: recovery issues commonly appear in forms, media, permissions, integrations, scheduled tasks, or email.
- Forgetting DNS and SSL: a restored application can still appear offline if DNS points to the wrong destination or its certificate is not configured.
- Relying on backups as a security control: backups support recovery but do not replace updates, access controls, malware detection, monitoring, or least-privilege administration.
If a restored site is missing its secure connection, use the SSL certificate setup and troubleshooting guide alongside the recovery procedure.
When to revisit
Review the website backup strategy before seasonal planning cycles and whenever workflows or tools change. At minimum, schedule a quarterly review for active business websites and a restore test at an interval appropriate to the site’s risk and change rate.
Revisit the plan immediately after a hosting migration, CMS or plugin change, storage-provider change, domain transfer, security incident, major redesign, database change, or update to DNS and email services. Also review it when the site begins accepting payments, storing customer accounts, publishing more frequently, or supporting a new business process.
For your next review, complete these actions:
- List every website component and external dependency that must be recovered.
- Compare backup frequency and retention with current RPO and RTO expectations.
- Confirm that an off-site copy exists and that authorized staff can access it.
- Run a controlled staging restoration and record the result.
- Correct one weakness before closing the review, such as missing DNS records, an untested database export, or an unmonitored backup job.
A short, documented restore test is more valuable than an elaborate plan no one has practiced. Keep this checklist with your hosting and domain records, and update it whenever the website’s architecture or recovery requirements change.