Website Backups: What They Must Include and How to Know a Restore Works
Find out what your website backup contains, where copies are kept, and how a safe restore test can show whether your recovery plan works.

Short answer: You can often recover a broken or hacked website if you have a recent, complete backup and someone knows how to restore it. A scheduled backup alone is not proof: it may omit the database, new uploads, form records, or other services, and no one may have tested that it restores correctly. Treat backups as a recovery plan, not just a folder of files.
What should a website backup cover?
For a typical content-managed site, ask for a matched copy of both the site files and the database. Files can include the site’s software, theme, plugins, custom code, configuration files, and uploaded images or documents. The database may contain pages, posts, settings, and other site data. WordPress’s backup documentation specifically says both files and database are needed to fully restore a typical WordPress site; it also warns that downloading the site directory does not automatically back up the separate database. This is WordPress-specific guidance, but the distinction is a useful question for any platform.
Use this practical checklist to find out what is and is not covered:
| Item | What to confirm |
|---|---|
| Site files and uploads | Are themes, plugins, custom code, settings, images, and downloadable files included? |
| Database | Is the database copied at roughly the same time as the files, so the pair represents one usable version? |
| Form submissions | Are entries stored in the site database, sent to email, or held by a separate form/CRM service? Back up or export each place that stores them. |
| Business email | Email may use the host or a separate provider. Do not assume a website backup includes mailboxes or attachments; confirm how email is retained or exported. |
| Domain and DNS | Keep a record or export of registrar details, renewal date, nameservers, and current DNS (Domain Name System) settings, including records used for email. These settings are not necessarily part of a website backup. |
CISA recommends first inventorying important data and specifically lists email, configuration files, and website databases among business information to protect in its Back Up Business Data guidance. Applying that inventory to a website means checking where each item actually lives. A form plugin that stores entries in the database is different from a hosted form service that keeps them elsewhere.
Where should backup copies live?
Do not assume that a copy stored only in the same hosting account is enough. The Federal Trade Commission (FTC) says to back up important files regularly to cloud storage or an external drive, and its ransomware advice recommends keeping a full environment backup on a drive or server not connected to the network (FTC small-business cybersecurity guidance). CISA’s 3-2-1 backup rule is a practical model: keep three copies, on two types of storage, with one copy off-site. Protect sensitive copies with encryption and keep at least one copy offline or otherwise inaccessible to compromised systems.
Choose the backup schedule based on how quickly important content changes and how much recent data the business could afford to lose. A site that receives frequent orders or inquiries may need more frequent database or submission backups than a mostly static brochure site. Record how long copies are retained and who can access them. CISA’s small-business cyber guidance says to choose a backup cadence and write down a restoration plan.
How do you know a restore works?
Ask the host or developer when a full restore was last tested, not just whether backups are scheduled. CISA’s backup guidance recommends testing both full and partial recovery and documenting the procedures. Our recommendation is to record how long your own test takes. A test should use a separate staging or recovery environment where possible, so it does not overwrite the live site.
During a test, check that:
- The chosen backup can be found, downloaded, and opened, and its date is clear.
- Both the files and matching database restore without errors.
- Important pages load and their images, documents, and other uploads appear.
- A safe test form submission reaches the right destination, and any locally stored submission is present. Avoid creating a real customer order or sending a live payment during a test.
- The restored site can be accessed by an administrator, and the domain, DNS, and email-related settings needed for launch are documented.
A successful file copy is not the same as a working website. Ask how long the tested restore took and what would still need to be changed to put the site back online. That answer helps set realistic recovery expectations.
If the site was hacked
Do not automatically put a possibly infected backup back online. A copy can contain the same vulnerability or malicious code that caused the incident. CISA’s #StopRansomware Guide recommends offline, encrypted backups and warns not to re-infect clean systems during recovery. For a suspected compromise, first involve the host or a qualified security professional to investigate and clean the affected site, then restore from a known-clean copy and address the access or software issue that allowed the incident.
Limits of this advice
The exact backup contents and restore steps depend on the site platform, host, form tools, and email provider. This checklist is general guidance, not a security assessment or a guarantee that every piece of data can be recovered. Ask your host and developer who is responsible for backups and restore testing. The website ownership checklist can help you organize the accounts involved.
Evidence
Sources
- Backups – Advanced Administration HandbookWordPress · Retrieved
- Back Up Business DataCISA · Retrieved
- Cybersecurity for Small BusinessFederal Trade Commission · Retrieved
- Cyber Guidance for Small BusinessesCISA · Retrieved
- #StopRansomware GuideCISA · Retrieved
A useful next step
Keep a useful record
Use the ownership checklist to organize the accounts and people involved in your site.
Open the ownership checklist