Web lists-archives.com

Re: slave to master




Am Freitag, 29. April 2016, 14:49:57 schrieb william drescher:
> On 4/28/2016 5:20 PM, Thomas wrote:
> > Hi,
> > 
> > I have setup an master slave replication.
> > This works fine.
> > I have running an Apache webserver and some other programms accessing the
> > master.
> > Whats the standard pocedure if master fail?
> > 

> 
> When the master is repaired and up you need to stop the programs
> on the slave from accessing mysql (ie: stop the programs on the
> slave), make a database copy of the slave, copy it to the master
> and reload the database on the master, and then use the Change
> Master to command on the slave to set up the slave to begin
> replicating and start slave.
> 
> This is the poor man's failover for low volume systems.
> In essence the slave becomes the main database server until you
> are ready to restart the master and replication.

Hi thanks for all the answers,
I only want that when master fails the slave will be the new master and do 
everythink that the master has before done. So I have more time to repair the 
master.
I have to change the slave to master because I need write access to the mySQL 
databases.

Sure that when mySQL data on the master are damaged I will have same problems 
on the slave, but for this I have an undependent data saving, not realtime but 
acceptable. Sure I need in this case more time to repair the whole system.

slave to master:
Like this:
https://dev.mysql.com/doc/refman/5.5/en/replication-solutions-switch.html

Is this the way to go?

thanks 
Thomas



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql