Re: [Burp-users] retention plan for database backups

[Pablo D. E. D. <pab...@gm...>]

Another tricky way but much more safest is to use 2 clients configs with 2
different names.

So in you /etc/burp dir you could have:

burp.conf
burp_logs.conf

then unique difference on both confs are:

cname=

You could name the burp_logs.conf cname=client_blogs (or whatever client
name you want).

Then on server side at /etc/burp/clientconfdir

You will have new file

client_blogs  (the name choosen on burp_logs.conf client file)

and unique difference will be:

include = /path/to/binarylogs
keep = 10

Also remmember to exclude the binarylogs on normal client backup, you could
do that al profile or clientconfdir level.


On client side you will need new cron task with line: burp -c
/etc/burp/burp_logs.conf -a t

This will make two clients for one server, but will allow to choose two
different selections of paths and two different retentions.

Maybe is tricky but allows you to do what you want on safest way.


El mié., 8 mar. 2017 a las 9:12, Michael Kohne (<mh...@ko...>)
escribió:

> On Wed, Mar 8, 2017 at 1:55 AM, Graham Keeling <gr...@gr...> wrote:
> > On Mon, Mar 06, 2017 at 03:29:44PM +0100, Christian Vieser wrote:
> >> Hi,
> >>
> >> I'm curious how to set up proper retention for our database backups.
> With our current system, we transfer daily db dumps and hourly binarylogs
> to the backup server. Data is deleted on the db servers after successful
> transfer to the central backup space.
> >>
> >> The daily full backups should be kept for 4 weeks, while the binarylogs
> (needed for point in time restore) only need a retention of 10 days. I
> currently see no easy way to define such a policy with burp, but perhaps I
> have overseen something. For the reduction algorithm of burp every single
> backup session seems to be equivalent, I've seen no possibility to mark the
> full backups as superior to the incrementals. If I interpret the manual
> correctly, it would work if I could manage to declare the full backups as
> "hardlinked". But unfortunately this seems to be no client option, so I
> can't set it along with the client backup invocation.
> >>
> >> Is there any way I could achieve the intended behaviour? Any
> suggestions how to change my backup procedure? (keeping the backup data on
> the db servers is not possible, this would need too much diskspace)
> >>
> >> Thanks for any advice,
> >> Christian
> >
> > Hello,
> >
> > Sorry, but I don't know how to achieve what you want, other than by
> keeping at
> > least 4 weeks of continuous backups.
> >
> > That is:
> > keep = 28
> >
>
> If you were to set hardlinked_archive=1 (making EVERY backup
> hardlinked) and keep=28 (or more) in your burp server config, then you
> could (via some other script) remove any backup you like without
> compromising burp's ability to restore from the remaining backups.
>
> YOU would have to take responsibility for figuring out which backups
> can safely be removed at that point.
>
> ALSO - this may significantly increase the amount of disk space that
> you'll need for backups, given that you'd be giving up deltas in burp.
>
>
> --
> Michael Kohne
> mh...@ko...
>
>
> ------------------------------------------------------------------------------
> Announcing the Oxford Dictionaries API! The API offers world-renowned
> dictionary content that is easy and intuitive to access. Sign up for an
> account today to start using our lexical data to power your apps and
> projects. Get started today and enter our developer competition.
> http://sdm.link/oxford
> _______________________________________________
> Burp-users mailing list
> Bur...@li...
> https://lists.sourceforge.net/lists/listinfo/burp-users
>
-- 
Pablo.