Ask what the most valuable program on a hydroponic farm is and nobody names the code inside the fertigation controller — yet that program holds every setpoint, recipe, alarm band and valve sequence the crop depends on, and most farms have never exported it once. When a board fails, a battery dies or a firmware update goes sideways, the farm re-learns months of tuning from memory and printouts. Controller program backups are cheap insurance on exactly that asset, and the discipline is closer to record-keeping than to IT.
What Lives Inside the Controller and What Can Be Lost
A working controller holds more than a settings page. Typical contents: irrigation start triggers and schedules, EC and pH target bands with dead-bands, dosing recipes per crop stage, alarm thresholds and escalation contacts, valve and zone maps, sensor calibrations, VFD or pump logic links, and the sequence programs that chain those pieces together. Some of it is recoverable from paperwork; the sequences and interlocks usually are not, because they were tuned live and only exist in the device.
The loss events are ordinary. A failed power supply or dead internal battery wipes volatile memory. A firmware update resets settings to defaults. A lightning-induced surge damages the board despite protection. And the slowest loss — a controller replaced after years, with the one person who knew the tuning having left. Hardware protection against the electrical cases is the subject of the guide to surge protection and UPS for controllers; backups cover everything that survives the electronics intact.
What to Export and How Often
Export everything the manufacturer’s tool allows, in the file format it natively produces — full program file, parameter set, and (where offered) an on-device backup image. A quarterly export rhythm catches seasonal retuning; add an immediate export after any meaningful change: a new recipe, a re-mapped valve, a changed alarm band, a firmware update. Keep a dated folder per controller — one file set per house, named clearly enough that a stranger knows which is which.
- Export the full configuration with the manufacturer’s tool to USB, SD or laptop.
- Copy the export off-site — cloud drive or office PC, not the same USB stick that lives in the controller cabinet.
- Write a one-line version note: what changed and why (“2026-06-02: lettuce recipe EC band 1.6–1.9, raised for summer stage”).
- Confirm the file opens and its size matches the previous export’s ballpark; an empty file is worse than none.
If the manufacturer’s tool offers scheduled automatic backups, enable it — but keep the manual export too, because automatic routines fail silently and the manual pass is the one somebody actually looks at.

Restore Drills: Testing the Backup Before You Need It
A backup that has never been restored is a hypothesis. Once per season — ideally during a planned maintenance week — load the latest export onto a spare controller of the same model, or onto the live unit during a crop-free window, and verify it behaves: setpoints match the version note, valve map fires the right zone on test, alarm bands trigger on a simulated excursion. As a planning expectation, a restore drill takes one to three hours per controller once the procedure is familiar, assuming the manufacturer’s tool is on hand and the file set is current.
The drill also teaches what the paperwork misses: a config file that restores numbers but not sequence logic shows up here, not during an emergency. Anything the drill exposes as “not covered by the backup” goes into a written manual record — usually the valve interlocks and the dosing sequence quirks — kept in the same folder as the exports.
Schedule the drill like any other maintenance item, and record its result — date, controller, file used, checks passed — in the same folder. A documented drill also settles the insurance and warranty conversation faster: the farm can show the recovery path worked on a chosen day, rather than hope it works on a forced one.
The integration logic between controller and other equipment is treated separately in the guide to controller integration, but its backup belongs in this folder too.
Backup Media and Version Notes Compared
Media choice matters less than the habit, but each option has its failure mode. The comparison below reflects what actually happens on farms.
| Backup medium | Strengths | Failure modes | Best practice |
|---|---|---|---|
| USB stick kept in the cabinet | Fastest to reach in an emergency | Same surge event can kill board and stick; sticks fail in drawers | Never the only copy; duplicate off-site |
| Cloud folder | Survives fire, theft, surge; version history for free | Needs someone to actually upload after each export | Upload within a day of every export |
| Office PC shared drive | Simple, no account dependencies | Single site; dies with the farm network | Pair with cloud or off-site copy |
| Printed settings sheet | Readable by anyone, no tools needed | Drifts from reality within weeks | Treat as a recovery aid, dated and re-verified |

Ownership, Supplier Files and Handover
Two ownership questions decide how useful the backups are. First, who holds the supplier’s commissioning program: at handover, request the original program files, the tool or software licence needed to open them, and the cable or interface — file them with the equipment documentation set, because a backup nobody can open is decoration. Second, who keeps the farm’s changes current: the export habit needs an owner named in the maintenance plan, or it decays silently until the event that needs it. A controller backup line inside the annual maintenance plan is the usual fix.
At staff turnover, the version notes carry the knowledge: a stranger reading six months of one-line entries can reconstruct what was tuned and why, which is more than any settings sheet achieves. Tie the folder into the farm’s wider record-keeping, where the asset register already lists each controller by serial and house.
Controller program backups are four exports a year, one restore drill per season and one page of version notes. That habit converts the most fragile black box on the farm into a documented, restorable asset — before the day it stops being optional.
FAQs About Controller Program Backups
How often should controller programs be exported?
Quarterly as a baseline, plus immediately after any recipe, valve map, alarm or firmware change. Seasonal retuning is exactly the work a backup protects, so the rhythm should follow the farm’s tuning calendar.
What does a restore drill actually involve?
Loading the latest export onto a spare or crop-free controller and verifying setpoints, valve map and alarms against the version note. As a planning expectation, one to three hours per controller once familiar, best done during a planned maintenance window.
Where should backup files be stored?
In at least two places: one copy in the cabinet for speed, one off-site (cloud or office network) for the events that damage both board and cabinet. An export that lives only on a stick in the same room as the controller is not a backup.
Do we own the supplier’s controller program after commissioning?
Whatever the contract says, request the program files, the software tool and the interface cable at handover, and file them with the equipment documentation. Buyers should confirm licence terms in writing before signing off the installation.
What do version notes need to contain?
Date, what changed, and why — one line is enough. The notes turn a folder of files into a history, and they are the fastest way for a new technician to reconstruct months of tuning after staff turnover.
Related Reading
- Surge Protection and UPS for Hydroponic Controllers — The hardware half of controller protection
- Hydroponic Nutrient Controllers: Automation, Dosing, pH and EC — What the program actually controls
- Hydroponic Alarm Systems: Thresholds and Escalation — The alarm bands the backup preserves
- Hydroponic Equipment Documentation and Manuals — Where supplier program files belong
- Hydroponic System Commissioning: Testing and Site Acceptance — When the first baseline export should happen
Next Step: What to Send for a Quotation
Controllers are quoted with varying export tools, licence terms and integration levels, and those differences only matter at the first failure or replacement. Asking about them up front is what gets a farm that owns its programs.
Specifying or replacing controllers? For RFQ or project consultation, send: number of controllers and houses served; control duties (dosing, irrigation triggers, alarm escalation); existing controller models and integration needs; whether program files, tools and licences transfer at handover; backup tooling wanted; spares ratio; delivery schedule; and the budget band. G AND N FORTUNE LIMITED supplies fertigation and climate control packages quoted to those parameters.
Planning a Hydroponic Project?
Need help choosing a growing system or equipment? Tell us about your project requirements.



