From owner-freebsd-virtualization@FreeBSD.ORG Wed Dec 10 02:55:23 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 2478629C for ; Wed, 10 Dec 2014 02:55:23 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EB4DEDF0 for ; Wed, 10 Dec 2014 02:55:22 +0000 (UTC) Received: from Julian-MBP3.local (ppp121-45-239-104.lns20.per1.internode.on.net [121.45.239.104]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id sBA2tHiw083008 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 9 Dec 2014 18:55:20 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <5487B610.2070502@freebsd.org> Date: Wed, 10 Dec 2014 10:55:12 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Pete Wright , freebsd-virtualization@freebsd.org Subject: Re: backups of bhyve images References: <20141208163358.GA52969@potato.growveg.org> <33053EB5-91C5-4036-8CC2-34103E33A0FA@mu.org> <548637D8.1060608@nomadlogic.org> In-Reply-To: <548637D8.1060608@nomadlogic.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: Wed, 10 Dec 2014 02:55:23 -0000 On 12/9/14, 7:44 AM, Pete Wright wrote: > > 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... there are three layers to consider. The client must have layed down a consistent set of blocks. Bhyve needs to have written them all to the file in question. The Host needs to have made sure that they are all consistent on the media. > > cheers, > -pete > >