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: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Block level domU backup
From: "Agent Rooker" <agentrooker@xxxxxxxxx>
Date: Thu, 30 Oct 2008 15:18:35 -0500
Delivery-date: Thu, 30 Oct 2008 13:19:22 -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:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=NqdlCNqd6mizuUkgA+Tmx46nuphoX/SaR1Wpw776GVE=; b=JrxaaI2fd7Mlo18+Auqvt1VnpYRjyQqXr695lT/Z956qF44AqfX8yKznHr7Ig9eUzf Kdwgluvn/Kc4FLTw4B25zWSRLRc7omC8ygDIcFgahJcluxK2GgKHb+x0JTOb6woPwIKB tuTOgKuC+AanaG4pLb6IO60sDI1sXIJguOzew=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=gOPbYeo7voLpOAD+s3Y3w0mErjXpuxV3x/MPn1k7Pzlv86jH3mzE7Mzq07weyltcow hqIaagAawzVyx65KfKdf4VSOuSmL32K4WdRgIT98YIpQVUd3CufYZ/Oi3pZHJ9lyL3cD 2izJ5rpt+48vpqMG4tquexqeoscNvU3maqa+w=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49083C22.2060207@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: <391d22bc0810281049u7bed51adw52ed00ca5c5f9c4a@xxxxxxxxxxxxxx> <20081028181028.GA10019@tp> <391d22bc0810281402v4f0dacah626505797e4b5135@xxxxxxxxxxxxxx> <49083C22.2060207@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Oct 29, 2008 at 5:34 AM, John Haxby <john.haxby@xxxxxxxxxx> wrote:
> Agent Rooker wrote:
>>
>> On Tue, Oct 28, 2008 at 1:10 PM, Nick Anderson <nick@xxxxxxxxxxxx> wrote:
>>
>>>
>>> The one case where I figured there would be a window for corruption
>>> was if information was coming over the wire that was being written.
>>>
>>
>> So would this be any worse than just yanking the network cable?
>>
>>
>>
>
> Yes.   When you take a snapshot backup of domU you're basically doing a
> fork() of a running system.   The parent, the original continues and runs
> all its outstanding transactions (receiving mail, sending mail, buying CDs
> from Amazon) and those transactions complete.
>
> When (or if) you restore the snapshot backup those half-completed
> transactions will continue as well.  Anything in-bound will have been lost
> and chances are the worst that will happen is that you'll log a message.
>  Anything outbound will be duplicated -- two copies of a mail messages, two
> CDs from Amazon, credit card debited twice.  Oops.
>
> You can, of course, prepare a system for a snapshot (or fork) so that
> transactions are completed or arrangements made for those important ones to
> not continue in the forked copy.   This isn't a problem unique to Xen, of
> course, you can have this problem with normal, bare-metal backups and
> transactions that are held on disk rather than in memory -- it's just that
> when you do bare-metal backups you're selective about what you back up and
> you don't typically backup things like, for example, the sendmail queue.
>
> jch
>
>

Assuming these transactions are done over TCP, wouldn't the duplicate
outgoing packets be discarded by the receiving server as out of order?
 The exact workings of TCP are a little out of my depth, but that is
my understanding of it.

But let's suppose that you're right.  What if I just disable
networking in the xen config file before doing an emergency restore
and then shutting down the domU cleanly before starting it up again
with networking.  That should make the process of restoring a domU
less risky.


-- 
Agent Rooker

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