Shamgar
June 3rd, 2007, 01:00 PM
I recently setup this tool, and switched to using binlogs (which honestly - I should've been using all along, but this is the first time in a long time I haven't had replication in place for the systems)
One of the databases I am trying to back up with it sees a *lot* of activity, so the binlogs are fairly large - which is causing space issues for me. It seems like once they are backed up (at the very least in a full backup) they ought to be deleted. (Historically with other database systems that's the way I've done it anyway). However, for some reason that doesn't seem to be happening.
Is there an aspect of the configuration that I have missed for making this happen? Or do I need to setup a custom job to handle this?
One of the databases I am trying to back up with it sees a *lot* of activity, so the binlogs are fairly large - which is causing space issues for me. It seems like once they are backed up (at the very least in a full backup) they ought to be deleted. (Historically with other database systems that's the way I've done it anyway). However, for some reason that doesn't seem to be happening.
Is there an aspect of the configuration that I have missed for making this happen? Or do I need to setup a custom job to handle this?