I’m working in new templates for www.lavozdelanzarote.com and is also time to update from 1.91 to spip 2. But it isn’t an easy task: the xml dump of the database weighs more than 180mb!! (+23000 articles). It’s may be the biggest spip site on the net.
I’ve make a few attempts in a local server (apache over ubuntu), with unsuccessful results. Reloading the page for hours, it was working but broke at the last part.
So, I need help.
I think may be I could split the XML in chunks, and then use the new feature that fusion dump with the running database. But I couldn’t find a software enough optimizated to manipulet a 180mb xml file. (my attempt to do it in python ended in the trash).
I think may be I could split the XML in chunks, and then use the new feature
that fusion dump with the running database. But I couldn't find a software
enough optimizated to manipulet a 180mb xml file. (my attempt to do it in
python ended in the trash).
for such a big database you should work with mysql backup (not the xml
backup from spip )
- take a dump of the production db (with mysqldump NameOfYourDB -uUser
-pPassword > mydump.sql )
- install a spip locally (the same version as in production), let's
say the name of the db is foo
- do a mysql foo -uUser -pPassword <mydump.sql
- then go back to ecrire and you should have your site locally
- put 2.0.2 files localy
- then in ecrire it should ask you to upgrade the database .
You can also use an export with phpMyAdmin (or any other standard sql export) and import it with bigdump.php : it’s a tool fantastic for big dumps.
Before exporting, maybe you should remove statistics, and indexation data.
I think may be I could split the XML in chunks, and then use the new feature
that fusion dump with the running database. But I couldn’t find a software
enough optimizated to manipulet a 180mb xml file. (my attempt to do it in
python ended in the trash).
for such a big database you should work with mysql backup (not the xml
backup from spip )
take a dump of the production db (with mysqldump NameOfYourDB -uUser
-pPassword > mydump.sql )
install a spip locally (the same version as in production), let’s
say the name of the db is foo
do a mysql foo -uUser -pPassword <mydump.sql
then go back to ecrire and you should have your site locally
put 2.0.2 files localy
then in ecrire it should ask you to upgrade the database .
You can also use an export with phpMyAdmin (or any other standard sql export) and import it with bigdump.php : it's a tool fantastic for big dumps.
Yes, usually smooth with ajax progress bar and clean.
But beware of not having "extended" syntax for your SQL export :
it provides shorter exports (all inserts at once in one order),
but if it is too big, bigdump cannot handle them !
I also sometime have nasty charset issues with bigdump.
I have to investigate...
On Sat, Jan 17, 2009 at 1:16 AM, JLuc <jluc@no-log.org> wrote:
Gilles VINCENT a écrit :
You can also use an export with phpMyAdmin (or any other standard sql export) and import it with bigdump.php : it’s a tool fantastic for big dumps.
Yes, usually smooth with ajax progress bar and clean.
But beware of not having « extended » syntax for your SQL export :
it provides shorter exports (all inserts at once in one order),
but if it is too big, bigdump cannot handle them !
This is a limit of this tool.
But I never use the « extended » option with phpMyAdmin…
I also sometime have nasty charset issues with bigdump.
I have to investigate…
There is a line that indicates the charset of the file to read.