Difference between revisions of "Setting Up a MySQL Replication Server"

From AgileApps Support Wiki
imported>Aeric
(Created page with "<includeonly>==== Setting Up a MySQL Replication Server ====</includeonly> It's a good idea to set up a replication server, for the sake of data safety. That server is also known...")
 
imported>Aeric
Line 8: Line 8:
:* For additional information on replication in general, see the MySQL manual:<br>http://dev.mysql.com/doc/refman/{{MySqlVersion}}/en/replication.html
:* For additional information on replication in general, see the MySQL manual:<br>http://dev.mysql.com/doc/refman/{{MySqlVersion}}/en/replication.html


{{Best|When you set up MySQL replication, it's a good idea to configure the Quartz scheduler, as well. That process gives you useful timestamps that let you monitor the health of the replication process.<br>''Learn more:'' [[Configuring the Quartz Scheduler]]}}
{{Best|When you set up MySQL replication, it's a good idea to configure the Quartz scheduler, as well. That process gives you useful timestamps that let you monitor the health of the replication process.<br>''Learn more:''
:* [[Monitoring MySQL Replication#Reviewing the Messages]]
:* [[Configuring the Quartz Scheduler]]}}
<noinclude>
<noinclude>


[[Category:Installation]]
[[Category:Installation]]
</noinclude>
</noinclude>

Revision as of 22:29, 16 April 2014

It's a good idea to set up a replication server, for the sake of data safety. That server is also known as a slave server. (The primary database server is also known as the master server.)

A full description of the process is outside the scope of this manual, but here is some information to get you started:

Thumbsup.gif

Best Practice:
When you set up MySQL replication, it's a good idea to configure the Quartz scheduler, as well. That process gives you useful timestamps that let you monitor the health of the replication process.
Learn more: