v2.0 breaking changes!

[ikluhsman]

We're in the process of writing version 2.0 already! I think its been less than a week and we already blew through v1.0 developing the web UI. Now we want to add data integrity to stay on top of any backup data corruption, but it seems an architecture re-design is the way in order to make it happen with native OS tooling.

That said, v2.0 is a ground-up rewrite of the fsbackup storage layer, replacing the rsync hardlink snapshot directory tree with per-target ZFS datasets. This is a breaking change — the snapshot directory structure is incompatible with v1.x. v1.x rsync hardlink snapshots remain available on v1.x tags.

Those that want to stick with the rsync snapshot tooling can stay on version 1. we may tag a release of 1.1 to wrap up v1 releases. It can still be run from a container, but be aware that data integrity for large datasets should not be trusted over long periods of time where the data is not accessed or read. Silent corruption of files will destroy the entire snapshot tree, hence why we wanted to integrate an integrity layer. The ZFS filesystem has native snapshot capabilities with periodic checksum scans and automatic corruption repair. This drove the decision for the architectural changes moving to ZFS targets.