MySQL Bugs: #20425: Scheduled backup failure

Bug #20425	Scheduled backup failure
Submitted:	13 Jun 2006 13:01	Modified:	13 Jun 2006 14:52
Reporter:	Lea Robson	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.1.9	OS:	Windows (W2K Server SP4)
Assigned to:		CPU Architecture:	Any

Description:
With reference to Bug #4565 I can replicate this failure exactly and corrective action using version 1.1.9.

From Bug #4565

I created a backup project and scheduled it. I noticed that Windows will run the
scheduled task, but it doesn't create any backup file. It only seems to work
when I run the backup job manually from Administrator.

How to repeat:
Schedule the backup job or manually run the Schedule (right click on Scudule and choose Run) and check for results. 

Suggested fix:
I can confirm that by changing the lower case '-c' to uppercase '-C' it resolves the failure in this version also.

Using '-c' Scheduler reports 0x0 (success) but it does not instantiate MySQL and no file is produced even with correct user name / password.  

ScedLgU.txt (the Schedular's log file) reports success, when clearly this is anything but!

I forgot to mention that if you change any backup settings from the mySQL GUI you must remember to change the -c to -C again.

This is a duplicate of bug #4565, really. Please, add your comments to that report. Or answer the last question there, at least:

"Could you verify if you have turned on the [Store Passwords] function in the
options?"

My apologies.  Please do concatenate my findings.

Further comments will be added to #4565.

Lea