Bundall, Gold Coast QLD 07 5610 1930 [email protected] Serving businesses across Queensland

The 3-2-1 Backup Rule Explained: An Essential and Practical Guide to Getting Covered

By Creative Technologies team
Published: 18 November 2026 | Last reviewed: November 2026

The 3-2-1 backup rule keeps three copies of your important data on two different types of storage, with one copy held offsite away from your main systems. Followed properly, it means a failed server, deleted folder or ransomware attack cannot take every copy at once.

This guide is for owners and managers in medium and large organisations across the Gold Coast, Brisbane and the Sunshine Coast. If a backup runs every night and you are still not sure it would save you, the 3-2-1 backup rule gives you a clear standard to check it against.

What is the 3-2-1 backup rule?

The 3-2-1 backup rule spreads copies of your data so no single failure, mistake or attack can remove all of them. Each number answers a different risk.

Part of the rule What it means The risk it answers
3 copies Your original data, plus two backup copies One copy is corrupt, deleted or lost
2 different media The copies sit on two different types of storage, such as local backup storage and cloud storage One device or platform fails
1 copy offsite One copy is held away from your main site, separate from your production systems Fire, flood, theft or ransomware reaches everything on site

The rule is a floor, not a ceiling. It says nothing about how often you back up, how long you keep copies or how fast you can restore. Those choices depend on how much data each system can afford to lose.

Regular backups are also one of the eight strategies in the Australian Signals Directorate’s Essential Eight. The Essential Eight maturity model expects backups of data, applications and settings to be performed and retained in line with business criticality and continuity needs, synchronised to a common point in time, and kept securely. The 3-2-1 backup rule gives that strategy a checkable shape.

A worked example of the 3-2-1 backup rule in practice

Consider this hypothetical example. Imagine a professional services firm with a file server, a line-of-business application and Microsoft 365 for email and files. Here is how the 3-2-1 backup rule looks when it is set up properly.

  • Copy 1 is the live data. It sits on the server and in Microsoft 365, where staff use it daily. This is the original, exposed to deletion, corruption and attack.
  • Copy 2 is a nightly backup on different storage. Backup software copies the server, application data and settings to separate backup storage on site, so a server hardware failure does not take this copy with it.
  • Copy 3 is an offsite backup in the cloud. The same backup is copied to cloud storage, held separate from the production systems. If the office itself is the problem, this copy is elsewhere.

The firm also runs an independent Microsoft 365 backup for email, OneDrive, SharePoint and Teams data, because the live service is copy 1, not a backup of itself.

That is the shape of a full data backup and disaster recovery scope: server and workload backup, Microsoft 365 backup, cloud backup for the offsite copy, and recovery testing to prove the copies work. Managed cloud services can hold the offsite copy and look after backup oversight for cloud workloads.

Why a synced folder is not a backup

Many businesses believe they are covered because their files sync to a cloud folder. Sync is useful. Under the 3-2-1 backup rule, it does not count as a backup copy.

Sync copies changes as they happen, including the changes you never wanted. A folder deleted on Monday is deleted everywhere by Monday afternoon, and files encrypted by ransomware are uploaded in encrypted form, replacing the good versions. Version history and recycle bins help with small mistakes, but they run for limited periods and sit under the same accounts staff use daily.

A backup keeps separate, dated copies, taken at set times, so you can go back to a point before the problem started and restore data, applications and settings together. The Australian Cyber Security Centre says the same in its guide to securing your devices: back up regularly to an external drive or trusted cloud service, and ensure backups can be restored.

The test is simple. If deleting or encrypting a file changes the only other copy you hold, you have sync, not backup, and the 3-2-1 backup rule is not met.

Why an always-connected backup can fail in the same incident

The second trap is a backup that is always connected to the network it protects. If backup storage stays online and everyday administrator accounts can reach it, an attacker in your network can reach it too. Deleting or encrypting the backups first is a standard early move in a ransomware incident: it removes your way back before any ransom demand arrives.

Separation stops one incident from becoming total loss. The Essential Eight maturity model requires that unprivileged accounts cannot access backups belonging to other accounts, and are prevented from modifying and deleting backups. In practice: separate credentials for backup storage, tight control over who can change copies, and at least one copy everyday accounts cannot touch.

Backup design therefore sits inside wider cyber security work. The access controls and account hygiene that protect your production systems have to extend to the copies you would rely on if those systems fell over.

A backup nobody has restored is a hope, not a plan

The 3-2-1 backup rule counts copies. It cannot tell you whether any of them work. A backup job can report success every night while the restore fails, because a setting changed, a database was never included, or the one person who knew the process left.

The Australian Cyber Security Centre expects restoration from backups to be tested as part of disaster recovery exercises. Treat that as the standard. Restore one file, then one mailbox, then a full system, and time each one. Compare the results with your recovery objectives: how much data, measured in time, you can afford to lose, and how quickly each system must be running again.

Our cloud migration checklist makes the same point from the other side: before any system moves, back it up and test a restore, because a backup that has never been restored has proved nothing.

Newer variants add an offline or immutable copy

You may see the rule written with extra numbers. The common change adds one copy that is offline, meaning disconnected from the network when not being written, or immutable, meaning it cannot be changed or deleted for a set period, even by an administrator account.

Read that as an evolution of the 3-2-1 backup rule, not a replacement for it. The original rule separated copies by number, by media and by place. The newer variants add separation by reachability: a copy an attacker cannot get to. If your setup meets the basic rule, an offline or immutable copy is the most valuable next step.

Score yourself against the 3-2-1 backup rule

Answer yes or no to each statement, based on what you could prove today, not what you believe is set up.

  1. We hold three copies of our important data, counting the original.
  2. The copies sit on two different types of storage.
  3. One copy is offsite, separate from our production systems.
  4. At least one copy is offline, immutable, or protected so normal accounts cannot modify or delete it.
  5. Our Microsoft 365 email, OneDrive, SharePoint and Teams data has its own independent backup.
  6. Our backups are synchronised, so systems can be restored to a common point in time.
  7. We have test-restored from our backups in a disaster recovery exercise, and recorded the result.
  8. Our recovery priorities, and how much data we can afford to lose for each system, are written down.

Scoring: eight yes answers means the 3-2-1 backup rule basics are covered, and your job is to keep testing. Five to seven means the rule is partly in place, and your no answers name the gaps to close first. Four or fewer means one incident could take data you cannot replace.

Frequently asked questions

What is the 3-2-1 backup rule?

The 3-2-1 backup rule is a simple standard for keeping data safe. Keep three copies of important data, store them on two different types of storage media, and hold one copy offsite, separate from your main systems. That spread means one failure cannot remove every copy.

Does Microsoft 365 count as a backup on its own?

No. Microsoft 365 is where your email and files live and work, so it holds the original copy, not a backup of itself. Microsoft keeps the service running, while protecting your data against deletion, ransomware and account compromise is your responsibility. Add an independent backup copy.

Why is a synced folder not a backup?

Sync copies changes as they happen, including deletions, corruption and ransomware encryption, so the damage reaches the synced copy within moments. A backup is different. It keeps separate, dated copies, so you can restore data from a point in time before the problem started.

How often should we test restoring from our backups?

Test as part of your disaster recovery exercises, and whenever a major system changes. The Australian Cyber Security Centre expects restoration to be tested, not assumed. Start with one file and one mailbox, then a full system, and record how long each restore takes.

Should we add an offline or immutable copy to the 3-2-1 backup rule?

For most businesses, yes. Newer variants of the rule add one copy that is offline or immutable, meaning it cannot be changed or deleted for a set period. That copy is the one an attacker on your network cannot reach, encrypt or quietly remove.

Sources

  • Australian Signals Directorate, Essential Eight maturity model, cyber.gov.au. Regular backups: performed and retained in line with business criticality and continuity, synchronised to a common point in time, restoration tested, and ordinary accounts prevented from modifying or deleting backups.
  • Australian Cyber Security Centre, Personal cyber security handbook: Secure your devices, cyber.gov.au. Back up regularly to an external drive or trusted cloud service, ensure backups can be restored, and keep an offline backup in a different location.
  • Service scope and recovery testing approach checked against the Creative Technologies website (data backup, cloud services and cyber security pages), November 2026.

Sources checked November 2026.

Not sure your business would pass its own scorecard? Call Creative Technologies on 07 5610 1930 or talk to our Bundall team for a review of your backup setup. We will check your copies against the rule and tell you plainly where the gaps are.


Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top