Re: Multiple-Master Replication recovery
Thanks a lot. I'll try. - Original Message - From: "Kishore Jalleda" <[EMAIL PROTECTED]> To: "古雷" <[EMAIL PROTECTED]> Cc: Sent: Wednesday, March 29, 2006 11:53 PM Subject: Re: Multiple-Master Replication recovery > any one of the servers could go down in many ways like > 1) disk crash > 2) replication failure > 3) power failure > 4) any hardware component failure > 5) OS hang > 6) Network failure > 7) MYSQL bug > 8) table corruption etc ... > 9) or just scheduled donwtime > > in any case what really matters is the difference in status of the failed > server from the point of failure to the point of recovery , so it all > depends on how up-to-date your data is on the failed server.. here are some > typical cases .. > 1) you have everything intact ( data, bin logs, *.info files, etc ) then > just bring back the failed server online and you are good to go > 2) if you rebuild the server from scratch it depends on how current your > backup is , in this take a snapshot of the main server ( either hot or cold > depending on your setup) and start the multi-master replication .. > > In theory you really dont have to take the server offline unless it really > demands , in the worst case as Barry said its lot easier to shut down the > master (if you can afford some downtime) take a complete > snapshot/backup/dump ( varies for MYISAM and INNODB) and bring back the > failed server back online > > Hope this helps > > Kishore Jalleda > > > On 3/28/06, 古雷 <[EMAIL PROTECTED]> wrote: >> >> Hello: >> >> If I use Multiple-Master Replication with two mysql server, when one of >> them goes down(disk crashed) must I shutdown the good one to recover the >> Multiple-Master Replication ? >> >> regards, >> >> gu lei >
Re: Multiple-Master Replication recovery
any one of the servers could go down in many ways like 1) disk crash 2) replication failure 3) power failure 4) any hardware component failure 5) OS hang 6) Network failure 7) MYSQL bug 8) table corruption etc ... 9) or just scheduled donwtime in any case what really matters is the difference in status of the failed server from the point of failure to the point of recovery , so it all depends on how up-to-date your data is on the failed server.. here are some typical cases .. 1) you have everything intact ( data, bin logs, *.info files, etc ) then just bring back the failed server online and you are good to go 2) if you rebuild the server from scratch it depends on how current your backup is , in this take a snapshot of the main server ( either hot or cold depending on your setup) and start the multi-master replication .. In theory you really dont have to take the server offline unless it really demands , in the worst case as Barry said its lot easier to shut down the master (if you can afford some downtime) take a complete snapshot/backup/dump ( varies for MYISAM and INNODB) and bring back the failed server back online Hope this helps Kishore Jalleda On 3/28/06, 古雷 <[EMAIL PROTECTED]> wrote: > > Hello: > > If I use Multiple-Master Replication with two mysql server, when one of > them goes down(disk crashed) must I shutdown the good one to recover the > Multiple-Master Replication ? > > regards, > > gu lei
Re: Multiple-Master Replication recovery
古雷 wrote: > Hello: > If I use Multiple-Master Replication with two mysql server, when one of them > goes down(disk crashed) must I shutdown the good one to recover the > Multiple-Master Replication ? I think yes. Depends on what you mean with "recover the Multiple-Master Replication" Do you want to have the server with the new disk behave again as the replicant? Normally you can switch it on demand but yeah i would prefer to shut it down and start it after you have set it up. Regards Barry -- Smileys rule (cX.x)C --o(^_^o) Dance for me! ^(^_^)o (o^_^)o o(^_^)^ o(^_^o) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
