MySQL 5.5 Bin logs & InnoDB logs (1 reply)

Hi,


Trying to understand the MySQL Server architecture. I couldn't understand the difference between the bin logs & Innodb/storage engine logs (transaction logs). A database in production has to have the logging turned on for backup and recovery purposes. Anyhow when i see the recovery methods in the MySQL, all they would say is restore a full backup and apply the Bin logs. There are parameters related to innodb_log_group_home_dir & innodb_log_arch_dir, which need to be turned on (both, if either one of it is turned on). I understand these logs are used for transactional purposes for the InnoDB engine.

My question is,

1) MySQL server logs the transactions in the BIN logs. That means the InnoDB engine transactions will be in the BIN logs as well right? So, what is the purpose of having InnoDB logs? Does MySQL log the transactions both in BIN & InnoDB logs? does that make it redundant?

2) In recovery purposes, we are going to roll forward using the BIN logs. Where do these InnoDB logs come in handy (except for logging transactions).

3) If we are not going to use the InnoDB logs, what is the purpose of having the innodb_log_arch_dir, where it archives the innodb logs.

Any info or direction to documentation links that could explain this would be helpful (don't link me to the dev.mysql reference links please, already have that).

Thanks,
Shiva