Definition
A config backup is a saved copy of an ASIC miner's working settings: its pool URLs and worker credentials, network configuration, fan and tuning parameters, and any web-UI passwords. Keeping one means that after a factory reset, a reflash, or a board swap you can return the unit to its known-good state in seconds instead of re-typing every value and risking a transcription error.
How to capture and restore it
Most stock and third-party firmware expose a backup option in the miner web UI, typically under a System or Backup page, that downloads the configuration as a file. Many firmware flashing flows also offer a "keep settings" checkbox that preserves config across an upgrade. When you flash an image that wipes settings, restoring the saved file rewrites pools, network, and tuning in one step.
Why it belongs in your runbook
The most common moment operators wish they had a backup is right after recovery: a unit comes back from SD card flashing with default settings and no pool configured. For a small fleet, exporting each unit's config once and storing the files off-device turns a stressful manual rebuild into a one-file restore. Re-export whenever you change pools or tuning so the backup stays current.
See our firmware update guide for where the backup and keep-settings options live across common firmware builds.
In Simple Terms
A config backup is a saved copy of an ASIC miner’s working settings: its pool URLs and worker credentials, network configuration, fan and tuning parameters,…