When the Line Goes Down, Your Backups Better Work: Data Protection for Idaho Manufacturers

A ransomware attack hit a mid-sized manufacturer on a Thursday morning. By Friday afternoon, they still couldn't access their ERP. Production was stopped. Customer orders were sitting in a queue no one could open. The backup existed — it just hadn't been tested in eight months, and it couldn't be restored.

Manufacturing is now the most targeted sector for ransomware, according to multiple years of cybersecurity reporting. The reason is straightforward: attackers know that downtime on a production floor costs money fast, and pressure to pay increases by the hour.

Good backup strategy doesn't just protect files. It determines whether you're back up in hours or days.

Manufacturing data is different from office data

Most backup conversations focus on files and email. Manufacturing environments have a broader problem.

The data your business depends on includes things most generic backup guides don't mention:

• ERP data — job costing, work orders, inventory, purchase orders, customer records. If your ERP (whether that's Epicor, SYSPRO, JobBOSS, or something else) goes down without a clean restore point, you're rebuilding manually.
• Machine configurations and PLC settings — CNC programs, PLC ladder logic, equipment calibration data. Losing these doesn't just mean lost files; it means production can't restart until someone reprograms the machines.
• Production schedules and shop floor data — active jobs, labor tracking, quality inspection records. Even if your ERP comes back, corrupted or missing schedule data creates downstream chaos.
• CAD and design files — for custom manufacturers, job shops, and fabricators, these are often irreplaceable intellectual property.
• Email and workstation data — Microsoft 365 does not back up your mailboxes by default. It takes a third-party solution.

Each of these has different backup requirements, different restore priorities, and different recovery timelines. A single backup strategy doesn't cover all of them equally.

The 3-2-1 rule, applied to manufacturing

The 3-2-1 framework is a solid starting point:

• 3 copies of your data
• 2 different storage types (local + cloud, for example)
• 1 copy stored offsite

For manufacturers, the "offsite" copy is especially important. A fire, flood, or physical break-in at your facility can destroy on-site backups along with everything else. Cloud-based copies survive facility-level events. They also matter to your cyber insurance carrier — most policies now require documented offsite backup as a baseline control.

But 3-2-1 is a framework, not a complete plan. The harder questions are: how frequently are each of those copies updated, and how fast can you actually restore from them?

Recovery time is the metric that matters on the plant floor

Two numbers should drive your backup architecture:

RTO (Recovery Time Objective) — how long can your operation be down before it causes serious damage? For a job shop running tight delivery windows, a two-day recovery is a crisis. For a business with buffer inventory and flexible customers, it might be manageable. Know your number.

RPO (Recovery Point Objective) — how much data can you afford to lose? If you back up nightly and get hit mid-afternoon, you've lost a full day of production records, orders, and labor data. Whether that's acceptable depends on your operation.

These aren't theoretical questions. They should drive the frequency and structure of your backups — and they should be documented so your team knows what to prioritize when something goes wrong.

A note for defense manufacturers

If your facility does work for the Department of Defense — weapons, aerospace components, precision machining for military contracts — your backup requirements aren't optional.

CMMC (Cybersecurity Maturity Model Certification) requires documented data protection practices, controlled access to backup systems, and protection of Controlled Unclassified Information (CUI) in stored and backed-up data. Backups of CUI must be encrypted, access-controlled, and tested. If you're working toward CMMC Level 2 or above, your backup strategy needs to reflect that.

TotalCare IT works with manufacturers in the Treasure Valley and East Idaho who are in various stages of CMMC readiness. Talk to our team if that's on your radar.

Testing is the part most manufacturers skip

Running backups is not the same as having working backups. Backup jobs can complete successfully and still fail to restore — because of file corruption, incremental backup fragmentation, or format incompatibility with the recovery environment.

Testing a restore for a manufacturing environment is also more complex than testing a file recovery for an office. You need to know whether your ERP database restores cleanly, whether machine configuration files are intact, and whether the restore can happen within your RTO window.

We recommend at minimum quarterly restore testing — and more frequently if you've recently changed ERP versions, migrated servers, or expanded production systems.

If a ransomware attack hit your facility tomorrow, what would happen?

That's the question worth sitting with. Not "do we have backups" — most manufacturers do — but whether those backups are current, tested, and recoverable within a timeframe your operation can survive.

TotalCare IT provides managed backup and recovery services for manufacturers in Boise, Idaho Falls, and throughout the Treasure Valley and East Idaho. We build backup architecture around your actual RTO and RPO, test restores on a documented schedule, and can help you align your data protection practices with CMMC requirements if needed.