A website backup is useful only if it is complete, accessible, and restorable. This practical small business website backup plan explains how often to back up different site types, what to include, how to test a restore, and which details to review before a migration or major change.
Overview
Your website is more than the files visible in a hosting control panel. A workable recovery plan may need website code, uploaded media, databases, email data, DNS records, SSL configuration, scheduled tasks, and third-party settings. The right backup schedule depends on how frequently each part changes and how much business activity would be lost after an incident.
Start by defining two targets:
- Recovery point objective (RPO): the maximum amount of recent work your business can afford to lose. For example, an RPO of 24 hours means a daily backup may be acceptable; an RPO of one hour requires more frequent capture or another way to preserve changes.
- Recovery time objective (RTO): the target time for restoring essential website functions. This should account for identifying the problem, obtaining the backup, rebuilding the environment, checking DNS, and testing the site.
Hosting backups are helpful, but they should not automatically be treated as a complete disaster recovery plan. Confirm what the host backs up, how long copies are retained, where they are stored, whether databases and email are included, and whether you can download or restore them without assistance. Keep at least one usable copy outside the production hosting account when practical.
For related launch and migration work, use the business website launch checklist and review your business web hosting requirements before selecting a new environment.
Checklist by scenario
Choose a starting backup schedule
| Site type | Suggested starting point | Extra protection to consider |
|---|---|---|
| Simple brochure site with infrequent edits | Weekly automated backups, plus a copy before every significant change | Monthly offline or separate-account copy |
| WordPress or CMS site with regular publishing | Daily files and database backups; more frequent database capture if comments, forms, or orders change often | Pre-update backup and restore test |
| Appointment, membership, or lead-generation site | Daily or more frequent backups based on form and account activity | Export important submissions or customer records according to your retention requirements |
| E-commerce site | Backups timed to order, inventory, and content changes; do not rely only on a daily snapshot | Document payment, shipping, tax, and integration settings separately |
| Frequently updated or high-traffic site | Shorter intervals, with a tested restoration process and a defined recovery team | Staging environment, monitoring, and scalable hosting capacity |
These are planning starting points, not universal rules. If losing a day of orders, bookings, or form submissions would be unacceptable, a daily backup may not meet your RPO. Ask your hosting provider which backup intervals, retention options, and restoration methods are actually available.
Back up the full website environment
- Website files: include application files, themes, plugins, configuration files, custom code, and uploaded media. Do not assume that a database backup contains images or documents.
- Databases: include the database used by the CMS, products, orders, customer accounts, settings, and form entries. Record the database engine and version where relevant.
- Email: determine whether business mailboxes are hosted with the website provider or a separate email service. Website backups often do not include mailbox contents. Confirm the provider's export and retention options.
- DNS: save a current record inventory, including A, AAAA, CNAME, MX, TXT, SPF, DKIM, DMARC, and verification records where used. DNS is configuration, not usually part of a website file backup.
- SSL and access settings: document certificate management, forced HTTPS rules, administrator accounts, SSH or SFTP access, firewall rules, and relevant environment variables. Never store passwords in an unprotected checklist.
- External services: record analytics, payment, forms, email marketing, search, CDN, and API integrations. Note account owners and where keys can be regenerated.
Use a restore checklist
- Choose a low-risk test window and tell the people responsible for the website.
- Select a backup by date and record its file size, source, retention status, and checksum if your tools provide one.
- Restore to staging or a temporary environment, not directly over the live site.
- Recreate the required hosting version, database, runtime, extensions, and environment variables.
- Import the database and website files, then update configuration values for the test environment.
- Open the homepage, key landing pages, navigation, forms, login areas, media, search, and any transaction or booking workflow.
- Check that links, redirects, permissions, scheduled tasks, email notifications, and HTTPS work as expected.
- Record the start and finish times, problems found, missing data, and corrective actions.
- Delete temporary credentials and the test environment when it is no longer needed.
For a recovery-time worksheet, record: incident time; person who declares recovery; backup selected; restoration start; website available; critical workflows verified; DNS changes required; third-party services reconnected; and final approval. The elapsed time between incident and essential service restoration is your observed recovery time. Compare it with your target and adjust the process rather than simply assuming the next restore will be faster.
What to double-check
Before a website update
Take a fresh backup before updating a CMS, theme, plugin, server runtime, or custom integration. Confirm that the backup completed rather than merely being scheduled. If possible, update in staging first and keep the previous version available until the live site passes its checks.
Before changing hosting or DNS
Export website files and databases, lower the risk of missed records by documenting DNS in advance, and keep the old hosting account active until the new site is tested. A domain points visitors to a service; it does not contain the website itself. Review the guide on pointing a domain to a new host and the DNS management checklist before changing records.
Verify the new server can run the application, has enough storage, supports the required database and runtime versions, and can send or connect to the services the site needs. For larger sites, use the hosting scalability planner to compare shared hosting, VPS, and dedicated environments.
After a restore
Check more than the homepage. Submit a test form, confirm that notifications reach the intended mailbox, test administrator access, inspect representative media, verify redirects, and review recent database records. Confirm that the restored SSL configuration works; the SSL certificate setup guide covers common certificate and renewal checks.
Common mistakes
- Keeping every copy in the same account: a compromised hosting account or accidental deletion may affect both the live site and its backups. Separate at least one copy where your risk and budget justify it.
- Backing up only the files: a CMS without its current database may restore an old or unusable site.
- Ignoring email and DNS: a website can load while contact forms, mail delivery, or domain verification fails.
- Never testing restoration: a successful backup job does not prove that the archive is complete or compatible with a new server.
- Using an old backup without checking its date: label copies clearly and define retention so the team knows which versions are available.
- Restoring directly over production: use staging or a temporary destination first, then plan the cutover and rollback.
- Forgetting privacy and access controls: backups may contain customer, employee, or order data. Restrict access, protect downloads, and follow the retention requirements that apply to your business.
When to revisit
Review this website disaster recovery plan twice a year and whenever the workflow or tools change. A scheduled review is useful before seasonal planning cycles, major campaigns, or periods when the business depends heavily on online orders, bookings, or leads.
Run a restore test after a major platform update, hosting migration, domain or DNS change, addition of a new integration, or change in the person responsible for website operations. Recalculate the RPO and RTO when the site begins processing more business activity. A plan that was adequate for a brochure site may not suit an e-commerce or membership site.
For each review, complete this short action list:
- List every system that must be recovered, including website, database, email, DNS, media, and external services.
- Confirm the latest successful backup and the location of an independently stored copy.
- Check retention, storage capacity, access permissions, and backup notifications.
- Restore a recent copy in a non-production environment.
- Measure recovery time and document any missing data or manual steps.
- Update contacts, credentials procedures, vendor details, and rollback instructions.
The goal is not to create the most elaborate backup system. It is to create a repeatable path from “the site has a problem” to “the essential business functions are working again,” with enough evidence that the path works.