linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Far Had <farhadk.it@gmail.com>
Subject: Re: [linux-lvm] lvm.conf backup section
Date: Mon, 3 Dec 2018 12:33:19 +0100	[thread overview]
Message-ID: <c40fad2f-09b0-a286-19ce-572b4536c1ed@redhat.com> (raw)
In-Reply-To: <CAB5m+-GyXYnSPxLszT7sRhLmHm4gwSGixkT2V821wAUCnnhSbA@mail.gmail.com>

Dne 01. 12. 18 v 13:44 Far Had napsal(a):
> How does it _make sure_ that I've backup files younger than 10 days old? What 
> if I delete those files?

Hi

Archives in /etc/lvm/archive subdirs are not 'a must have' - they are optional 
and purely for admin's pleasure.

So admin can erase them anytime he wants to - but in that case it's probably 
more clever to disable archiving in lvm.conf ;) as archiving eats some CPU...

lvm2 itself does *only* care about metadata stored in the 'metadata' area in 
PV header - where there is also ring-buffer which typically keeps pretty long 
history of all metadata modifications - this buffer has these days ~1MiB in 
size. So unless your metadata are pretty big - the history can be relatively 
easily extracted also out from this place for i.e. recovery purpose.

I must admit I don't understand the  'make sure' part of your question??
Are you aiming at some particular issue ??

Regards


Zdenek

  reply	other threads:[~2018-12-03 11:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28  9:51 [linux-lvm] lvm.conf backup section Far Had
2018-11-28 11:05 ` Zdenek Kabelac
2018-11-28 12:18   ` Far Had
2018-11-28 12:24     ` Zdenek Kabelac
2018-12-01 12:44       ` Far Had
2018-12-03 11:33         ` Zdenek Kabelac [this message]
2018-12-03 12:10           ` Far Had
2018-12-03 14:56             ` Zdenek Kabelac

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=c40fad2f-09b0-a286-19ce-572b4536c1ed@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=farhadk.it@gmail.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;
as well as URLs for NNTP newsgroup(s).