Kern Sibbald wrote:
> On Tuesday 06 September 2005 08:49, Masopust Christian wrote:
>>Hello all,
>>Bacula run fine till last weekend. Since Sunday every job fails with
>>messages that entries to database ("INSERT INTO FILE (......") could not be
>>made because of "Duplicate entries"....
>>
>>First i thought that i caused this problem myself as i run a "mysqldump" of
>>the whole bacual-db last week and after that i reloaded id (maybe dumb, but
>>i heard that this could decrease size of db a little as mine is above 8GB).
>
> Hmmm. It looks like MySQL may have changed the behavior of their
> dump/restore,
> which used to delete everything before doing a restore. If you did not
> explicitly delete your database before doing the restore, you probably
> unknowingly duplicated all the records -- not very good.
Unless I'm missing something, there is no mysqlrestore utility, and if
loading a dump into mysql has ever cleared the database first, it's news
to me.
Even using the deprecated BACKUP TABLE and RESTORE TABLE commands, which
work only on MyISAM tables, a RESTORE TABLE will fail if the table
already contains data (or, I think, if it exists at all).
That said, inserting a row that already exists but has a unique primary
key SHOULD fail rather than creating a duplicate row.
--
Phil Stracchino [EMAIL PROTECTED]
Renaissance Man, Unix generalist, Perl hacker
Mobile: 603-216-7037 Landline: 603-886-3518
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
