OOmnistu

Blog / Security

Security

Website backups for small sites: what to copy, how often, and how to test a restore

Check what your host's backup terms actually promise. What a real backup covers, how the 3-2-1 rule maps to a small website, and why only a tested restore counts.

OOmnistu
Reviewed 2026-11-20 · 5 min read

A bad plugin update, a deleted folder, a hacked account, a hosting failure: most small websites are one ordinary accident away from losing content that took months to build. A backup is a secure copy of your data stored separately from your primary systems, as the US Cybersecurity and Infrastructure Security Agency (CISA) puts it - and the restore is the part that actually saves you. This guide covers what to copy, how often, and how to prove a restore works, grounded in CISA's small-business guidance and WordPress's own documentation.

What to copy

A website is usually two things, and you need both. The database holds your content: WordPress's documentation notes it contains every post, every comment and every link on the site. The files hold everything else: themes, plugins, uploads like images and documents, and configuration. Restoring only the files gives you an empty shell; restoring only the database gives you content with no way to display it. Add anything configured outside the site itself that you would struggle to rebuild, such as email routing or third-party service settings, to a written list so a rebuild does not depend on memory.

"My host already does backups"

Maybe, but read what the terms actually promise. As one concrete example, the backup section of Hostinger's hosting agreement for its shared, VPS and reseller accounts (checked 2026-11-20) states that customers are solely responsible for maintaining independent backup copies, describes the service as a courtesy that may be modified at any time, runs it weekly with about two weeks of backups retained, and excludes cPanel shared hosting accounts using more than 30 GB of disk space from its off-site weekly backup. Other providers word it differently, and some managed plans include more; the point is not that host backups are useless but that their scope, retention and guarantees live in your provider's terms, not in assumptions. There is also a structural gap: a backup stored inside the same hosting account can be deleted or encrypted by whoever or whatever compromises that account. CISA's definition requires the copy to be stored separately from your primary systems, so keep at least one copy somewhere independent.

How often

The right frequency is the answer to one question: how much work can you afford to redo? If your site changes weekly, a week of lost changes may be tolerable; if you take orders or publish daily, it is not. WordPress's documentation suggests weekly backups for smaller websites with fewer posts, and - whatever your schedule - backing up before every upgrade, since updates are a common moment for things to break. CISA frames the same idea with two planning terms: a recovery point objective (how much data loss you can accept) and a recovery time objective (how long you can be down). Pick yours from how your site actually changes, not from a default someone else set.

The 3-2-1 rule, mapped to a small site

The guideline most backup advice converges on is 3-2-1: keep three copies of important data, on two different types of storage, with one copy off-site. CISA recommends it for small businesses; Backblaze, a backup vendor, has promoted the rule since the late 2000s. For a small website this can stay simple:

Whatever the mechanism, choose something that runs automatically on a schedule, as CISA advises; a backup that depends on remembering tends to stop happening quietly.

The restore is the backup

A backup you have never restored is a hope, not a plan. CISA recommends testing backup procedures so you can restore data both fully and partially, and being able to roll back at least seven days when needed. For a small site, a practical test is restoring to a staging copy or a local environment - somewhere separate from the live site, never over it - and clicking through: do pages render, do images load, does the contact form still work? Put the test on a calendar - quarterly is one reasonable rhythm to start from - and treat a failed test as a broken backup to fix, not a nuisance. Recovery without backups, CISA warns, can take weeks or months, and may be impossible.

FAQ

Is my host's backup enough?

It depends on the terms of your plan, which vary by provider: some retain copies for days, others for weeks, and responsibilities differ. As one example, the backup section of Hostinger's hosting agreement for its shared, VPS and reseller accounts (checked 2026-11-20) calls the service a courtesy and makes the customer solely responsible for independent copies. Read your own provider's terms, and keep at least one backup outside the hosting account either way.

How long should I keep backups?

Long enough that a problem discovered late can still be undone. CISA recommends being able to roll back at least seven days. If you update the site in batches or notice issues slowly, keeping a few older points - for example several weekly snapshots - costs little for a small site and covers slow-burning breakage.

Do backups protect against ransomware?

They are the main recovery route, not a guarantee. CISA cites Verizon's 2025 Data Breach Investigations Report finding that ransomware figured into 44% of the breaches it investigated, and calls backups your best hope of recovery from a ransomware attack - while also recommending offline copies and encryption, because backups reachable from a compromised system can be encrypted or deleted along with it.

Where should the off-site copy live?

Somewhere with a different login and a different failure domain than your hosting: a cloud storage service or your own computer both qualify. Protect the account with a strong password and two-factor authentication, and encrypt the archives if they contain customer or business data - a backup is a copy of everything sensitive on your site.