Usage
Running jobs manually
How to run fsbackup scripts manually from the command line or web UI.
All scripts can be run manually from the command line. This is useful for testing, re-running failed jobs, or running jobs outside of the scheduled window.
Scripts run as the fsbackup user. Use sudo -u fsbackup or the web UI's Run Jobs page.
Doctor
Checks SSH reachability and source path existence for all targets in a class.
sudo -u fsbackup /opt/fsbackup/bin/fs-doctor.sh --class class1
sudo -u fsbackup /opt/fsbackup/bin/fs-doctor.sh --class class2
Any FAIL must be resolved before the runner will succeed for that target.
Snapshot runner
Dry run (safe, no changes)
sudo -u fsbackup /opt/fsbackup/bin/fs-runner.sh daily --class class1 --dry-run
Run for real
sudo -u fsbackup /opt/fsbackup/bin/fs-runner.sh daily --class class1
Run a single target
sudo -u fsbackup /opt/fsbackup/bin/fs-runner.sh daily --class class1 --target myapp.data
Force re-sync an existing snapshot
By default, unchanged files are skipped. To force a full re-sync:
sudo -u fsbackup /opt/fsbackup/bin/fs-runner.sh daily --class class1 \
--target myapp.data --replace-existing
Retention
Prunes ZFS snapshots beyond the configured KEEP_* counts:
sudo -u fsbackup /opt/fsbackup/bin/fs-retention.sh --dry-run
sudo -u fsbackup /opt/fsbackup/bin/fs-retention.sh
S3 export
sudo -u fsbackup /opt/fsbackup/s3/fs-export-s3.sh
Checking logs
# Per-class backup logs
tail -f /var/lib/fsbackup/log/backup-class1.log
tail -f /var/lib/fsbackup/log/backup-class2.log
# S3 export log
tail -f /var/lib/fsbackup/log/s3-export.log
# Web UI log
sudo journalctl -u fsbackup-web -f
# Timer run output (journal)
sudo journalctl -u fsbackup-runner-daily@class1.service -f
sudo journalctl -u fsbackup-s3-export.service
sudo journalctl -u fsbackup-retention.service