[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [linux-lvm] Is it possible to bypass LVM and mount contained partition directly?



You might be able to make those partitions available using nbd from the server, importing them on the vms.

--rich

Hull, Brett (MSE) wrote:
Hello,

  Can you restore these backups to another system?  Such as one designated to do this job?  Maybe using a virtual machine? You could then create the environment restore the data and move the "recovered files" to the production box. I do not know your environment, but you might not want to change the backed up data because that is what you will use to restore if there is a full loss of data on your production system.

Best regards,
Brett

-----Original Message-----
From: linux-lvm-bounces redhat com [mailto:linux-lvm-bounces redhat com] On Behalf Of Ray Morris
Sent: Monday, May 31, 2010 2:45 PM
To: LVM general discussion and development
Subject: Re: [linux-lvm] Is it possible to bypass LVM and mount contained partition directly?

   In general, no, though in your specific case it may be
that all of the extents are stored contigously and it might
work. You would probably need to use losetup -o and specify
the offset.  This would be more of a last ditch data recovery
effort than something you'd design into a production system,
though.

   You might have better results altering one of these issues
that is causing you to consider such action:

  
 I can't import the pv/vg because they have the same name/uuid
as the existing VG (it's really the same system) and I can't change
them with something like vgimportclone because the backed up vm image
files are read-only.
    

   In other words, you would back up to one of the following questions:
How can I change the names and UUIDs of the backups?
How can I import an LV which has a conflicting UUID?
How can I use vgimport with a read only source?

   Specifically, you might be able to ignore the meta data on
the backup volumes with pvmetadatacopies  = 0 and use "dirs"
in lvm.conf, so you can change the working meta data even
though they are read only.
--
Ray Morris
support bettercgi com

Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/

Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/

Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php


On 05/31/2010 02:21:36 PM, Romeo Theriault wrote:
  
I apologize if this has been asked before but I was unable to find any
references to it in the mailing list archives and googling around
isn't helping much.

Is there a way to directly mount, bypassing LVM, a ext3 partition that
resides in a LVM LV and VG? It resides on one PV.

The problem is that I have read-only copies of VM's that are backed up
via a SAN based snapshot/backup tool. I'm trying to create a method to
allow the VM admins to restore their files from the snapshot backed up
VM's. I'm at the point where I can access the partitions and can mount
the ext3 partitions fine but I'm having trouble with the LVM volumes
because I can't import the pv/vg because they have the same name/uuid
as the existing VG (it's really the same system) and I can't change
them with something like vgimportclone because the backed up vm image
files are read-only.

Thanks for any help.

--
Romeo Theriault

_______________________________________________
linux-lvm mailing list
linux-lvm redhat com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


    


_______________________________________________
linux-lvm mailing list
linux-lvm redhat com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

_______________________________________________
linux-lvm mailing list
linux-lvm redhat com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
  

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]