Re: Point-in-Time (Incremental) Recovery Using the Binary Log

[Gerard Roy Co]

Hi,

Engine = INNODB
MySQL server version = 5.5.20 MySQL community server

when restoring the data from binlog, i got so many error for Duplicate Entry and when i checked the binlog content it seems that auto_increment causing the issue, the auto_increment values are not exactly same as the mysqldump backup data even i issue FLUSH TABLES WITH READ LOCK.

What i did to get rid of the Duplicate Entry, I comment out all the SET INSERT_ID

Like this #SET INSERT_ID and tried to restore again and gives no error. Im not sure if im doing the correct way, is it safe?

Thanks