ENHEIT

payless.host

How website backups work, and how to test yours

Updated Nov 22, 2026

What a backup actually is

A backup is a copy of your site's files and database, stored separately from the live version. If something breaks — a bad update, a hack, accidental deletion — you restore from that copy. The backup is only useful if it can be restored, which means testing it is not optional.

Most hosting plans include automated backups. What they back up, how often, and how long they keep copies varies. Some providers back up files but not databases, or keep copies for seven days rather than thirty. Read your plan's backup policy before assuming it covers what you need.

Step 1: Find out what gets backed up

Log into your hosting control panel and locate the backup section. Check three things: what is included in each backup, how often backups run, and how many copies are kept.

Files and databases are backed up separately in most systems. A complete backup includes both. If your plan only backs up files, your database — which holds posts, settings, user data — is not protected. DreamHost's Web Hosting Launch plan includes automated backups, but the scope varies by plan tier.

Backup frequency matters less than retention. Daily backups kept for three days means you have three restore points. Weekly backups kept for a month means you have four. If a problem goes unnoticed for a week, the daily system may have already overwritten every good copy.

Step 2: Trigger a manual backup

Most control panels let you create a backup on demand. Do this now, before testing a restore. Automated backups run on a schedule; a manual backup gives you a known restore point created today.

In cPanel, this is under "Backup" or "Backup Wizard". In custom panels, look for "Create Backup" or "Download Backup". The process generates a compressed archive of your files and a separate database export. Depending on your site's size, this takes anywhere from seconds to an hour.

Download the backup to your own computer once it completes. This gives you a copy outside your hosting account, which matters if the account itself becomes inaccessible.

Step 3: Restore to a test location

Never test a restore by overwriting your live site. Create a subdomain or staging area first — most control panels include a staging tool, or you can manually create a subdomain like `test.yoursite.com`.

Upload the backup files to the test location and import the database using phpMyAdmin or your panel's database tools. Update the site's configuration file to point at the test database and the new URL. For WordPress, this means editing `wp-config.php` and running a search-replace on the database to swap the old URL for the new one.

Load the test site in a browser. If it displays correctly, the backup worked. If you see database connection errors, the configuration file is pointing at the wrong database. If pages load but images are missing, the file backup was incomplete.

Step 4: Check what actually restored

A site that loads is not the same as a complete restore. Log into the test site's admin area and check recent content. If your last post was written yesterday but the test site only shows content from last week, the backup is a week old — which may or may not match the schedule you thought you had.

Check uploaded media, especially recent files. Navigate to a page that uses a form or a plugin with its own data. Open a few database tables in phpMyAdmin and compare row counts between the live and test databases. You are looking for gaps.

What can go wrong

The backup exists but cannot be restored. Corrupt archives, incomplete database exports, and missing file permissions all produce backups that fail during restore. The only way to know is to test.

The backup is older than you thought. Automated systems fail silently. A provider may claim daily backups while the last successful run was three weeks ago. Testing reveals this.

The database backup is missing or partial. File backups run separately from database exports. One can succeed while the other fails, leaving you with half a site.

The backup does not include email. Email is often excluded from hosting backups entirely. If you rely on email hosted with your site, that needs a separate backup plan.

How often to test

Test a restore when you first set up hosting, then every three months. Also test after any major change — a new plugin, a theme update, a server migration — because those are when backup systems break.

If your provider offers one-click restores, test that feature rather than doing manual restores. HostGator includes automated backups across its shared plans, with restore tools in the control panel. A one-click restore that has never been tested is a promise, not a backup.

A backup you have not restored is a backup you do not have.

The providers in this article