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: Fri, 23 Nov 2007 09:27:06 +0100 [thread overview]
Message-ID: <1195806426.5874.4.camel@localhost> (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)???
Would it also work when I create lv_storage, take a snapshot of it and
then when I need to restore a virtual machine I tempararly export the
snapshot true iSCSI to the Xen server.
Then on the Xen server I should see the PV and LV's Xen created both on
the real iSCSI exported disk, as the exported snapshot from the storage
server. So then I should be able to do a dd from one lv to the other,
right?
>
> > 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..
prev parent reply other threads:[~2007-11-23 8:27 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
2007-11-23 8:27 ` S. J. van Harmelen [this message]
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=1195806426.5874.4.camel@localhost \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).