Thanks Jocke and Christian for your reply, I appreciate it.
I tried "mysqldump --opt dbmail > backup-dbmail.sql" to backup the
dbmail and restore the database to the temporary server using "mysqldump
--opt dbmail > backup-dbmail.sql" but it errors with the error message:
ERROR 1064 at line 3726: You have an error in your SQL syntax. Check
the manual that corresponds to your MySQL server version for the right
syntax to use near
'YedOkRcCBfDnHSrsWUzhEPk8NYJRiitl/oKWWX0hIDRAmjoXHCqtDyVdKq2fTZ'
The MySQL version of the two servers are the same.
Ver 12.21 Distrib 4.0.15a, for slackware-linux (i486)
Thanks and best regards,
Kenneth
Christian G. Warden wrote:
On Wed, Apr 28, 2004 at 11:32:23AM +0200, Jocke wrote:
If you want to set it all up, just make sure you start an update-log on your
master server and connect the slave to it.. then if you're running mysql 4.0
or higher just issue the command "LOAD DATA FROM MASTER;" and the slave will
become up-to-date. After that it will continue to read the updatelog and
manage on its own.
"LOAD DATA FROM MASTER" doesn't work with InnoDB. Since he's using
two different table handlers, mysqldump is probably the best way to
bring the slave up to date.
Has anyone looked into using MySQL Cluster? Information on NDB is
scarce on mysql.com.
xn
_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
--
"Even if you're on the right track, you'll get run over if you just sit
there."
-- Will Rogers