Can't Restore A Db From 3 Mb Big/small Sql File

[Soran]

Hi!

 

My vBulletin database became corrupt, and i tried to restore it - but no luck.

 

I get : #1153 - Got a packet bigger than 'max_allowed_packet'

 

It's till a small forum, actually not even "live" yet, i still test administration/moderation/etc.

 

The SQL file is less than 3 MB

 

I tried to split this sctipt, and found out that admin log table is bigger than 1 MB and can not be splitted.

 

 

May be someone from TCH could restore this DB for me,

but this is actually not what i need.

I need to be able to restore my DB myself any time of day and night if i need it,

without asking TCH support.

 

 

So my question: is it possible?

I didn't have a backup made with "Backup" function ( i mean the site /x/backup ) ,

just a backup made in phpMyAdmin ,

but would it really help it i had a default backup?

 

I have a backup from other ISP ( created on the backup site of CP, very similar DB ),

i tried to restore it here, and it does not work ,

after the upload finishes, a "Restoring Database" message is displayed and nothing more happens.

 

 

I really need a long term solution for this problem,

because i can't accept not being able to restore(alone) a legit vBulletin database,

and it's even not a big forum....

 

 

Sincerely,

Soran

[Soran]

OK, i found out why restore via /frontend/x/backup/ didn't worked :

it was a minus sign ( - ) in the file name!

Anyway it's quite irritating that there is no appropriate warning / error message.

 

But since my statement about restore via /frontend/x/backup/ was wrong, i apologize!

 

 

Still i have some questions...

 

What is the file size limit for upload/restore via /frontend/x/backup/ ?

( for gzip file or the unzipped content inside )

 

Could it cause some trouble if i have few big files in the database? ( 5-10 mb )

 

Is there some way to make the backup/restore application not to display the complete script in browser?

( CPU load is 100% for 1-2 minutes during the 2nd phase of restore on my computer...

( Athlon TB 1G, 512 ram )

and it's just a 3 mb database ( 500 kb gzip ), i'm afraid that my PC might just crash

if i have to restore a 100 mb database ( from 15 mb gzip ) one day... )

[TCH-Don]

Hi, first sorry to have missed your first post.

 

Welcome to the Family

 

and your new home!

I am sorry I have no experence with vBulletin script

so I can't help with the backup part of that script.

 

But to just back up just your database

goto cpanel > backup

and click on the link for that database to download a compressed file

that you can upload in the same place later.

these files should be smaller that what your forum backup will be

and should upload with less trouble.

 

As to upload limits, again I am not familiar with vBulletin

but with cpanel > backup I don't think you would have any trouble with a large datatbase.

 

I will move this to scripting,

and maybe someone else here uses that script

and can help.

 

We really are like family here.

So if you need anything,

just ask your new family!

We love to help

[Soran]

Hi Don!

 

Thank you for your answer and a warm welcome

 

 

Anyway the upload limit is not vBulletin related,

i'm just asking about the limits of restore functionality in general.

 

 

Basicly i just would like to know what is the size of the biggest databases

which you or other people here restore via /frontend/x/backup/

( Backup link in CPanel )

 

 

Also, could i run into some troble during resore via /frontend/x/backup/

if there are some very long INSERT's

( for example if a big file is stored in the database, like 5-10 mb or even bigger ),

is there any limit for the size of a single INSERT?

 

 

The 3rd question is also not about script but the same /backup/ page in CPanel

( or accessable via CPanel ) -

on restore the complete code of the backup is displayed ( at least by default ),

i just would like to know if there is any way around

so it would not be displayed.

By the way, it parses HTML tags, so that i see many input boxes and alike

( since some tables in the database contain HTML code ).

I'm just afraid what happens if i the database is much bigger,

the browser (or even Windows) might just crash

trying to display a site that's 100-200 mb big

( while gzip backup is might be just 15-40 mb )

[TCH-Don]

Hmm I think TCH-Mike might be able to comment

on the size of this forums backup, it may give you an idea of any limits.

 

AS to the restore in cpanel

I don't think you can change the display after.

Its just displaying it as it is restored, its not parsing it.

[Soran]

Not sure if it should be called parsing,

but here is an example of what i see in my browser during/after restore:

 

Restore ( upload not included ) took about 3:30

( may be part of this time was used just for building the site to display after resore )

and during this time my poor athlon tb 1G was at 100%,

so i try to figure out what happens if i upload not 3 mb db ( 500 kb gzip ),

but a 100 mb db ( 15-20 mb gzip )

[TCH-Rick]

For a database the size you mention it would be best to upload the file to your root directory of your site and submit a Help Desk ticket asking to have the data imported into an empty database you have created. We can then import the data on the server when loads are low and prevent any problems.

[Soran]

For a database the size you mention it would be best to upload the file to your root directory of your site and submit a Help Desk ticket asking to have the data imported into an empty database you have created. We can then import the data on the server when loads are low and prevent any problems.

<{POST_SNAPBACK}>

Well... if i ever would need to restore a database

( i do hope that it will not happen often ),

it will be an emergency situation, thus i just wouldn't have the time to ask support to restore it.

( no matter how fast the support is, it still costs additional time )

If i need to restore a DB, it probably means that my forum is down, and i would want to bring it back ASAP.

So i wouldn't be really happy to see asking support in this case

as planed solution for restore.

I wouldn't like to test the patience of my forum members,

because i know how it feels when my favorite forum is down ( horrible / i miss the "cry" smiley )