archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <>
To: LVM general discussion and development <>,
	Far Had <>
Subject: Re: [linux-lvm] lvm.conf backup section
Date: Wed, 28 Nov 2018 12:05:54 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Dne 28. 11. 18 v 10:51 Far Had napsal(a):
> Hi
> There are two parameters in lvm.conf which I don't understand the exact 
> meaning of.
> 1. retain_min
> 2. retain_days
> What do "*the minimum number of archive files you wish to keep*" and "*minimum 
> time you wish to keep an archive file for*" mean?
> Is there any auto deletion mechanism for backup archives?


There is kept history for 'created' VGs, where you can specify how many
and for how long archives for individual VG you want to store.

This works reasonably well if you use 'same VG names' all the time.

However - when you use lvm2 on some testing machine where the VG name is 
essentially some random hash md5 lengthy string - you will sooner or later end 
with gazillion archive files in your /etc/lvm/archive directory.

In this case it's admins responsibility to prune VG archive files that are no 
longer necessary.

lvm2 has no idea if the VG named like: "myvg01320982woicdo8uagcd97wghcd"
will be still ever needed again - so such archives are kept mostly forever....

Every command you run which modifies metadata of particular VG does care only 
about that particular VG and it's archives.

Hopefully this explains it.



  reply	other threads:[~2018-11-28 11:05 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 [this message]
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
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).