I am considering the --no-lock option for some of my backups, but I feel like I need to understand it better before implementing it. The documentation states that it is safe to use if:
- You use only InnoDB tables AND
- You are not actively adding users, tables, stored procedures, etc. (things that change the data dictionary) AND
- You “DO NOT CARE” about the binary log position of the backup.
This last part of the statement is what gets my attention. Does this mean that using --no-lock causes innobackupex to NOT produce a file with the binary log position? So, backups would not be good for creating slaves, but otherwise could be restored?
Just want to make sure I understand the ramifications.
Thanks,
Dave