Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
OT backup and restore is the discipline of capturing controller logic, HMI projects, and system configurations so an industrial plant can be rebuilt and returned to production after an incident.

What Is OT Backup and Restore?
Ask an industrial site how quickly it could rebuild a control system destroyed by ransomware and the honest answer is often a shrug. The Windows servers are backed up by the corporate team. The controller logic lives on an engineer’s laptop. The HMI project exists in three versions and nobody is certain which one matches the plant. OT backup and restore is the discipline that closes that gap: capturing everything needed to reconstruct a control system, and proving the reconstruction works.
Norsk Hydro’s experience in March 2019 is the reference point. LockerGoga encrypted systems across the aluminium producer’s global operations, several plants reverted to manual control, and recovery ran into months at a reported cost of well over £45 million. What saved the company was the existence of restorable data, not the absence of an attacker.
Most failed recoveries are not failures of backup media. They are failures of assumption.
Apply the familiar 3-2-1 rule — three copies, two media types, one off-site — and add an OT-specific condition: at least one copy must be offline and immutable, held somewhere ransomware with domain credentials cannot reach. Many operators keep write-once media or a physically disconnected drive in the control room safe alongside the licence dongles.
Set frequency by rate of change rather than by calendar habit. Controller logic may be stable for a year and then change ten times during a commissioning campaign, so trigger a backup from the change management process and not only from a schedule. Historian data usually follows a nightly cycle. Agree recovery time and recovery point objectives per system with the production manager, because a two-hour objective for a packaging line and a two-hour objective for a safety-instrumented function cost very different amounts.
A backup is a hypothesis until a restore tests it. Run a bare-metal recovery of one engineering workstation and one controller each year, ideally during a planned outage or against spare hardware on the bench. Record how long it took, what was missing, and who had to be telephoned. Fold the result into the disaster recovery plan and into OT incident response playbooks, where the realistic restore time usually turns out to be the deciding factor in whether to run the plant manually.
Under the NIS Regulations 2018, operators of essential services are assessed against the NCSC’s Cyber Assessment Framework, where Principle D1 expects tested recovery capability rather than documented intent. The NCSC’s own offline backup guidance is the clearest short statement of what good looks like.
At Privia Security, our Emergency Action Plan Services help industrial operators write and rehearse recovery procedures that match the plant as it actually is.
Tie it to change rather than to a timetable. Export and archive the project after every download to a live controller, and additionally on a quarterly schedule to catch undocumented changes. Many sites also run an automated tool that reads the running application weekly and raises an alert when it differs from the approved archived version.
Often yes for the Windows layer, provided the agent is supported by the control system vendor and the backup traffic does not cross the IT and OT boundary uncontrolled. Controller logic, firmware, and licence files usually need separate handling, because they come out of engineering tools as files that no agent knows to collect.
Yes. Safety-instrumented system applications are change-controlled under IEC 61511 and restoring one is a safety-relevant activity, not an IT task. Keep those backups in a separate, access-restricted store, record the approval chain alongside each version, and make sure the restore procedure names who must verify the function before it is returned to service.
Licences and dongles. Teams back up project files diligently and then discover during a restore that the programming environment will not start, the vendor licence server is unreachable, or the hardware key is in a drawer nobody can open. Record every licence, its location, and its reissue contact in the recovery documentation.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.