I'll post what are my findings for other people to enjoy. Since than, I started to do my own "cron" jobs. I got this same issue in PostgreSQL because o windows "at" is different from linux "cron". Of course you have to do everything by hand but is also better. I guess it might be associated with windows "cron" jobs. I am logging to win 7 under my primary account and scheduling the backup under the new account. to solve this problem i defined a new standard account in WIN 7. When i scheduled the backup under a standard ACCOUNT it operated fine. I realy don't know why but when i scheduled the backup(when i SAVE the new created project) under a user with an ADMIN account it didn't operate. I faced the same problem.MySQL ADMIN is scheduling the backup via the windows scheduler. I tried also using version 1.2.17 with win 7. That time give proper system username and password Solution 3 I got Solution, When you create schedule backup that time MySQL Administrator take information your system username and password. "%mySqlPath%\bin\mysqldump.exe" -u ?User% -p?Password% -result-file="%path%\%file%" ?Name% * This will backup file in specified path with db name date and time* off CREATE A USER WITH MINIMUM PERMISSION mysql> grant select,lock tables on foo.* to identified by'backup' ĬREATE A BATCH FILE LIKE FOLLOWING AND SCHEDULE IT
0 Comments
Leave a Reply. |