Date: Thu, 11 Feb 2016 10:52:20 -0800 From: Sergei G <sergeig.public@gmail.com> To: Alexander Moisseev <moiseev@mezonplus.ru> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: rolling backup Message-ID: <CAFLLzCOfaZxT=qu_cc7fD-SdaJckJyvLcLftuLv6e6o_6zpGGQ@mail.gmail.com> In-Reply-To: <af40c683-0474-8b00-0df1-ea58fd744c8c@mezonplus.ru> References: <56A5F7FF.1050606@gmail.com> <56A6017E.4020801@freebsd.org> <af40c683-0474-8b00-0df1-ea58fd744c8c@mezonplus.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
I ended up creating a rolling backup script. It does not use exponential strategy, but is simple enough for me: https://github.com/Kulak/rollingdump I pushed it to github as a backup strategy :) On Mon, Jan 25, 2016 at 3:37 AM, Alexander Moisseev <moiseev@mezonplus.ru> wrote: > On 25.01.16 14:05, Matthew Seaman wrote: > >> Deleting 'all but the last N' is a good strategy with backups. Suppose >> for whatever reason, backup fails for N nights in a row. If you just >> deleted backup files that were over N days old, you'ld be left without >> any backups at all after a certain time. However, keeping a certain >> number of files means that you still have some backups available, albeit >> older than would be ideal. >> >> An exponential expiry strategy can solve that problem. > > https://github.com/moisseev/rmexp/blob/master/rmexp/rmexp.pod > There is no support for backups stored locally as files yet, but it is not > complicated to add. > > -- > Alexander > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFLLzCOfaZxT=qu_cc7fD-SdaJckJyvLcLftuLv6e6o_6zpGGQ>