[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Backup running Windows machines - redundancy


  • To: Bart Coninckx <bart.coninckx@xxxxxxxxxx>
  • From: Mike Sun <msun@xxxxxxxxxx>
  • Date: Thu, 10 Feb 2011 14:36:16 -0500
  • Cc: Paul PISCUC <paul.piscuc@xxxxxxxxxx>, Guido Hecken <guido.hecken@xxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 10 Feb 2011 11:37:16 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=DJ73llvadN3it1TLvEdS+Y2M1TPMchDS6wpdzXvgmojwkxlicDE+yQ6aVtO0CGsTG/ w9B476XVkiNy2Atr1ygZG5GiCbBuw7+1ln8Rob1lWafyElwC5KD4ahIvBvRyCG9KGXqf pxk263Wp+Rxxq46W7X6lAqxCeJ7XlW46XLYC4=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi Bart,

> That's what I actually suggested in previous post: do a xm save -f, take
> a snapshot of the underlying LV, do a xm restore and then dd the snapshot.
> This is 100% safe for restore if you also backup the memory state file.

You're right, it's only 100% safe if you backup the *memory* state as
well.  Otherwise, from all the other proposed methods I've seen in
this thread, just by pausing or saving the VM does not guarantee that
the file system will be put into a consistent state, which is
important for those who care about file system backups and not VM
snapshots.

Mike

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.