[Burp-users] retention plan for database backups
Brought to you by:
grke
|
From: Christian V. <chr...@gm...> - 2017-03-06 14:29:57
|
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 |