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
 
(3 intermediate revisions by the same user not shown)
Line 6: Line 6:
:* The Percona backup system makes it relatively painless, and it's fast.<br>http://www.percona.com/doc/percona-xtrabackup/2.1/howtos/setting_up_replication.html
:* The Percona backup system makes it relatively painless, and it's fast.<br>http://www.percona.com/doc/percona-xtrabackup/2.1/howtos/setting_up_replication.html


:* 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, see:<br> MySQL version 5.5, see http://dev.mysql.com/doc/refman/{{MySqlVersion}}/en/replication.html.<br>MySQL version 5.7, see https://dev.mysql.com/doc/refman/5.7/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]]}}
<noinclude>
<noinclude>


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

Latest revision as of 06:16, 17 March 2017

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: