Hello Jeremy, Friday, March 29, 2002, 3:10:35 AM, you wrote:
>> Also a good thing with DRBD you will not have to store and track >> replication log files and the setup will not require to take MySQL >> down to copy the snapshot of database. JZ> Why would you need to take down MySQL for a backup (assuming you use JZ> MyISAM tables at least)? To establish replication you need a snapshot for all of the tables for specific point so you may do it without shutting MySQL down by lock all tables read; flush all tables; flush logs and copy old one to separate place. copy all data for replication unlock tables; As you see this will block any updates to MySQL for the time you copy data (which may be rather long) The same thing you need if you want really consistent snapshot. If you will jut copy table one by one (even with mysqlhotcopy) the backuped data may be not logically consistent. -- Best regards, Peter mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
