--safe-slave-backup on Master?

In my preparations to implement a backup strategy with innobackupex, I came across a line in the online documentation that states it is recommended to use the --safe-slave-backup option when backing up master databases. I wanted to ask about it to see if anyone can tell me why this would be recommended?

I’m estimating that my backup against my master database will require somewhere between 90 and 120 minutes. During that time period, a great deal of activity will still be taking place, and it is replicated on 4 other servers. If I halt the slave process during the backup, then my slaves will all be nearly 2 hours behind by the time the backup is finished. Two of the 4 servers are used as read-only replicants. So, the data queried from them would be incorrect for some queries. For this reason, I’m hesitant to use that option when backing up my Master. I’m not even sure I like the idea when backing up my slaves - for the same reason.


Can you point to the URL that says this? It’s wrong. This is only needed on a replica. The documentation explains this option:
http://www.percona.com/doc/percona-xtrabackup/innobackupex/i nnobackupex_option_reference.html#cmdoption-innobackupex–sa fe-slave-backup

Hi Baron,

I could have sworn that it was on this page:
http://www.percona.com/doc/percona-xtrabackup/innobackupex/r eplication_ibk.html

Either I misread it, or it has already been corrected. I thought I read the last line as:
“Using this option is always recommended when taking backups from a master server.”