Bug #56199 There is no way to enable or disable logging in innobackup.
Submitted: 23 Aug 2010 21:40 Modified: 23 Dec 2013 8:13
Reporter: Hema Sridharan Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Enterprise Backup Severity:S3 (Non-critical)
Version:innobackup 1.7 OS:Any
Assigned to: CPU Architecture:Any

[23 Aug 2010 21:40] Hema Sridharan 
Description:
Currently the new feature is implemented to support the table based logging for innobackup. There are more details mentioned in WL#5495. This design does not specify about enabling or disabling logging. 

Users should have the feasibility to use the following options when innobackup is run
1. Use just the backup_history logs or backup_progress logs
2. Use both the logs
3. Use none.

With the current design, both history and progress logs will be generated when innobackup is executed.

How to repeat:
Please see WL#5495

Suggested fix:
As per Satya, we can implement an option like --logs=history/progress/none
[24 Aug 2010 11:06] Sveta Smirnova 
Thank you for the report.

Verified as described using WL.
[6 Oct 2010 10:39] Satya B 
Deferred to later release.
Decision made in one of the backup decision meeting(forgot the exact date).
Reasoning is it doesn't add much overhead for logging, this will be done later.

BTW, the code is modular enough to do this just by adding new option, switch and calling relevant functions.
[6 Oct 2010 10:39] Satya B 
Deferred to later release.
Decision made in one of the backup decision meeting(forgot the exact date).
Reasoning is it doesn't add much overhead for logging, this will be done later.

BTW, the code is modular enough to do this just by adding new option, switch and calling relevant functions.
[23 Dec 2013 8:12] Jothir Ganesan 
Not applicable anymore. Wont fix
[23 Dec 2013 8:13] Jothir Ganesan 
innobackup is removed and the tool to be used is mysqlbackup. So closing this bug.