Website Backup and Restore Checklist: How to Protect and Recover a Site
website backupsrestore processWordPresshostingdisaster recoverywebsite security

Website Backup and Restore Checklist: How to Protect and Recover a Site

HHelps Website Editorial Team
2026-11-10
6 min read

Use this website backup and restore checklist to protect files, databases, and DNS details, test recovery, and review your plan regularly.

A reliable website backup is more than a file saved somewhere: it is a recoverable copy of your files, database, configuration, and supporting records. This website backup and restore checklist explains what to protect, how to apply a practical 3-2-1 backup strategy, how to test restoration safely, and when to review your recovery process.

Overview

Website owners often discover a backup problem only after an update fails, a server becomes unavailable, a domain is moved incorrectly, or malicious code changes important files. A backup can reduce recovery time, but only if it is recent, complete, accessible, and separated from the original site.

The goal is not to create the largest possible archive. The goal is to maintain a documented recovery path that someone can follow under pressure. Before choosing a tool, identify what your site needs to operate:

  • Site files: themes, plugins, uploads, images, scripts, configuration files, and custom code.
  • Database: posts, pages, users, orders, settings, comments, and other changing records.
  • Environment details: hosting account, PHP or runtime requirements, server settings, scheduled jobs, and deployment notes.
  • Domain and DNS information: registrar access, DNS records, email-related records, and nameserver details.
  • Credentials and keys: store these securely and separately from an ordinary website archive.

A WordPress backup and restore plan should include both the WordPress files and its database. A static site may need fewer moving parts, but its repository, build instructions, deployment settings, and domain configuration still matter. For broader setup context, review the website-building guide and the DNS records guide.

What to track

Keep a simple backup register. It can be a protected document or an internal operations page. Record the following for every backup method:

  • Backup type and scope: full site, files only, database only, or configuration export.
  • Creation date and time, including the time zone.
  • Storage location and whether it is separate from the hosting account.
  • Retention period and the number of usable recovery points.
  • Encryption and access controls.
  • Whether the backup has been restored successfully in a test environment.
  • Who can start or approve a restoration.
  • Any dependencies, such as a required hosting plan, plugin, database version, or server setting.

Use this comparison when reviewing your coverage:

Backup sourceUseful forLimitations to check
Hosting backupsFast recovery within the same hosting platformRetention, access during an outage, and whether files and databases are both included
WordPress backup toolScheduled copies managed from the WordPress dashboardStorage limits, performance impact, plugin compatibility, and restore requirements
Database exportRecovering changing content and settingsDoes not restore uploaded files, themes, plugins, or server configuration
Off-site copyProtection if the hosting account or server is unavailableAccess permissions, encryption, retention, and whether the archive can be downloaded
Repository or deployment archiveTracking custom code and repeatable deploymentsMay exclude user uploads, database records, secrets, or production configuration

Apply the 3-2-1 website backup strategy as a planning rule: keep at least three copies, use at least two different storage locations or media, and keep at least one copy off-site. Adapt the arrangement to your site, risk level, and operational resources. Do not treat a synchronized folder as an independent backup unless older versions and deletion recovery are available.

Cadence and checkpoints

Choose frequency according to how quickly your site changes and how much data you could recreate. A site with frequent orders, registrations, or publishing activity needs more frequent database protection than a rarely updated brochure site. Schedule backups before major updates and migrations, but do not rely only on pre-update copies.

Before a planned change

  1. Confirm that the latest backup completed rather than assuming a scheduled job ran.
  2. Check its size, timestamp, and storage location.
  3. Make an additional backup when the change is high risk, such as a core update, theme replacement, database migration, or hosting move.
  4. Write down the intended change and the rollback point.

Monthly or quarterly review

  • Restore a recent copy to a private staging site or isolated local environment.
  • Open key pages and test login, forms, media, search, and important transactions without using real customer actions.
  • Confirm that uploads, permalinks, redirects, scheduled tasks, and database content are present.
  • Verify that off-site copies can be accessed by an authorized person.
  • Review storage usage, retention settings, failed jobs, and administrator access.
  • Update recovery notes if hosting dashboard labels, plugin steps, storage limits, or server requirements have changed.

Keep production restoration separate from testing. A test restore should use a temporary URL, blocked indexing, restricted access, and scrubbed or carefully controlled data where appropriate. Never overwrite the live site simply to find out whether an archive works.

How to interpret changes

A successful backup job is a useful signal, not proof that recovery will work. Investigate changes in the following way:

  • Backup size suddenly drops: check whether uploads, database tables, or excluded directories were removed from the backup scope.
  • Backup size grows quickly: look for large log files, cache directories, temporary files, or unexpected uploads. Confirm that the storage destination still has capacity.
  • Jobs begin failing: check credentials, quotas, timeouts, connection settings, and recent hosting or plugin changes.
  • The archive restores but the site is broken: compare runtime versions, database credentials, file permissions, rewrite rules, environment variables, and external service settings.
  • Only old restore points remain: review retention and schedule settings. A backup that is too old may not meet your recovery needs.

Use a simple recovery decision tree. If the site is available but a recent change caused the problem, roll back the affected component or restore to a staging copy first. If the site is unavailable but hosting access works, check the host’s recovery options while retaining an independent off-site copy. If the hosting account is inaccessible, use the off-site archive and documented domain, DNS, and deployment information. If you suspect compromised files, preserve evidence, restrict access, and avoid restoring unverified files over the original environment.

For WordPress specifically, do not assume that reinstalling WordPress restores content. Confirm that the database, uploads directory, active theme, plugins, configuration, and site URL settings are consistent. Pair backup reviews with the broader WordPress maintenance checklist.

When to revisit

Revisit this website restore checklist on a monthly or quarterly cadence, depending on how frequently the site changes and how critical its data is. Also review it immediately after any of these events:

  • A hosting, domain, or DNS change.
  • A migration, redesign, or deployment workflow change.
  • A WordPress core, theme, plugin, runtime, or database update.
  • A change to storage, retention, administrator access, or security controls.
  • A failed backup notification or unexplained archive-size change.
  • A security incident, unexpected outage, or failed restore test.
  • A change in the people responsible for recovery.

End each review with three concrete actions: confirm the next scheduled backup, record the location of the latest verified restore point, and assign an owner for the next restore test. If the answer to any of these is unclear, the recovery plan is not finished. Keep a short recovery runbook with the hosting account, domain registrar, DNS provider, backup locations, staging instructions, and escalation contacts. During a real outage, clear documentation is as important as the archive itself.

For related operational checks, see the website troubleshooting checklist, the domain transfer checklist, and the monthly WordPress maintenance guide.

Related Topics

#website backups#restore process#WordPress#hosting#disaster recovery#website security
H

Helps Website Editorial Team

Senior SEO Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.