I am trying to backup my 3.5.4 board's MySQL (version 4.1.20) using SSH.
Using the regular
mysqldump --opt -Q -u dbusername -p databasename > /path/to/backupname.sql
I was able to backup MySQL to the directory I wanted fine. However, the backup was only 229 megs on the server, when I know the full MySQL database is 429 megs.
Since we recently upgraded our MySQL & PHP versions to MySQL 4.1.20 and PHP 4.3.9 specifically so we could upgrade to vB 3.6 read Ianomed's post about --Hex-Blob on MySQL 4.1.8+.
I assume my missing 200 megs has something to do with --hex-blob .
However I am not quite sure where to put --hex-blob in the mysqldump command, and I've tried almost combo I can think of.
1st) Do you think that --hex-blob is the likely cause of my missing 200megs?
2nd) If --hex-blob is the problem, could someone help me correct my mysqldump command as the use the --hex-blob syntax correctly?
(Current example : mysqldump --opt -Q -u dbname -p mywebsite_com_-_vb-mysql >
/var/www/vhost/mysite.com/wwwdoc/mysite_com_-_vb-bckup.sql )
Thanks in advance.
~Fin
Using the regular
mysqldump --opt -Q -u dbusername -p databasename > /path/to/backupname.sql
I was able to backup MySQL to the directory I wanted fine. However, the backup was only 229 megs on the server, when I know the full MySQL database is 429 megs.
Since we recently upgraded our MySQL & PHP versions to MySQL 4.1.20 and PHP 4.3.9 specifically so we could upgrade to vB 3.6 read Ianomed's post about --Hex-Blob on MySQL 4.1.8+.
Ianomed <xananda at gmail dot com>Apr 20th '05, 11:11amIf you run MySQL 4.0.23+ or 4.1.8+ you best supply the switch --hex-blob as well. Otherwise if you have thumbnails, attachments and/or avatars stored in the database, you may run into problems restoring these in-tact. These MySQL versions of course also apply on restoring, or the hexadecimal encoded binary fields won't be understood.
See http://dev.mysql.com/doc/mysql/en/mysqldump.html for additional details.
See http://dev.mysql.com/doc/mysql/en/mysqldump.html for additional details.
However I am not quite sure where to put --hex-blob in the mysqldump command, and I've tried almost combo I can think of.
1st) Do you think that --hex-blob is the likely cause of my missing 200megs?
2nd) If --hex-blob is the problem, could someone help me correct my mysqldump command as the use the --hex-blob syntax correctly?
(Current example : mysqldump --opt -Q -u dbname -p mywebsite_com_-_vb-mysql >
/var/www/vhost/mysite.com/wwwdoc/mysite_com_-_vb-bckup.sql )
Thanks in advance.
~Fin
Comment