Back up and restore a server’s stored state.
The runtime exports its stored state as a backup document and imports it back. Each backup is composed of named sections — access-control policies, presets, and whatever else the host and its plugins register. You choose which sections to export and which to import; nothing is all-or-nothing.
List the sections
See which sections are registered and can be exported or imported.
Export
Export the named sections as a backup document. The document prints to stdout — redirect it to a file to save it. --section is repeatable.
Import
Import selected sections from a backup document file. Name each section to apply; a section in the file that you do not name is left untouched.
Importing a section applies its payload over the live state. Export the current state first so you have a document to roll back to, and import only the sections you mean to overwrite.
manifest or env section applies live and fleet-wide: the import runs the same mutation pipeline a config change does — validate, persist, reload the calling process, then broadcast on the worker bus. The import report carries the per-origin fleet report of that reload, so a worker a restore did not reach is named rather than hidden.
See also
