Website Backups: What “We Have Backups” Should Mean

Posted October 14th, 2026 under Hosting, security & maintenance

IT technician connecting a network cable in a server rack — website backups start with knowing exactly where your data lives

Ask a small business owner whether they have website backups and nearly everyone says yes. Ask when they last restored one to check it actually works, and the room goes quiet. Patchstack logged 11,334 new WordPress vulnerabilities in 2025 alone — 91% of them in plugins, with mass exploitation beginning a median of five hours after disclosure. A hacked or broken site without a backup you have actually tested isn’t a backup plan. It’s a hope.

What does “we have backups” actually mean?

Most hosting plans include some kind of backup, but “included” hides a lot of variation. Many budget shared-hosting snapshots live on the same server as the site itself, are kept for as little as seven days, and have never been restored by anyone to confirm they actually work. A files-only backup — just the uploads folder, no database — restores an empty shell of a site. A database-only backup loses every image and the theme along with it. Website backups only count as a real safety net when they capture the whole site, files and database together, stored somewhere a server failure can’t reach.

How often should your website backups actually run?

The honest answer depends on how fast your content changes, not a fixed number. The baseline most backup specialists recommend: back up daily at minimum, and trigger an extra backup before any core, theme or plugin update — updates are exactly when something tends to break. An active WooCommerce store needs more than that: back up hourly, or on every order, because a daily backup can lose a full day of sales if something goes wrong at 4pm on a Saturday. A rarely-touched brochure site can stretch to weekly, plus a manual snapshot before any change.

Why a backup you’ve never restored is just a guess

A backup job can report success while the archive underneath it is actually truncated, the database dump is inconsistent, or a timeout quietly stopped the process halfway through — and nobody finds out until the day it matters most. As backup specialists put it, a backup you have never restored is a guess, not a safety net. The fix is a quarterly restore drill: pull the backup onto a separate staging copy, never over the live site, and confirm the site actually comes back. It takes about half an hour and tells you your real recovery time, instead of an assumed one.

Technician’s hand working on cables inside a server cabinet in a data center

What a real backup plan needs: the 3-2-1 rule

Security specialists summarize solid website backups with the 3-2-1 rule, and it holds up well for a small business site:

  • Three copies of your data. The live site counts as one. A local or host-side backup is the second. A third copy kept somewhere entirely separate is what actually protects you.
  • Two different storage locations. A backup saved to the same server as the site fails together with that server — that is not a backup, it is a second file in the same building.
  • One copy off-site. Your own cloud storage — Google Drive, Dropbox, Amazon S3 — kept independent of your host. It is the one copy that survives a server failure, a billing dispute, a suspended account, or switching hosts altogether.

Skipping the tested, off-site part doesn’t just risk losing content — it raises the price of recovering from anything that does go wrong. Cleaning malware off a small business site typically runs $300 to $1,500, climbing higher for an infection left to run for months; a deep or backdoor infection on an online store commonly runs $1,200 to $2,500 or more. Keep backups for at least 30 days, and 60 to 90 days for a store — malware and corruption can sit unnoticed for days, so a short retention window may hold nothing but infected copies.

What this means for a small business on Aruba

Most small businesses on Aruba run on a shared hosting plan, often sold with “daily backups” listed as a bullet point in the package. Before trusting that bullet point, ask the host directly: where is the backup stored, how long is it kept, and has anyone actually tested a restore from it? A webshop taking payments from tourists loses real sales for every hour it sits down, and a site built across English, Spanish, Dutch and Papiamento takes real time and cost to rebuild from scratch if the only copy disappears along with the server. A tested, off-site backup is one of the cheapest insurance policies a small business website can have. Read more on what actually breaks when nobody is watching.

Small business owner handwriting a checklist in a notebook over coffee

A website backups checklist you can run this week

  • Find out who is actually backing up your site. Your host’s automatic snapshot, a plugin you installed, or — more often than owners expect — nobody at all.
  • Check where the backup is stored. Same server as the site is a risk; a separate off-site location is what actually protects you.
  • Check how long backups are kept. At least 30 days, 60 to 90 for a store, so a slow-developing problem doesn’t outlast your retention window.
  • Run one test restore this quarter. To a staging copy, never over the live site, and time how long it actually takes.
  • Back up before every update. Core, theme and plugin updates are the single most common moment something breaks.

Talk to 139 Design Studio about a WordPress or WooCommerce maintenance plan that includes tested, off-site backups alongside core updates, security monitoring and speed optimization — handled end to end, so you’re never the one finding out a backup didn’t work.

Sources: Patchstack — State of WordPress Security in 2026 · G7Cloud — WordPress Backup Strategy Guide · Jetpack — How Often Should You Back Up Your Site? · Cloud House Technologies — Malware Removal Service Cost 2026