Updated Common snapshots and holds (markdown)
@ -23,3 +23,15 @@ To prevent accidental deletion of the common snapshot zfs-autobackup uses holds.
|
||||
This can be quite frustrating for new users who try to delete old datasets that still have holds. (`Dataset is busy`) Use `zfs holds ` and `zfs release` to release a snapshot.
|
||||
|
||||
If you know what you're doing you can use --no-holds.
|
||||
|
||||
## Holds and offline backups
|
||||
|
||||
Normally when you split up the snapshotting part and backupping part you would do it like this: [[https://github.com/psy0rz/zfs_autobackup/wiki#splitting-up-snapshot-and-backup-job]]
|
||||
|
||||
The snapshotter will still connect to the target server and figure out the common snapshot so that it wont be deleted. It can also cleanup old snapshot from the source if it determines the target doesnt need them (anymore)
|
||||
|
||||
However, if you use the snapshot-only mode, the snapshot tool cant "see" the target machine.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user