Repository navigation
Problems
You did not set up an SSH login with keys. See Set up SSH login.
The target dataset has changes. Read Mounting first.
- Always use
--clear-mountpoint. See Mounting. - Set
readonly=onon the target dataset. This prevents changes to the contents of the dataset. zfs-autobackup can still receive new datasets and change properties. - Use
--rollbackto remove the changes automatically.
Usually this occurs when you make a snapshot on the target during a backup. Run zfs-autobackup again. It removes the partially received snapshot and starts again.
The target system does not fully support some properties. This can occur, for example, from Linux to FreeBSD.
Try --filter-properties xattr or --ignore-transfer-errors.
This occurs between different operating systems, ZFS versions or feature sets.
Use --ignore-transfer-errors. zfs-autobackup then ignores the error, but still checks that it received the snapshot.
The target datasets are encrypted and you did not use --encrypt. See Encryption.
There can be different causes. First, look for holds on the snapshot:
zfs holds zpool/fs1@snapshot1Use zfs release to remove a hold. To not use holds, use --no-holds. Read Common snapshots and holds before you do this.
- Questions about zfs-autobackup: GitHub discussions
- Bugs and feature requests: GitHub issues
- General ZFS questions: r/zfs
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: