Date: Fri, 21 Jun 2019 20:21:43 -0700 From: George Hartzell <hartzell@alerce.com> To: mike tancsa <mike@sentex.net> Cc: freebsd-questions@freebsd.org Subject: Re: ZFS replication suggestions Message-ID: <23821.40647.901447.793730@alice.local> In-Reply-To: <fce897b7-5576-83f8-6f8b-3f9ffd502261@sentex.net> References: <fce897b7-5576-83f8-6f8b-3f9ffd502261@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
mike tancsa writes: > I have a new project coming up with replication.=A0 In the past, I h= ave > used various scripts out of ports, but was wondering what people are= > using these days to sync their ZFS files systems between servers ?=A0= It > will be about 10-40G in daily diffs.=A0 Would like to send every 5-1= 0 min > or so. Files being slightly out of sync for a short period of time i= s > not a big deal eg. in case of total failure on one box (e.g both pow= er > supplies die) missing some data for a period of short time is tolera= ble I've been playing with [sanoid] for generating/pruning snapshots on a remote machine, `syncoid` from the same package for "pull" syncing from the remote machine to a FreeNAS system, and [sanoid] on the local backup server solely to prune the snapshots. It's working reasonably well (e.g. I just got a weird email (cron) about it failing to remove something, but it's gone on the next iteration, so....). I've submitted [a bug report][new-ports] that contains a release port and a devel port. Any help getting it committed would be most welcome. I also have both ports in my ["personal ports tree"][my-ports], it's intended to be layered over the full ports tree with e.g. portshaker. g. [sanoid]: https://github.com/jimsalterjrs/sanoid [new-ports]: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238584= [my-ports]: https://github.com/hartzell/freebsd-ports/tree/master/sysut= ils
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23821.40647.901447.793730>