Update and backup (admin)

For administrators: how to update Probe and what needs backing up — and why the ODB database is re-creatable.

View as Markdown (for AI/KB) Whole knowledge base (llms.txt)

This page is for the administrator.

Update

Probe is updated by unpacking a new release into the same install directory (in place). That’s why the version-neutral directory matters — see Probe on Windows. For the Docker path you pull new images and restart the stack.

What needs backing up

Probe’s ODB database is derivable — it can be re-created by re-ingesting the source material. So in some setups it’s deliberately left out of the routine backup. What you don’t want to lose is what’s not re-ingestable: review decisions, observations, concerns, uploaded datasheets and your own guides/standard packs.

Before a major change

Before an upgrade or a move: stop Probe cleanly, move the whole install directory if needed (the configuration comes with it), and re-point the service at the new location. Then start.


Related: self-hosted with Docker and change log and audit.

Probe is E-Sharp’s design-review engine.

Book a demo of Probe

Show us your board — we review it and go through the findings together.

Prefer to email? info@esharp.se