From owner-freebsd-fs@freebsd.org  Mon May 16 13:56:38 2016
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 781DAB3DF25
 for <freebsd-fs@mailman.ysv.freebsd.org>; Mon, 16 May 2016 13:56:38 +0000 (UTC)
 (envelope-from borjam@sarenet.es)
Received: from cu01176a.smtpx.saremail.com (cu01176a.smtpx.saremail.com
 [195.16.150.151])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 36C3A135D;
 Mon, 16 May 2016 13:56:37 +0000 (UTC)
 (envelope-from borjam@sarenet.es)
Received: from [172.16.8.36] (izaro.sarenet.es [192.148.167.11])
 by proxypop03.sare.net (Postfix) with ESMTPSA id 35EB89DD37C;
 Mon, 16 May 2016 15:51:03 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Best practice for high availability ZFS pool
From: Borja Marcos <borjam@sarenet.es>
In-Reply-To: <5E69742D-D2E0-437F-B4A9-A71508C370F9@FreeBSD.org>
Date: Mon, 16 May 2016 15:51:02 +0200
Cc: freebsd-fs@freebsd.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <F3716A47-BC73-4C51-BF7C-911BCFE4D29F@sarenet.es>
References: <5E69742D-D2E0-437F-B4A9-A71508C370F9@FreeBSD.org>
To: Palle Girgensohn <girgen@freebsd.org>
X-Mailer: Apple Mail (2.3124)
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2016 13:56:38 -0000


> 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.