One common mistake we’ve often seen people make when trying to migrate data from an old server to a new one is to attempt to copy the MySQL datafiles from /var/lib/mysql to the new server. While this method can work, it’s not guaranteed and I’ve seen a number of attempts fail in corrupt databases and frustration. So as a solution, we have created a guide that includes a recommended method to back up your database.
One of the problems with managing a fleet of Linux servers is that security updates and patches seem to be released in an almost continuous stream.
A VPN, or Virtual Private Network, is a commonly used method to create a secure network connection between computers. In most usage scenarios a client computer will connect to a server. Once connected, all or some of the network traffic from the client computer may be encrypted, and is sent to the server.
For those who haven’t been following this series and have started at part 3, in the first part of this series we looked at what database replication is and why it could be useful, as well as starting the configuration of our MySQL master server. In part 2, we prepared our master server for replication and backed up the databases we wished to replicate. Today we’ll be configuring the slave server to replicate the databases from the master.
When managing Linux servers, the Secure SHell (SSH) is the most commonly used tool for connecting to remote servers to do this.