Støt Julemærkesagen
Hi,
From my experience, if You have to write
...
LOAD DATA FROM MASTER
Your replication is not setup
correctly.
LOAD DATA FROM MASTER is reload of the whole table,
and by that You also get the updates.
When working correctly, the replication starts when
MASTER and SLAVE are started and get in contact with each other, the updates are
stored in a "update-file" and also copyed to the SLAVE - unless You
use ex. SLAVE STOP will stop the
replication, SLAVE START will start the replication - or, when having added
commands in the SLAVE myini.cnf file, the SLAVE might delay in starting
replication.
It is all well explained in the
manual.
And also You question regarding "both" MASTER /
SLAVE is explained as far as I remember - I do not think both system can
be both - one MASTER and one SLAVE (and as far as I remember, it is also in the
manual shown how to switch).
I would stick to one MASTER which also apply the
updates, and one SLAVE as backup which will take over if MASTER is down, based
on latest update-status from MASTER - and, only if MASTER is down for long time,
I would consider start updating SLAVE.
If You need further backup, it might be backup of
the database-data in regular dump's, and further the SLAVE can do a
"file-backup" of changes.
So, there are a lot of options (chapter
4.10).
Best regards
Peter
----- Original Message -----
From: "Richard Bewley" <[EMAIL PROTECTED]>
To: "'Richard Bewley'" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thursday, December 04, 2003 3:15
AM
Subject: RE: More database
replication
>
> Thanks,
> Richard
>
> -----Original Message-----
> From: Richard Bewley [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 02, 2003 7:10 PM
> To: [EMAIL PROTECTED]
> Subject: More database replication
>
> Hi,
>
> I have a "mission critical" database, that I want to be redundant, so I'm
> using, as discussed in another thread, the Cisco LocalDirector, two mysql
> machines, and db replication. mySQL version 4.0.16, compiled from source.
>
> Should I make both servers both master and slave, or will this cause
> problems? Would it be better, to make one primary server master, and just
> have a slave as a "failover" db server for the LocalDirector to send traffic
> to only if the primary is down?
>
> Also, the problem I've come across is, I have gotten replication setup
> correctly, and it works, but only when I type
>
> mysql> LOAD DATA FROM MASTER;
>
> I'd rather have it automatically be replicating rather than have to run that
> command every time, or rather than having a cron job do it, which I see as
> messy at best.
>
> Any suggestions?
>
> Thanks,
> Richard
>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
>
>
>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
>
>
