MySQL Bugs: #24984: Administrator provides no way to debug problems with scheduled backups

Bug #24984	Administrator provides no way to debug problems with scheduled backups
Submitted:	11 Dec 2006 23:42	Modified:	12 Feb 2009 14:03
Reporter:	Matthew Lord	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	all	OS:	Any (all)
Assigned to:		CPU Architecture:	Any
Tags:	administrator, backups, bfsm_2006_12_21

Description:
When you schedule a backup job there is no log of what actually happens.  It's possible, at least on some platforms, to enable logging by editing mysqladmin_options.xml in this block:
<group name="AdminBackups">
<property name="AddDateTimeToBackupFiles" value="1"/>
<property name="WriteBackupLog" value="0"/>
<property name="BackupLogDir" value="C:\"/>
<property name="BackupLogEntryAfterRows" value="0"/>
</group>

However, not only is this undocumented and apparently windows only but Administrator only logs information on _successful_ runs.

Due to this fact it is nearly impossible to debug and support.

How to repeat:
Create a scheduled backup which you know will fail, perhaps use a connection with an invalid username/password.  Try and find out why it's failing while pretending that it's a mystery.

Suggested fix:
We need to have a default audit trail of what mabackup runs are doing.

backup project which can be used as an example of not having logging along with just not working.

Attachment: test backup.mbp (application/octet-stream, text), 208 bytes.

Matt, at least on Windows there are settings to control the logging. Go to menu Tools -> Options -> Administrator. I'm not sure how it is on Linux, but I'd assume it's very similar. I admit however the design is not optimal, as it does not allow to enable logging per project.

There is no backup logging feature for Linux and OSX at all. So this must be implemented yet. Matt, for now, if possible, use the Windows client to log things. The other platforms will have to be made ready later.

Thank you for your bug report. This issue has already been fixed in the latest released version of the supported platforms of that product, which you can download at

  http://www.mysql.com/downloads/