Repository navigation
Monitoring
DatuX edited this page Nov 13, 2026
·
3 revisions
zfs-autobackup gives an exit code:
| Exit code | Meaning |
|---|---|
0 |
No important errors. |
x |
The snapshots are correct, but x datasets failed with a fatal error. |
255 |
Incorrect options or another large failure. Probably nothing succeeded. |
Without --verbose or --debug, zfs-autobackup only writes errors and warnings to stderr. No output means that all is correct. Thus, cron only sends you an email when there is a problem.
On a terminal (tty), zfs-autobackup also writes progress to stdout.
You can use my zabbix-jobs script. Put this command directly after zfs-autobackup in your cron job:
zabbix-job-status backup_smartos01_fs1 daily $?This sends the exit code to the Zabbix server. Zabbix also gives an alert if the job did not run for more than 2 days.
zfs-autobackup:
- Introduction (README.md)
- Getting started
- Full manual
- Mounting backup datasets
- Performance tips (recommended)
- Common problems and errors
- Thinning out obsolete snapshots
- Common snapshots, holds and bookmarks
- Handling ZFS encryption
- Transfer buffering, compression and rate limiting.
- Custom Pre- and post-snapshot commands
- Monitoring
Examples: