Skip to content

Restow 0.4.0

Choose a tag to compare

@github-actions github-actions released this 16 Oct 11:20
· 221 commits to main since this release
v0.4.0

Restow 0.4.0. Released 2026-10-15, 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.0 backs up SMB and NFS file shares from the server, without an agent on the
file server, and restores them with their permissions. It adds a notification matrix per
channel and event, shows the progress of running Proxmox VE backups, lets an update wait
for or cleanly stop the backups in progress, and moves the database to another disk from
the web interface. It adds immutable backups (S3 Object Lock per repository, a deletion
delay for directories), ransomware detection on every new restore point with a retention
hold while a finding is unresolved, boot tests and file restore (Preview) of Proxmox VE VM
restore points, backup and restore of SharePoint Online sites, agent policies, and file
restore for the restore role. S3 endpoints saved from now on must use HTTPS. Seventeen
database migrations run at start; file share backup and the database move need the 0.4.0
docker-compose.yml (run the 0.4.0 installer again after the update, see Upgrade Notes).
SharePoint needs an added permission and a new admin consent per tenant.

Breaking Changes

Nothing stops working on update: existing compose files, webhooks, notification
recipients, API clients and agents keep working as before. What behaves differently:

  • Notifications follow the matrix. Every channel (the bell, each webhook, each
    notification recipient) now keeps the events it gets, and an alert rule no longer sends
    an event to a channel whose column has it off. Migration 0038 fills every column with
    exactly what the channel received before, so nothing changes on update. Afterwards:
    • The webhook dialog no longer has an event picker. Choose a webhook's events under
      Integrations › Notifications.
    • A webhook created after the update (in the interface, or through the API without
      events) starts with the defaults of its format: a Discord, Slack or Teams webhook
      gets errors and warnings, a signed JSON (restow) webhook everything. A rule that
      sends other events to it delivers them only once they are switched on in the matrix.
    • The webhook stream keeps its event names (job.failed, job.completed,
      verify.completed) and payloads. backup.succeeded is the matrix's name for what the
      stream calls job.completed (an alias, not a rename); a webhook subscribed to
      job.completed keeps getting it. events on create and update still means the
      subscribed stream events; the session API also returns the webhook's column as
      notifyEvents.
    • The four flags of a tenant's notification recipients (notify_job_failures,
      notify_weekly_report, notify_readiness_red, notify_license_updates) are replaced
      by an event list. The tenant API still accepts and returns categories; a recipient
      now also carries events. "Licence and update notices" never sent anything and is no
      longer returned. Only scripts that read these columns from the database directly need
      a change.
  • New installations start the mounter. install.sh now starts the mounter (compose
    profile mounts, it holds the Docker socket) by default, because file share backup runs
    through it. Scripted installations that do not want it pass --no-mounter (or
    --without-mounter). Running the installer again on an existing installation keeps that
    installation's choice.
  • Installer guard. Once the database was moved to another disk, install.sh refuses
    (exit code 8, nothing changed) to put in place or start a docker-compose.yml that does
    not read RESTOW_POSTGRES_DATA from .env, so an older release file cannot start the
    stack without its database.
  • Building from source needs Node.js 22.12 or newer (engines in package.json;
    commander 15 requires it). The Docker images run on node:22-slim as before; nothing
    changes for Docker installations.

Added

Unless marked otherwise, everything below is part of every edition (the Community core).

File shares (SMB and NFS)

  • File share backup, in the menu next to VMs & containers. Restow mounts an SMB share
    (Windows Server, Samba, a NAS) or an NFS export read-only for the length of one run, in
    a short-lived runner container started by the mounter, and backs it up with restic into
    a repository of its own (file-shares/<share id>/ on the tenant's primary repository).
    No agent on the file server, and the api and the worker are never restarted. NTFS
    permissions (and NFSv4 or POSIX ACLs, best effort) are kept in each restore point. Open,
    unreadable and offline files are skipped and listed in the run, which then ends "with
    warnings". SMB 2.1 to 3.1.1; SMB1 and NTLMv1 are refused. Requirements (the mounter, the
    cifs module or the NFS client on the Docker host, the ports, the account) are in
    docs/FILESHARES.md.
  • Add file share tests the connection and whether permissions are readable; the
    password is sealed with the tenant key and never shown again. Backup jobs of the kind
    File shares: schedule (at most hourly), folders, file types to skip, retention
    (daily, weekly, monthly). Tenant admins manage their own shares; a share on a private or
    loopback address needs a provider admin's approval or the installation switch Tenants
    may use private networks
    .
  • Restore from a restore point (browse, search, versions): download as ZIP, restore to
    a new folder, to the original location (overwrite, keep both, skip) or into another
    share, with permissions where the target allows it. Restores into a share need Allow
    restore to this share
    on it (off by default).
  • Restore checks: every new restore point is checked by reading up to 20 sampled
    files back and comparing them, and the repository gets a weekly restic check of 5 % of
    its data; Recovery readiness rates a share by its newest restore point. A restore check
    of a restore point without samples (every file changed in the hour before the run) rates
    yellow and says why.
  • Copy jobs: on a schedule, the newest restore point of share A that passed its restore
    check is written into a folder of share B, in mode overwrite or mirror (mirror
    deletes only inside that folder; refused into a share root or the source share, and
    stopped when the restore point has fewer than half the files of the last copy). A copy
    job keeps no versions and is labelled as not being a backup.
  • Budgets per share, per tenant and as a default (off by default; provider admins): a
    warning at 80 %, no new backups at 100 %.
  • File shares count in the status tab, the start page, Recovery readiness, warnings,
    History, the statistics and the provider view, with the alerts
    file_share_backup_failed and file_shares_without_job.
  • Enable network shares (Installation › Default repository & network shares, and the
    notice on the File shares pages) starts the mounter of an existing installation through
    the opt-in updater, for the provider owner, with a recent sign-in and an audit entry.
    File share runners, on the same page, sets how many runs go at a time and the memory per
    run.

Immutable backups

  • Immutability per repository, on each repository's card (Repositories › Change
    immutability
    ), off until an administrator turns it on. What is locked: packs,
    committed manifests and wrapped keys of the chunk store (Microsoft 365, IMAP, Proxmox VE
    disks) and the data/, snapshots/, keys/ and config objects of every restic
    repository (machines, file shares, Proxmox VE containers). Not locked: checkpoints,
    staging, exports, downloads, restic locks/ and index/ files (restic repair index
    rebuilds the index from the locked packs). See docs/STORAGE.md, "Immutable backups".
  • S3 Object Lock (compliance or governance, 1 to 3650 days): turning it on checks
    the bucket's Object Lock configuration and refuses a bucket without it. Every locked
    object is written with a retain-until date of the period plus 7 days; the daily retention
    job renews the lock of every object still in use once the last complete renewal is 6
    days old, so data that new restore points reuse stays locked for at least the period.
    A renewal that was interrupted continues where it stopped. Retention, garbage collection
    and restic prune treat a deletion the storage refuses as "not yet": the restore point
    stays visible and restorable, and space comes back once the lock has run out (up to the
    period plus 7 days later). Restow never sends the governance bypass header.
  • Deletion delay for directories (the Docker volume, an NFS share): Restow's own code
    refuses to delete or overwrite a locked file until the period has passed since it was
    written. It protects against misuse of Restow (a stolen administrator account, a
    retention policy shortened to delete restore points), not against someone with access to
    the server or the share, and the interface says that it is not immutability.
  • Verification: the daily retention job and Verify now ask the storage for the
    retention of a sample of recent objects; objects without a lock or in a weaker mode, a
    renewal that is overdue or failed and deletions waiting for their lock are shown on the
    repository card, the dashboard's storage tile and, as immutability_warning, in the
    provider view. Restore points of the restore explorer and of a machine show "Immutable
    until ", green only for a COMPLIANCE retention the storage itself reported.
  • Who may change it: raising the protection is open to whoever may configure the
    repository; lowering it (fewer days, a weaker mode, off) is for the provider owner with a
    sign-in from the last ten minutes and applies only to data written from then on. Every
    change and verification is audited (storage.target.immutability_changed).
  • What it protects against: an attacker on the Restow server, someone holding Restow's
    storage key, a stolen administrator account, a shortened retention policy. What not:
    someone who controls Restow can stop new locks and the renewal (what is locked stays
    locked until its date); a GOVERNANCE lock is lifted by any account with
    s3:BypassGovernanceRetention; delete markers and newer versions can hide locked data
    (the locked versions stay and can be brought back); the master key is not in the bucket.

Ransomware detection

  • Every new restore point is judged for signs of ransomware from data the backup
    already has, every two minutes, for runs of the last 72 hours: the amount of change
    (new and changed files, bytes added) against the object's own history, mass deletions,
    renamed extensions, known ransomware extensions and ransom notes (versioned lists,
    matched on the server), the entropy of sampled new files, and the compression and
    deduplication ratio of the run's new data. The signals apply per kind of object:
    machines, file shares, Proxmox VE containers and VMs, mailboxes, OneDrives, SharePoint
    sites and IMAP accounts (deletions, renames, names and entropy exist only for machines,
    file shares and OneDrives). A signal without data says "not
    available", never clean. It never reads the data a second time, never blocks a backup
    and is no virus scanner. See docs/RANSOMWARE.md.
  • Suspicious badge (red) on the restore point and the object in every restore view;
    when the newest restore point is suspicious, the restore views offer the newest one
    without findings. A click shows each finding with its numbers and the state of every
    signal.
  • False alarm: technicians and administrators mark a finding as a false alarm with a
    note, or take it back (audited, suspicion.false_alarm, suspicion.false_alarm_revoked);
    the restore point then counts as clean and joins the baseline.
  • Retention hold: while an object has a suspicious restore point nobody resolved,
    retention, restic forget and prune delete no restore point of that object, so clean
    older restore points are not pruned while encrypted ones pile up. Backups go on and
    quotas still apply. Only an administrator ends a hold, never a later clean restore point:
    Mark as false alarm, or Release hold (administrators, recent sign-in, audited
    suspicion.hold_released). The object shows "Retention paused" until then.
  • Notifications: backup.suspicious (error, once per attack episode, says that
    retention is paused) and backup.suspicious_hold (warning, when a hold is still open
    after 14 days and every 14 days after), in the bell, the rules and the webhooks.
  • Installation › Ransomware detection: the thresholds of every signal, each signal's
    switch, the retention hold's switch and its reminder days (settings.ransomware.updated;
    the provider owner changes them, every provider admin reads them).
  • The activity report (deletions, renames, names, entropy) needs the endpoint agent 0.4.0
    on machines; the compression signal needs the agent 0.4.0 on machines and restow-pve
    0.4.0 for containers. File shares get it with the 0.4.0 runner, VMs and Microsoft 365
    objects with the server.

Notifications

  • Notification matrix under Integrations › Notifications (#76): the events as rows,
    grouped and marked by severity; the bell, every webhook and every notification recipient
    as columns, each with the quick choices "Errors only", "Errors and warnings" and "All".
    Saving is written to the audit log (report.matrix_updated). Installation events (an
    update is available, low disk space) are rows for provider admins only.
  • New events backup.succeeded and verify.completed for mail and the bell (off in the
    bell by default), and installation.disk_low (see Updates and the database).

Proxmox VE

  • Progress of a running backup (#51): VMs & containers, the inventory and the guest's
    page show a progress bar ("34% · 3.2 GB of 9.4 GB · 85 MB/s"). Needs restow-pve 0.4.0 on
    the node; a backup of an older helper shows "No progress reported yet".
  • The helper's own lines in the run's log (#61): the run id, what restic added, what it
    could not read and the commit of the restore point now reach the log Restow keeps for the
    run. A backup that succeeded with gaps names the items restic could not read (the first
    20).
  • Proxmox VE jobs in Servers & clients › Jobs (#53), next to the machine jobs with a
    Type column: guests per job, schedule, last and next run, "2 of 5 guests done" while a
    round runs, and a backup started by hand as a row "Manual backup · " until it
    ends. New job is a menu with one entry per type; the Proxmox VE job form lists the
    VMs and containers to put into the job.
  • Create recommended job (#52) next to every "no job" notice (jobs, inventory,
    sources, directory, VMs & containers) and "Protect everything without a job" on the
    dashboard's readiness card: a preview of what the click creates or adds to, then one
    job per kind (mail every 8 hours; machines per system and profile; one Proxmox VE job,
    daily at 22:00 in snapshot mode). A second click adds to the same job instead of making
    another. Admins only; recorded in the audit log.
  • Files of a container in Servers & clients › File restore (#62): every container with
    a restore point is listed in the group "Proxmox VE containers"; browse a restore point
    and download files and folders as one ZIP, read by the server from the container's
    repository. The guest page links each container restore point there (Browse files).
    Reads and downloads are in the audit log.
  • Files of a VM in Servers & clients › File restore (Preview): VMs with a restore
    point are listed in their own group "Proxmox VE VMs", marked Preview, and the guest
    page links them (Browse files). Each readable file system of the VM's disks is a
    folder (scsi0-p2, vg0-root): partitions of GPT and MBR disks and linear LVM logical
    volumes with ext2, ext3, ext4 (the journal replayed in memory), XFS, NTFS or FAT12/16/32.
    Browse and download files and folders as one ZIP; files that cannot be read are named in
    _not-restored.txt inside it. The server reads the disks from the tenant's chunk store
    with its own user-space readers in a short-lived, restricted child process; nothing is
    mounted, on the server or on the node. Not readable: btrfs, ZFS, ReFS, LVM thin, RAID,
    BitLocker and LUKS, NTFS-compressed and EFS files; the XFS log and NTFS's $LogFile are
    not replayed. Same routes, roles and audit actions as for containers (with kind: "vm").
    The volume list asks to compare an important restored file with the original before
    relying on it. See docs/PVE.md, "Files of a VM".
  • Boot tests of restore points: a Proxmox VE job can boot the newest restore point of
    each guest weekly or after every backup (off by default; a memory limit, default 8 GiB,
    and a wait for the guest agent, default five minutes), and Boot test now on a restore
    point asks for one by hand. The guest's node restores it as a new guest in the pool
    restow-restore, isolates it before the start (every NIC link_down=1 or an isolated
    bridge, passthrough devices, serial ports, bind mounts and the hook script removed),
    starts it, waits for the QEMU guest agent (a container: its init) and destroys it in
    every case; leftovers are removed when the service starts. One test per node at a time,
    never beside a backup, and only with enough memory and storage. Green when the guest
    agent answered, yellow when the VM only started, red when the restore, the start or the
    boot failed. Readiness rates the newest restore point by its boot test where there is
    one. New events boot_test.failed and boot_test.unproven. Needs restow-pve 0.4.0 on
    the node (restow-pve config --boot-tests, --boot-test-storage, --boot-test-bridge);
    the guest's page says when its node cannot. Requesting one is audited
    (pve.boot_test.requested). See docs/PVE.md, "Boot test".
  • A guest shows the average a follow-up backup adds (over the newest 10 restore points
    after the first backup) (#58).

Servers and clients

  • Data folders a job misses (#59): the endpoint agent 0.4.0 reports which of a fixed
    list of Linux data folders (/opt, /usr/local, /srv, /var/www, Docker and Podman
    volumes, the PostgreSQL, MySQL and MongoDB folders under /var/lib) exist and hold
    files, names only. The job editor names the folders the job's machines really have and
    leaves out, and a machine's page offers Add this folder to the job. With older agents
    the notice of 0.3.5 stays.
  • A machine's page says what it runs as (container, virtual machine, physical, with or
    without a desktop) (#59).
  • The file browser of a restore point says which folders it contains, with a link to the
    job's folders (#59). A machine's restore points say what they contain and what they
    added, like Proxmox VE guests (#58).
  • Agent policies for servers and clients, on three levels: the installation
    (Installation › Agent policy), the tenant (tenant page › Agents) and the backup job (the
    job editor). Each level may override a setting unless the installation locks it; every
    view says where a value comes from and whether it is locked. The settings: a backup
    window
    (weekdays and a time range, also across midnight, in the zone of the job's
    schedule) in which scheduled backups, catch-ups and retries may start (a running backup
    continues, Back up now ignores it); catch up missed backups as soon as the
    machine is on again or in the next backup window, optionally only up to a maximum age;
    the upload limit of a job without its own (a job can also choose Unlimited,
    which sets a policy's limit aside unless the installation locks it; a job whose limit is
    empty keeps inheriting); only on AC power; and the number of automatic retries
    (0 to 10). Without a policy agents behave exactly as before. The server writes the
    effective policy into each machine's configuration (a new configuration version) and
    audits every change (settings.agent_policy.updated, tenant.agent_policy.updated,
    endpoint.config.changed). The page of a server or client shows the policy that applies
    to it, each setting with its source (default, installation, tenant, backup job or the
    machine itself) and whether it is locked, read-only (restore operators see it too), and
    why a due backup waits next to the next planned start: for the backup window, for an
    update to finish, for AC power, or to catch up in the next window. The agent 0.4.0 sends
    that reason with its heartbeat (waiting); for an older agent the page shows none.
    Window, catch-up, retries and the waiting reason need the agent 0.4.0; the upload limit
    and AC power reach older agents too.
  • Agents respect the update pause (#46): while an update pauses new runs, the agent
    0.4.0 starts no scheduled backup, retry or catch-up and waits for the pause to end (the
    configuration and the heartbeat say startsPaused); the wait does not count as a missed
    or failed backup. A Back up now request stays queued on the server until the pause
    is over, also for older agents, and restow-agent backup-now on the machine waits with
    a message. restow-agent status shows the policy and why a due backup waits.
  • File restore for the restore role: restore operators (membership role "restore",
    tenant_restore) now open Servers & clients › File restore. They list the machines, read
    a machine's restore points and their immutability, browse them, download files as a ZIP
    and restore files onto the machine; for Proxmox VE they read the overview and a guest's
    restore points and browse and download files of container and VM restore points. Settings,
    tokens, jobs, backing up, verify and boot tests, restoring a whole guest, revoking or
    deleting and the repository password stay with the administrators (backing up answers
    403), and the web app leaves out the links to pages they may not open. Every read,
    download and restore is audited with the operator as actor.

Jobs, live view and dashboard

  • Running backups in the sidebar (#57): the Jobs entries and VMs & containers show a
    spinner with the number of running backups and the waiting ones beside it; the tooltip
    lists them, a click opens the run.
  • Live run drawer (#54): the charts move with time between measurements, the numbers
    count up, the time left counts down, and a line says when the run last reported (or that
    Microsoft Graph throttles it). The browser tab's title shows the percent while the drawer
    is open.
  • All tenants in Jobs (#63, Service Provider): under "All tenants", Jobs of Mail & SaaS
    and of Servers & clients list every tenant with its jobs per kind, what runs and waits,
    how the newest backups ended and the next run, with filters and sorting; a row opens the
    tenant's jobs read-only.
  • Storage growth on the dashboard (#64): 1 week, 1 month, 3 months or 1 year, from 3
    months on with the estimate as a band between the slowest and fastest growth, and when
    the repository runs full at this growth where its free space is known.

Microsoft 365

  • The first backup of a large mailbox shows "First backup: X of Y items" over all
    attempts, with an estimated time left (#47). A OneDrive shows "X items so far" until it
    is fully listed.
  • SharePoint Online sites: every directory sync finds the tenant's sites
    (/sites/getAllSites; sites of Microsoft 365 groups and Teams included, personal sites
    left to their owner's OneDrive), and each site is a protected object of its own, in the
    mail jobs like mailboxes and OneDrives. The protection rules have a sites mode: all sites
    (the default) or only the selected ones. A backup holds every document library (with the
    OneDrive engine: delta per library, optional versions, checkpoints), every list with its
    columns and each list item's field values as JSON, and the site's description; a library
    or list Graph refuses is reported and keeps its last copy. New sites get their first
    backup at once; a deleted site fails with graph.site_unavailable.
  • Restore of SharePoint sites in the explorer (libraries, folders, files, lists, items):
    download as ZIP; files and folders into the original library or another library of a
    backed-up site of the same source ("Keep both", "Overwrite" with SharePoint keeping the old
    file as a version, "Skip existing"); list items into their original list as new items,
    writable fields only. Restore checks sample library files like a OneDrive. Sites appear in
    the status, count as no protected mailbox, and are seen by restore operators and
    administrators only. Not backed up: Teams chats, attachments of list items, site design,
    navigation and workflows; permissions are kept as information and never restored. See
    docs/MICROSOFT.md, "SharePoint Online".

Updates and the database

  • Runs in progress during an update (#46): the install dialog counts what runs and
    waits in every tenant and asks: Stop them cleanly (the default: Microsoft 365 and
    mail runs save a checkpoint and stop, runs on agents and of file shares are waited for,
    30 minutes at most), Wait until they finish (two hours at most) or Do not wait
    (as before). From the confirmation until the update is over no new run starts;
    schedules that fall due meanwhile run afterwards. Everyone signed in sees a banner; the
    Updates tab shows what still runs, Start now and Cancel.
  • Installation › Database (#73): where the database keeps its data, its size, the
    free space under it and under the local default repository, and what the next update
    needs. With the opt-in updater, the provider owner moves the database to a directory on
    another disk: checked first (another local file system, ext4, XFS, Btrfs or ZFS, room
    for the data), then copied, compared file by file, test-started and switched, with
    automatic rollback on any failure. The old copy is kept and blocked from starting until
    it is removed. See docs/DATABASE.md.
  • Low disk space warning (#73): every 15 minutes the api checks the disk under the
    database (through the updater) and under the local default repository; below a tenth
    free, and always below 5 GiB, the provider admins get a notice in the bell, and rules
    that list "Low disk space" send it, once per episode.
  • Kept database dumps (#73): the Updates tab lists the updater's pre-update dumps; the
    provider owner can download one (one-time link, recent sign-in, audit log) or delete it.

API

  • Integration API contract 1.4.0 (additive): GET /api/v1/status has fileShares
    (counts of file shares) and the readiness summary sharesWithoutJob, and events is
    optional when a webhook is created. Nothing was removed or renamed.

Changed

  • Updates: the updater's preflight now adds up what an update writes (the dump, the
    images, room for the migrations, plus RESTOW_UPDATER_MIN_FREE_MB as a margin) and
    refuses an update that does not fit (blocker disk_space, with the numbers), instead of
    requiring a fixed 1 GB (#73).
  • A Linux machine enrolled with a client token whose agent (0.4.0) reports a container or
    a virtual machine without a desktop gets the server profile, because it runs services;
    the machine's page says why (#59). Existing machines keep their profile.
  • Adding a folder to a machine job narrows an exclusion of a parent folder: adding
    Docker's volumes turns /var/lib/docker into /var/lib/docker/* and
    !/var/lib/docker/volumes (#59).
  • Notification recipients: the categories in the tenant wizard and on the tenant page add
    or remove their events and leave everything else chosen in the matrix alone.
  • The live channel stays open while the tab is in the background (closed after ten
    minutes, or when the browser freezes the tab), so a page no longer reloads when you come
    back (#54).
  • Mailboxes and OneDrives are named by their person (display name, else address), not by
    their technical id, which moves to a tooltip (#55).
  • The sidebar's Installation section folds away to its header; the choice is remembered in
    the browser (#56).
  • A machine's danger zone reads "Stop backing up this machine" and says that nothing is
    deleted; revoked machines are hidden in the inventory until "Show revoked machines" and
    have their own group in File restore (#65).
  • The machine job editor says that Proxmox VE VMs and containers are backed up by Proxmox
    VE jobs, with links (#53).
  • Proxmox VE: sizes are named ("9 GB allocated"); "Waiting for the node" says since when,
    and turns amber while the node is disconnected.
  • Container backups on Proxmox VE (restow-pve 0.4.0) let restic scan before it backs up
    (no more --no-scan), so there is a total to show progress against.
  • docs/ARCHIVE.md explains what journaling captures and misses compared with the mailbox
    backup, and when to use which (#48).
  • Dependencies: major updates of the build and test tooling and of two libraries: vite 8,
    @vitejs/plugin-react 6, vitest 5, lucide-react 1.x, commander 15, archiver 8,
    @biomejs/biome 2.5.
  • Performance on large installations: the "All tenants" view of Jobs looks up each
    object's newest backup through an index, reads four tenants at a time and keeps each
    tenant's figures for 30 seconds for every viewer (the page refreshes every 15 seconds
    while something runs, else every minute); the sidebar's Proxmox VE badge asks a slim
    endpoint instead of the whole VMs and containers overview; the ransomware judgement
    reads new restore points through partial indexes, judges batch after batch for up to a
    minute per pass and logs restore points that leave its 72-hour window unjudged; the
    reconciler of left-behind jobs runs in one worker at a time; a heartbeat no longer
    rewrites the machine's settings when its facts did not change.
  • The file share search needs at least three characters of the name.
  • Performance with the largest workloads; memory now stays bounded whatever the size:
    • File share catalog: the first catalog of a share (or one after a gap) streams
      restic ls into the database in batches of 5,000 instead of holding every file in
      memory and writing it in one transaction. An interrupted pass stays pending and
      continues without duplicates.
    • SMB file share runner: the permission reuse streams the previous sidecar into a
      compact index (about 50 bytes per file instead of about 190), so incremental runs of
      shares with millions of files no longer run out of memory. Above a third of the
      runner's memory limit the run reads all permissions instead
      (RESTOW_SHARE_REUSE_MAX_ENTRIES overrides the limit).
    • SharePoint: a site run indexes the previous restore point once instead of scanning it
      for every list and library, so sites with thousands of lists and a million items no
      longer take quadratic time.
    • Proxmox VE: the block maps of VM disks being browsed or restored are cached by size
      (256 MiB by default, PVE_BLOCK_MAP_CACHE_MB) instead of by count.
    • Object Lock renewal sends 32 requests at a time instead of 8
      (IMMUTABILITY_RENEWAL_CONCURRENCY) and continues an interrupted pass where it
      stopped instead of starting over.

Fixed

  • A Proxmox VE backup running while Restow was updated failed: the node helper gave up
    after about 30 seconds, while an update restarts the api and runs migrations. The node
    (restow-pve 0.4.0) now keeps trying for five minutes (#46).
  • A Proxmox VE backup run whose end never reached the server stayed "running" for 48 hours.
    It is now closed once the node (restow-pve 0.4.0) no longer lists it in its heartbeat
    (#46).
  • restow-pve's own lines never reached the run's log in Restow: vzdump writes a backup
    provider's lines to the PVE task log only, not to the guest's log file (#61).
  • Jobs of a worker that was killed (not stopped) stayed "running" until they expired, 23
    hours for a backup, because nothing gave them back. The next worker now returns them to
    the queue two minutes after its start (#46).
  • A job stopped by a restart or an update before its first checkpoint used up one of its
    attempts, and on its last attempt the explanation said it would continue although its
    checkpoint was discarded (#46).
  • An update could fill the disk with its database dump and stop PostgreSQL midway, because
    the preflight only checked for 1 GB free (#73).
  • Adding /var/lib to a machine job, as the 0.3.5 notice offered, still left Docker's
    named volumes out, because the default exclusion /var/lib/docker covers them (#59).
  • The live run drawer's charts shrank to the last 80 seconds and grew back every ten
    seconds, because each live event replaced the run's measurements instead of adding to
    them (#54).
  • Notification mail through the backup's app registration from a tenant that never
    consented to it reported "app not found" and asked to check IDs that were right. It now
    says that consent is missing in the sender's tenant and links the admin consent.
  • The update dialog's confirm button was enabled while the runs in progress were still
    being read, so a quick click announced the update before the admin saw them. It now
    stays disabled until they were read (or reading them failed).

Security

No vulnerability was fixed. Security-relevant changes:

  • Database dumps can be downloaded from the Updates tab. A dump holds the whole database,
    the encrypted secrets included: provider owner only, with a recent sign-in, through a
    one-time link, recorded in the audit log. Keep a downloaded dump as carefully as the
    master key.
  • New installations start the mounter by default, which mounts the Docker socket (root on
    the host); read docs/MOUNTS.md, or install with --no-mounter. File share runners have
    no network but an internal one to the api, and write with a credential that is valid for
    one run and append-only.
  • Tenant admins can add file shares themselves; shares on private or loopback addresses
    need a provider admin's approval or the installation switch.
  • Browsing and downloading files of a Proxmox VE container are recorded in the audit log
    (pve.snapshot.browsed, pve.snapshot.downloaded); a prepared download can be started
    once, within ten minutes, by the admin who prepared it. The same holds for files of a
    VM (kind: "vm"), which a reader in a restricted child process reads without mounting
    anything (threat model in docs/PVE.md).
  • S3 endpoints need HTTPS. A new or changed S3 endpoint over plain http:// is refused
    (endpoint_insecure), for provider admins and the installation default too, except to
    localhost, 127.0.0.1 and [::1]. Endpoints saved before and S3_ENDPOINT keep
    working; their card, Installation › Default repository and every test say in red that they
    should move to HTTPS. S3_ALLOW_INSECURE=true accepts plain HTTP for test and
    development setups only.
  • Restore operators can now browse, download and restore files of machines and of Proxmox
    VE guests (see Servers and clients); every read, download and restore is audited.
  • Lowering a repository's immutability and releasing a retention hold need a recent
    sign-in and are audited; lowering is for the provider owner only.

Upgrade Notes

New image, seventeen database migrations (0035 to 0051), and a new docker-compose.yml for
file shares and the database move.

  1. Update as usual (the opt-in updater, or docker compose pull && docker compose up -d).
    The api applies the migrations as it starts. With the updater, the install dialog now
    asks what to do with runs in progress; the default stops them cleanly.
  2. Run the 0.4.0 install.sh again in the installation directory (README.md). It replaces
    docker-compose.yml with the 0.4.0 file (checked against the signed SHA256SUMS), keeps
    the previous one as docker-compose.yml.bak-<timestamp> and leaves .env as it is.
    Without it everything else works, but file share runs cannot start (the mounter reports
    runner_network_missing) and Installation › Database cannot move the database. A
    compose file kept by hand needs the changes of the release file: the database volume
    read from .env, the internal runners network on the api, and RESTOW_MOUNTER_URL,
    the runner limits and the restow-mounter-shared volume on the worker.
  3. For file shares, start the mounter if it is not running: Enable network shares in
    the web interface (with the opt-in updater) or
    docker compose --profile mounts up -d mounter. The Docker host needs the cifs module
    for SMB and the NFS client for NFS.
  4. Proxmox VE nodes: restow-pve 0.4.0 updates itself (it checks every six hours and updates
    while idle), or run restow-pve update on the node. Older helpers keep working without
    progress, without the five-minute retry window and without the list of active runs.
  5. Servers and clients: the endpoint agent 0.4.0 updates itself unless the tenant paused
    agent updates. Older agents keep working without data folders, machine facts, the
    backup window, catch-up rules and retry count of an agent policy, and do not hold their
    own schedules during an update pause.
  6. Plain-HTTP S3 endpoints: a repository or default repository that uses http:// to a
    host other than the machine itself keeps working, but its card asks in red to move it to
    HTTPS, and changing its location needs https:// (docs/UPDATING.md). Test setups with
    an object store on the compose network set S3_ALLOW_INSECURE=true in .env (api and
    worker).
  7. SharePoint Online: the backup's app registration needs the application permission
    Sites.ReadWrite.All (Sites.Read.All is enough to back up, not to restore). Add it to
    the app registration, then the customer's admin opens the source's consent link again
    (docs/ENTRA-SETUP.md). Until then mail and OneDrive keep working, and the directory sync
    warns that sites are neither found nor backed up (sites_unavailable).
  8. Immutable backups with S3 Object Lock need a bucket created with Object Lock (and
    versioning); it cannot be added to an existing bucket. The access key needs
    s3:GetBucketObjectLockConfiguration, s3:PutObjectRetention, s3:GetObjectRetention,
    s3:ListBucketVersions and s3:DeleteObjectVersion, and should not have
    s3:BypassGovernanceRetention, s3:PutBucketObjectLockConfiguration or
    s3:PutBucketVersioning. Nothing is locked until an administrator turns it on.
  9. Ransomware detection is on after the update and judges backups of the last 72 hours; its
    retention hold is on as well, so a suspicious restore point pauses retention of its
    object until an administrator resolves it. Thresholds and both switches are under
    Installation › Ransomware detection.
  • Database migrations, in this order: 0035_file_shares,
    0036_backup_job_kinds_share_copy, 0037_backup_job_file_shares (file shares),
    0038_notification_matrix (it translates the recipient flags and webhook event lists of
    every tenant and drops the four flag columns), 0039_pve_run_progress,
    0040_recommended_jobs, 0041_pve_downloads (container downloads),
    0042_job_start_pause (the update pause), 0043_disk_alerts (the disk warning state),
    0044_pve_boot_tests, 0045_ransomware_detection, 0046_sharepoint_sites,
    0047_immutable_backups, 0048_suspicion_retention_hold (the release of a retention
    hold and its reminders, five columns on restore_point_suspicions), 0049_perf_indexes
    0050_agent_policies (the installation's and each tenant's agent policy,
    settings.agent_policy and tenants.agent_policy, both {}, which changes no machine's
    configuration) and 0051_agent_waiting (endpoints.agent_waiting, what a due backup
    waits for as the agent reports it; empty until an agent 0.4.0 reports). They change the schema and backfill only the notification recipients and
    webhooks, a few rows per tenant, so they should take seconds on any installation, except
    0049_perf_indexes below. They ran on a 0.3.6 schema in the Postgres test suites; they
    were not timed on a production-size database.
  • 0049_perf_indexes adds six partial indexes (jobs, endpoint_runs,
    file_share_runs, pve_runs, pve_tasks). Each build reads its table once while writes
    to it wait (the migrator cannot build them concurrently): seconds on most installations,
    about a minute per ten million rows on large ones (docs/UPDATING.md).
  • 0035 creates the pg_trgm extension for the file share search when the database role
    may; an external PostgreSQL without it searches more slowly, with the same results.
  • New optional environment variables: RESTOW_POSTGRES_DATA_TYPE and
    RESTOW_POSTGRES_DATA (where the database lives; empty means the volume pgdata; the
    updater writes them when it moves the database), RESTOW_MOUNTER_MAX_RUNNERS (hard cap
    of file share runners, default 8) and RESTOW_MOUNTER_RUNNER_MAX_MEMORY_MIB (default
    16384). No new required variables.
  • Downtime: the containers restart and the migrations run, as for 0.3.6.
  • Rollback: the migrations are not reversible; go back to 0.3.6 only with the database dump
    taken before the update. After a database move, keep a compose file that reads
    RESTOW_POSTGRES_DATA: the 0.3.6 file does not, and PostgreSQL then refuses to start on
    the old copy.

Known Issues

  • Not tested against real systems before the tag: a Proxmox VE node (progress, the
    helper's log lines, the five-minute retry window and the closing of dropped runs were
    tested against the simulated node of the test suites), the database move and the
    Enable network shares button through a real updater and its Docker helper container,
    and the new pages in a browser by hand (they are covered by component tests).
  • File shares were tested against Samba in the release smoke tooling, not against Windows
    Server (NTFS permissions, Backup Operators, a file kept open in Excel), a Synology or
    TrueNAS share, real NFS exports (NFS is not in the smoke check) or a host with SELinux
    enforcing.
  • File shares have no VSS over SMB (files open with an exclusive lock are skipped), no
    alternate data streams, DFS namespaces, Kerberos or SMB1; repositories live on the
    primary repository only; tenant users have no self-service restore of shares; scheduled
    reports have no file share block yet.
  • While an update waits or runs, agents older than 0.4.0 do not hold their own schedules:
    a backup such a machine starts by itself during that time runs, and may fail if the api
    restarts under it.
  • Files of Proxmox VE containers and VMs are downloaded as a ZIP; restoring single files
    into the running guest is not built. VM file restore is a Preview: btrfs, ZFS, ReFS,
    LVM thin, RAID, BitLocker and LUKS are not readable, and the XFS and NTFS logs are not
    replayed, so a crash-consistent restore point can lack the last writes; compare an
    important file with the original before relying on it.
  • Immutable backups, SharePoint Online, boot tests, VM file restore
    and agent policies were tested against simulated services only (a fake S3 with Object
    Lock, a simulated Microsoft Graph, a simulated Proxmox VE node), not yet against a real
    S3 service with Object Lock, a real Microsoft 365 tenant or a real Proxmox VE cluster.
    The ransomware signals were tested with simulated attacks, not with live ransomware.
  • Immutable backups: the installation default repository cannot be made immutable (give
    the tenant a repository of its own or an immutable copy); restic index files are not
    locked; a tenant whose retention schedule was deleted is not renewed; space of deleted
    data comes back only once its lock has run out; a file share whose repository is still
    locked cannot be purged before then.
  • SharePoint: attachments of list items, site design, navigation, workflows and
    permissions are not restored; a deleted site or library is not recreated; list items go
    back only into their original list.
  • In "This restore point contains", Windows paths are listed but do not open.
  • Deleting a revoked machine together with its restore points is not possible yet.
  • The known issues of 0.3.6 still apply.

Verification

Before the tag, on 2026-10-15, on the release branch (main plus the 0.4.0 branches):
lint and typecheck of all workspaces, the build, every unit suite, the Postgres suites on
Postgres 16 (129 test files, 1505 tests), the Go agent tests, the Perl plugin tests of the
Proxmox VE integration, the server installer tests (679) and the CI and smoke tooling
tests (241). Smoke check 12 (file shares: back up, browse, search, ZIP download, restore
with permissions, copy job against Samba) passed in CI on the 040-fileshares branch (run
38668096804). 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 94s
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 8s
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 22s
9. Image scan (Trivy) and dependency audit (pnpm audit) PASS 19s
10. Endpoint backup: the agent enrolls, backs up a folder, restores it PASS 12s
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 15s

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.0
ghcr.io/restow-backup/restow-web:0.4.0
ghcr.io/restow-backup/restow-community:0.4.0
ghcr.io/restow-backup/restow-web-community:0.4.0

The digests of the multi-arch manifests (the opt-in updater verifies the pulled images against the two lines of its build):

restow: sha256:ef593adaf97cdb241bdf790595dc9422fbf4a138f899900d9af379603a01173e
restow-web: sha256:99ea385d46fffd4a8ac91ac7dcbcf036b633addb801c721f58296d9f76c3e165
restow-community: sha256:4b5aaeda6e907c78e55d50fac87577315cfa1dbe6120b43f6e3dbb42a7d07d13
restow-web-community: sha256:d42451ed8e2a2f9ddb23b683a433bbb7286b8326cdc2c242bc6c67e0efbcbc2d

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.0 \
  --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.0 \
  --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.0 \
  --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.0 \
  --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).