Repository navigation
Restow 0.4.1
Restow 0.4.1. Released 2026-10-16, channel beta.
Beta release. Run it alongside your existing backups, not as your only one, until
you have verified restores against your own data.
Summary
Restow 0.4.1 counts the restic repositories of machines, file shares and Proxmox VE
containers in the stored bytes, instead of the chunk store alone, and says when a running
container backup shows no progress because its node runs an older restow-pve. One database
migration.
Breaking Changes
None. physicalBytes of GET /status and of usage in GET /storage now include the
restic repositories (see Fixed); the fields and their types stay.
Added
None.
Changed
- Repositories › Usage: the chart is called "Chunk store per day", and its note says that
the restic repositories keep no history and are not part of the growth.
Fixed
- Repositories › Usage, the Stored tile of the dashboard, the statistics and
GET /status
andGET /storageof the API counted only the packs of the chunk store: a tenant with
10 GB of container backups saw "Stored 10.9 kB" and "0 B backed up". Stored now adds the
restic repositories of machines, file shares and Proxmox VE containers, and the usage card
shows how much of it is in the chunk store and how much in restic repositories. The
deduplication saving, the growth and the chart stay figures of the chunk store, and say
so; "Protected data" names the sources it does not include instead of "No completed
backup yet". The dashboard tile lists the repositories on a line of their own instead of
"0 B backed up". - The size of a container's restic repository was not recorded. The restic route now
measures it once at the first upload after the update, then counts every upload and
deletion, and the worker measures it again after a prune. A view never lists a
repository (it may live on NFS). - A running container backup on a node with restow-pve before 0.4.0 showed "No progress
reported yet" for its whole run. It now says that progress needs restow-pve 0.4.0 on that
node, which version the node runs, and to update the node. - restow-pve asked for an update only six hours after it started, so a restarted node kept
an old version for hours. It now asks two minutes after the start, then every six hours;
the update still waits until no backup or restore runs.
Security
None.
Upgrade Notes
New image and one database migration, 0052_pve_guest_repository_bytes
(pve_guests.repository_bytes and repository_measured_at), which runs in seconds. No new
required environment variables, and the docker-compose.yml of 0.4.0 stays.
- The repository of a container counts under Stored from its next backup on, of a machine
or file share as before (from its next backup or retention run); until then it counts as
zero. - Nodes pick up restow-pve 0.4.1 by themselves, within two minutes of their next start or
within six hours, while no backup runs. - Rollback: the migration only adds two columns; 0.4.0 runs with them.
Known Issues
- A repository's size has no history: the statistics count the current size of a restic
repository at every moment of a period since its machine, share or container was added,
so the growth of Stored there comes from the chunk store only. - Uploads that finish while the first measurement of a repository lists it may be left out
until the next prune or retention run measures it again. - "Protected data" still counts the chunk store's sources only; the logical size of
restic backups is not added up. - The known issues of 0.4.0 still apply.
Verification
Before the tag, on the release branch (main plus the 0.4.1 fixes): lint and typecheck of
all workspaces, the server installer tests (679), gofmt, go vet and the Go tests of the
agents, and the full unit and Postgres suites on Postgres 16: packages/db 195, packages/i18n
273, packages/core 2311 (6 skipped), apps/scheduler 73, apps/api 3816 (5 skipped), apps/web
4124, apps/worker 529, ee/api 247, ee/licensing 59, ee/web 176, ee/worker 5, packages/cli
34, the demo seed 208; 141 Postgres test files, none skipped. A container backup with the
real restic binary checked the size the restic route counted against the repository. The
re-measurement after a prune ran in no test with a real repository. The release smoke runs
in the release pipeline; no Microsoft 365 tenant was used before the tag.
Release pipeline, 2026-10-16:
| Check | Result | Duration |
|---|---|---|
| 1. Install: images, compose up, migrations (new install and upgrade) | PASS | 91s |
| 2. Health endpoints, worker and scheduler registered | PASS | 0s |
| 3. Passkey sign-in E2E with a virtual authenticator, tenant creation, i18n de/en | PASS | 2m 08s |
| 4. Microsoft 365 backup and restore against the dev tenant | SKIPPED | 0s |
| 5. IMAP backup and restore against Dovecot, hash comparison | PASS | 9s |
| 6. Journal receipt, chain verification, export | PASS | 3s |
| 7. Standalone restore with restow-restore from the storage of check 5 | PASS | 24s |
| 8. Storage targets: S3 (Garage), local path, mounted directory | PASS | 19s |
| 9. Image scan (Trivy) and dependency audit (pnpm audit) | PASS | 18s |
| 10. Endpoint backup: the agent enrolls, backs up a folder, restores it | PASS | 11s |
| 11. Mail import (folder and upload) and export (EML ZIP, MBOX), compared by hash | PASS | 8s |
| 12. File share backup against Samba: back up, browse, ZIP, restore with permissions, copy job | PASS | 2m 19s |
11 of 12 checks passed in full, 0 partly, 1 skipped, 0 failed. The full report, including the reason for every skipped or partial check, is attached to the release as smoke-report.md.
The Community images were smoke-tested on their own (smoke-report-community.md, smoke-report-community-arm64.md): amd64 PASS with gaps: 9 of 12 checks passed in full, 0 partly, 3 skipped (see the reasons below); arm64 PASS with gaps: 9 of 12 checks passed in full, 0 partly, 3 skipped (see the reasons below).
Images
Two builds of the same release. The full build is the Apache-2.0 core plus the Business and Service Provider modules (Restow Enterprise License), which stay locked until a license key is installed. The Community build is the Apache-2.0 core alone.
ghcr.io/restow-backup/restow:0.4.1
ghcr.io/restow-backup/restow-web:0.4.1
ghcr.io/restow-backup/restow-community:0.4.1
ghcr.io/restow-backup/restow-web-community:0.4.1
The digests of the multi-arch manifests (the opt-in updater verifies the pulled images against the two lines of its build):
restow: sha256:faef86f33a34799b56f302cd78ad060d1e4b9d95bc9dd7140ca9cd7ed204762a
restow-web: sha256:44dbff44a0853d2f377b1f7dd46bd1061faae9475f076991d5094cb6d04edb85
restow-community: sha256:60f14820f9010511ff21325de9d5d4864ac926d56869f9d9a5d54b659ab418e3
restow-web-community: sha256:ff97f51aded5639e6b983d35ab5718cb93d2ad7216daab3dde4ee7a40067fa11
All four images are multi-arch (linux/amd64, linux/arm64), signed with cosign (keyless) and carry an SPDX SBOM as attestation. Verify any of them with:
cosign verify ghcr.io/restow-backup/restow:0.4.1 \
--certificate-identity-regexp '^https://github.com/restow-backup/restow/\.github/workflows/release\.yml@refs/tags/v' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
cosign verify ghcr.io/restow-backup/restow-web:0.4.1 \
--certificate-identity-regexp '^https://github.com/restow-backup/restow/\.github/workflows/release\.yml@refs/tags/v' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
cosign verify ghcr.io/restow-backup/restow-community:0.4.1 \
--certificate-identity-regexp '^https://github.com/restow-backup/restow/\.github/workflows/release\.yml@refs/tags/v' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
cosign verify ghcr.io/restow-backup/restow-web-community:0.4.1 \
--certificate-identity-regexp '^https://github.com/restow-backup/restow/\.github/workflows/release\.yml@refs/tags/v' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
docker-compose.yml and env.example are the release stack (deploy/release/); install.sh installs it on a dedicated Linux VM (README.md, "Install with the script"; install.sh.sha256 for sha256sum -c after the download); restow-agent-THIRD_PARTY_NOTICES.txt holds the licenses of the agent binaries and of the restic they run; SHA256SUMS lists every file of this release and is signed (SHA256SUMS.sigstore.json).