Hi

Ofer Inbar wrote:
> Scenario:
> host a is the master
> host b is a replication slave
> host c is to become a second replication slave
> there's no full dump from host a
[snip]
> One possibility I can think of:
> - stop slave on host b
> - run the dump on host b
> - note its position in host a's binlogs using "show slave status"
> - restore the dump on host c
> - start c slaving using the binlog name and position from "show slave status"
>
> Will that work?

Yes.

> Is there a way to do this *without* stopping replication on host b?

No, unless you have a snapshot-capable file system like LVM, and even then there
are caveats. Just be aware of which columns of SHOW SLAVE STATUS mean what --
there are three sets of binlog coordinates in that output. (There's a note on
the online manual that should make it clear).

Baron