Website snapshots and full website backups serve different recovery needs. A snapshot can help restore a hosting environment quickly. An independent backup gives you more control over website files, databases, uploads, configuration, and related records.
Table of Contents
What is the difference between a snapshot and a full backup?
A hosting snapshot is a recovery point held within the hosting environment. It is most useful when the hosting environment needs to return to an earlier state and the required data is available in that recovery point.
A file-and-database backup stores the website files and the database separately or as a coordinated backup. Website files can include application code, themes, plugins, and uploaded content. The database may contain content, settings, orders, customer records, or other application data. A restore is only complete when the files and the related database are compatible.
A complete off-site copy is stored outside the hosting environment. It can include website files, database data, uploads, configuration, and DNS-related records. A downloaded backup can contain website, database, email, or hosting data, so it may also contain sensitive information and must be stored securely. Learn why downloaded backups should be stored securely.
How the recovery methods compare
| Recovery method | Recovery speed | Coverage | Storage and isolation | Restoration flexibility |
|---|---|---|---|---|
| Hosting snapshot | Often the most direct option when the hosting environment and its recovery point are available. | Depends on what the snapshot captured. It may not provide a separate copy of every file, database, upload, configuration item, or DNS-related record. | Remains connected to the hosting environment, so it is less independent than an off-site copy. | Best suited to restoring the captured hosting state rather than selecting individual parts for a different recovery plan. |
| File-and-database backup | Requires the files and database to be restored in a compatible state. | Covers the website files and application data included in the backup. A usable recovery plan also needs application data and database-consistent backups, not only copied files. See the website backup restore testing checklist. | Can be kept separately from the live hosting environment, depending on where it is stored. | Allows a business to work with the website files and database as separate recovery components. |
| Complete off-site copy | May require more recovery steps because the data must be retrieved and rebuilt or restored in the required environment. | Can be planned to include files, databases, uploads, configuration, and DNS-related records in one recovery set. | Stored outside the hosting environment, which gives it greater separation from a hosting outage or an incident affecting that environment. | Provides the broadest basis for rebuilding or moving the website, provided the copy is complete and usable. |
Why recovery coverage matters
Website recovery is more than copying visible pages. A restore test checks whether a backup contains the data the website needs and whether it can be restored when recovery is urgent. Files alone may not recreate the working site if the application data or database is missing. Database consistency also matters because files and database records must work together after the restore. The restore testing checklist covers these recovery requirements.
The incident also affects which recovery source is suitable. Accidental deletion, a website attack, and an email outage can affect different systems. One restore method does not fit every situation, so a business continuity plan should match the backup source to the incident. See the staged recovery example.
Which combination suits each type of business?
Small website
A small site can use a hosting snapshot for a direct recovery of the hosting state and keep an independent copy of its website files and database. The independent copy adds protection if the hosting environment is unavailable or if the site needs to be rebuilt from selected components.
Ecommerce website
An ecommerce site should use more than a file copy. Its recovery set should include database-consistent application data as well as website files and uploads. A hosting snapshot can support a direct recovery, while an independent off-site copy provides a separate source for incidents that affect the hosting environment or require a controlled restore.
Multi-site business
A business with several websites should maintain recovery copies that identify each site’s files, database, uploads, configuration, and related records. Hosting snapshots can support environment-level recovery, while complete off-site copies provide a broader recovery option when several systems or the hosting environment are affected.
Recommended recovery model
Use hosting snapshots for a direct recovery path and independent backups for coverage and separation. Keep the file and database data coordinated, include uploads and configuration in the recovery plan, and include DNS-related records when the goal is to rebuild the complete website setup. Test a restore before an outage so the business can confirm that the backup contains the data required for recovery.