Re: Chronicle of fixing broken replication, and a question

2011-07-26 Thread Reindl Harald
Am 26.07.2011 19:13, schrieb Todd Lyons: > On Tue, Jul 26, 2011 at 8:18 AM, Reindl Harald wrote: >>> 1. I did a full copy of the running master database server using >>> xtrabackup to a backup server via nfs. It took 2 hours, of which the >>> last 15 minutes did a write lock of the entire serv

Re: Chronicle of fixing broken replication, and a question

2011-07-26 Thread Todd Lyons
On Tue, Jul 26, 2011 at 8:18 AM, Reindl Harald wrote: >> 1.  I did a full copy of the running master database server using >> xtrabackup to a backup server via nfs.  It took 2 hours, of which the >> last 15 minutes did a write lock of the entire server as it copied >> over the *.frm files and the

Re: Chronicle of fixing broken replication, and a question

2011-07-26 Thread Reindl Harald
Am 26.07.2011 16:18, schrieb Todd Lyons: > 1. I did a full copy of the running master database server using > xtrabackup to a backup server via nfs. It took 2 hours, of which the > last 15 minutes did a write lock of the entire server as it copied > over the *.frm files and the few myisam tabl

Chronicle of fixing broken replication, and a question

2011-07-26 Thread Todd Lyons
Yeah it happens to all of us. Some master->slave replication system breaks and goes unnoticed. In my case, I had a monitoring script, but it was being called with a --verbose flag, and internally that "verbose" was being mapped to "debug", and the routine to notify sysadmins of broken replication