The script is capable of both backing up databases and restoring them by part (refreshing every so often) so as to avoid time out problems. It is theoretically possible to restore or backup databases of any size using it.
The file readme.txt contains the information you will require for setting the script up on your host.
Still timing out? If you are still getting time out problems try forcing a lower execution time between refreshes by editing "var $maximum_time = 0;" on line 26 changing 0 to the number of seconds you wish the script to execute (work up from 15)
I get an error after submitting the database settings You are either using the wrong details or your MySQL server is offline. Consult your hosting provider for more information, quoting the error the script gives you.
Getting the duplicate entry error when restoring? This is always caused when you are attempting to restore a backup over a database that already has data in it. Try restoring to an empty database instead.
The first one should work for most platforms, but here is another that works just as well - but its more configurable, and also more picky
your mileage will vary
...
BigDump: Staggered MySQL Dump Importer http://www.ozerov.de/bigdump.php Staggered import of large and very large MySQL Dumps (like phpMyAdmin 2.x Dumps) even through the web-servers with hard runtime limit and those in safe mode. The script executes only a small part of the huge dump and restarts itself. The next session starts where the last was stopped.
This program is for you if you want to restore the very large backup of your mySQL database (or a part of it) into the new or the same mySQL database. Also if you can't access the server shell and you can't import the dump using phpMyAdmin or any other scripts due to hard memory resp. runtime limit of the web-server.
That is EXACTLY what I have needed in my life. I've been searching for reasons why I can't import an sql file bigger than 2 megs using phpadmin. How many boards' tables have a 'posts' table under 2 megs?
I was even able to highlight every table, and export them from my live site to my local database in a super batch process. WOW!
Guys, I have an HUGE problem. Recently I had several problems with w3t_posts reported as "in use", a few days ago I tried an update to 6.5 but the update failed in the altertabe phase on w3t_posts as reported in this message:
The problem is 100% related to a sort of corruption in my database.
Now I got a backup of the database (in .SQL format) from my server admin. The file itself is ok and I can open it with a text editor but I can't manage to do anything else.
I tried to import it using MySQL-Front but it stop douring the process.
The question is: Is there a tool to check and fix probles in an .SQL file BEFORE imporing it in the SQL server ?
Do you have a backup of your w3t_Posts table before it corrupted? If not, you may be screwed unfortunately, and will have to start with a newly created table.
Create a new database (just for testing) and see if you can successfully import just that one table into it.
1) If you can't (and we know the REPAIR TABLE command hasn't worked), then it may be seriously damaged beyond repair. It's difficult to know how fixable it is without actually taking a look at it.
2) If you can import it, then this means that you'll have to DROP the current w3t_Posts table from your main database first *before* importing the backup.
here my feedback, hope it could be useful for someone:
After I understand that the issue was related to w3t_posts I opened the .sql with a text editor, deleted everything before w3t_posts and saved it as "PRE_W3T_POSTS.SQL", than open again the original .sql, removed everithing from the beginning to the end of w3t_posts and saved it as "POST_W3T_POSTS.SQL". Opened again and removed everything before and after w3t_posts and saved it as "W3T_POSTS.SQL".
After I created those 3 files used MySQL-Front to import all in my database. Obviously I got a problem with the w3t_posts one but MySQL-Front recorded a .err file with all operations failed. I opened the .err and copied row by row and executed them in MySQL-Front...
Donate to UBBDev today to help aid in Operational, Server and Script Maintenance, and Development costs.
Please also see our parent organization VNC Web Services if you're in the need of a new UBB.threads Install or Upgrade, Site/Server Migrations, or Security and Coding Services.
