It's 6:40 on a Tuesday morning. First shift is clocking in, three jobs are due to ship Friday, and the file server won't boot. Nobody can pull prints. The CAM programs are on that server. JobBOSS won't open, so nobody can even see what's supposed to run today.
Every machine in the building works fine — and not one of them can make a part.
Whether that morning is an inconvenience or the beginning of the end comes down to one thing: your backup and recovery plan. That's what "data loss" actually looks like in a shop. It isn't an abstract IT problem. It's a floor full of people standing around while ship dates slip and a customer starts asking questions.
FEMA's often-cited numbers say 40% of small businesses never reopen after a disaster, and another 25% close within a year. Most of them weren't killed by the fire or the crash itself. They were killed by not being able to get back up.
Here's the good news: data backup and disaster recovery that actually works doesn't require an IT department or an enterprise budget. Below is the plain-English plan we use with shops around Parkesburg and across Chester and Lancaster County — small manufacturers with 5 to 25 computers and zero patience for downtime.
Why Backups Are a Production Problem, Not an IT Problem
In a manufacturing business, data isn't paperwork. It's throughput.
- Your job system — JobBOSS, E2, Global Shop, Epicor, or QuickBooks plus a mountain of spreadsheets — holds every quote, traveler, due date, and price.
- Your CAD/CAM files — SolidWorks, Mastercam, Fusion 360 — are the parts. If the file server dies, the floor can't pull prints and can't post programs.
- Everything else — customer POs, quality records, financials, email — is what you need to invoice, pass an audit, and win the next job.
Lose any of it — a failed drive, ransomware, a deleted folder, a lightning strike — and you're not "down a computer." You're not quoting, not cutting, and not shipping.
And two outside forces now care about your backups even if you don't:
- Your cyber insurance carrier. Renewal questionnaires ask point-blank about tested, off-site backups. The wrong answers mean higher premiums — or no renewal at all.
- Your biggest customers. More OEMs are sending vendor security questionnaires, and "how do you back up and recover your data?" is on the first page.
So here's the plan.
A Simple Backup and Recovery Plan for Your Shop
1. Follow the 3-2-1 backup rule
Three copies of your data, on two different kinds of storage, with one copy off-site.
In practice for a small shop: your live data is copy one. Copy two goes to a backup device in the building — a NAS or backup appliance — so restores are fast. Copy three goes to the cloud, so a fire, flood, theft, or ransomware hit can't take everything at once.
2. Back up the whole server, not just the files
For the machine running your ERP and file shares, use image-based backup — a snapshot of the entire server, settings and databases included. When the hardware dies, you restore the whole thing to new hardware (or a temporary virtual machine) in hours, instead of spending a week reinstalling software and hunting for license keys.
That's the difference between a bad morning and a bad month.
3. Automate it — and cover second and third shift
Manual backups fail because people are busy running a shop. Automate the schedule and let the software alert you when a backup fails — don't wait to find out the hard way.
One thing generic advice always misses: if your shop runs a second or third shift, a backup that finishes at 6 pm misses everything those shifts produce. Data changes around the clock in a manufacturing business, so back it up accordingly — frequent snapshots for the ERP and active job files, and at minimum nightly for everything else.
4. Keep old versions, not just last night's copy
A synced folder is not a backup. If ransomware encrypts your files, OneDrive or Dropbox will faithfully sync the damage right over your good copies.
Real backup keeps multiple restore points, so you can roll back to before the trouble started — before the infection, before the corrupted update, before somebody saved over the only copy of a fixture drawing. Keep several weeks of versions, and take a snapshot before anything big, like an ERP upgrade.
5. Watch your storage
"Backup Failed — Storage Full" is not a message you want to discover after the crash. CAD files and job photos grow fast. Check usage monthly, turn alerts on, clear out duplicates, and keep 20–30% headroom so backups never quietly stop running.
6. Test the restore, not the backup
The only backup that counts is one you've actually restored. Plenty of shops find out during a crisis that their backups were incomplete or corrupt — the worst possible moment to learn it.
Once a quarter, run a fire drill: restore a folder of prints, restore the job-system database to a test location, and time it. Then answer two questions in plain English:
- How long can the floor sit idle? That's your recovery time target.
- How much re-entered work can you live with — an hour of orders, or a whole day? That's your recovery point target.
If the drill can't hit those numbers, fix the plan now, not mid-disaster.
7. Train your people
Most ransomware walks in through email — one clicked "invoice" from a fake vendor, and the whole network is encrypted by morning. Ten minutes at a toolbox talk goes a long way: what a phishing email looks like, where files must be saved (the server, not desktops), and who to call the second something looks off.
Your people are either the easiest way in or your first line of defense. Training decides which.
When Disaster Strikes Anyway: Your First Four Recovery Moves
Even good plans get tested. When it happens:
- Size it up. One workstation, or the whole server? If you suspect ransomware, disconnect the affected machines from the network first — don't give it time to spread.
- Restore in production order. Job system and current job files first. The floor needs prints and travelers before anyone needs the 2019 archive.
- Tell the team. Who's doing what, what runs on paper in the meantime, and what to tell a customer if a date is at risk. Silence creates more chaos than the outage.
- Write down what happened. The cause, how long recovery took, what was missing. Then fix the plan while it's fresh.
The Quiet Bonus: Cyber Insurance Renewals and Customer Audits Get Easier
Do everything above and something nice happens: the scary paperwork gets easy. Documented, tested, off-site backups are exactly what cyber insurance carriers and OEM security questionnaires ask about. At Starlux IT, we build the backup piece so it can go straight to your broker or your customer — boxes checked, no scrambling.
Backup and Recovery FAQs for Small Manufacturers
What is the 3-2-1 backup rule?
The 3-2-1 rule means keeping three copies of your data, on two different types of storage, with one copy off-site. For a small shop, that's your live data, a backup device in the building for fast restores, and a cloud copy that survives a fire, theft, or ransomware.
How often should a small manufacturer back up its data?
Back up your ERP or job system and active job files with frequent snapshots — hourly or better — and everything else at least nightly. If your shop runs a second or third shift, schedule backups around the clock, because a 6 pm backup misses everything those shifts produce.
Does cyber insurance require data backups?
Most carriers now ask directly about backups on the renewal application — whether they're automated, encrypted, tested, and stored off-site where ransomware can't reach them. Weak answers mean higher premiums, coverage exclusions, or a declined renewal. A documented, tested backup plan is one of the fastest ways to improve your application.
Is OneDrive or Dropbox a backup?
No — file sync is not backup. If ransomware encrypts your files or someone deletes a folder, sync copies that damage everywhere within minutes. Sync tools keep limited version history; a real backup keeps independent restore points you can roll back to.
What's the difference between backup and disaster recovery?
Backup is the copy of your data. Disaster recovery is the plan and tools for getting the shop running again — how fast systems come back, and how much re-entered work you can tolerate. You need both: a backup with no recovery plan can still mean days of downtime.
Not Sure Your Backups Would Actually Save You?
Most owners we meet think they're covered — until we test a restore together. We're Starlux IT in Parkesburg, and managed IT for small manufacturers is what we do every day — for shops in Parkesburg, Coatesville, Downingtown, Gap, and across Chester and Lancaster County. We speak JobBOSS and Epicor, we know what a server full of SolidWorks files needs, and our techs are local enough to be on-site the same day.
If you're not 100% certain your shop could be running the day after a crash, let's find out before it matters. Free 30 minutes, no pressure — we'll check what you have, show you the gaps, and you'll know exactly where you stand, whether you hire us or not.
Book a free 30-minute backup check →