Hey guys,
I'm running a master/slave setup with v4.0.20. There are a hand full
of databases being replicated. For backups, we stop replication on the
slave and pull a text dump using mysqldump. I also record a 'SHOW
SLAVE STATUS' from the time of the backup.
My replica server crashed last night.
knowledge on the correct procedure.
Regards,
Scott Tanner
Systems Administrator
Rowe/AMi
Gary Richardson [EMAIL PROTECTED]
10/08/2004 01:01 PM
Please respond to Gary Richardson
To: [EMAIL PROTECTED]
cc:
Subject:Restarting Replication from Backup
Hey guys
PROTECTED]
10/08/2004 01:01 PM
Please respond to Gary Richardson
To:[EMAIL PROTECTED]
cc:
Subject:Restarting Replication from Backup
Hey guys,
I'm running a master/slave setup with v4.0.20. There are a hand full
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
Hey guys,
I think I have this figured out. I'm just doing some testing. If I
manually recreate the master.info file, it sort of works, but I get
the following error from the IO thread:
Error reading relay log event: slave SQL thread aborted because of I/O error
So, instead of manually creating
On Friday 08 October 2004 19.01, Gary Richardson wrote:
Hey guys,
I'm running a master/slave setup with v4.0.20. There are a hand full
of databases being replicated. For backups, we stop replication on the
slave and pull a text dump using mysqldump. I also record a 'SHOW
SLAVE STATUS' from
Yeah, that's exactly what I figured out.. We do record the SHOW SLAVE
STATUS settings before each backup.
I find we need individual tables restored far more frequently than
whole databases. It's much easier using mysqldump and perl to dump
each table in text to its own file. This is especially
