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

[Xen-users] Re: 100% safe way to backup domU: (was Yet another backup)

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: 100% safe way to backup domU: (was Yet another backup)
From: "Ulrich Windl" <ulrich.windl@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 12 Jan 2007 09:27:40 +0100
Delivery-date: Fri, 12 Jan 2007 00:28:17 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070111203952.GA30834@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/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>
Organization: Universitaet Regensburg, Klinikum
Priority: normal
References: <200701111954.33047.mark.williamson@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 12 Jan 2007 at 2:09, Ligesh wrote:

[...]
>  I forgot about the 'save' feature. If we have a consistent file system that 
> can be mounted and backed up, and if we add the ram separately, the we have 
> the entire state of the system. So I think the actual steps would be.
> 
>  xm sync-and-save domU file

Complete overkill IMHO: When having a say 8GB virtual RAM DomU, saving of the 
virtual RAM takes a very long time (several minutes).

>  take lvm snapshot
>  xm restore file
>  backup snapshot + file
> 
> 
>   Backing up the all the domUs live from the dom0 is an extremely
> important feature. In the hosting industry, taking down the server for
> getting a task done is not an idea that people can even understand, let
> alone accept. 

Actually I believe that in a HA environment where several related files are 
used 
to store some state, a transactional database should be used instead. You are 
fighting symptoms, not the bugs. If strong time-relationship of file contents 
is 
not necessary, a plain backup (full or incremental) would be sufficient.

You are talking about desaster recovery: A desaster by definition is something 
noticable. When planning for desaster, why care about varying point-in-time 
backups, when you actually may loose several hours of data?

For the non-desaster: Just restore the last (or any other) saved version of the 
file desired to be restored.

Regards,
Ulrich


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

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