I meant that it would be beneficial to do the reset on the master at
the same time you issue the stop slave, so that the binary log file on the
master would only contain updates that are not the backup. It would be
very difficult to ensure data integrity though - if an update happened
between the stop slave command and the reset master command.
If your backup stores the information from the show slave status
command ( Read_Master_Log_Pos ) then you should be recreate the
master.info file, though I'm not sure what would need to be in the
relay-log.info file.
Scott Tanner
Systems Administrator
Rowe/AMi
"Gary Richardson" <[EMAIL PROTECTED]>
10/08/2004 02:04 PM
Please respond to Gary Richardson
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
Subject: Re: Restarting Replication from Backup
Hey,
The perl script that does the backup issues a SLAVE STOP just before
it starts dumping. It also grabs SHOW SLAVE STATUS, which has a bunch
of file positions and I'm pretty sure it's everything that is in the
master.info file.
The backup I'd be pulling is going to be at least a day old, so it
will be out of sync and reseting the master will not help.
Thanks.
>
