-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, Feb 21, 2017 at 06:21:40PM +, Rusty Bird wrote:
> Chris Laprise:
> > On 02/21/2017 07:43 AM, Rusty Bird wrote:
> > > Hi Chris!
> > >
> > > > On 02/20/2017 08:28 AM, Rusty Bird wrote:
> > > > > A small qvm-backup wrapper script that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Chris Laprise:
> On 02/21/2017 07:43 AM, Rusty Bird wrote:
> > Hi Chris!
> >
> > > On 02/20/2017 08:28 AM, Rusty Bird wrote:
> > > > A small qvm-backup wrapper script that handles running VMs by chrooting
> > > > into a temporary dom0 filesystem
On 02/21/2017 07:43 AM, Rusty Bird wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Chris!
On 02/20/2017 08:28 AM, Rusty Bird wrote:
A small qvm-backup wrapper script that handles running VMs by chrooting
into a temporary dom0 filesystem snapshot. The backed up data is the
same as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Chris!
> On 02/20/2017 08:28 AM, Rusty Bird wrote:
> > A small qvm-backup wrapper script that handles running VMs by chrooting
> > into a temporary dom0 filesystem snapshot. The backed up data is the
> > same as if those VMs had just been
On 02/20/2017 08:28 AM, Rusty Bird wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Something for the btrfs crowd:
A small qvm-backup wrapper script that handles running VMs by chrooting
into a temporary dom0 filesystem snapshot. The backed up data is the
same as if those VMs had just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Something for the btrfs crowd:
A small qvm-backup wrapper script that handles running VMs by chrooting
into a temporary dom0 filesystem snapshot. The backed up data is the
same as if those VMs had just been killed, which seems to work fine for
the
