The 3-2-1 backup rule says to keep three copies of your data, on two different kinds of storage, with one copy kept off-site. It is a simple way to make sure no single failure, theft, fire or attack can wipe out everything.
Almost every organization says it has backups. Far fewer can say when they last restored something from one. The 3-2-1 rule is a good starting point because it is easy to remember and easy to check.
This guide walks through the rule, the modern additions that help against ransomware, and the two questions that matter most after an outage: how much did we lose, and how long until we are working again?
Keep the original data you work from every day, plus two backups. If one copy fails, you still have a spare while you fix it. One backup sounds like enough until the day you discover it has been quietly failing for weeks.
Do not keep every copy on the same kind of device or in the same system. If the server and its backup share one set of disks, one hardware failure takes both. A typical mix is a local backup appliance or storage device plus cloud storage.
At least one copy should live somewhere else, so a fire, flood, tornado, theft or power surge at the building does not destroy the data and the backup together. Today this usually means a cloud backup service or a second location.
The original rule was written with hardware failure and disasters in mind. Ransomware changed the picture. Attackers now look for the backups first and try to delete or encrypt them before they lock anything else, because an organization with no backups is more likely to pay.
That is why you will often see the rule extended to 3-2-1-1-0. The extra 1 means one copy is offline or immutable. The 0 means zero errors when you verify and test your backups.
A backup is a copy of your data. Disaster recovery is the plan and the equipment to get your organization working again. You need both, and having the first does not give you the second.
Here is the difference in practice. Suppose your main server dies. With backups alone, your data is safe, but you have nothing to restore it onto. Someone has to order hardware, wait for delivery, install software and then restore. That can take days. With a disaster recovery plan, you have already decided where systems will run in the meantime, who does what, in which order systems come back and how staff will work while they wait.
For a care facility, that last part matters a great deal. If the EHR is unavailable, nurses still need medication records. A good plan includes downtime procedures, such as printed or offline copies of critical information, and a clear list of who to call.
These two terms sound like jargon, but they are simply business decisions about time.
Recovery point objective is the maximum amount of recent data you are willing to lose, measured in time. If backups run once a night and the server fails at 4 p.m., everything entered since last night is gone. That is an RPO of about a day. If that is too much, you need more frequent backups.
Recovery time objective is how quickly a system needs to be working again. The phone system at a nursing home may need to be back within minutes. An archive of old files may be fine for a week. Shorter recovery times cost more, so set them system by system.
Only you know what an hour of downtime costs your operation and your residents, patients or customers. Your IT provider's job is to tell you what each target costs and then build to the targets you choose. If nobody has ever asked you these two questions, your backups were designed by guesswork.
A backup you have never restored is a hope, not a plan. Backup software can report success for months while the copies are incomplete, corrupted or missing the one folder that matters. The only way to know is to restore.
The gaps tend to be in the same places.
You do not need to be technical to find out where you stand. Ask whoever manages your IT these questions and ask for the answers in writing.
Is saving files to the cloud the same as having a backup? Not quite. File sync services keep your files available on many devices, but a deletion or ransomware encryption can sync everywhere too. Version history helps for a limited time. A true backup is a separate copy kept independently.
How long should we keep backups? It depends on your records requirements and how far back you might need to go. Healthcare, financial and legal records often have retention rules set by regulators or contracts. Decide with your compliance advisor, then have IT set the retention to match.
Are backups required by HIPAA? The HIPAA Security Rule calls for a contingency plan that includes data backup, disaster recovery and a plan for operating in an emergency. How you meet that depends on your organization. This is general information, not legal advice.
If we have good backups, are we safe from ransomware? Backups let you recover without depending on a criminal, which is a major advantage. They do not stop data from being stolen and they do not prevent the downtime while you restore. You still need prevention and detection.
How do I know what downtime really costs us? Add up what stops when systems are down: staff time, delayed billing, missed appointments and, in care settings, slower access to records. Our downtime calculator can help you put a rough number on it.
A free 15-minute readiness check gives you a plain answer on your backups, MFA and recovery plan.
Call or text: 405-285-3845
New customers: start@unitycareit.com
Existing customers: support@unitycareit.com
Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas
Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support