Data Backup and Recovery for Small Businesses: The 3-2-1 Rule, Done Properly

By the Cehpoint teamPublished 7 min read

Short answer: Good data backup and recovery for a small business means three copies of important data, on two kinds of storage, with one off-site and at least one offline or immutable so ransomware cannot reach it. Most backups fail because they are never restored, so run a timed restore drill every month and record the result.

Ask most small business owners in India whether they have backups and the answer is yes. Ask when they last restored a full day's work from that backup, timed it, and checked the files opened correctly, and the room goes quiet. A backup that has never been restored is a hope, not a plan.

This guide explains the 3-2-1 rule, why typical SME backups fail exactly when they are needed, and a monthly restore drill that an office manager can run without an IT team.

What is the 3-2-1 backup rule?

The rule is simple and has been standard practice for years:

  • 3 copies of your important data: the live copy plus two backups.
  • 2 different types of storage, for example a NAS in the office and cloud object storage, so one failure mode cannot take both.
  • 1 copy off-site, physically away from your office, so fire, flood or theft does not destroy everything.

Since ransomware became the main threat to small businesses, many practitioners add one more condition: at least one copy must be offline or immutable, meaning a computer on your network cannot change or delete it. Some call this 3-2-1-1-0, where the final zero means zero errors in restore testing.

Why do most small business backups fail when needed?

The failure is rarely the backup software itself. It is usually the setup around it. The common patterns:

1. The backup sits on the same network as the ransomware

A USB drive permanently plugged into the accounts PC, or a NAS mapped as a drive letter on every computer, will be encrypted along with everything else. CISA's ransomware guide states plainly that many ransomware variants try to find and delete or encrypt accessible backups, and recommends maintaining offline, encrypted backups of critical data.

2. Nobody has ever tested a restore

Backup jobs report "success" while silently skipping open files, a renamed folder, or the Tally data directory that moved last year. CISA also recommends regularly testing the availability and integrity of backups in a disaster-recovery scenario. The only proof a backup works is a restore.

3. Only files are backed up, not systems

You have the documents but not the configured accounting server, the licence files, or the email settings. Rebuilding from scratch takes days. CISA suggests keeping "golden images" of critical systems so they can be rebuilt quickly.

4. Cloud sync is mistaken for backup

Google Drive, OneDrive or Dropbox sync is useful, but it syncs deletions and encryption too. If ransomware encrypts the local folder, sync dutifully uploads the encrypted versions. Version history can help, but it has limits and must be checked, not assumed.

5. The backup credentials are the same as everything else

If the attacker gets the admin password, and the backup console uses that same password, the backups are gone before the ransom note appears.

What should a small business actually back up?

DataWhere it usually livesHow oftenNotes
Accounting data (Tally, Busy, ERP)Accounts PC or serverDaily, plus before year-endBack up the data folder and the company configuration
Shared documentsNAS, file server, shared foldersDailyKeep at least 30 days of versions
EmailGoogle Workspace or Microsoft 365DailyProvider retention is not the same as your own backup
Website and databaseHosting serverDaily database, weekly filesStore copies outside the hosting account
CRM / SaaS dataVendor cloudWeekly exportCheck the export actually includes attachments
Phones of key staffMobile devicesAutomaticWhatsApp business chats often hold orders and approvals

A sensible 3-2-1 setup for a 10 to 50 person office

  1. Copy 1, local: a NAS in the office receives nightly backups from PCs and servers. It is not mapped as a drive on user machines; the backup software pushes to it with a separate account.
  2. Copy 2, off-site cloud: the NAS replicates nightly to cloud object storage with versioning and object lock (immutability) switched on for a fixed retention period. If data must stay in India, choose an Indian region.
  3. Copy 3, offline: once a week or month, a rotating external drive is written and taken off-site, for example to the owner's home. Encrypt it.
  4. Separate credentials: backup accounts use unique passwords and two-factor authentication, held by the owner and one trusted person.

Define two numbers for each system before choosing tools. RPO (recovery point objective): how much work you can afford to lose, for example one day. RTO (recovery time objective): how long you can be down, for example four hours for billing. These two numbers decide whether nightly backups are enough or you need something more frequent.

The monthly restore drill: a routine anyone can run

Put this on the calendar for the first working Monday of every month. It takes about an hour.

  1. Pick a random target. One folder, one mailbox, or the accounting data. Rotate so every system is tested at least once a quarter.
  2. Restore it to a different location, never over the live data. A spare laptop or a test folder is fine.
  3. Open the files. Do not just check that they exist. Open a few documents, open the accounting company and check that the last day's vouchers are present.
  4. Time it. Note how long the restore took. If it is longer than your RTO, you have learnt something important cheaply.
  5. Check the off-site and offline copies too, not just the local NAS. Confirm the latest offline drive date.
  6. Record the result in a simple register: date, what was restored, from which copy, time taken, success or problem, who did it.
  7. Fix and repeat anything that failed within the week.

Once a year, run a bigger exercise: pretend the main server is gone and rebuild the billing system on spare hardware from backups alone. This is where missing licence files and forgotten passwords show up.

What about ransomware and legal reporting in India?

Backups decide whether ransomware is an inconvenience or a crisis, but they do not end your obligations. CERT-In's April 2022 directions list malicious code attacks, explicitly including ransomware, among the incidents that body corporates must report to CERT-In within six hours of noticing them. The same directions require logs of ICT systems to be kept for a rolling 180 days within India. If customers' personal data is affected, the DPDP Rules, 2025 (notified on 14 November 2025 and being phased in) require affected individuals to be informed of a personal data breach without delay. Keep the CERT-In reporting email (incident@cert-in.org.in) in your incident plan alongside your backup contacts.

Quick self-check

  • Is at least one backup copy offline or immutable?
  • Can a logged-in office PC delete your backups? If yes, fix that first.
  • Have you restored something in the last 30 days?
  • Do you know your RPO and RTO for billing and accounts?
  • Are backup passwords different from domain or admin passwords, with two-factor turned on?

If you want a free first look at your own machines, our security self-check is a reasonable starting point.

How Cehpoint can help

We design and run backup and recovery setups as part of our cloud and DevOps service: offline and immutable copies, India-region storage where needed, documented restore procedures and scheduled restore tests. For businesses that want continuous monitoring for ransomware activity as well, see our managed SOC service.

Frequently asked questions

Is Google Drive or OneDrive enough as a business backup?

No, not on its own. Sync services copy changes, including deletions and files encrypted by ransomware, to the cloud. Version history can help you roll back, but it has time and storage limits. Treat sync as convenience and keep a separate backup with its own credentials, versioning and at least one offline or immutable copy.

How often should a small business test its backups?

Restore something every month, rotating between systems so each one is tested at least quarterly, and run a full rebuild exercise once a year. Testing means restoring to a separate location, opening the files, timing the restore and writing the result down. A backup job that reports success is not proof that you can recover.

What is the difference between RPO and RTO?

RPO, the recovery point objective, is how much data you can afford to lose, measured in time, for example the last 24 hours of entries. RTO, the recovery time objective, is how long a system can be down before it seriously hurts the business. Together they decide how often you back up and how fast your restore method must be.

Do we need to report a ransomware attack in India if we restored from backup?

CERT-In's April 2022 directions require body corporates to report listed cyber incidents, including ransomware and other malicious code attacks, within six hours of noticing them. Restoring from backup does not change the fact that the incident happened. If customer personal data was affected, obligations under the DPDP framework may also apply, so take legal advice on your specific case.

Need help with this?

Tell us what you are dealing with. We reply with a plain plan, and where it makes sense, a working demo before you commit.