The binary log is useful for more then just replication and can be used to
take incremental backups or to perform forensics on what your server has
done. I would recommend learning how to use them to your advantage over
turning binary logging off as some have recommended. Make sure you're
monitoring your storage so you don't end up running out of space. Use
to auto purge your logs and if you have replication in place ensure that
this is set high enough so that you don't remove logs that haven't been
used by the slave.
On Mon, Nov 14, 2011 at 6:15 PM, Basil Daoust <bdaoust@stripped> wrote:
> If you search on "mysql-bin.000001" you get a lot of good info.
> o They are mysql log files it contains all the queries u can view
> these files with the command mysqlbinlog just man it for more details
> o These are your binary log files.. you might not want to switch them
> off depending on your setup - but you can purge them (look in the
> manual for PURGE MASTER LOGS)
> I've heard people talk about using them for recovery.
> I know they are used for replication.
> You can delete/purge the old ones that you have a backup for, because
> trying to recover by playing them all back is probably not a realistic
> On Mon, Nov 14, 2011 at 12:01 PM, Rob Tanner <rtanner@stripped> wrote:
> > Hi,
> > In my MySQL directory, I have more than a few gig and a half sized
> files, mysql-bin.000001, mysql-bin.000001 and et cetera. They date from
> today all the way back to early 2010. I don't know exactly what those
> files are but I would like to delete as many as are no longer is use since
> I had a 40GB partition fill up over the weekend which resulted in bringing
> down our web server. So what are those files and can I delete all but the
> most recent?
> > Thanks.
> > Rob Tanner
> > UNIX Services Manager
> > Linfield College, McMinnville Oregon
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1