The most commonly known backup rule is the “3-2-1” backup rule, this is the baseline that all backup infrastructure should at least meet:

• 3 copies of your data (including the original)
• 2 stored on different types of media
• 1 copy kept off-site

At first glance, it might sound excessive, but this rule is a time-tested data protection and disaster recovery risk mitigation strategy.

Let’s look at a few real-world scenarios where it proves its value:

• Scenario 1: A user deletes a file.
  No problem. The original is gone, but you’ve got two more copies.
• Scenario 2: The primary backup repository is offline.
  Again, you’ve got additional copies to restore from.
• Scenario 3: The entire production site is unavailable.
  This is where the “1” in 3-2-1 matters. Your off-site copy allows for recovery even in major incidents.
• Scenario 4: Simultaneous hardware failure in production and backup.
  It’s not uncommon for hardware purchased together to fail concurrently. Using two different storage types reduces this risk significantly.

As you can see, it doesn’t take much to fall back to your last good copy, so that copy needs to be there, intact, secure and recoverable.

The 3-2-1-1-0 rule enforces redundancy and validation, but it doesn’t replace standard infrastructure-level security controls:

• Role-Based Access Control (RBAC) — only authorised users should have access, and at appropriate privilege levels.
• Multi-Factor Authentication (MFA) – Confirms user identity through a second verification step.
• Dual Authorisation – Ensures that any admin action requires two admins to perform that action, such as a delete operation.
• Principle of Least Privilege – Only granting the permissions necessary for that role.

These security layers help protect not just your production data, but also your backup data too.

Crucially, your backup platform must be independent of your production platform. If your production environment goes offline (due to failure or attack), your backups must still be:

• Accessible — ideally hosted in an alternate domain or location
• Portable — capable of being restored to a different environment, such as a new cloud tenant, alternate region, or on-prem infrastructure

Data mobility and platform-agnostic restore capabilities are increasingly important. For example, if an attack locks you out of your admin environment during a ransomware attack, can you restore to private cloud, public cloud, or an alternate region? That’s the litmus test for true portability.

Avoid vendor lock-in and ensure your backup solution supports multiple restore targets not just the source environment.