Comments on: Quick and Dirty Backup Script for MySQL on Windows

By: Backing up WPMU under windows « Blogs

Backing up WPMU under windows « Blogs — Tue, 01 Jun 2010 13:57:42 +0000

[...] http://blog.gerke-preussner.de/2010/02/quick-and-dirty-backup-script-for-mysql-on-windows/ [...]

By: Gerke M. Preussner

Gerke M. Preussner — Wed, 10 Feb 2010 14:43:44 +0000

For SSL to work you need to have it enabled in MySQL. By default, it is off in the Windows version. You can check whether SSL is enabled by running the following SQL query on your database:

show variables like 'have_openssl'

You will also need a valid SSL certificate on the server. For starters you could possibly use a self-signed certificate. I have never used SSL with MySQL, but you should be able to find plenty of information on the internet.

By: Charles3

Charles3 — Tue, 09 Feb 2010 11:29:03 +0000

One more thing. The other reason for not running the dump and compression on the master sql server, is to save on resources. I definitely would like to use the ssl option. Can you please tell me if the above option will work?

Thanks

By: Charles3

Charles3 — Tue, 09 Feb 2010 11:24:02 +0000

Great thanks, yes I forgot mysqldump. I have the suse mysql only allowing certain IP access remotely, so I got that covered. Also, the SQL server is not directly exposed to the public. It’s just that the blades only have limited HD Space (scsi server rated), so I have to run the dump on the auto backup server. As far as the SSL, excellent recommendation. Would it look like this:

mysqldump -ssl -uUSER -p%password% -h10.1.10.189 DATABASENAME > %backuppath%\backup.sql

By: Gerke M. Preussner

Gerke M. Preussner — Tue, 09 Feb 2010 03:31:49 +0000

Charles,

that command line should work, except that the ‘mysql’ should be a ‘mysqldump’, which is probably what you meant. The -h parameter specifies the host. You can also use -host=HOSTNAME as an alternative. Giving mysqldump a database name as in your case will only dump that particular database.

As for database security, I usually allow access only on localhost through named pipes. Exposing your MySQL over the internet is probably not a good idea. It might be better to run the backup script on the computers that are hosting the databases and having them copy out the results to a location on the local network or the internet instead.

Also, the user name and password will be sent as plain text. You may want to look into mysqldump’s -ssl option to encrypt the transfer.

By: Charles3

Charles3 — Mon, 08 Feb 2010 13:35:27 +0000

Your script is great for my local server. But I have remote sql servers in a bladecenter room. How can I edit your script to backup up remote dbs. For example one of the dbs is on 10.1.10.189. Would it be like so:

mysql -uUSER -p%password% -h10.1.10.189 DATABASENAME > %backuppath%\backup.sql

Or is there other commands/scripts?