All of lore.kernel.org
 help / color / mirror / Atom feed
From: "S. J. van Harmelen" <svh@dds.nl>
To: malahal@us.ibm.com
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM snapshots in a iSCSI and XenSource environment
Date: Tue, 20 Nov 2007 18:56:18 +0100	[thread overview]
Message-ID: <1195581378.10434.29.camel@sanderbal> (raw)
In-Reply-To: <20071120172910.GA26444@us.ibm.com>


On Tue, 2007-11-20 at 09:29 -0800, malahal@us.ibm.com wrote:
> S. J. van Harmelen [svh@dds.nl] wrote:
> > 
> > Now my thoughts where to take snapshots on the storage server. So that
> > would mean I would take a snapshot of lv_storage. This should not be a
> > problem. But what if virtual machine 2 crashes and has to be restored?
> > 
> > In that case I cannot restore lv_storage with a dd command, because then
> > all the data will be restored (lv_virtualmachine1 and
> > lv_virtualmachine2, because they are both on lv_storage). So is it
> > possible to "restore" only lv_virtualmachine2 when I took a snapshot of
> > lv_storage?
> 
> I see, it is possible but a bit cumbersome. You should be able to run
> LVM on the storage server on the restored/old data (LVM on top of LVM??) and
> get the data for the lv_virtualmachine2 from the storage server to
> XenSource (ftp/tar whatever method). Then, restore that data (tar
> extract) at XenSource.
> 
> If things are NOT changing at the XenSource LVM, you could just "dd" on
> the crashed LV, but things may go really bad otherwise.
> 
> Any better method(s)???

Well of course this could also be done from the Xen server. Then there
is no need for LVM on the storage server and the lv_storage part can be
left out of this picture.

I could then create a second iSCSI target on a second LUN to export to
the Xen server so that Xen can take snapshots to that second exported
disk. If a problem does occur, then a restore is simple because then I
could do a dd from the snapshot lv (on the Xen server) to the other lv
(also on the Xen server).

But how about network traffic on this one? Everything I do will go
across iSCSI so it will go over the network.

And then I will manually have to greate lv-snapshots for each virtual
machine instead of just one big lv-snapshot as I could do when
lv_storage exists.

Any thoughts?

> 
> > I can see the PV and LV's Xen created on lv_storage on the storage
> > server when I run pvs by the way...
> 
> Yes, you will see them but you want the storage server's LVM to NOT use
> them under normal conditions.
> 
> BTW, for backup, you may want snapshot-origin target rather than snapshot
> target directly..

  reply	other threads:[~2007-11-20 17:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20 11:13 [linux-lvm] LVM snapshots in a iSCSI and XenSource environment S. J. van Harmelen
2007-11-20 11:37 ` Tomasz Chmielewski
2007-11-20 12:21   ` S. J. van Harmelen
2007-11-20 13:06     ` Tomasz Chmielewski
2007-11-20 16:12       ` S. J. van Harmelen
2007-11-20 17:29         ` malahal
2007-11-20 17:56           ` S. J. van Harmelen [this message]
2007-11-23  8:27           ` S. J. van Harmelen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1195581378.10434.29.camel@sanderbal \
    --to=svh@dds.nl \
    --cc=linux-lvm@redhat.com \
    --cc=malahal@us.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.