The day the backup story meets reality
A laptop dies on a job site. Someone deletes a shared folder. Ransomware locks the accounting files. That is when you learn whether you had a backup or a slogan. Many small businesses in Henderson and across the Southwest discover too late that “everything is in the cloud” meant sync, not a tested restore—or that the only copy lived on the same computer that failed.
This article is about backups that actually work when a computer dies or ransomware hits: what to protect, how often, where copies should live, and how to know a restore will succeed. Plain language. No theater.
Sync is not the same as backup
OneDrive, SharePoint, Google Drive, and Dropbox are excellent for sharing and working from more than one place. If ransomware encrypts files that then sync everywhere, or if someone empties a folder and the trash retention is short, sync can spread the problem. A backup keeps separate copies you can roll back to a known-good point in time.
Ask a blunt question: if every laptop vanished tomorrow, and a bad actor encrypted the shared drive, how do we get last week’s files and email back—and who does it?
What a small company should actually back up
Start with what would stop the business:
- Microsoft 365 / Outlook email and calendars (including important shared mailboxes)
- Shared files and project folders
- Accounting and payroll data
- Line-of-business apps (job management, EMR front office, CRM exports—whatever you live in)
- Any on-site server or NAS that still holds the “real” copy
Phones and personal downloads matter less than the systems that invoice customers and pay staff. Map those first. Everyday managed IT should include that map, not assume you remember where QuickBooks lives.
The 3-2-1 idea in plain English
A durable approach many owners can remember:
- Three copies of important data (the live one plus two others)
- Two different types of storage (for example, cloud backup plus a local device)
- One copy off-site or offline so office fire, theft, or ransomware cannot touch everything at once
You do not need to recite the slogan. You need two places that are not the same laptop, and a restore path that someone has practiced.
How often is enough?
For active offices, daily backups of critical systems are common; some need more frequent copies for accounting or job data that changes all day. The right answer is: how much work can you afford to re-type? If losing a full day of invoices would hurt, back up at least daily. If a laptop holds unique photos or field files, include it or move that work to a shared, protected location.
Ransomware changes the rules
Modern ransomware looks for backups and tries to delete or encrypt them too. That is why “a drive plugged into the server all day” is a weak sole strategy, and why backup systems need versions history and credentials that are separate from everyday admin logins.
Practical expectations:
- Version history so you can restore from before the attack
- Copies the malware cannot easily reach with the same password everyone uses for email
- A written order of operations: isolate infected machines, then restore clean files
- Protection and updates on each computer so fewer attacks succeed in the first place
Backups are the safety net. MFA, email safety, and protection on each computer are how you fall into the net less often. See managed cybersecurity for how those pieces fit together for shops without a security team.
Test restores—or you are guessing
A green checkmark on a backup dashboard means the job ran. It does not mean you can open last month’s QuickBooks file in an hour. Schedule restore tests: pick a file, a mailbox, or a small folder, recover it to a safe place, and time how long it took. Do this at least a few times a year, and after any big change to your IT setup.
Write down the results. That note is gold for cyber insurance questionnaires and for your own peace of mind. Our article on the cyber insurance checklist explains how underwriters phrase the backup questions.
Email backups deserve a special mention
Microsoft 365 keeps a lot of mail, but retention, litigation holds, and accidental deletion still surprise owners. If email is how contracts and customer history live, confirm whether you have an extra backup of mailboxes—or at least a clear retention and recovery process your provider can execute under stress. “It’s in the cloud” is not a restore plan.
When a computer dies
Hardware failure should be annoying, not existential. If user files live only on the laptop desktop, you will lose work. Prefer saving to shared locations that are backed up. Keep a spare or a fast replacement path for critical roles. Image-level or full-PC backups help some shops; file-level backups of the important folders help most. Choose based on how customized each machine is—not on fear.
Who owns backups in a 15-person company?
Someone named. Not “IT in general.” Not “the person who set up OneDrive in 2019.” Your managed IT provider should be able to show: what is covered, last successful job, last restore test, and how to reach them if ransomware hits at 6 p.m. If you cannot get those answers, you do not have a backup program yet.
A simple scorecard for owners
You are in decent shape when you can say yes to most of these:
- We know where every critical system’s data lives
- Backups run on a schedule we can describe
- At least one copy is off the main office machines
- We have restored something on purpose in the last year
- MFA and computer protection reduce how often we need the safety net
- We can answer the insurance backup questions without guessing
If half of those are no, start with inventory and a tested restore of your accounting and shared files. Perfect is optional. Recoverable is not.
How PrimeTech thinks about this
We treat backups as part of keeping a local business running—alongside computers, Wi‑Fi, printers, and Microsoft 365—not as a separate science project. If you want help mapping what matters and proving restores work, contact us. Henderson-based, serving the Southwest, plain English.
FAQ
Is OneDrive or SharePoint enough?
They are valuable and may be part of your design. For ransomware and serious deletion events, you usually want versioning plus a separate backup strategy and a tested restore. Ask what happens if encrypted files sync to everyone.
How long should we keep backup history?
Long enough to recover from a problem you notice late—often weeks to months for file versions, depending on industry and storage cost. Accounting and legal needs may require longer. Your provider should propose a retention you can afford and explain.
Do we need a backup if we have no server?
Yes. Laptops fail. Cloud accounts get locked. Mistakes happen. Serverless offices still need recoverable email and files.
What is the first restore we should test?
Something you truly need: a recent shared folder, a mailbox, or the accounting company file. Time it. Fix whatever was confusing. Then schedule the next test on the calendar.
Will a good backup stop ransomware?
No—but it can keep ransomware from ending the company. Prevention (MFA, safer email, updates, protection on each computer) still matters. Backup is how you refuse the worst outcome.
Want backups you can prove with a restore?
PrimeTech helps Southwest small businesses design and test backups that survive dead computers and ransomware—tied into everyday managed IT, not a forgotten appliance.
Book a 15-Minute Call → Managed IT Managed Cybersecurity More Insights