Dean Wilson@UnixDaemon: ... It's not even close to relevant.

Wed, 07 Jul 2004

Just Don't (1 of ?)
Just don't copy MySQL data files while the tables are in use and expect the backup to work.

The conversation was going to be a painful one, sysadmin, the hero of our story felt it in the stream of vindaloo sauce that passed as his blood. "I noticed that our MySQL backups are just raw copies of the data files. I also saw some errors from the tar command about the files being written to while the backup was being run." "Yes, we know about that risk but if we ever need one of the backups we can probably repair the tables." "But isn't the worst possible time to try and repair tables when we have a broken system and need the actual data?" "We've never needed them so far. Anyway this doesn't lock the database or slow it down." *sound of head hitting desk*

If this is you PLEASE think about the possible options, a separate replication host that can be stopped and backed up, online backups (if you use InnoDB tables) or even (this is also bad) just a read lock and table by table SQL dumps are better than copying data you know is probably in an inconsistent state.

Like this post? - Digg Me! | Add to del.icio.us! | reddit this!

Posted: 2004/07/07 21:35 | /justdont | Permanent link to this entry | This entry + same date

August 2008	10
July 2008	9
April 2008	4
March 2008	1
February 2008	1
January 2008	15
August 2007	2
June 2007	9
May 2007	6
April 2007	8
March 2007	31
February 2007	3
January 2007	21
December 2006	1
November 2006	4
October 2006	6
September 2006	32
August 2006	17
July 2006	14
June 2006	9
May 2006	13
March 2006	11
February 2006	16
January 2006	11
December 2005	1
November 2005	6
October 2005	19
September 2005	25
August 2005	16
July 2005	16
June 2005	13
May 2005	2
April 2005	19
March 2005	31
February 2005	20
January 2005	31
December 2004	21
November 2004	30
October 2004	32
September 2004	18
August 2004	7
July 2004	14
June 2004	5