[clug] database backups with git

[Alex Satrapa]

The main issue addressed through incremental backups and "maintain X weeks worth of backups" is the growth of the backup set. Does fit have a convenient way of collapsing old versions in order to save space? How much new or changed data is being added each time?

I have already experienced the problems of machines that stall due to well-intentioned but clueless people running backups with no plan to cull old backups. These problems can be addressed by monitoring disk consumption, routinely culling over-full directories, etc. better to not allow a problem to occur in the first place 

Alex Satrapa | web.mac.com/alexsatrapa | Ph: 0407 705 332

On 08/06/2012, at 12:15, Carlo Hamalainen <carlo at carlo-hamalainen.net> wrote:

> Most incremental backup tools have a way of deleting old increments (e.g. rdiff-backup has "--remove-older-than").