This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: Bart Coninckx <bart.coninckx@xxxxxxxxxx>
Subject: Re: [Xen-users] Backup running Windows machines - redundancy
From: Paul Piscuc <paul.piscuc@xxxxxxxxxx>
Date: Fri, 11 Feb 2011 10:50:37 +0200
Cc: James Harper <james.harper@xxxxxxxxxxxxxxxx>, Guido Hecken <guido.hecken@xxxxxxxxxxxxx>, Mike Sun <msun@xxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 11 Feb 2011 00:52:33 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D54ECA5.2020807@xxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <889950206.4537831297249585810.JavaMail.root@xxxxxxxxxxxxxxxxxxxxx> <4D531B75.50209@xxxxxxxxxx> <FB8F9F087039D8499E37A3F706D5EE160D6CAE@xxxxxxxxxxxxxxxxx> <AANLkTimr_SyX-qdWoA_=gw0TuqsoQtsDd5=FEVsnieDQ@xxxxxxxxxxxxxx> <4D53F0C3.8050108@xxxxxxxxxx><AANLkTikZqi07V3upOoZ+LcO76dpq1g4iQW9TDux-Kf-G@xxxxxxxxxxxxxx> <4D544B17.8080007@xxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01C55402@trantor> <4D546E4D.5000902@xxxxxxxxxx> <4D54ECA5.2020807@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110207 Lightning/1.0b2 Shredder/3.1.9pre
Ok, cool. What about reinstalling the system, to rebuild the boot sector ( or better, restore with dd from an earlier backup - let's assume a week old), and then use rdiff to bring the system up to date, from a more recent backup ? To be tested.

Again, the purpose of this thread is to find an incremental backup solution. DD and other methods work fine, but you cannot do daily backups on 8 machines with 100GB storage, and keep those backups for a week or more. Also, if one would like to restore a single file from the image, things will get ugly.

On 02/11/2011 10:00 AM, Bart Coninckx wrote:
No way. Rdiff will not take care of things like what you need to boot
Windows. You need dd or another imaging tool there. If you use Xen
devices on image files you can obviously easily copy them. If you use
block devices or LVM, you're back to dd or something else.

On 02/11/11 00:01, Paul Piscuc wrote:

I'll be testing the method also, for different Windows versions, with
and without memory state backed up. One more question thought ... what
are the performance and latency aspects of doing a xm save on a Windows
machine? Does is save only the memory state, or other information
regarding the state of the machine?

And one more thing we can test. What about restoring a rdiff backup(+MBR
backup) to a fresh lvm disk ... maybe it will boot in blue screen, but
it might work.

On 02/11/2011 12:36 AM, James Harper wrote:
Hi Mike,

agreed. For situations however where data files that are typically
opened with user applications like Word, Excel and other, I think it
might be safe to just snapshot the underlying LVM while the Windows DomU
is running and the users are not accessing the files (typically at
night), mount this and copy from it. I'm actually testing this now. If
there's interest I will post my findings.

The Citrix Windows PV drivers include a VSS provider that (I think)
allows you to ensure that your snapshot is consistent at both a
filesystem and application level. I've thought about this for GPLPV
but have never actually done anything about it.


Best regards,
System Administrator - Appnor MSP S.A.
US: (+1) 650 336 57 50
RO: (+4) 021 569 46 56

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>