On Fri, Jun 11, 2004 at 03:38:05PM +0300, Egor Egorov <[EMAIL PROTECTED]> is thought to have said:
> "Tabor J. Wells" <[EMAIL PROTECTED]> wrote: > > > > Is it safe to just shutdown ServerB, copy all of the mysql data dir (including > > the ibdata files) to ServerC, restart ServerB, and then change the my.cnf of > > ServerC to set a new server-id, master-host, replicate-do-db entries and start > > ServerC? > > You better dump data using mysqldump. Don't forget the --opt option. Ugh. Well that leads to more questions: 1) How long will it take to restore this data (60ish gb) then? 2) If I use mysqldump -opt how do I handle the case where by the time I'm dumping db 20 of 23, db #1-20 may have changed? If they've changed then how can I be sure that that when replication starts those changes are done? Or will mysqldump -opt --all-databases actually lock all of them at once and unlock them all at the end? 3) Are you absolutely sure I can't just copy the files if mysql isn't running on ServerB? :) -- -------------------------------------------------------------------- Tabor J. Wells [EMAIL PROTECTED] Fsck It! Just another victim of the ambient morality -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
