Binary Characters in *.SQL backup file

[Anthony_R]

Hi All,

I have no problems backing up my Forums using the Admin Console and saving as a SQL file. All backups get the correct completed message at the end of the file.

However, when I look through the file I notice that there is a lot of non-printable characters for the tables that contain binary data.

My question is, will this restore correctly via PhpMyAdmin?

I plan on setting up a local MySQL server and test copy of vBulletin to check if it does restore correct and operate, but thought it worth asking on here to see if anyone is aware of any gotcha that might not be readily apparant.

[Steve Machol]

That is normal for binary data - attachments, etc.

Please note that the only reliable method of backing up and restoring a database is with shell access via telnet or ssh. Please see the instructions here:

Backup:

http://www.vbulletin.com/docs/html/maintenance_ssh_backup

Restore:

http://www.vbulletin.com/docs/html/maintenance_ssh_restore

This is because backing up with a PHP script like that in the Admin CP or phpMyAdmin can result in PHP timeouts errors and an incomplete backup file.

[Anthony_R]

That is normal for binary data - attachments, etc.

Okey, just wanted to confirm that it would restore OK. Wasn't sure if SQL supported nonprintable characters.

Please note that the only reliable method of backing up and restoring a database is with shell access via telnet or ssh. Please see the instructions here:

Backup:

http://www.vbulletin.com/docs/html/maintenance_ssh_backup

Restore:

http://www.vbulletin.com/docs/html/maintenance_ssh_restore

This is because backing up with a PHP script like that in the Admin CP or phpMyAdmin can result in PHP timeouts errors and an incomplete backup file.

Unfortunatley I could not get that to work with my ISP. MySQL access is restricted to their webserver, so I can't remotely connect.

I tried the backup cron php script from one of the unoffical support forums, but the execution of mysqldump didn't work (possible security settings by my host).

Anyway what I did was take the code you guys wrote for doing the backup to .SQL file and added to the cron job to backup to a non HTTP accessable spot on the server. I then found some native PHP code for zipping and zipped the file up.

I can now access the file via FTP and every backup has been perfect.It backs up every night creating a new archive each time. As this is all happening on the server I figured the timeout problem won't occur (and it certainly hasn't).

So I'm happy with the process I have set in place. Can you see any issues with what I have done?

[Steve Machol]

Can you see any issues with what I have done?

Eventually your database will be too big to backup this way and you will be left with an incomplete backup and not know it.

[Anthony_R]

Eventually your database will be too big to backup this way and you will be left with an incomplete backup and not know it.

Arrr .... OK. I will investigate the issues I mentioned earlier with my web host then so I can use the recommend method.