{"id":221,"date":"2009-11-12T09:04:35","date_gmt":"2009-11-12T09:04:35","guid":{"rendered":"http:\/\/kedar.nitty-witty.com\/?p=221"},"modified":"2014-06-24T18:59:21","modified_gmt":"2014-06-24T18:59:21","slug":"scheduled-backup-mysql-administrator-windows-scheduler-odd","status":"publish","type":"post","link":"https:\/\/kedar.nitty-witty.com\/blog\/scheduled-backup-mysql-administrator-windows-scheduler-odd","title":{"rendered":"Scheduled Backup MySQL Administrator & Windows Scheduler \u2013 Odd"},"content":{"rendered":"

Creating scheduled backup using administrator is an easy task.<\/p>\n

Follow the GUI and you’re done. But I observed something different!<\/p>\n

MySQL Version: <\/strong>5.0.83 Community<\/p>\n

MySQL Administrator: <\/strong>1.2.17<\/p>\n

Machine: <\/strong>Intel P4, Windows XP, Enough RAM \ud83d\ude42<\/p>\n

Logs: <\/strong>General, Error & irrelevant here though Slow query.<\/p>\n

Prologue: <\/strong>Administrator performs scheduled backup properly in normal scenario.<\/p>\n

What I was watching:<\/strong> Administrator’s Auto-Backup behaviour with windows Scheduler service and tracing steps out.<\/p>\n

Some facts:<\/strong><\/p>\n

MySQL Administrator stores backup project’s details in <PROJECT-NAME>.mbd files in xml format under directory<\/p>\n

C:\\Documents and Settings\\<USER-NAME>\\Application Data\\MySQL<\/address>\n
<\/address>\n

Along with it it also adds a scheduled task with name <PROJECT-NAME>.<\/p>\n

“C:\\Program Files\\MySQL\\MySQL Tools for 5.0\\MySQLAdministrator.exe” “-UDC:\\Documents and Settings\\<USER-NAME>\\Application Data\\MySQL\\” “-cbkupconn” “-bp1” “-btC:\\” “-bx1”<\/address>\n

If you find trouble getting automated backup work, make sure your Scheduler [Task Scheduler] service is running.<\/p>\n

Start >> Run >> services.msc<\/em><\/p>\n

MySQL Administrator does not log these events unless specified explicitly.<\/p>\n

To enable logging:<\/p>\n

Menu: Tools >> Options<\/address>\n
Category: Administrator<\/address>\n
In Backup Section:<\/address>\n
    \n
  • \n
    Tick checkbox “Write log file for scheduled backup” and spcify path.<\/address>\n<\/li>\n
  • \n
    Tick checkbox “Log Row Processing Progress” and specify number.<\/address>\n<\/li>\n<\/ul>\n
    <\/address>\n

    To view Scheduled task’s log you may:<\/p>\n

    Start\u00a0 >>\u00a0 program\u00a0 >>\u00a0 accessasory\u00a0 >>\u00a0 System Tools\u00a0 >>\u00a0 Scheduled Tasks<\/address>\n
    Click on menu: Advance >> View Logs<\/address>\n
    <\/address>\n
    Or<\/address>\n
    <\/address>\n
    Open Windows\/SchedLgU.Txt<\/address>\n

    \n

    My observation:<\/strong><\/p>\n

    Whenever I keep task scheduler Enabled & Started, I could see updates in logs of Scheduled task and also in Event Viewer. For backups you get logged in General Query Logs.<\/p>\n

    But with my surprise I’m not able to get the MySQL Administrator’s log file (with default setting).<\/p>\n

    Also if scheduler is Disabled & Stopped, Nothing is getting logged. Neigher in logs of Scheduled task nor in Event Viewer.<\/p>\n

    And again there is no MySQL Administrator’s log file getting generated. Also this even is not getting logged in to Error Log!<\/p>\n

    Later I read the bug: http:\/\/bugs.mysql.com\/bug.php?id=28821<\/address>\n

    I tried to change the path from default, C:\\ to D:\\SOMEDIRECTORY. And with my surprise MySQL Administrator logged successfully executed scheduled tasks to log.<\/p>\n

    Next observation after disabling Scheduler(Task Scheduler) Windows Service I made was, backup had failed but Administrator haven’t logged it into C:\\MySQLAdminBackupLog.txt !!<\/p>\n

    Even now I have “Log file path” as D:\\ and I’m reading log updates in C:\\MySQLAdminBackupLog.txt. There is nothing in D:\\!<\/p>\n

    Is it the problem with way Administrator writes to .mdb file (bug?) or am I doing something wrong!<\/p>\n