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] Block level domU backup

To: "Javier Guerra" <javier@xxxxxxxxxxx>
Subject: Re: [Xen-users] Block level domU backup
From: "Agent Rooker" <agentrooker@xxxxxxxxx>
Date: Fri, 31 Oct 2008 16:09:29 -0500
Cc: Dustin.Henning@xxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 31 Oct 2008 14:10:16 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=+Ry4+lKsMxl/yTeao5jbEQJKhQrGOFjSLTFLjpBa8fs=; b=YCwIsIG90fEcRM/xRoF6dtiz0OF3dHePsc/zQBo6OXBIFqpdylIcfvWs744MP7aJEU dP8pACCI1gUnKW/j7hQbApwN80nYEhpJqOZfuqkR4hVYStLeJjxYIYwP8qA4aVMgoGHY hDgyBi40AA2RmZMpGL4KGwCRrPXEPsyAlhay4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=s+m3szfj8AQqxxRLvQPmzosruDZ1cgzKEPhfHEphm4ZHrJdUTs+s8hDXuabqBTw6Zh sJV3aSbCDyHHqxs6tZYxBQRVjxoHzUrTTbqR5Wp2K9U7sjcECKELWR4cEu8N1GTkS82b Kzh6QyiE6+/2zkOrRfIaIvuKoL+fU4pi9MTps=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <90eb1dc70810310705y7f1d96b8o67241216e66af4de@xxxxxxxxxxxxxx>
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: <391d22bc0810281049u7bed51adw52ed00ca5c5f9c4a@xxxxxxxxxxxxxx> <20081028181028.GA10019@tp> <391d22bc0810281402v4f0dacah626505797e4b5135@xxxxxxxxxxxxxx> <49083C22.2060207@xxxxxxxxxx> <391d22bc0810301318g15c55ba1n7b07dd05a92cd753@xxxxxxxxxxxxxx> <8149255414818938354@unknownmsgid> <90eb1dc70810310705y7f1d96b8o67241216e66af4de@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, Oct 31, 2008 at 9:05 AM, Javier Guerra <javier@xxxxxxxxxxx> wrote:
> On Fri, Oct 31, 2008 at 7:59 AM, Dustin Henning
> <Dustin.Henning@xxxxxxxxxxx> wrote:
>>        You are correct, outgoing packets that were part of a stream would
>> be discarded for being out of order.  However, new connections (for mail
>> about to be delivered from queue, for example) would be established as new
>> connections and go through.  This would be true even if you tried restoring
>> without networking, which may or may not be an option, as the mail would
>> still be in queue upon starting up.
>
> this would also happen with a traditional backup.
>
> not something to lose sleep on
>
>
> --
> Javier
>

Anyway, I finally got around to testing it.  Everything seems to work
just fine.  Here is my script's logfile for the test run with time
stamps.

Oct 31 15:27:20 --> Beginning sync.
Oct 31 15:27:20 --> Pausing domU webserver and saving xen checkpoint file...
Oct 31 15:27:40 --> Creating root snapshot...
  Logical volume "webserver_snapshot" created
Oct 31 15:27:43 --> Creating swap snapshot...
  Logical volume "webserver_swap_snapshot" created
Oct 31 15:27:43 --> Restoring Xen domU...
Oct 31 15:28:03 --> Syncing swap volume...
Oct 31 15:28:29 --> Removing swap snapshot...
  Logical volume "webserver_swap_snapshot" successfully removed
Oct 31 15:28:30 --> Syncing root volume...
Oct 31 15:30:08 --> Removing root snapshot...
  Logical volume "webserver_snapshot" successfully removed
Oct 31 15:30:09 --> Transferring checkpoint file...
Oct 31 15:30:42 --> Transferring config file...
Oct 31 15:30:43 --> Done!

As you can see, the domU remains paused for a little over 40 seconds,
and the snapshots exist for a little more than 2 minutes.  For those 2
minutes, I/O efficiency will suffer, but as long as we do this during
non-peak hours, it should be a non-issue.  I'm still nervous about
some bug in xen causing the domU to not restore after the snapshots
get created, but after some more extensive testing I hope to put that
worry to rest.

I did run into an issue when I restored the domU on the backup server.
 I was not able to ssh in.  That was the only service running on that
domU.  However, after restarting, I was able to ssh just fine, and
everything else seems normal.  I'll keep testing and report any
findings.


-- 
Agent Rooker

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

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