From owner-freebsd-virtualization@FreeBSD.ORG Mon Dec 8 23:44:26 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AF541202 for ; Mon, 8 Dec 2014 23:44:26 +0000 (UTC) Received: from mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::4]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 947B7224 for ; Mon, 8 Dec 2014 23:44:26 +0000 (UTC) Received: from mail.nomadlogic.org (localhost [127.0.0.1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.nomadlogic.org (Postfix) with ESMTPS id 6D2F0125EE1 for ; Mon, 8 Dec 2014 15:44:25 -0800 (PST) Received: from pop.rubicorp.com (unknown [72.34.113.100]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.nomadlogic.org (Postfix) with ESMTPSA id 5344D125EBA for ; Mon, 8 Dec 2014 15:44:25 -0800 (PST) Message-ID: <548637D8.1060608@nomadlogic.org> Date: Mon, 08 Dec 2014 15:44:24 -0800 From: Pete Wright User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: Re: backups of bhyve images References: <20141208163358.GA52969@potato.growveg.org> <33053EB5-91C5-4036-8CC2-34103E33A0FA@mu.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 23:44:26 -0000 On 12/08/14 15:30, Craig Rodrigues wrote: > (3) When you want to backup the VM, do a "zfs snapshot" take take a > snapshot of the ZFS zvol. will this ensure that your zvol is consistent, or rather will the filesystem overlaid on the zvol device be ensured it is consistent when the hypervisor issues a snapshot command? it's been a while since i've done this - but IIRC on NetApp WAFL systems (which are similar to zfs in terms of being a COW filesystem) you need to ensure the guest filesystem is in a consistent state before issuing a snapshot from it's parent. my data may be out of date since it's been several years since i've done this though... cheers, -pete -- Pete Wright pete@nomadlogic.org twitter => @nomadlogicLA