Difference between revisions of "Setting Up a MySQL Replication Server"
From LongJump 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 a…") |
imported>Aeric |
||
| Line 1: | Line 1: | ||
<includeonly>=== Setting Up a MySQL Replication Server ===</includeonly> | <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 as a ''slave'' server. (The primary database server is also known as the ''master'' server.) | 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.) | ||
Revision as of 20:12, 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:
- The Percona backup system makes it relatively painless, and it's fast.
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.
- For additional information on replication in general, see the MySQL manual:
http://dev.mysql.com/doc/refman/5.5/en/replication.html
- For additional information on replication in general, see the MySQL manual:
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: Configuring the Quartz Scheduler
