Re: Slave Bin Log Question
After you stop the slave and start mysqldump, execute the below on slave db. show slave status\G. Note down the Master_Log_File and Exec_Master_Log_Pos. This will be the point from which you need to do the recovery. regards anandkl On 9/25/07, Eric Frazier <[EMAIL PROTECTED]> wrote: > > Boyd Hemphill wrote: > > I have executed a strategy for backup where I stop a slave and do a > mysqldump with --master-data. Both master and slave are 4.1.20 > > > > My assumption was that the log coordinates in the dump file would > provide me with the place to replay the log for a point in time recovery. > > > > What I learned today however is that it appears the binary log only > captures statements run directly on the slave. Any SQL run by the SQL > thread of replication seems only to go in the relay log. This effectively > renders the --master-data useless for my purpose. > > > > So, I have two questions. > > 1. Can someone verify that the binary log on the slave is not capturing > SQL from the replication SQL thread. > > > > It sounds like you need --log-slave-updates > > http://dev.mysql.com/doc/refman/5.0/en/replication-options.html > > 2. If the above is really true, what strategies are you using to backup > InnoDB without InnoDB hot backup? > > > > Thanks for your time! > > > > Peace > > Boyd > > > > > > > > > > > > > > > > CONFIDENTIALITY NOTICE: This email & attached documents may contain > confidential information. All information is intended only for the use of > the named recipient. If you are not the named recipient, you are not > authorized to read, disclose, copy, distribute or take any action in > reliance on the information and any action other than immediate delivery to > the named recipient is strictly prohibited. If you have received this email > in error, do not read the information and please immediately notify sender > by telephone to arrange for a return of the original documents. If you are > the named recipient you are not authorized to reveal any of this information > to any other unauthorized person. If you did not receive all pages listed or > if pages are not legible, please immediately notify sender by phone. > > > > > > > > > > > > > > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] > >
Re: Slave Bin Log Question
Boyd Hemphill wrote: I have executed a strategy for backup where I stop a slave and do a mysqldump with --master-data. Both master and slave are 4.1.20 My assumption was that the log coordinates in the dump file would provide me with the place to replay the log for a point in time recovery. What I learned today however is that it appears the binary log only captures statements run directly on the slave. Any SQL run by the SQL thread of replication seems only to go in the relay log. This effectively renders the --master-data useless for my purpose. So, I have two questions. 1. Can someone verify that the binary log on the slave is not capturing SQL from the replication SQL thread. It sounds like you need --log-slave-updates http://dev.mysql.com/doc/refman/5.0/en/replication-options.html 2. If the above is really true, what strategies are you using to backup InnoDB without InnoDB hot backup? Thanks for your time! Peace Boyd CONFIDENTIALITY NOTICE: This email & attached documents may contain confidential information. All information is intended only for the use of the named recipient. If you are not the named recipient, you are not authorized to read, disclose, copy, distribute or take any action in reliance on the information and any action other than immediate delivery to the named recipient is strictly prohibited. If you have received this email in error, do not read the information and please immediately notify sender by telephone to arrange for a return of the original documents. If you are the named recipient you are not authorized to reveal any of this information to any other unauthorized person. If you did not receive all pages listed or if pages are not legible, please immediately notify sender by phone. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Slave Bin Log Question
I have executed a strategy for backup where I stop a slave and do a mysqldump with --master-data. Both master and slave are 4.1.20 My assumption was that the log coordinates in the dump file would provide me with the place to replay the log for a point in time recovery. What I learned today however is that it appears the binary log only captures statements run directly on the slave. Any SQL run by the SQL thread of replication seems only to go in the relay log. This effectively renders the --master-data useless for my purpose. So, I have two questions. 1. Can someone verify that the binary log on the slave is not capturing SQL from the replication SQL thread. 2. If the above is really true, what strategies are you using to backup InnoDB without InnoDB hot backup? Thanks for your time! Peace Boyd CONFIDENTIALITY NOTICE: This email & attached documents may contain confidential information. All information is intended only for the use of the named recipient. If you are not the named recipient, you are not authorized to read, disclose, copy, distribute or take any action in reliance on the information and any action other than immediate delivery to the named recipient is strictly prohibited. If you have received this email in error, do not read the information and please immediately notify sender by telephone to arrange for a return of the original documents. If you are the named recipient you are not authorized to reveal any of this information to any other unauthorized person. If you did not receive all pages listed or if pages are not legible, please immediately notify sender by phone.
