HELP!!!!!!


Got a BIG problem... tried updating my server stuff from earlier versions of the above stuff to the latest...and like a prat tried doing it all in one hit
Result: totally fscked-up database!

Luckily I was intelligent enough (just!) to do a full back-up BEFORE I started the upgrades, and then discovered that PhpMyAdmin doesn't like restoring a backup if its bigger than 2Mb...Mine weighed in at 22Mb!!
Got around that problem in the end by re-installing all the old stuff, and then using the Mysql command prompt to create the table and restore the data with the command ">mysql source mybackup.sql" which worked, but took bloody ages!

Question is, is there another way to get from PHP 4.x + MySQL 4.1.1 + vBulletin 3.5 to PHP 5.x + MySql 5.x + vB 3.7.2 EASILY???

Any help greatly appreciated..Thx!
__________________

Why not do a backup using vbulletin, install the new one using the new mysql version/php version, and then install a fresh vbulletin installation on the new software, then do a restore using that back up file?

As an aside, maybe for managing your mySQL thingies, have you checked out mySQL Administrator? It's a free DL from the mySQL page, and makes a lot of menial things easy.

Do as Krammeh is suggesting. I guess vB 3.5 and 3.7 is so different that you will need to setup 3.7 pretty much from scratch anyway. At least template wise.

Also, if you move the attachments out of the database and into the filesystem, you might get under the 2MB limit.

Quote from Bladerunner :

Question is, is there another way to get from PHP 4.x + MySQL 4.1.1 + vBulletin 3.5 to PHP 5.x + MySql 5.x + vB 3.7.2 EASILY???

Backup everything. Backup your SQL data using mysqldump
Remove PHP 4, remove MySQL 4.1.1.

Install PHP 5, fresh. Install MySQL 5, fresh. Do not use any config files from older versions.

Restore your backup
Create a user for the forum db using what ever method you prefer.

Install vB 3.7 fresh, pointing it at the db, and restore any custom templates. You will need to edit them for 3.7, as a few things have changed. If I remember correctly it should notice and do an upgrade on the db when you do the install.

If possible move your attachments into the filesystem, just remember to give the web server enough permissions to write there.

i will add thoses option to the_angry_angel solution, since you seem to say your restore was very long.

mysqldump -u root -p yourforum > backup.sql

if you add: --net_buffer_length=200 , the Dump will try to group Insert Value together until a Max Line length Reached or the 200 limit.

What it does?

I have my self a 1.2Gig MySQL backup each day... if i don't put this, restoring will take some hours, if i put this Restoring will take some minute!

So this is to speed up thing when restoring.

If you do your backup on a Distant computer i will say add: "-C" to compress data on your transport media, 22meg will become about 1 meg.

MyPHPAdmin is able to restore big backup, but in fact is the Session PHP who is limiting, from your php.ini Config, there is a maximun time and a maximun memory limit a PHP script can use, But i will say using mysql.exe and mysqldump.exe is the best solution out there i know.

For vBulleting.. i can't help! im a InnoForum User, who has the Update Tool working all good

I found a little script called BigDump very useful in the past for bypassing the size and excution limits on some PHP installs.

Just for reference, here's the upgrade procedure from the vBulletin manual.

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

Wow, hey slow down guys and thing about this! All he has to do to restore the database is change the max upload size for his server. I think he is only being held back by the PHP max post size. Hell, he could even just split the SQL dump into 11 parts and upload it bit by bit. From there just restore the files he edited, should be able to get them from the vB site.

OK...got the HARD part done...updated vBulletin and PHP, just MySQL to go now...hopefully THAT shouldn't be too much hassle (Except from my version to current version is a BIG jump )

Haven't had to call on my back ups YET, but making a fresh backup after every successful install

They are backward compatible, the only difference should be a speed improvement.

Quote from Dygear :

Wow, hey slow down guys and thing about this! All he has to do to restore the database is change the max upload size for his server. I think he is only being held back by the PHP max post size. Hell, he could even just split the SQL dump into 11 parts and upload it bit by bit. From there just restore the files he edited, should be able to get them from the vB site.

No, you slow down... and re-read the post (hehe). He wants to upgrade the software, too - so the import is the least of the 'worries'. Besides, doing a db dump is pretty much hassle-free, anyway.