From: "Perplexer" <perplexer@thz.net>
To: mauelshagen@redhat.com,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] *** Hint: Metadata Backups ***
Date: Fri, 19 Mar 2004 13:44:34 +0100 [thread overview]
Message-ID: <000701c40daf$ef7f9410$0400a8c0@vector> (raw)
In-Reply-To: 20040319105619.GA8676@redhat.com
Should that be backupped regulaly (as in every week or so) or only after
actual changes to VGs/LVs (added/removed VG, added/removed PV,
added/removed or extended LV, ...) ?
---------
Perplexer
----- Original Message -----
From: "Heinz Mauelshagen" <mauelshagen@redhat.com>
To: <linux-lvm@redhat.com>
Cc: <hjm@redhat.com>
Sent: Friday, March 19, 2004 11:56 AM
Subject: [linux-lvm] *** Hint: Metadata Backups ***
>
> Please remember to include the LVM Metadata
>
> o /etc/lvmconf/ for LVM1
> o /etc/lvm/ for LVM2
>
> in your regular backups.
>
> Those are necessary in case metadata on your PVs gets accidentially
> overwritten (e.g., some diligent installer) in order to recover
> with vgcfgrestore(8).
>
>
> 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
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> _______________________________________________
> 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/
>
prev parent reply other threads:[~2004-03-19 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 10:56 [linux-lvm] *** Hint: Metadata Backups *** Heinz Mauelshagen
2004-03-19 12:44 ` Perplexer [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='000701c40daf$ef7f9410$0400a8c0@vector' \
--to=perplexer@thz.net \
--cc=linux-lvm@redhat.com \
--cc=mauelshagen@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 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.