A Nice SQL dump with table locked are also very good, the problem is you will lock the database for the time needed to dump it. If you do it good like:
lock all tables flush logs dump unlock tables you will know where to start in case of recovery dump+binary logs Cheers! Claudio 2010/4/21 Johan De Meersman <vegiv...@tuxera.be> > > > On Wed, Apr 21, 2010 at 10:50 AM, Claudio Nanni > <claudio.na...@gmail.com>wrote: > >> Johan, >> Is the fact that InnoDB ignores the command FLUSH TABLES WITH READ LOCK; >> enough? :) >> >> InnoDB has buffers and activities going on even if you locked the tables >> and you are not sure that its buffers are on the disk when you snapshot. >> Again, you might be lucky and trust in the InnoDB recovery, what I state >> is that there is only one 100% guaranteed safe way to have binary backups. >> > > Aha, that's a tidbit I didn't know :-) It does hold back queries, but the > engine doesn't stop it's maintenance threads. > > I tend to do a full dump with --single-transaction once a week, and copy > the binlogs on the other days, though. That should suffice, I guess ? :-) > > > -- > Bier met grenadyn > Is als mosterd by den wyn > Sy die't drinkt, is eene kwezel > Hy die't drinkt, is ras een ezel > -- Claudio
