Website Backup Plan for Small Business NZ: Your Disaster Recovery Guide
- Bright Box
- September 28, 2026
- Business
- 0 Comments
Most New Zealand small business owners treat their website backup plan as a tick-box: install a plugin, forget about it, move on. That is not a working website backup plan for small business, it is a false sense of security. A proper plan tells you exactly how much of your site you could lose, how long you could realistically be offline, and what to do in the first hour something breaks. This guide covers all three, with a schedule you can copy today.
What a website backup actually needs to cover
A screenshot of your homepage is not a backup. A real website backup has two parts: the files (theme, plugins, images, uploads) and the database (every page, post, product and form entry). Most free backup plugins only grab the files by default, which is why a “restore” often comes back with the design intact but the content from six months ago. Before you trust any backup, check it actually captures both.
If your site takes payments, bookings or enquiries, add a third layer: anything stored outside WordPress itself, such as a booking calendar, payment gateway records or an email marketing list. These often live on a different platform entirely, so your website backup will not touch them.
How much downtime and data loss your business can actually afford
Two questions decide the shape of your website disaster recovery plan, and neither is technical.
- How long can you be offline before it costs you real money or trust? An hour, a day, a week. This is your recovery time.
- How much recent content or data could you stand to lose? The last form submission, the last week of blog posts, the last month of product changes. This is your recovery point.
A brochure site for a tradie can usually absorb a day of downtime and a week of lost content without much damage. A booking site for a clinic or salon cannot; every hour offline is missed appointments, and every lost form is a lead you never call back. The real website downtime cost is rarely the hosting bill, it is the bookings, sales and enquiries missed while the site is unreachable. Decide where your site sits on that scale before you pick a backup schedule, not after something goes wrong.
The 3-2-1 rule, simplified for a website
The 3-2-1 backup rule is standard advice for any business, and it adapts well to a website: three copies of your data, on two different types of storage, with one copy kept somewhere other than your live server.
- Copy one: the live site itself.
- Copy two: an automated backup stored with your hosting provider or backup plugin, separate from the live files.
- Copy three: a copy stored off-site, such as cloud storage or a download kept somewhere else entirely.
The point of the third copy is simple: if your host has an outage, gets hacked, or a server fails, your backup should not fail with it. A backup stored in the same place as the site it protects is not really a backup.
How often should you back up your website
There is no single right answer, it depends on how often your site changes and how much a lost day of content would cost you. As a starting point for NZ small businesses:
| Site type | Backup frequency | Why |
|---|---|---|
| Static brochure site (rarely updated) | Weekly | Little changes between backups, so daily is overkill |
| Blog or content-driven site | Daily | New posts and pages are added often and are costly to redo |
| Booking or enquiry-based site | Daily, or real-time database backup | Lost form submissions mean lost leads |
| Ecommerce store | Real-time or multiple times daily | Orders, stock levels and customer data change constantly |
Rule of thumb: if redoing a day’s worth of changes would take you more than an hour, you need daily backups at minimum. If it would take more than ten minutes, you likely need real-time or near-real-time backups instead.
The step nobody tests: restoring your backup
A backup you have never restored is a guess, not a plan. Backup jobs fail silently more often than business owners expect: a plugin update breaks the schedule, storage fills up, or a database export gets corrupted, and nobody notices until the day it matters. Twice a year, ask whoever manages your site to actually restore a backup to a test environment and confirm the site works. It takes half an hour and it is the only way to know your plan is real.
What to do in the first hour your website goes down
Downtime is stressful, and stress is when people make the situation worse by guessing. Work through this order instead.
- Confirm it is actually down, not just down for you. Use a second device on a different network, or a free “is it down” checking tool.
- Check your host’s status page for a known outage before touching anything yourself.
- Do not make changes while troubleshooting. Every edit during an incident makes it harder to know what caused it and complicates a restore.
- Contact your host or developer with the exact time it went down and what, if anything, changed recently (a plugin update, a new form, a theme change).
- Only restore from backup once the cause is understood. Restoring blind can wipe out the evidence of what actually broke.
- After it is fixed, write down what happened. A one-paragraph note saves you from repeating the same recovery process from scratch next time.
Who should own your backups: you, your host, or your agency
This is the question that causes the most damage, because most small business owners assume someone else has it covered. Your hosting provider may offer backups as a paid extra, a basic default, or not at all, and it is worth checking which one applies to your plan rather than assuming. If you pay for ongoing website maintenance, confirm in writing that backups, and restore testing, are actually included, not just implied. And regardless of who runs the backup day to day, make sure you personally know where a copy lives and who can access it. That question sits alongside the broader issue of who actually owns your website in the first place, since a backup is worth nothing if you cannot get to it when your agency or host relationship ends.
The same discipline applies if your site is ever compromised rather than just offline. A tested backup is also your fastest way back from being hacked, which is a separate risk to plan for alongside simple downtime.
FAQ
How much does a website backup service cost in NZ?
Entry-level backup plans through NZ hosts and agencies typically start around fifty dollars a month, often bundled into a broader care or maintenance plan. Real-time backups for ecommerce sites cost more, reflecting the higher frequency and storage involved.
Can I just rely on my hosting provider’s backups?
Only if you have confirmed they exist, how often they run, how long they are kept, and that you can actually request a restore. Many budget hosting plans include no backup at all, or keep only a few days of history.
What is the difference between a website backup and website security?
A backup protects you from data loss, whatever the cause, whether that is a failed update, human error, or a hack. Security measures try to prevent the incident happening in the first place. You need both, since no security setup is guaranteed to stop everything.
How long should I keep old backups?
Most small business sites are well served by keeping at least the last thirty days, with a handful of older monthly copies kept longer in case an issue is not noticed straight away.
Want results like these for your business?
We are a full-service digital marketing agency based in Auckland. No lock-in contracts. No generic templates. Just clear strategy and results that matter.
Request a Free QuoteWe will tell you exactly what we would do and what it will cost.
