![schedule server 2003 backup batch file schedule server 2003 backup batch file](https://www.data-protector.org/wordpress/wp-content/uploads/2016/05/EADR_01.png)
#SCHEDULE SERVER 2003 BACKUP BATCH FILE HOW TO#
I had little luck Googling solutions on how to backup all the databases individually, zip them into one file, and delete the older archives so I sat down and wrote my own batch file. The only windows solutions seemed to use php which seemed overly complex, relied on unnecessary systems that could fail, and introduced security concerns when you could use a simple batch file with a few lines of code to accomplish the same task. Obviously there are lots of scripts out there and easier solutions for linux based systems. Great tool save one missing feature, they decided to no longer support scheduled MySQL backups. What replaced MySQL administrator? Enter the new MySQL Workbench. Well, if you are like us and you constantly add new databases the new ones simply wouldn’t be backed up, Annoying. For example once you created a scheduled backup it would only include the databases you told it to at the time of creation.
![schedule server 2003 backup batch file schedule server 2003 backup batch file](https://i2.wp.com/farm3.static.flickr.com/2007/2486557666_ea3df7629b.jpg)
While it worked well it had some major shortcomings.
![schedule server 2003 backup batch file schedule server 2003 backup batch file](https://www.practical365.com/wp-content/uploads/2010/12/windows-server-backup-scheduling-00.png)
Typically we have used the backup facility built into MySQL administrator, which unfortunately has now reached end of life.