linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Far Had <farhadk.it@gmail.com>
To: zkabelac@redhat.com
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] lvm.conf backup section
Date: Sat, 1 Dec 2018 16:14:15 +0330	[thread overview]
Message-ID: <CAB5m+-GyXYnSPxLszT7sRhLmHm4gwSGixkT2V821wAUCnnhSbA@mail.gmail.com> (raw)
In-Reply-To: <efff92af-60d9-fed7-4418-6f252994d781@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]

How does it *make sure* that I've backup files younger than 10 days old?
What if I delete those files?

On Wed, Nov 28, 2018 at 3:54 PM Zdenek Kabelac <zkabelac@redhat.com> wrote:

> Dne 28. 11. 18 v 13:18 Far Had napsal(a):
> > 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.
>
> Hi
>
> Archive file should be kept for at least 10 days, and there should be kept
> at
> least 15 archive files.
>
> So in better example:
>
> If you have i.e. many files generated daily - this makes sure you should
> have
> files at least 10 days back as well  (otherwise it could happen you could
> have
> backup only from last few recent commands)
>
> If you run lvm2 modifying commands very occasionally - you should still
> have
> at least 15 historical archives  (otherwise it could happen you could have
> very few archives if any....)
>
> As you can see both are 'arming' at slightly different work flow.
>
> Regards
>
> Zdenek
>

[-- Attachment #2: Type: text/html, Size: 1568 bytes --]

  reply	other threads:[~2018-12-01 12:44 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 [this message]
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:
  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=CAB5m+-GyXYnSPxLszT7sRhLmHm4gwSGixkT2V821wAUCnnhSbA@mail.gmail.com \
    --to=farhadk.it@gmail.com \
    --cc=linux-lvm@redhat.com \
    --cc=zkabelac@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).