MAS -

what you may have forgotten to do is tell system C where (or when if
you think of it that way) to start replicating. Either that or system
C wasn't empty when you started replicating into it.

The procedure to set up replication like this would be: freeze master,
flush data, record binlog filename and position, then either mysqldump
or mysqlhotcopy the data, then start master again. Copy the data into
an empty slave (system C) and set the slave options to start reading
at the correct file and position, then start replicating.

See http://dev.mysql.com/doc/refman/5.0/...ion-howto.html

Also have a look at the mysqldump "--master-data" option; could make
things easy for you in terms of the snapshot.

Of course if you are replicating at the table level, doing circular
replication, etc., things are more complex - but sounds like you don't
need to consider these right now.

Dan


On 10/12/06, MAS! <marco.stagno@gmail.com> wrote:
> I'd like to know what is the best way to setup the replication on my
> system.
>
> I hve all myisam tables and:
>
> - main db on production (master: system A; mysql 4.0.x);
> - slave db as backup/backoffice (system B; mysql 4.0.x);
>
> both are working and the replication works well.
>
> - system B is also the master for (system C; mysql 5.0.22)
>
> I did the hotcopy from the sistem B and I put it on my new sistem;
> the db is working well, but the slave on system C doesn't work, since
> I have a lot of "duplicate keys" in the insert queries.
>
> what I did wrong? why it seems I'm unable to sync system C with the
> other ones?
>
> what is the best 'recipe' to setup correctly a slave system (better
> without stop the master db, if it's possibile)
>
> thank you in advance
>
> bye bye
>
> MAS!
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=drbuettner@gmail.com
>
>