A ransomware-resistant backup is not simply a folder copied to another drive. It is a recovery plan with enough independent, protected copies of important data, clear priorities, and a restore process that has been tested. This guide shows home users and small businesses how to estimate storage needs and costs, design a practical 3-2-1 backup layout, protect backup accounts and devices from malware, and verify that files can actually be recovered.
Overview
The purpose of a malware-safe backup strategy is to preserve a usable copy even when a computer, phone, server, or cloud-synchronized folder is compromised. Ransomware can encrypt files that are reachable from an infected device. A destructive incident may also involve stolen credentials, deleted cloud data, or connected external drives. Backups reduce the impact, but only when at least one recovery copy is separated from the systems that could be attacked.
The familiar 3-2-1 backup rule is a useful starting point:
- Three copies: keep the original data plus at least two backup copies.
- Two types of storage: use different storage locations or technologies rather than relying on one device or one account.
- One copy separated from everyday systems: this may be offline, disconnected, access-restricted, or protected by an immutability feature.
The rule is a design guide, not a guarantee. A backup that has never been restored, uses the same password as the infected computer, or silently excludes important folders may fail when needed. Pair the storage plan with endpoint protection, software updates, multi-factor authentication, and a clear incident process. If ransomware is suspected, stop using affected systems and follow a documented recovery sequence; the ransomware incident response checklist can help organize those first decisions.
How to estimate
Start with the amount of data that must be recoverable, then estimate the storage and operating cost of each backup layer. Use a simple worksheet rather than choosing capacity by guesswork.
- Inventory protected data. List documents, photos, project files, databases, email exports, configuration files, and any data stored on phones or removable media. Separate replaceable applications from irreplaceable data.
- Measure the current footprint. Record the size of each important folder or device. Include hidden or overlooked locations, such as desktop folders, local mail archives, accounting data, and shared business folders.
- Estimate change volume. Note how much new or changed data is created each day or week. A business that changes large files frequently needs more version history than a household that mainly adds photographs once a month.
- Choose retention. Decide how many daily, weekly, or monthly versions should remain available. Longer retention improves the chance of recovering a file from before an infection, but it requires more capacity.
- Calculate usable capacity. A practical estimate is: required capacity = current data + retained changes + recovery overhead. Add room for growth rather than filling a drive immediately.
- Price each layer separately. Include storage, backup software, replacement media, administration time, and any optional features such as immutable storage or advanced version history. Treat staff time as a real planning input even when the tool is free.
For a rough planning model, calculate each destination independently. A local backup may need enough capacity for several versions, while a cloud destination may use deduplication or compression that changes the billed amount. Do not assume that a provider's advertised capacity, synchronization feature, or recycle bin is equivalent to a ransomware-protected backup. Check whether it supports historical versions, account recovery, access controls, and deletion protection.
Inputs and assumptions
Use these inputs in a spreadsheet or written plan:
| Input | What to record | Why it matters |
|---|---|---|
| Protected data | Total size by device, folder, or system | Sets the minimum capacity and identifies gaps |
| Change rate | Typical new or modified data per period | Determines version and retention requirements |
| Recovery priority | Critical, important, or convenient | Helps decide restore order and acceptable downtime |
| Recovery point objective | How much recent work can be lost | Guides backup frequency |
| Recovery time objective | How quickly each system must return | Guides local copies, spare equipment, and procedures |
| Protection model | Offline, restricted, immutable, or a combination | Shows how a copy is isolated from malware |
| Access and encryption | Separate accounts, multi-factor authentication, and key custody | Reduces the risk of stolen credentials or exposed data |
For home use, a sensible layout might include an automated local backup, a second copy on a different device or service, and a periodically disconnected copy of the most important files. For a small business, consider protecting shared storage, employee laptops, cloud accounts, and essential configuration data separately. Keep backup administration independent from ordinary user accounts where possible, and document who can approve deletion or restore operations.
Encryption protects confidentiality if backup media or accounts are exposed, but it creates a key-management responsibility. Store recovery keys or passphrases in a secure location that is not dependent on the infected computer. If nobody can access the key, an encrypted backup may be unusable. Test the recovery process without exposing the only copy of the key.
Worked examples
Home user with documents and photos
Suppose a household has one computer and a phone containing documents, scanned records, and photographs. The owner lists the important folders, measures their combined size, estimates how much is added each month, and chooses a retention period that preserves several earlier versions. The plan could use an automated local backup for convenient restores, a separate cloud or removable-media copy, and an offline copy updated on a schedule. The offline destination should be disconnected after the backup completes so ransomware on the computer cannot immediately encrypt it.
The owner then restores a sample document, a large photo folder, and one older file version to a temporary location. The test checks more than whether a backup job reports success: it confirms that the files open, names and permissions are sensible, and the recovery instructions are understandable.
Small business with shared files
Consider a small team that stores active work in a shared drive and keeps some files on employee laptops. The administrator first ranks data by business impact. Customer records, financial documents, operational files, and authentication or configuration information may require faster recovery than archived material. The estimate includes the shared data, laptop data that is not already centralized, the desired history, and capacity for growth.
A practical design may combine frequent automated backups with a separate account or storage boundary, a protected historical copy, and an offline or immutable layer for critical data. The team should test restoring a complete folder, a single file, and an essential service or application configuration. Record who performs each step, where credentials are stored, and how a clean replacement device would be prepared. For wider account and device cleanup after an incident, use the malware incident recovery checklist.
When to recalculate
Review the plan at least quarterly and after any major change. Recalculate storage and recovery assumptions when a device is replaced, a new employee joins, a shared folder expands, a cloud service changes its limits or features, or the business begins retaining larger files. Recheck pricing inputs whenever a subscription renews or storage requirements change; do not rely on an old estimate.
Run a small restore test monthly for critical data and a broader exercise at least quarterly. Check that backups are completing, versions are available from before the test, disconnected media can still be read, and recovery credentials and encryption keys work. Review whether antivirus and other security controls are still active on the systems that create or manage backups; the safe antivirus verification checklist provides a related maintenance reference.
Use this action list for the next review:
- Measure current data and compare it with the last estimate.
- Confirm that all critical devices, accounts, and folders are included.
- Verify that at least one recovery copy is isolated from everyday access.
- Check multi-factor authentication, separate administrator access, encryption, and recovery-key storage.
- Restore representative files and record the time, problems, and follow-up tasks.
- Update the written procedure, owners, retention settings, and next test date.
A backup plan becomes dependable through repetition. Estimate with current inputs, protect copies from the same credentials and devices that could be compromised, and test restoration before an emergency makes the result important.