Backup/Restore:
When trying to export large tables as .sql files, quite often only part of the table is exported, although SQLyog reports the export has been completed, is this a known bug, due to connection problems or something else
Full Version: Backup Problems ..
We need more information to help you with this!
But my best guess is that you are connecting to a MySQL server at an ISP, using HTTP-tunnel. Is it so ?
In that case it could be because of a not very generous PHP comfiguration at the webhost! Do you have some means to list your PHP configuration parameters ?
But ... please ... (much) more info!
But my best guess is that you are connecting to a MySQL server at an ISP, using HTTP-tunnel. Is it so ?
In that case it could be because of a not very generous PHP comfiguration at the webhost! Do you have some means to list your PHP configuration parameters ?
But ... please ... (much) more info!
The most important information that we require is whether you are using HTTP Tunneling or Direct Connection.
Mark answered me by mail this:
@mark - please use the Forums - simply because then not only one person will be able to help you then!
QUOTE
thanks for your reply
I put an info file up,
http://test.sigmahotels.com/info.php
to display the PHP settings,
you could be right, its a php timeout, I just wondered why SQLyog reports the export has been completed, I would expect it do detect the error, and report it.
erm to give you more info
I am using the free version, as a client side GUI, the database is on my hosting provider's server, I have a 256/64 ADSL connection, living Cyprus so its not so high tech here
I also get a lot of lost connection to mysql problems, i managed in the end to upload the table, my using a previous dump I had taken with mysql front, and editing that, it was about 6 meg, 25,000 rows, uploading with sqlyog caused many failures due to lost connection, however by using the error log, I was able to edit the .sql file to remove rows already inserted and continue with a smaller file, doing this about 5 times I managed to get all the data in. Of course this won't help me taking large dumps, I have a similar problem with phpmyadmin, it times out after 300 secs so I get a partial dump. As my provider doesn't give SSL access the option of using command line SQL commands to take a dump to the server and zip it and ftp it down is not available, but I do need to find a way to take full backups as this a commercial site and the hosting company only does backups weekly, maybe I need a better hosting provider
Thanks for you help anyway, all suggestions welcome
I put an info file up,
http://test.sigmahotels.com/info.php
to display the PHP settings,
you could be right, its a php timeout, I just wondered why SQLyog reports the export has been completed, I would expect it do detect the error, and report it.
erm to give you more info
I am using the free version, as a client side GUI, the database is on my hosting provider's server, I have a 256/64 ADSL connection, living Cyprus so its not so high tech here
I also get a lot of lost connection to mysql problems, i managed in the end to upload the table, my using a previous dump I had taken with mysql front, and editing that, it was about 6 meg, 25,000 rows, uploading with sqlyog caused many failures due to lost connection, however by using the error log, I was able to edit the .sql file to remove rows already inserted and continue with a smaller file, doing this about 5 times I managed to get all the data in. Of course this won't help me taking large dumps, I have a similar problem with phpmyadmin, it times out after 300 secs so I get a partial dump. As my provider doesn't give SSL access the option of using command line SQL commands to take a dump to the server and zip it and ftp it down is not available, but I do need to find a way to take full backups as this a commercial site and the hosting company only does backups weekly, maybe I need a better hosting provider
Thanks for you help anyway, all suggestions welcome
@mark - please use the Forums - simply because then not only one person will be able to help you then!
To take a dump of a table in HTTP Tunneling, we need to load all the table data in memory. Most of the ISPs put a limit on resources and thus the backup fails.
We plan to overcome this issue in v4.3 by doing incremental export where the dumps will be taken in batch of 1000 rows (or maybe user-specified value as we will need to reduce the row count if there are lot of blob columns).
This is very strange as SQLyog will indeed throw up an HTTP error.
We plan to overcome this issue in v4.3 by doing incremental export where the dumps will be taken in batch of 1000 rows (or maybe user-specified value as we will need to reduce the row count if there are lot of blob columns).
QUOTE
you could be right, its a php timeout, I just wondered why SQLyog reports the export has been completed, I would expect it do detect the error, and report it.
This is very strange as SQLyog will indeed throw up an HTTP error.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.