I have the task of setting up MariaDB (10.0) replication from a master running in a datacenter to a slave running out in an AWS VPC. Reading up on the instructions on Setting Up Replication - MariaDB Knowledge Base there's mention of taking a lock on all tables on the master (
FLUSH TABLES WITH READ LOCK) while using mysqldump to transfer the Databases across to the slave. This step has me concerned a slight bit for the following reasons
- We have a number of large databases (~20 DBs @ 40G) with some huge ones (~3 @ 100G).
- It takes about ~40 minutes to transfer each DB across to the slave. In total, this entire process could take up to
20hours (assuming good conditions).
- We can't keep locks on the master for too long - as we disrupt business while the tables are locked.
- Should anything fail in the process of copying the dumps across to the slave - we'll have taken the master down in vain and may need to attempt this again.
What would be a good way to go about setting up replication in this scenario with minimal downtime to production. I'm open to some out of the box thinking - is there a way to do this by breaking things down and doing them in stages so that we can verify each stage?
EDIT I should add that we do take nightly dumps of the DBs as part of the backup strategy. Perhaps there's a way of using these to aid the process?