Smart Web Support logo Smart Web SupportPlain answers for keeping a small business website running
Security and Backups

How to Test a Website Backup by Actually Restoring It

A tailoring shop called me on a Saturday because their site was showing a blank white page and their host had suspended the account for sending spam. Standard job, I thought.

A laptop showing a restored test copy of a shop website beside an external drive holding backup archives

A tailoring shop called me on a Saturday because their site was showing a blank white page and their host had suspended the account for sending spam. Standard job, I thought. They had daily backups included with hosting, the owner had the control panel login, and I expected to be done before lunch. The backups went back seven days. The malware had been sitting in the site for at least three weeks, so every one of those seven copies was infected. The clean copy we eventually used was a zip file on the previous developer's laptop, dated fourteen months earlier.

That shop lost about a year of product photos and every page they had added since. Not because nobody made backups, but because nobody had ever opened one. I have cleaned up enough of these to say the pattern plainly: the question is never whether a backup exists. It is whether anyone has restored it, on purpose, when nothing was on fire.

The three ways a backup quietly fails

Backups do not usually fail by not existing. They fail in ways you cannot see from a list of filenames.

The first is incompleteness. A plugin set to back up files but not the database gives you a site with no pages, no posts, no settings and no orders. The reverse happens too, a database export with no uploads folder, which produces a site where every image is a broken icon. I see this split more often than any other fault, usually because someone changed a setting during a storage squeeze and never changed it back.

The second is corruption. A nightly job that times out at 60 or 120 seconds on a shared plan writes a truncated archive, and the plugin still ticks it green because the job started fine. You find out when the unzip stops at 78 percent. Any site with an uploads folder past roughly 1.5 GB on cheap shared hosting should be treated as suspect until proven otherwise.

The third is contamination, which is what caught the tailor. Backups taken after an intrusion are backups of an intrusion. Short retention windows make this worse, because the only copies you hold are from the compromised period. Seven days of retention protects you against a bad plugin update. It does nothing against malware that sat quietly for a month harvesting logins, which is the normal timeline.

The restore drill, start to finish

Here is the exercise I run for clients once a quarter. It takes under two hours on a small business site and needs no special tools. Pick a weekday morning, not a Friday afternoon.

Create a subdomain on the same hosting account, something like test followed by your own domain, and point it at an empty folder. Add a password at the server level so visitors and search engines never see it. Download your most recent backup to your own machine first, which matters because you are testing whether you can get the file out, not just whether it sits in a dashboard.

Unzip it locally and look at what you actually have before uploading anything. You want a database file, normally with a .sql extension, and a folder tree containing wp-content with uploads, themes and plugins inside it. Check the size of the database file. A real small business site database is rarely under 2 MB, and if yours is 400 KB, you are holding an export that stopped early.

Then restore into the test subdomain: upload the files, create a fresh empty database, import the .sql, and edit wp-config.php to point at the new database name and user. Set the site address in the database or let a migration plugin rewrite it. If you have ever moved a site before, this is the same work in a smaller box, and the order is the same one described in moving a site to a new host without downtime.

Now the part people skip. Click around as a visitor and as an administrator, and write down what is wrong.

Check on the restored copyWhat a pass looks likeWhat it usually means when it fails
Homepage and three inner pages loadNo white screen, no PHP warnings at the topTruncated database import, or a missing plugin folder
Images on an older postPhotos visible, not broken iconsThe uploads folder was excluded from the backup
Contact form sendsA test message arrivesMail settings live outside the backup, which is normal and worth noting
Admin login with the real passwordYou reach the dashboardThe users table did not import, or the password hash predates a reset
Newest post or product presentSomething from the last 48 hours appearsThe job has been failing silently for weeks
Total time from download to working siteUnder two hoursYour real recovery time is a full day, and you should plan for that

That last row is the whole point of the drill. Most owners assume recovery takes twenty minutes. Measure it once and you will know the real number, and you can stop promising customers an hour when the truth is Monday afternoon.

Your host's backups are not a plan, and the plugin alone is not either

The advice you hear is that hosting includes backups, so you are covered. I want to push back on that harder than most people in my trade will, because it sells a comfortable idea.

Host snapshots live on the same account you are trying to recover from. When an account is suspended for sending spam, as the tailor's was, you may lose access to the control panel that holds the snapshots at exactly the moment you need them. I have had to email support and wait eleven hours for a copy of a backup that was technically mine the whole time. Billing problems create the same situation, and so does a hacked registrar.

The other half of the comfortable idea is that a backup plugin solves it. Plugins fail in the opposite direction: they run inside the site, so a site too broken to load is a site whose backup plugin cannot run either. A plugin writing to a remote storage bucket is genuinely good. A plugin writing to a folder inside wp-content is a second copy of the thing you already have.

What I run for clients is dull and cheap. The host's nightly snapshot stays on, because it is free and convenient for small mistakes. A plugin pushes a weekly full copy to object storage that costs around 6 dollars per terabyte per month, which for a 3 GB site is pennies. And once a month I download one archive to a local drive and keep the last three. Three copies in three places, one of them somewhere nobody can suspend. If you want the longer argument for that third copy, I made it in the case for offsite backups.

Retention is the setting nobody changes

Default retention on cheap hosting is commonly seven days. Paid extensions to 30 days often cost 3 to 5 dollars a month, which is the best value in this entire article. Malware dwell time on small business sites runs to weeks, and the specific attack I see most, a fake plugin folder dropped through a vulnerable form and left alone until it is needed, is designed to be patient.

Keep daily copies for 30 days, then one weekly copy going back three months. That is roughly 42 restore points and it costs very little in storage because the weekly copies deduplicate well. On the survival games I play at weekends I keep a save from before every big expedition, for exactly the same reason: the useful copy is the one from before you knew anything was wrong.

FAQ

How often should I actually test a restore?

Once a quarter for a normal small business site, and once after any big change: a new host, a new theme, a migration, or a change to the backup settings. Testing the day after you change the setting is what catches the file and database split described above.

Can I test without paying for a staging site?

Yes. A password protected subdomain on the same account works, and so does restoring onto your own computer with a local development tool. Local is slightly better because it proves you can rebuild the site even with the hosting account gone.

What never ends up in the backup?

DNS records, email accounts and anything stored at your registrar. Those live outside the website and a restore will not bring them back. Keep a written record of your DNS entries with your backups, because retyping them from memory during an outage is miserable.

After a hack, should I keep the infected copy?

Keep one, offline and clearly labelled. It is the only evidence of how the attacker got in, and it sometimes holds content created after your last clean backup that you can lift out by hand once the files have been checked.

AI
Adaeze Ilori

Adaeze cleans up hacked small business sites for a living and plays survival games on weekends, which may explain why she keeps three copies of everything.

More posts by Adaeze

More from the blog

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto ankertoto