Moving from 3.0 to 3.6 and new HOST

[crucialjames]

I'm currently hosting 3.0.7 on provider A and 3.6.8 on provider B (My New Host).

When backing up the mySQL database on 3.0.7 and uploading to the new hosting provider I get this error when executing the backup into the new mySQL

$ mysql -uUSER -pPASS vbulletin < vbulletin.sql

ERROR 1064 at line 182439: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '<br />
<b>Fatal error</b>: Maximum execution time of 30 second

Current Host: mySQL 3.x
New Host: mySQL 4.x

If I'm jumping to 3.6.8 too fast please let me know what version I should be going to that might work with this transistions as I don't have much time before old hosting provider shuts me off. The database size is 205M

James

[snakes1100]

What did you use to dump the database on the old server?

What version of 4.x is it exactly?

[crucialjames]

Thanks for a quick response...

I logged into the admin cp disabled the board for a few minutes and backed it up to my PC then transfered it via binary mode on my ftp client to the new server.

New Server mySQL = version: 4.0.17

I have full access on the new server, just plesk on the old server and their crontab wont do a mysqldump thats why I resorted to admincp for dump.

[slappy]

You did not say if you created the backup with phpMyAdmin, the AdminCP or MySQL.

In posts on vBulletin.com I find:

This is a server time limit. To temporarily up your limits edit your includes/config.php file and add this line right under the <?php line:

ini_set("max_execution_time", "240");

This, and other post on vBulletin.com also said:

This is a server issue where the process is taking longer than the maximum allowed on the server.

The only consistently reliable method of backing up and restoring a database is with shell access via telnet or ssh. This is because backing up with a PHP script like that in the Admin CP or phpMyAdmin can result in PHP timeout errors and an incomplete backup file.

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

If you don't have telnet or SSH access, some people have reported success with these scripts:

MySQLDumper:
http://www.mysqldumper.de/en/index.php

MySQLHotxcopy:
http://www.vbulletin.com/forum/showthread.php?t=134821&highlight=mysqlhotcopy

Bigdump (restore only):
http://www.ozerov.de/bigdump.php

Hope that helps.

Regards,

[crucialjames]

I just actually moved it 100%. I manually got the webhost to do a backup of the DB for me.

thanks everyone