Repository navigation
v4.0 pre release discussion #294
psy0rz
announced in
Announcements
Replies: 2 comments 4 replies
|
Using a single underscore as the separator between the snapshot name and the tag seems unnecessarily restrictive on the snapshot name. How about using two underscores instead? Otherwise these changes all sound good to me. |
2 replies
|
Development is still going on ? |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Since v4.0 will have some major changes, it would be nice to have some feedback about what people think of it, before the actual release.
Development is still going on in the v3.4 branch and its not ready for testing yet.
Here are the release notes so far:
This version has some major changes that affect how zfs-autobackup operates.
Tag support
You can now use
--tagto add a tag to the snapshot names. While zfs-autobackup ignores these, they are usefull for the system administrator.For example if you make an extra manual snapshot, you might want to tag this:
( yes you can use spaces)
Your snapshot will be something like
@offsite1-20241014123300_pre upgrade snapshot"This will add an _ and the text,
Also see the discussion in #151
Impact on existing users: You can no longer use the tag seperator (underscore by default) in snapshot names. Use
--no-tagsto get back the old behaviour and disable tag support.Bookmark support
By default zfs-autobackup will now use bookmarks if possible. This means you can delete the common snapshot on the source side, possibly saving space.
Because of this, the scheduler can now delete all snapshots on the source side, if conifgured like that. (e.g. --keep-source=0)
This also means we no longer hold snapshots on the source side, to make things easier.
The guid of the target-path will be used as tag for bookmarks. This way you can send data to multiple locations, without zfs-autobackup destroying bookmarks that are still needed.
Bookmarks only get used if both sides support it.
To get back the old behaviour use
--no-bookmarks.autobackup: properties are now filtered by default (see #150 and #221)
A long standing issue was the fact that it sometimes was hard to distinguish a source from an actual backup
We had some tricks for it like --exclude-received, but its much better if we just would filter all autobackup: properties by default.
So thats what zfs-autobackup does by default now: All properties that start with autobackup:... are filtered.
If you make a zfs-autobackup of an existing zfs-autobackup, you might want to pay attention if this still works like you expect.
Other stuff
These changes should have no impact on existing zfs-autobackup users:
All reactions