Underneath the backup
Read this right after A backup and an export. Every command here reads; none changes the cluster.
$ shc config get backup.repo/var/backups/shc/repoThe setting is one path for the whole cluster, and each node opens its own repository at that path. home01’s holds the snapshots:
$ ls -1 /var/backups/shc/repoconfigdataindexkeyslockssnapshots$ ls -1 /var/backups/shc/repo/snapshots...It is a restic repository, encrypted with the key shc init sealed in the
vault. placed has two backups:
$ shc backup ls -s placedID STATUS SIZE BYTES TIMESTAMP POINT IN TIME VERIFIED ENCRYPTION NAME TENANT STACK ENVIRONMENT DATA SCOPE LOCATION VERIFIED AT VERIFY SUMMARY RESTORED AT20261104T182653Z_b451d2e889032469 completed 29626430 2026-11-04 18:27:01 assured - restic pre-restore-20261104T182632Z_a2bacb2dfd730027 prod placed prod unknown restic:/var/backups/shc/repo:737d012a7d9c5d3fbea45935e06cd7c2160856dd71b279b03e34fd20e288ac95 - - -20261104T182632Z_a2bacb2dfd730027 completed 29625366 2026-11-04 18:26:42 assured manifest restic kept prod placed prod unknown restic:/var/backups/shc/repo:1d5090f8b54d9646d67f6d95ffb7dae60fd1af755cf9a240814a2bbadae9f352 2026-11-04 18:26:49 the snapshot is present in the repository; its sealed container's member table accounts for all 29625366 bytes the repository records; its in-repo manifest reads back and names this backup; it holds 1 data subject: pgdata, totalling 29597696 bytes; 1 declared by the deployment; 29608448 bytes total including deployment metadata 2026-11-04 18:27:13The second row is the backup from the last page. The first is the one the
restore took of placed before it restored, named pre-restore- and the id
it restored. If the restore had gone wrong, that backup would bring back the
state before it.
Next: Nextcloud on Postgres.
shc@docs:~$