From owner-freebsd-virtualization@FreeBSD.ORG  Mon Dec  8 16:34:31 2014
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
Delivered-To: freebsd-virtualization@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 20FF9DE2
 for <freebsd-virtualization@freebsd.org>; Mon,  8 Dec 2014 16:34:31 +0000 (UTC)
Received: from potato.growveg.org (potato.growveg.org [62.49.247.163])
 (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 D59E5B12
 for <freebsd-virtualization@freebsd.org>; Mon,  8 Dec 2014 16:34:30 +0000 (UTC)
Received: from john by potato.growveg.org with local (Exim 4.84 (FreeBSD))
 (envelope-from <john@potato.growveg.org>) id 1Xy1G2-000Dq8-CQ
 for freebsd-virtualization@freebsd.org; Mon, 08 Dec 2014 16:33:58 +0000
Date: Mon, 8 Dec 2014 16:33:58 +0000
From: John <freebsd-lists@potato.growveg.org>
To: freebsd-virtualization@freebsd.org
Subject: backups of bhyve images
Message-ID: <20141208163358.GA52969@potato.growveg.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: John <john@potato.growveg.org>
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: john@potato.growveg.org
X-SA-Exim-Scanned: No (on potato.growveg.org); SAEximRunCond expanded to false
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Dec 2014 16:34:31 -0000

Hello list,

I have a few questions about creating backups to be stored offsite.

If a guest is running, can I compress the image without it becoming 
inconsistent? If not, can it be copied without it becoming inconsistent?  
By inconsistent, I mean will I see weird effects and broken files if the 
backup is restored? Previously I've shut the VM down to avoid this, 
before archiving.

I have each image on its own (external to the image) ZFS filesystem.  
Internally the image is using ufs if freebsd, ext3fs if linux.  Would 
using some ZFS method of duplication be better? In this case, would the 
image become inconsistent?

Basically, what I want to do is to run accurate backups without shutting 
down and restarting the VM. Is this possible? If it isn't, I think the 
only alternative is to make a script that shuts the vm down, copies it, 
restarts the vm then runs its compression and backup-over-ssh routine.

thanks,

-- 
John