Database restore by admin gives blank page

[superfrank]

I have made several database backups. The earlier ones are possible to restore through the admin panel. But from a certain database backup - and all the later ones - this is not possible anymore. When I try to restore, the browser immediately outputs an empty page, and the backup is not restored.

 

However, the weird thing is that if I use the mysql client I can restore those 'errorous' backups without any problem.

 

I also tried: I restored the latest backup by the mysql client, the shop works fine, like before. Then made a backup from that database. Also this backup cannot be restored through the admin panel.

 

I would say if there is a database error, it wouldnt work, no matter what way it is restored.

If I messed up some code somewhere, the older databases wouldnt work neither.

 

I noticed that the errorous databases are made after jan 1st 2007, the okay ones are from 2006.

The okay databases are smaller than 1900 kB, the errorous ones are larger than 2200 kB.

 

Is this a bug, or is there a limitation on the filesize of the database?

 

Does anyone has a good idea how to solve this?

[Barbie]

I have made several database backups. The earlier ones are possible to restore through the admin panel. But from a certain database backup - and all the later ones - this is not possible anymore. When I try to restore, the browser immediately outputs an empty page, and the backup is not restored.

 

However, the weird thing is that if I use the mysql client I can restore those 'errorous' backups without any problem.

 

I also tried: I restored the latest backup by the mysql client, the shop works fine, like before. Then made a backup from that database. Also this backup cannot be restored through the admin panel.

 

I would say if there is a database error, it wouldnt work, no matter what way it is restored.

If I messed up some code somewhere, the older databases wouldnt work neither.

 

I noticed that the errorous databases are made after jan 1st 2007, the okay ones are from 2006.

The okay databases are smaller than 1900 kB, the errorous ones are larger than 2200 kB.

 

Is this a bug, or is there a limitation on the filesize of the database?

 

Does anyone has a good idea how to solve this?

 

Unfortunately large database backups can not be restored from the admin panel which is why I keep a regular backup of my DBs on my computer as they largely exceed the size of yours. Have never found anyone who could solve this problem.

[superfrank]

Unfortunately large database backups can not be restored from the admin panel which is why I keep a regular backup of my DBs on my computer as they largely exceed the size of yours. Have never found anyone who could solve this problem.

This seems strange ... I've read on this forum about people having shops of 10,000's of articles (mine is 'only' 2,000), and I havent found any posts or bug reports on this.

 

The only thing I found that could be connected to this problem, it's in the admin/backup.php file, around line 190:

 

if (isset($restore_from) && file_exists($restore_from) && (filesize($restore_from) > 15000)) {
 $fd = fopen($restore_from, 'rb');
 $restore_query = fread($fd, filesize($restore_from));
 fclose($fd);
}

But I'm not so much of a PHP guru... Besides, the number 15000 refers to 15kB, and my problem seems to occur between 1.8 and 2.2 MB.

 

The problem must be somewhere in the osC files, since the mySQL client doesn't have any problem to restore the backup.

 

Does anybody have a clue?

[Jack_mcs]

It fails because the limit of your server is being reached. All shared servers have a limit on how much processor time a script can use. With larger databases, that limit is reached and the server ends the process.

 

Jack

[superfrank]

It fails because the limit of your server is being reached. All shared servers have a limit on how much processor time a script can use. With larger databases, that limit is reached and the server ends the process.

 

I don't think thats the problem; restoring by command line takes less than half a second.

Also, the page would at least write some basic time-out error for myql or php.

 

When succesfully restoring from a (smaller) database, the page just 'waits' untill the restore process has finished, for several seconds. With the other database the blank page appears instantly.

[Jack_mcs]

The command line isn't subject to the same resource limits as the admin section is.

 

Jack

[ugtar]

I have a pretty good idea that this is due to a change in php. You probably upgraded your php version (or your host did) and you don't know it. The reason I say this is I can make a backup file, and I'll be able to restore it via the admin panel on the hosted site (my main site) works fine. But if I try to restore the exact same file on my development server (my home computer) I get the same error you describe. The only differences between my hosted server and my development server is my dev server have higher versions of mysql, php, and apache.

 

Unfortunately I never really looked into the problem since restore works fine on my main site, and on my home computer I can just restore via local mysql commands from a shell.

 

It's not an answer but I hope that at least gives you a place to start looking...

 

Uri

[Guest]

Hi Folks,

This is my first post here.

I am having exactly the same problem. Has anyone found a solution to this. Please!!!

 

Regards

Hayden