zrepl
zrepl copied to clipboard
One-stop ZFS backup & replication solution
I've got a zrepl configuration with separate `snap` and `push` jobs, and each periodic `snap` job wakes up various `push` jobs using post-snapshot hooks. This means that sometimes, a hook...
I'm trying to set up a backup scheme that's a combination of the "Local Snapshot" and the "Continuous Backup of a Server" examples. Specifically, this is what I'm trying to...
The docs say: > Jobs with periodic snapshots can run hooks before and/or after taking the snapshot specified in snapshotting.hooks: Hooks are called per filesystem before and after the snapshot...
* Another detail in the replication job, the progress bar never finish but the job is completed: ``` Job: zfsnode Type: push Replication: Status: Completed Progress: [=================================================>-] 59.6 GiB /...
``` NOTE: not all steps could be size-estimated, total estimate is likely imprecise! rpool/enc/ROOT/fedora STEPPING (step 11/27, 911.6 MiB/2.1 GiB) (some steps lack size estimation) ``` We always show this...
* bookmarking and snapshotting can take up to 5 seconds (the time until we move to the next transaction group) * it's not clear to me why I didn't see...
Use `machine` type in CircleCI on Ubuntu-based image. Should work.
I have a `push` job on one side and `sink` on the other. My push job is stuck with the following error: ``` Replication: zdata/pve/backups/vms PLANNING-ERROR (step 0/0, 0 B/0...
I'm using IPv6 across my network, and as a result most machines have multiple addresses (a 'static' address assigned by DHCPv6 and a 'random' address assigned using SLAAC). Since the...
A `source` job currently maintains a single set of zrepl ZFS abstractions and does not encode the client identity of the pulling side into these abstractions. Multiple concurrent `pull` jobs...