What to Include in a Backup
What a Complete Website Backup Contains
What to include in website backup is everything needed to rebuild the site exactly as it was. That means the site's files, its database and the settings that connect the site to the rest of the internet.
A file-only copy looks complete but often is not. Themes, code and uploads may be present, while the content that visitors actually see sits in the database, which is missing. The result is a site that loads but has lost its posts, orders or customer accounts.
The reasons for keeping a copy at all are covered in what a website backup is and why you need one.
The Parts of a Complete Restore Set
A restore set is the group of copies you need to rebuild a site. A complete set usually includes the following parts.
- Site files. Application code, themes, plugins, and uploaded images and documents. Uploads are often the largest part and the easiest to forget.
- Databases. Posts, pages, products, customer accounts, orders and form submissions. Most dynamic sites keep their content here, and database backups need their own care to stay consistent.
- Email. Mailboxes and mail settings, if your host runs email for the domain. Email is separate from the website files, so a site backup alone does not preserve it.
- Configuration. Server and application settings, including the configuration files that hold database connection details, and the scheduled tasks that send newsletters or clean up old data.
- DNS records. The entries that point your domain name to the server, including mail and verification records. Losing them can make a site unreachable even when its files are intact.
- SSL certificates. The certificates and private keys that secure HTTPS. Without them, visitors may see security warnings after a restore.
Why a File-Only Restore Failed
A developer restores a client's website from a backup of its files. The theme and images return, but the shop shows no products and no one can log in. The database that held those records was never copied.
The developer then searches for an older export and finds that the domain still points to the old server. Only after the database and DNS records are restored does the site work again. A complete restore set would have avoided the delay.
Frequently asked questions
Is a Database Backup Enough for a Website?
No. The database holds the content, but the files hold the code, themes and uploaded images. Without the files, the database has nothing to run on and the uploads are lost. Back up both together, so the files and database match each other after a restore.
Should Email Be Included in a Website Backup?
It depends on where your email is stored. If your host runs mailboxes for your domain, a website backup usually does not include them, so check whether email is covered by a separate backup. If it is not, you need to copy the mailboxes yourself or arrange a separate copy with your provider.