Hi,
Could you take the database down long enough (scheduled downtime) to
make the master a slave to the slave? I seem to remember reading on
this mail list that you can do circular replication... or am I talking
nonsense?
That way when you took the original master down for maintenance, then
with mysqldump??
Can anyone shed some light??
Thanks,
Steve Williams
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
require the shutting down of the database (production). The shutting down of the
disaster recovery one isn't a problem... I may resort to it, but I'd prefer to just
figure out which timeout is causing the problem.
Thanks,
Steve Williams
-Original Message-
From: dan orlic [mailto:[EMAIL
Hi,
This only delays the agony. I have done that (using bzip2), but
eventually this will not work. I would rather engineer a solution that
will just work and will scale properly (given infrastructure support
ie: network/disk).
Thanks,
Steve Williams
William R. Mussatto wrote:
How about