Date: Fri, 1 Oct 2021 16:20:55 +0200 From: Julien Cigar <julien@perdition.city> To: freebsd-questions@freebsd.org Subject: Re: zfs q regarding backup strategy Message-ID: <20211001142055.fv6dqigixdgos2xu@x1> In-Reply-To: <YVcXsF5NFq2abE%2B7@ceres.zyxst.net> References: <YVZM1HnPuwIUQpah@ceres.zyxst.net> <ba54a415-da45-e662-73fe-65702c4131e2@holgerdanske.com> <YVcXsF5NFq2abE%2B7@ceres.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--r5cvot5bxqywiq27 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 01, 2021 at 03:14:08PM +0100, tech-lists wrote: > Hello, >=20 > On Thu, Sep 30, 2021 at 08:06:28PM -0700, David Christensen wrote: >=20 > > Michael Warren Lucas is my go-to author for FreeBSD and ZFS: >=20 > I think those were written quite a while ago? I need something covering > both the old zfs and OpenZFS. I'm looking for the differences, any > incompatibilities that might apply in my context. It'd be great if he > has more recent stuff. >=20 > > I use zfs-auto-snapshot for snapshot creation/ management, and homebrew > > commands/ scripts for replication. The homebrew stuff is problematic. >=20 > yeah homebrew I'm trying to avoid for lots of reasons. >=20 > > I need to evaluate something like zfs-replicate (available as a FreeBSD > > package of the same name): >=20 > Thanks for the suggestion. Problem with zfs-replicate is its dependence > on python, which from what I've observed historically, is a bit of a mess. > On my desktop there's lots of ports still needed that are dependent on > python2 even though upstream have retired it. They show up in > reports as EoL'd due to python2; there's loads right now and the desktop > builds its ports in poudriere weekly. >=20 > What I'm looking for is something (ideally) written in sh. Or even perl. > But even before that, need to understand incremental backups properly. > Basically the backup needs to be (effectively) write-only. By that, I > mean only added to. >=20 > Maybe zfs snapshots aren't the way to go; maybe rsync in the backup > direction only (apart from when something needs to be restored) would > suit my context better. What do you think? We use zrepl at work and it works pretty well. It handles snapshots, send/recv, pruning, etc. > --=20 > J. --=20 Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. --r5cvot5bxqywiq27 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEnF27CBNtOraRNmgqCLYqJMpBHmkFAmFXGUMACgkQCLYqJMpB HmnH4g//Qsdr+tm/0G8EWLlPp0NpZF6dsgUgskrBJOh8ouJ8RyXwOHpbM7nBxxVt XQL5uFFPTw1cIGmAjND/iZyLnrF6Q60eH2bG/4gwmriraybJU1NSZvBq6FjtA8E3 baMtlY6RQ0jRTQmbxr1Mt5BIAHmnSs9N2MN4nlboVwKz+yZkXb2iwo80Rthj9V+P 98Upw5equyVSHW+w7zeo+bitdD55wM1cpmFOTjWObqWdwkpvX1p9mMHRD7jU10Rd 0Uj1sEOIIz0s8QWJnIjIhXPUVe5k+SpAWh9Kit9LYA289ztzc6B/j7NFDTdvblSM sjqV4q+zdZ48W9DiWGhcYqRX+dpeHewNqnIivp9LIqWGBu2HExwd5l/FRugVMq3e r38USDjTr8dSTFqggVIBLvyubSUCHEEXTGui27A0bAVUHtNxU/xGSIclCQq34RF/ +zW9qutIsJycToBLBt+k5a3u9FZ9bkw53yGwhWfrBZoyuzlCBaMAFARJ/SAXSsgl nV+h0vKP81qnLU/MX+/HsyngPEDJFtg31LUrxxhALIHeX/2kysOo6wNQoLS5oi3Y UF3O26x43B2Ivm+n6wfxD1vB3EGjhAfbf2XqtVXHuC7bC5RLP9bjJYB2WpJ1VWCu 30TiOGkrCg08BIuTE4DhTEoRPkJx/UcBXjtnRoSqct3KIqqW8Ds= =VjwE -----END PGP SIGNATURE----- --r5cvot5bxqywiq27--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20211001142055.fv6dqigixdgos2xu>