Backups, restore and upgrades

Admin 5 · 3:28

A backup of Weik.io, checked against its manifest, restores one deleted document or the whole installation, 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 the archive 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 from the archive, 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 2026.2.1
$ weikio-backend doctor
$ weikio get agents --behind

Transcript

0:01This video covers backups, restore and upgrades for your Weik.io installation.
0:10The drawing shows the installation as Admin video 3 left it.
0:15Agent dev runs hello in devtest at the hub.
0:18Agent fi-01 runs the same deployment in production at the site.
0:26Backups come from weikio-backend backup, the backend's command on the hub host.
0:32It writes an archive into a folder you name.
0:36ls backups lists the archive in the backups folder.
0:42manifest.json is the only file not sealed.
0:46The master key and the operator seed stay out of the archive.
0:52weikio-backend restore only checks the archive.
0:57The archive opens with the master key and matches its manifest.
1:03weikio delete variable sandbox/erp-url for environment devtest asks for a yes,
1:11then deletes the variable.
1:13The erp-url chip greys, then leaves the devtest band.
1:17weikio get variables for devtest says none are left.
1:24weikio-backend restore document brings the variable erp-url back.
1:29erp-url was gone, so a new record takes the archive's value.
1:35weikio-backend commands write as system:operator.
1:41Every change lands in the audit log under Settings.
1:44The rows read Restored variable, Deleted variable and Took a backup.
1:53A full restore starts with the master key and operator seed in place.
1:58The stack stops, then the message storage empties.
2:02weikio-backend restore fills that empty storage from the archive.
2:07The hub is back at the time this backup was taken.
2:09weikio status sandbox/hello shows hello running again.
2:18weikio version prints the release the Weik.io CLI and the installation run.
2:25upgrade describe lists the steps an upgrade from one release to the next would run.
2:33upgrade.sh lives beside the stack, written by weikio-backend init.
2:40The script runs as root, after a backup of the installation.
2:46A check only lists the files the upgrade would write.
2:51weikio-backend doctor names the release that wrote this stack.
2:57weikio get agents says no agent is behind the release.
3:04Every part on the Health page is online.
3:11You now have a verified archive of the hub.
3:13One document came back from the archive, then the hub.
3:17The hub and its agents run the same release.