Andrew, Andrew Hall wrote: > > John, > > Thank you for your reply. I have read the replication chapter and this > seems to be easier, but I do have a few questions. > > 1. I am using InnoDB tables, at least there are innodb argument to > mysqld in the start script, so should I use mysqldump instead of tar-ing > the data dir to create the baseline for the slave? I believe thats what > the docs are stating, but I wanted to be certain.
You'll only be using innodb tables if you specified that table type when you created each table or if you have " default-table-type=innodb" in a my.cnf file somewhere. You would also have to create the innodb tablespace and log files before you could create the tables. You can copy the innodb files to a slave, but the my.cnf files on both machines should match. > 2. I want to have a failover scenario here, so what would the impact be > on the mysql db if I go master->slave->master? > I wouldn't recommend this. We had a instance a couple of weeks ago where the master db was having disk issues and when we had to repair some tables. When we did, we lost information in the master but luckily the slaves had replicated the data so we were able to restore that info back. > 3. What happens if the master fails, dies, and goes offline. Must I > change all my apps to connect to the IP of the slave for connections to > work? I am unclear if replication will provide failover capabilities. > For all of our "services", we run "floating ip addresses". That way if something like mysql or dns crashes, we can automatically drop the ip on the main machine and bring it up on the backup without being concerned about the server's actual ip address. Searching google for pirinna and heartbeat should help you with the fail-over part. > 4. What is necessary to bring the master back up after a failure? > Should I? or should I leave the slave (new master) up, and make the old > master the new slave? I'd leave the "new master" up until you can stop both databases and sync the data. > 5. I am running 3.23.54 and I know I should upgrade, but its not going > to happen today, so are there any show stopping bugs with this version? We've been running .53 for over a year and half with no problems. We use iptables on the db servers to get around the security updates > Thank you for your time, > > Andrew > > On Tue, 2003-12-02 at 17:10, John Griffin wrote: > > Hi Andrew, > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] Hope this helps! walt -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
