WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] Backup solution

To: "'Fajar A. Nugraha'" <fajar@xxxxxxxxxxxxx>, "'xen-users'" <Xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Backup solution
From: "Artur Linhart" <Artur.Linhart@xxxxxxxxxxx>
Date: Mon, 9 Jul 2007 19:28:36 +0200
Delivery-date: Tue, 10 Jul 2007 10:04:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4688CAD0.9080208@xxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4688B9D1.8000606@xxxxxxxxxxxxx> <4688BCA3.4070200@xxxxxxxxxxxxx><4688C54D.2050305@xxxxxxxxxxxxxx> <4688CAD0.9080208@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ace8jmzLuf2WsZ4yQSezVukD03Vu/wFvbbKQ
OK, but - if You create the LVM snapshot volume and make the backup of it,
You assume the OS running in VM has written everything correctly to the
logical volume and the logical volume is in consistent state. 
But this assumption seems to be dangerous for me, especially by Windows DomU
- how can You be sure, the OS hdd driver has written everything to the
logical volume before You create the snapshot volume?

I would like also to use the LVM snapshots for backup, but this topic is a
problem for me, which I could not solve yet...

        With regards

                Archie

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Fajar A. Nugraha
Sent: Monday, July 02, 2007 11:52 AM
To: xen-users
Subject: Re: [Xen-users] Backup solution

Xin Chen wrote:
> but LVM snapshot still has risk, must be survived from a  power failture.
> correct me if i am wrong...
> what I do now is shutdown, copy, start....
>

Correct.
However, for production system, you'd generally design a system that
MUST be able to survive a power failure/hard reboot anyway. This means
activating archive log (for Oracle), using Innodb (MySQL), using
journaling filesystem, etc. So this shouldn't be an issue.

Reading Jordi's post I assume his priority was how to keep the VM during
backups, so LVM snapshot should be a feasible solution.

Regards,

Fajar

> Fajar A. Nugraha wrote:
>
>> Jordi Espasa Clofent wrote:
>>  
>>
>>> Hi all,
>>>
>>> We are planning to use XEN VPS in production environment. Before it we
>>> need to design a realiable backup policy for obvious reasons. I view
>>> two approaches:
>>>
>>> a) Use a "snapshot" system for backup ALL VM file (image).
>>> b) Use a traditional backup system (rsync, tar, cpio) for backup
>>> SELECTED data into VM.
>>>
>>> I prefer A option but I've read in this list it is not possible unless
>>> you stop de VM during a few time (the time required for backup
>>> operation itself).
>>>   
>>
>> If your vm image are files, and use LVM snapshot, you don't need to STOP
>> the VM for backup.
>> This thread might help you :
>> http://lists.xensource.com/archives/html/xen-users/2007-06/msg00688.html
>>
>> Regards,
>>
>> Fajar


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


__________ Informace od NOD32 2373 (20070703) __________

Tato zprava byla proverena antivirovym systemem NOD32.
http://www.nod32.cz



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

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