It might be a better idea to try a restore using bash. You can contact your server company and ask if you can run the following code...
mysql -u user_name -p your_password database_name < file_name.sql
where user_name and password are the logon for your db (same as vbulletin uses in config.php) and database_name is your database name (same as vbulletin uses in config.php). Your file_name.sql would be backup.sql
That command will overwrite any current data in the database so watch out. However, it *will* be a full restore from your file. I've found that some "web" restore things like vbulletin and others in php will chop off the end of your file, fooling you into thinking you have a bad .sql file.
If your database already exists and you are just restoring it, try this line instead:
mysqlimport -u user_name -p your_password database_name file_name.sql
also in the future, to do a REAL backup of your database, bash this.
mysqldump -u user_name -p your_password database_name > file_name.sql
(this will store to your ftp login default dir) at least it should if you are set up right.
|