| List: | Replication | « Previous MessageNext Message » | |
| From: | Marcus Bointon | Date: | November 23 2007 10:21am |
| Subject: | Re: replication on Linux broken after db restore | ||
| View as plain text | |||
On 23 Nov 2007, at 09:15, FMGreen wrote: >> mysql> FLUSH TABLES WITH READ LOCK; If you're using InnoDB for everything, there is an alternative that's much less disruptive: mysqldump --opt --single-transaction --master-data > dump.sql This ensures that the data dump is in a consistent state and provides master log file and position info, ready to import into a slave. Marcus -- Marcus Bointon Synchromedia Limited: Creators of http://www.smartmessages.net/ UK resellers of info@hand CRM solutions marcus@stripped | http://www.synchromedia.co.uk/
| Thread | ||
|---|---|---|
| • replication on Linux broken after db restore | FMGreen | 21 Nov |
| • Re: replication on Linux broken after db restore | martÃn arrieta | 21 Nov |
| • Re: replication on Linux broken after db restore | FMGreen | 23 Nov |
| • Re: replication on Linux broken after db restore | Jan Bruvoll | 23 Nov |
| • Re: replication on Linux broken after db restore | Marcus Bointon | 23 Nov |
| • Re: replication on Linux broken after db restore | FMGreen | 23 Nov |
| • Re: replication on Linux broken after db restore | FMGreen | 23 Nov |
| • Re: replication on Linux broken after db restore | Christian Schramm | 21 Nov |
| • Re: replication on Linux broken after db restore | FMGreen | 22 Nov |
| • Re: replication on Linux broken after db restore | Christian Schramm | 22 Nov |
