On Monday 01 October 2007 13:06:52 Frank Sweetser wrote: > Christoph Klünter wrote: > > Hi, > > > > We are doing full backups for all clients on the first Sunday of the > > month. Every Month our Mysql-Database gets corrupted during a Full > > Backup: > > > > 30-Sep 06:43 backup02-dir: develJob.2007-09-30_01.42.12 Fatal error: > > sql_create.c:751 sql_create.c:751 insert INSERT INTO File > > (FileIndex,JobId,PathId,FilenameId,LStat,MD5) VALUES > > (62943,17583,1270644,7391280,'gF pYle IGk B h h A BLmL BAA Jo BG/FGu > > BG3n6P BG+67E A A E','Si5GuPTd5ntZ1av6n1J0lw') failed: > > Duplicate entry '205008230' for key 1 > > I'd very strongly recommend that you run a mysql repair on all of your > tables to make sure that there isn't any low level corruption causing the > problems. There was a corrupt table this month, but not last. But MySQL didn't crash. How can a Table get corrupted without any mysql-Errors ? Strange. I think I should use Postgresql :-)
Regards, Christoph ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
