From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References:

In-Reply-To: From: Far Had Date: Wed, 28 Nov 2018 15:48:15 +0330 Message-ID: Content-Type: multipart/alternative; boundary="000000000000c9e508057bb88e77" Subject: Re: [linux-lvm] lvm.conf backup section Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: To: zkabelac@redhat.com Cc: linux-lvm@redhat.com --000000000000c9e508057bb88e77 Content-Type: text/plain; charset="UTF-8" Thanks for the response, but I still don't get the point. Assume that I use same names for my VGs, In this case if I do for example: *retain_days = 10* and *retain_min = 15* in lvm.conf file, what is the system's behaviour when archiving backup files? Please explain specifically. On Wed, Nov 28, 2018 at 2:35 PM Zdenek Kabelac wrote: > 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? > > Hi > > > 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. > > Regards > > Zdenek > --000000000000c9e508057bb88e77 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Thanks for the response,

but I still don't get the= point. Assume that I use same names for my VGs, In this case if I do for e= xample:

retain_days =3D 10

and

reta= in_min =3D 15

in lvm.conf file, what is the system's beha= viour when archiving backup files? Please explain specifically.

=

On Wed, Nov 28, 2018 at 2:3= 5 PM Zdenek Kabelac <zkabelac@red= hat.com> wrote:

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*&q= uot; and "*minimum
> time you wish to keep an archive file for*" mean?
> Is there any auto deletion mechanism for backup archives?

Hi

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: "myvg01320982woicdo8uagcd97wghc= d"
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 on= ly
about that particular VG and it's archives.

Hopefully this explains it.

Regards

Zdenek

--000000000000c9e508057bb88e77--