mysqldump on slave (without stopping replication)

by user   Last Updated February 13, 2018 14:06 PM

Is it okay to run mysqldump --single-transaction on Slave DB without stopping replication (stop slave;)? This is for regular daily backup. Most of the tables are InnoDB, only a couple of them are MyISAM.

Official documentation says that "you should stop replication on the slave before starting the dump process to ensure that the dump contains a consistent set of data".

What does it mean consistent data? Does it mean like latest data?

I know --single-transaction means that it takes data from the time it was issued, so new further changes while the dump was happening will not be recorded to the dump. Am I correct?

Do not want to run the backup on master due to lag it creates on our application.



Related Questions





MySQL Replication - Filter replicated rows in a table

Updated October 12, 2017 23:06 PM

Master DB Ran Out Of Space

Updated August 01, 2018 04:06 AM