Skip to content
Weik.ioUniversity
Try Weik.io

Backups, restore and upgrades

Admin 5 · 3:31

A backup of the hub, checked against its manifest, restores one deleted document or the whole hub, and an upgrade starts with a backup. The video continues from Admin 3.

Download the mp4Recorded on 2026.2

What it covers

  • A sealed backup archive from weikio-backend backup on the hub host
  • Checking every file against its manifest with weikio-backend restore --verify-only
  • Restoring the deleted variable erp-url alone with weikio-backend restore document, and its audit row
  • Restoring the whole hub on a fresh host, with hello running again in both environments
  • The upgrade steps between two releases with weikio-backend upgrade --describe, and the stack's upgrade script
  • Checking the release with weikio-backend doctor and the Health page

Commands in this video

Terminal
$ weikio-backend backup --to backups/hub-2026-10-24
$ ls backups/hub-2026-10-24
$ weikio-backend restore --from backups/hub-2026-10-24 --verify-only
$ weikio delete variable sandbox/erp-url --env devtest
$ weikio get variables --env devtest
$ weikio-backend restore document --from backups/hub-2026-10-24 variable/erp-url@devtest --project sandbox
$ weikio-backend restore --from backups/hub-2026-10-24
$ weikio status sandbox/hello
$ weikio version
$ weikio-backend upgrade --describe 2026.2.0-rc.5 2026.2.0-rc.6
$ weikio-backend doctor
$ weikio get agents --behind
Transcript
  1. 0:01This video covers the hub as its software moves on.
  2. 0:09The drawing starts as video three left it.
  3. 0:11hello runs on dev and on fi-01.
  4. 0:15The video shows what a saved copy holds.
  5. 0:18A lost piece or the whole hub comes back.
  6. 0:24The backup is the backend's own command,
  7. 0:27typed on the hub host where the backend runs.
  8. 0:30The archive stands in the hub host's backups folder and holds the configuration,
  9. 0:35the built bundles, the audit log, the agent records and the keys.
  10. 0:41Every file but the manifest is sealed with the master key.
  11. 0:45The master key and the operator seed are never in the archive.
  12. 0:50The check changes nothing.
  13. 0:52Every file is read back and matches its manifest.
  14. 0:58The variable erp-url of sandbox is deleted by mistake.
  15. 1:03The reply says the variable is deleted.
  16. 1:06weikio get variables reads the list back.
  17. 1:10The answer says sandbox has no variable in devtest.
  18. 1:15One document comes back alone.
  19. 1:17The backend opens the archive and writes this document back.
  20. 1:21The reply reports a new record, and the chip is back.
  21. 1:30It carries the archive's value, updated by system:operator.
  22. 1:36The audit log holds the hub's record.
  23. 1:39The newest row reads Restored variable in devtest.
  24. 1:45A fresh host starts with the master key and operator seed.
  25. 1:50The rest ran here off camera.
  26. 1:53The block prints the time and the parts restored.
  27. 1:57What the hub stored after the backup is gone.
  28. 2:00weikio status reads both deployments.
  29. 2:03hello runs in devtest and in production again.
  30. 2:12A release is the version the hub and agents run.
  31. 2:15Both rows read release candidate 6.
  32. 2:19The backend's command names an upgrade's steps.
  33. 2:22Between release candidate 5 and 6, no upgrade step runs.
  34. 2:30The stack carries its own upgrade script.
  35. 2:32It runs as one command on the hub host, after a backup.
  36. 2:37The panel compares a hub that release candidate 5 wrote against release candidate 6's images.
  37. 2:43Nothing was written.
  38. 2:51Doctor's row names release candidate 6, the release that wrote this stack.
  39. 2:56No agent matches, so no agent is behind.
  40. 3:02The Health page lists the hub's parts.
  41. 3:05The backend row stands Online with release candidate 6.
  42. 3:13The backups folder holds the checked archive.
  43. 3:16The lost document came back.
  44. 3:18One restore brought the whole hub back.
  45. 3:21A new release starts with a backup.