baudolo 7.1.x writes volume generations with `rsync -aHAX`, so the producing host keeps `user.*` extended attributes (OpenCloud keeps its storage metadata in `user.oc.*`). Every later copy dropped them again, because none of the other rsync calls passed `-X` (nor `-A`/`-H`): - NFS export snapshots (svc-bkp-nfs-2-local `script.sh`), - the backup host's pull (svc-bkp-remote-2-local `pull_specific_host.py`), - the device sync (svc-bkp-local-2-device `script.py`), - every recover into a live target (`utils/recovery/base.py`, used by the volume, NFS and device recover scripts), - the `recover full` and `recover remote` tree pulls. A disaster recovery through the documented chain therefore restored OpenCloud without `user.oc.*`, silently: the copies succeeded and the dirval stamp does not cover attributes. All of these now run `rsync -aHAX` (`-aHAXP` for the device sync). A target filesystem without xattr support makes rsync exit non-zero as soon as a source file carries attributes, so the hop fails loudly instead of dropping them; there is no per-device opt-out. The single-image pull in `recover remote` keeps `-a`. The provider's ssh-wrapper needs no change: its glob accepts any server flags and its character guard allows them. Two tests write a `user.oc.id` attribute and assert it survives the NFS snapshot and the recover; with the old `-a` both fail with `OSError: [Errno 61] No data available`. Closes #1021 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
6.0 KiB
Backup NFS
Description
A scheduled differential backup of the NFS export onto the local backup directory.
Each run stores a discrete snapshot under <backups>/<machine-hash>/backup-nfs-to-local/<generation>/files/, hard-linked against the previous generation via rsync --link-dest.
Overview
This role installs the backup script and the systemd service that drives it on the configured schedule (SYS_SCHEDULE_BACKUP_NFS_TO_LOCAL), and serialises the run against the rest of the manipulation group via sys-lock.
The source path is the NFS export base resolved from the svc-storage-nfs-server services SPOT; deploy the role on the host that serves the export.
Deploy sys-ctl-cln-bkps to keep the snapshot tree bounded and user-backup so downstream hosts can pull the tree.
Cosmos
The diagram places Backup NFS in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).
flowchart LR
subgraph deps [Dependencies]
dep_svc_storage_nfs_server["svc-storage-nfs-server 💻"]
dep_sys_ctl_cln_faild_bkps["sys-ctl-cln-faild-bkps 💻 ⚙️"]
end
subgraph role [svc-bkp-nfs-2-local 💻]
svc_nfs_server["nfs-server"]
svc_nfs_2_local["nfs-2-local"]
end
subgraph dependents [Dependents]
dpt_svc_storage_nfs_server["svc-storage-nfs-server 💻"]
end
dep_svc_storage_nfs_server -. "0..1" .-> svc_nfs_server
dep_sys_ctl_cln_faild_bkps -- "1:1" --> svc_nfs_2_local
svc_nfs_2_local -. "0..1" .-> dpt_svc_storage_nfs_server
Solid 1:1 edges are fixed relationships; dashed 0..1 edges are conditional (enabled only in matching deployments); red 0..0 edges are turned off in this role. Node markers show the role's deploy modes (💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly turned off, and ⚙️ an Ansible role dependency declared in meta/main.yml.
Schema
flowchart TD
TIMER["systemd timer<br>SYS_SCHEDULE_BACKUP_NFS_TO_LOCAL (01:30)"] --> UNIT
PRELOAD["sys-service-loader preload<br>MODE_BACKUP, run_after svc-storage-nfs-server<br>(force_flush_instant + state started)"] --> UNIT
UNIT["svc-bkp-nfs-2-local.<version>.<domain>.service"] --> LOCK["ExecStartPre: sys-lock against the manipulation group"]
LOCK --> SCRIPT["ExecStart: script.sh <export_base> <backups_dir><br>backup-nfs-to-local <state>/backup"]
SCRIPT -->|export_base missing| ALARM["ERROR exit 1<br>OnFailure alarm"]
SCRIPT --> RSYNC["rsync -aHAX --delete<br>--exclude /<state>/backup (no backups-in-backups)<br>--link-dest previous generation (hard links)"]
RSYNC -->|exit 24: live export churn| WARN["WARN, snapshot kept"]
RSYNC -->|any other failure| CLEAN["generation removed, exit != 0"]
RSYNC --> TREE["<backups_dir>/<sha256(machine-id)>/<br>backup-nfs-to-local/<YYYYmmddHHMMSS>/files/..."]
TREE --> PULL["svc-bkp-remote-2-local via ssh<br>user-backup ssh-wrapper: whitelisted ls/rsync per type<br>pulls the newest generation"]
Features
- Differential snapshots: rsync
--link-destagainst the previous generation deduplicates unchanged files. - Baudolo-compatible layout: snapshots land in the same
<machine-hash>/<repo>/<generation>tree as the container backups, so pull and cleanup tooling applies unchanged. - Schedule-coordinated: the systemd unit is part of the global manipulation group, so it never races backup/cleanup/repair jobs on the same host.
Quick Setup
Development
Clone, set up the workstation, and deploy Backup NFS onto the local stack:
git clone https://github.com/infinito-nexus/core.git
cd core
make onboard
make compose-deploy mode=reinstall apps=svc-bkp-nfs-2-local full_cycle=false
Production
Install Backup NFS directly onto the target machine: clone the repository, install the OS prerequisites and the repository toolchain, then deploy against localhost over a local connection (no SSH, no container):
git clone https://github.com/infinito-nexus/core.git
cd core
bash scripts/install/package.sh
make install
source scripts/meta/env/load.sh
APP=svc-bkp-nfs-2-local
DOMAIN=<your-domain>
TLS_MODE=self_signed
SSH_PUBLIC_KEY="<your-ssh-public-key>"
INVENTORY=inventories/production
infinito administration inventory provision "$INVENTORY" \
--inventory-file "$INVENTORY/devices.yml" \
--host localhost \
--include "$APP" \
--vars "{\"TLS_MODE\": \"$TLS_MODE\", \"DOMAIN_PRIMARY\": \"$DOMAIN\", \"users\": {\"administrator\": {\"authorized_keys\": [\"$SSH_PUBLIC_KEY\"]}}}"
infinito administration deploy dedicated "$INVENTORY/devices.yml" \
--password-file "$INVENTORY/.password" \
--diff -vv
Recover
Run files/python/recover.py on the host that serves the NFS export:
recover.py <backups>/<machine-hash>/backup-nfs-to-local/<generation>/files/<state>/<volume> <export-base>/<state>/<volume>
- Stop every stack consuming the subtree:
docker stack rm <stack>. - Run the script; it first starts the role's deployed backup unit (a fresh differential
backup-nfs-to-localgeneration of the live export), then mirrors the snapshot into the target (rsync -aHAX --delete, with the shared<state>/backuproot protected from deletion and never copied in).--no-safety-backupskips the unit run when the target holds nothing worth saving. - Redeploy the stack; the NFS clients re-mount and pick up the restored state.
The target subtree must already exist; the script refuses to create export subtrees implicitly.
Credits
Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).