mysql replication issues

[Jamesk5]

I've got replication working on two machines, both running Debian (etch) and the latest version of mySQL-server-5.0, but I've got an issue with the slave.
If the machine goes down, the slave 'feature' of mysql doesn't seem to automatically turn its self on - not sure why. I've followed the mySQL docs on replication.
Also, when I run the 'start slave' command on the slave, it doesn't go and automatically carry out any changes that have been done on the master since the slave went down.

Any suggestions will be appreciated,
James

[falko]

Did you take a look at this tutorial? http://www.howtoforge.com/mysql_database_replication

[Jamesk5]

Yes I did, but in your tutorial you only cover how to replicate a single database, where as I need the whole MySQL DB replicated for data redundancy and a hotswap incase my main machine goes down.
Your tutorial barely differs from the docs on the MySQL site - which is why I posted the question.
Thanks for the how-to anyway, but I've basically used parts of your tute and the rest of the stuff from the mysql docs.

[falko]

Originally Posted by Jamesk5

where as I need the whole MySQL DB replicated for data redundancy and a hotswap incase my main machine goes down.

Basically you must list all databases in my.cnf on the master and slave.

Master:

binlog-do-db=db1
binlog-do-db=db2
binlog-do-db=db3
binlog-do-db=db4
binlog-do-db=db5
binlog-do-db=db6
binlog-do-db=db7
...

Slave:

replicate-do-db=db1
replicate-do-db=db2
replicate-do-db=db3
replicate-do-db=db4
replicate-do-db=db5
replicate-do-db=db6
replicate-do-db=db7
...

[Jamesk5]

ahhh ok, so every time I add a DB to the master I need to add it to the list in both my.cnf files. It just seems a bit silly too me - considering that it works to some degree without all the lines that you mentioned above.

[falko]

Yes, maybe a little bit silly, but it's working.