CoolComputing Logo
Coupons/Deals  ·  New Promo Codes/Coupons  · February 20, 2018

A Solution for mysqldump: Got errno 32 on write

Posted on Monday, August 22, 2011 @ 01:20:10 PM CDT by David Yee [] [read 14629 times]

 
Tips: Linux/Unix world
I was using mysqldump to backup mysql data from one server to another. It was working well until recently after I added a few more lines to my command line backup script- basically to backup more tables. In the script I have individual lines to backup single tables in this example format:

mysqldump -uusername -ppassword -hsource_server --compress --skip-lock-tables --lock-tables=false database_to_backup table_to_backup | mysql -uusername_of_local_server -ppassword_of_local_server name_of_local_database

Whenever cron ran the script, I was getting the error:

ERROR 1049 (42000): Unknown database 'database_to_backup'
mysqldump: Got errno 32 on write

It turned out that I had a typo for the name of the local database which did not exist. Basically my destination database has a different name than the database to be backed up, but I still used the same name. Dumb-dee-dum-dumb. So if you are having this error double check your spelling/existence of the local target database you are doing the backup to!



Please rate this article or post a brief review of A Solution for mysqldump: Got errno 32 on write or comment on benchmark/performance, features, availability, price or anything else regarding A Solution for mysqldump: Got errno 32 on write. Thanks!

A Solution For Mysqldump: Got Errno 32 On Write Rating: 2.0/5 (28 votes cast)

Your Name:
I have read and agreed to the Review Posting Agreement.
Review Title:
Comment/Review: