Date: Mon, 16 May 2016 15:51:02 +0200 From: Borja Marcos <borjam@sarenet.es> To: Palle Girgensohn <girgen@freebsd.org> Cc: freebsd-fs@freebsd.org Subject: Re: Best practice for high availability ZFS pool Message-ID: <F3716A47-BC73-4C51-BF7C-911BCFE4D29F@sarenet.es> In-Reply-To: <5E69742D-D2E0-437F-B4A9-A71508C370F9@FreeBSD.org> References: <5E69742D-D2E0-437F-B4A9-A71508C370F9@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 16 May 2016, at 12:08, Palle Girgensohn <girgen@freebsd.org> wrote: >=20 > Hi, >=20 > We need to set up a ZFS pool with redundance. The main goal is high = availability - uptime. >=20 > I can see a few of paths to follow. >=20 > 1. HAST + ZFS Which means that a possible corruption causing bug in ZFS would vaporize = the data of both replicas. > 3. ZFS replication (zfs snapshot + zfs send | ssh | zfs receive) If you don=E2=80=99t have a hard requirement for synchronous replication = (and, in that case, I would opt for a more application aware approach) it=E2=80=99s the best method in my opinion. Borja.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F3716A47-BC73-4C51-BF7C-911BCFE4D29F>