Friday, May 4, 2012

MySQL Administrator tool

After completing the automation of the primary, active, moodle dbs in my last post. I was looking at a couple other moodle instances that do not get much activity, and thought "better overkill than no kill". Translate means, back them up anyway, only not as often.

I opened my backupDB.bat file and went to adding the two additional schemas, then realized that I would be backing them up every day, like the others.  No go.

I decided to create a second .bat file and then a separate AT command that would call it only once a week.  This would work.  I ventured into the MySQL Administrator to add schema backup rights to my user account and looked a little more closely at the Backup GUI.  It appears all the tools necessary exist in the GUI to schedule the backup of the the DB.  The picture below is that GUI.
When I tried to activate the Schedule this backup project, I was yelled at about not having a stored connection.  Once I added a stored connection via the File | New Instance Connection menu, I was able to schedule the backup job the same way I would have from the command line.  You can decide which method is better.  I am assuming the GUI above is using the mysqldump.exe file, just like the AT job calls it. 

Same outcome, different ways to complete.

Automated daily backups of the more active schemas. (from command line AT job)

Automated weekly backups of the less active schemas. (Via GUI tool)


No comments:

Post a Comment