Recovering mysql data - mysqlbinlog
vaughajj at jmu.edu
Thu May 1 19:13:49 UTC 2008
Thank you Mel and Paul for the suggestions. From what I understand the
general query log is more for debugging and the binary log is for point in
time recovery and replication. I'll be adding a my.cnf file (using the
my-large.cnf as a skeleton) soon. I'm glad the issue was caught earlier on
and now I'm the wiser thanks to you guys. I wonder why the default is no.
I can't think of anyone who wouldn't find the binary logging beneficial.
I didn't run myisamchk since I'm trying to restore data that was mistakenly
deleted and not recovering from a corruption.
From: Mel [mailto:fbsd.questions at rachie.is-a-geek.net]
Sent: Thursday, May 01, 2008 2:23 PM
To: freebsd-questions at freebsd.org
Cc: John; jjvaughan at gmail.com
Subject: Re: Recovering mysql data - mysqlbinlog
On Thursday 01 May 2008 19:45:32 John wrote:
> Can someone direct me to where the MySQL transaction logs are stored? I
> running FreeBSD 6.1 with MySql 5.0.41 which I installed from ports, no
> extra config. From what I've read online, unless you disable them (which
> couldn't find in the makefile) the logs should be being created. Doing a
> find / --name "bin." Didn't turn up anything.
By default they end up in /var/db/mysql and are named $hostname-bin.###
Also, the information you read online is incorrect. By default, binary
(which are the transaction logs) is disabled. I don't recall whether this is
a FreeBSD port specific modification.
You can turn it on by putting a my.cnf in /var/db/mysql. Templates named
my-$size.cnf are in /usr/local/share/mysql and are well-commented.
> I'll also note that it is not in var/db/mysql with the rest of the mysql
> data files and the ib_logfiles which would have been useful, but the data
> am trying to recover is from a MyISAM.
I take it you tried myisamchk?
Problem with today's modular software: they start with the modules
and never get to the software part.
More information about the freebsd-questions