Monitor-snapshot-plan CLI - Check if ZFS snapshots are successfully taken on schedule, successfully replicated on schedule, and successfully pruned on schedule

OpenZFS
1
  • The v1.11.0 release brings several new things, including …
  • [bzfs_jobrunner] Added --monitor-snapshot-plan CLI option, which alerts the user if the ZFS ‘creation’ time property of the latest or oldest snapshot for any specified snapshot pattern within the selected datasets is too old wrt. the specified age limit. The purpose is to check if snapshots are successfully taken on schedule, successfully replicated on schedule, and successfully pruned on schedule. See the jobconfig script for an example.
  • [bzfs_jobrunner] Also support replicating snapshots with the same target name to multiple destination hosts. This changed the syntax of the --dst-hosts and --retain-dst-targets parameters to be a dictionary that maps each destination hostname to a list of zero or more logical replication target names (the infix portion of a snapshot name). To upgrade, change your jobconfig script from something like dst_hosts = {"onsite": "nas", "": "nas"} to dst_hosts = {"nas": ["", "onsite"]} and from retain_dst_targets = {"onsite": "nas", "": "nas"} to retain_dst_targets = {"nas": ["", "onsite"]}
  • [bzfs_jobrunner] The jobconfig] script has changed to now use the --root-dataset-pairs CLI option, in order to support options of the form extra_args += ["--zfs-send-program-opts=--props --raw --compressed"]. To upgrade, change your jobconfig script from ["--"] + root_dataset_pairs to ["--root-dataset-pairs"] + root_dataset_pairs.
  • [bzfs_jobrunner] Added --jobid option to specify a job identifier that shall be included in the log file name suffix.
  • Added --log-subdir {daily,hourly,minutely} CLI option.
  • Improved startup latency.
  • Exclude parent processes from process group termination.
  • Nomore support python-3.7 as it has been officially EOL’d since June 2023.
  • For the full list of changes, see https://github.com/whoschek/bzfs/compare/v1.10.0…v1.11.0
2

If you want to advertise bzfs updates here, you need to put bzfs in the thread title, please. It’s a bit much to expect the entire forum to know what you’re talking about when you name a new argument you’ve added without naming the app itself! :beer::+1:

2 Likes
3

I recommend you don’t underestimate users. I have confidence that anyone interested in monitoring snapshots (the title) will manage to read the rest of the text that mentions the name and even a link, and decide for themselves :slight_smile:

4

Fine: I recommend you don’t piss off the forum administrator who began this by manually approving the posts of yours that the forum had flagged as potential spam and hidden in the first place.

Please put bzfs in the thread title when dumping changelogs in here, or you will no longer be permitted to dump changelogs in here at all.

Are we clear?

1 Like
5

I recommend you don’t ruin your reputation as a forum administrator by pissing off highly valuable contribution to the community.

2 Likes
6

Well, I didn’t expect to ban anybody today, but here we are. I will of course refund your entire $0.00 cost of admission. Bye.

edit: upon further reflection, make it a thirty day timeout. See you at the end of April, I suppose.

4 Likes