feat(running-backups): the host's own backups a restart would abort #73

Merged
christianmanivong merged 1 commits from feature/running-backups-2318 into main 2026-11-11 07:40:54 +00:00
Owner

Summary

  • get_running_backups() (napalm-device-types 4.34.0, RunningBackupsMixin) through LinuxProcessReadingsMixin, so OpenMediaVault and QNAP inherit it.
  • One round trip as the login user: the clock, ps -eo pid=,etimes=,args= and each process's cgroup. A process of restic, resticprofile, autorestic, borg, borgmatic, duplicity, duply, rsnapshot, rdiff-backup, proxmox-backup-client, kopia or btrbk doing a backup, prune, check or copy counts (not a mount, restore or listing); borg serve counts as the receiving end of another host's backup.
  • Its job is the systemd service it runs in (the timer's service); none for cron or a login session.
  • A ps without etimes (busybox) fails the reading instead of reporting nothing.

Related Issue

NetOrk/netork#2318

Testing

  • tests/test_running_backups.py (36), full suite 402 passed, ruff, napalm-standard check and ratchet locally; the command run on a real Linux host.

Depends on

NAPALM/napalm-device-types#102 (4.34.0, RunningBackupsMixin). CI installs napalm-device-types from PyPI, so the install jobs fail until 4.34.0 is tagged and published there; rerun them then.

## Summary - `get_running_backups()` (napalm-device-types 4.34.0, `RunningBackupsMixin`) through `LinuxProcessReadingsMixin`, so OpenMediaVault and QNAP inherit it. - One round trip as the login user: the clock, `ps -eo pid=,etimes=,args=` and each process's cgroup. A process of restic, resticprofile, autorestic, borg, borgmatic, duplicity, duply, rsnapshot, rdiff-backup, proxmox-backup-client, kopia or btrbk doing a backup, prune, check or copy counts (not a mount, restore or listing); `borg serve` counts as the receiving end of another host's backup. - Its job is the systemd service it runs in (the timer's service); none for cron or a login session. - A `ps` without `etimes` (busybox) fails the reading instead of reporting nothing. ## Related Issue NetOrk/netork#2318 ## Testing - `tests/test_running_backups.py` (36), full suite 402 passed, ruff, `napalm-standard check` and `ratchet` locally; the command run on a real Linux host. ## Depends on NAPALM/napalm-device-types#102 (4.34.0, `RunningBackupsMixin`). CI installs napalm-device-types from PyPI, so the install jobs fail until 4.34.0 is tagged and published there; rerun them then.
christianmanivong added 1 commit 2026-11-10 22:46:02 +00:00
feat(running-backups): the host's own backups a restart would abort
driver / standard (pull_request) Successful in 15s
driver / lint (pull_request) Successful in 13s
driver / types (pull_request) Successful in 59s
driver / test (3.12) (pull_request) Successful in 1m3s
driver / test (3.13) (pull_request) Successful in 54s
driver / lowest (pull_request) Successful in 28s
driver / build (pull_request) Successful in 26s
driver / security (pull_request) Successful in 54s
CI / driver (pull_request) Successful in 2m25s
driver / publish (pull_request) Skipped
78374cfb42
netOrk holds a host's restart after patching while a backup runs on it
(NetOrk/netork#2318) and asks right before the restart. On a Linux host a
file-level backup is a process of a backup tool, started by a timer, a cron
line or by hand, so get_running_backups() (napalm-device-types 4.34.0) reads
the processes, the clock and each process's cgroup in one round trip as the
login user. What a tool does comes from its subcommand: restic backup is a
backup, restic forget a prune, restic mount none; borg serve counts, as the
receiving end of another host's backup. The systemd service a backup runs
in is its job, the timer's service netOrk shows as its scheduled job.

A ps without etimes (busybox) fails the reading rather than report nothing.
christianmanivong merged commit 10240c20bb into main 2026-11-11 07:40:54 +00:00
christianmanivong deleted branch feature/running-backups-2318 2026-11-11 07:40:54 +00:00
Sign in to join this conversation.