ZFS Automatic Snapshot Daemon
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Thor e2ffeda501 Fix problems with shutdown, REPL, etc. 4 years ago
.mypy_cache/3.8 Commit changees so far 4 years ago
.vscode Fix problems with shutdown, REPL, etc. 4 years ago
bin/osx Fixed issue with wrong relative path in zasctl 4 years ago
log Initial commit 4 years ago
src Fix problems with shutdown, REPL, etc. 4 years ago
third_party Fix problems with shutdown, REPL, etc. 4 years ago
.env Fix problems with shutdown, REPL, etc. 4 years ago
.gitignore Initial commit 4 years ago
.gitmodules Fix problems with shutdown, REPL, etc. 4 years ago
.pylintrc Adjusted paths for third-party packages 4 years ago
.scraps.txt Check-in of progress so far 4 years ago
README.md Add more details to README 4 years ago
asyncio-test.py Check-in of progress so far 4 years ago
dependencies.md Further work 4 years ago
mypy.ini Check-in of progress so far 4 years ago
vs.code-workspace Fix problems with shutdown, REPL, etc. 4 years ago

README.md

ZFS Automatic Snapshot Daemon

This is a daemon, written in Python 3, that will schedule regular snaphots of ZFS datasets (pools, filsystems) according to a set of configurable schedules. Options for interval and crontab-style schedules are available.

The daemon only includes an installer for macOS at the moment, but a multi-platform installer is coming soon.

As of now, snapshots are conditional. A snapshot will only be taken if a dataset has been modified since the last snapshot. An option to turn this off per schedule is coming soon.

The daemon should not interfere with other snapshots you have on the system, unless you give them names that adhere to the dataset@tag:serial syntax zasd uses, and the tag parts happen to match of the tags in zasd.conf.py. If you're already using similar syntax for something else, you may need to change the separator setting in zasd.conf.py.

DISCLAIMER: This program is still in beta. Use at your own risk. It works fine on my system, but your mileage may vary.