Re: [Xen-devel] consistent LVM snapshot of domUs from dom0

["Mike Sun" <msun@xxxxxxxxxx>]

Ok... I see where you're coming from Nikola... you're only concerned
with safe, consistent snapshots of the filesystem state without
checkpointing the running vm state.  Yes, implementing a special xm
fssnapshot command would be the way to go.  I was just curious if
there were any other pitfalls given my approach of checkpointing the
entire VM with a suspend followed by an lvm snapshot.  Thanks for the
clarifications.  I'm actually considering  an attempt to implement the
COW memory functionality that's been discussed on this list in the
past.

Mike

On Dec 8, 2007 5:17 PM, Nikola Ciprich <extmaillist@xxxxxxxxxxx> wrote:
> Hi Mike, well, I maybe don't understand where the question is ;) but I
> guess that Your procedure is perfectly correct (for creation of a
> checkpoint of running system), if You want to restore the backup later,
> You restore system into running state, so a filesystem is in state
> consistent with running system....
> n.
>
>
>
>   On Sat, 8 Dec 2007, Stefan de Konink wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA512
> >
> > Nikola Ciprich schreef:
> >> Hi Mike,
> >> I think that this problem can be solved using procedure Mark proposed -
> >> freeze filesystems of all running domUs using some xm command, then
> >> create snapshot and unfreeze them all again. I think that You won't need
> >> suspend at all.
> >> We just now need to implement it :)
> >
> >
> > Just a question about unsafely. I have implemented iscsi and zfs as
> > combination with Xen on Linux. Is the only safe procedure:
> >
> > pause
> memory snapsnot
> > [send out disk snapshot]
> > resume
> >
> >
> > Stefan
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v2.0.7 (GNU/Linux)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >
> > iD8DBQFHWxFIYH1+F2Rqwn0RCiT7AKCBAnfW4E0M8pLjHKZUHOOX0mwoZwCfcfY3
> > Rns2S2AETOMypqLDmRnljx4=
> > =ADlt
> > -----END PGP SIGNATURE-----
> >
> >
>
> --
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel