MySQL Forums
Forum List  »  Replication

Advanced Search
New Topic

Re: failure to setup replication using mysqldump and --single-transaction
Posted by: Rick James
Date: September 22, 2012 05:34PM

> I restored the backup on the slave server, then started the slave process and immediately started getting errors pertaining to being unable to write to tables due to duplicate entries for the primary key, which is auto incremented.

That sounds like you started the Slave at the wrong spot. Where did you get the parameters for the CHANGE MASTER?

I vote for Xtrabackup -- it has essentially zero downtime, or even lock time for InnoDB tables. mysqldump is more invasive.

I suspect that (for your case), letting xtrabackup lock the MyISAM and Archive tables would be a non-problem during certain times of the day.

Navigate: Previous Message• Next Message
Options: Reply• Quote


Subject
Views
Written By
Posted
failure to setup replication using mysqldump and --single-transaction
2695
Peter Sylvester
September 21, 2012 10:20AM
Re: failure to setup replication using mysqldump and --single-transaction
1349
Scott Nemes
September 21, 2012 11:29AM
Re: failure to setup replication using mysqldump and --single-transaction
1192
Peter Sylvester
September 21, 2012 11:52AM
Re: failure to setup replication using mysqldump and --single-transaction
1135
Rick James
September 22, 2012 05:34PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.