patrick/zfs_autobackup
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated Problems (markdown)

DatuX
2023-09-27 23:13:29 +02:00
parent 3aa78f9d04
commit 71f3cb94a4
1 changed files with 9 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
Problems.md

@ -4,17 +4,21 @@
You forgot to setup automatic login via SSH keys, look in the example how to do this.
## "cannot receive incremental stream: invalid backup stream"
This usually means you've created a new snapshot on the target side during a backup. If you restart zfs-autobackup, it will automaticly abort the invalid partially received snapshot and start over.
## "cannot receive incremental stream: destination has been modified since most recent snapshot"
This means files have been modified on the target side somehow.
This means your target dataset has been modified somehow.
Make sure you read how [[Mounting]] works.
* You can use `--rollback` to automatically rollback such changes.
* Try using `--clear-mountpoint`, so the filesystems wont be mounted. Mounting will sometimes lead to changes since it might have to create mount-point directories in filesystems. `--clear-mountpoint` only affects newly received filesystems, so you might have to set the `canmount=noauto` property on existing target filesystems yourself.
* Set the `readonly` property of the target filesystem to on. This prevents all modifications on the target side. Note that readonly prevents changes to the CONTENTS of the dataset directly. Its still possible to receive new datasets and manipulate properties etc.
* Always use `--clear-mountpoint`, see [[Mounting]]
## "cannot receive incremental stream: invalid backup stream"
This usually means you've created a new snapshot on the target side during a backup. If you restart zfs-autobackup, it will automaticly abort the invalid partially received snapshot and start over.
## "internal error: Invalid argument"