Linux LVM users
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Backup/Recovery Strategies
Date: Mon, 8 Nov 2004 18:33:15 +0100	[thread overview]
Message-ID: <20041108173315.GA21451@redhat.com> (raw)
In-Reply-To: <20041106221645.0AFFA97930@snark.apl.washington.edu>

On Sat, Nov 06, 2004 at 02:16:46PM -0800, Axel Schweiger wrote:
> Can anyon  suggest backup/recovery strategies for filesystems under LVM.
> (Version 1 and 2)
>  
> 1) If I loose the data in the /etc/lvm directory (or lvm.d) do I loose the
> filesystems controlled by lvm?

No, those are work files which can be recreated running vgscan
for LVM1. LVM1 keeps metadata archive files in /etc/lvmconf/ which
needs to be covered by your backup.

By default, /etc/lvm/ contains subdirectory for metadata archive in
the case of LVM2.

Best practice therefore is to backup /etc/lvm*

> 2) How do I recover from a loss or corrpution of the LVM data.

vgcfgrestore the recent metadata archive (from /etc/lvmconf/ for LVM1
or from /etc/lvm/backup/ for LVM2.

> 3) What happens if the LVM filesystems have changed since the last backup of
> the metadata?

You are refering to VGs and LVs here.

If you don't have an actual backup of /etc/lvm* *and*
corrupt your LVM metadata on the defices after a change, you can
restore the most recent archive from your last /etc/lvmconf/ backup (LVM1)
or from /etc/lvm/backup/ (LVM2) which might be ok still or not, depending
on your changes.

>  
> Sorry if this shows a profound lack of understanding of LVM but I''m new to
> this and haven't been able to find any recipes for doing 
> backups?

The only LVM related backup is about its metadata archives and covered
in 'man lvm'.
Of course all data stored in LVs should be subject to regular backups
as with any block devices.

> 
> Thanks much
> Axel

> _______________________________________________
> 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/

-- 

Regards,
Heinz    -- The LVM Guy --

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Red Hat GmbH
Consulting Development Engineer                   Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@RedHat.com                            +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2004-11-08 17:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-06 22:16 [linux-lvm] Backup/Recovery Strategies Axel Schweiger
2004-11-08 17:33 ` Heinz Mauelshagen [this message]
2004-11-17 21:54   ` [linux-lvm] LVM Config Files Krzysztof
2004-11-17 23:59     ` Jetkins
  -- strict thread matches above, loose matches on Subject: below --
2004-11-08 18:40 [linux-lvm] Backup/Recovery Strategies Axel Schweiger

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=20041108173315.GA21451@redhat.com \
    --to=mauelshagen@redhat.com \
    --cc=linux-lvm@redhat.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