Database export/import question

Events happening in the community are now at Drupal community events on www.drupal.org.
cdragin's picture

I have been attempting to make a local version of a client's site for development. I was able to export a .gzip using phpmyadmin, but when I import it locally and compare to the live version, a lot of the tables are missing or are quite a bit smaller than the live version. A .zip export was only 4k so I assumed it was no good. The uncompressed database is around 117mb. I exported and downloaded it, and set the file size parameters in php.ini so that I don't get a "this database is too big" error. However, it has been loading for well over an hour now, and my guess is that nothing's really happening...although it hasn't stopped and given me an error message so I don't know for sure. Having never imported an uncompressed database, I have no idea how long it should take.

-Any idea why the .gzip export is incomplete?
-Any idea if there is are timing parameters I should adjust in php.ini? I see a number of settings relating to time but am not sure what ones would need to be edited.
-Any other clues?

Unfortunately the client just left town for a few days...if I can't figure it out I'll have to have him hook me up with his webhost when he returns.

Thanks

cd

Comments

Gzipping problems

JuliaKM's picture

Hi Claire,

You might want to try and install the Backup and Migrate module. I've had a lot of problems getting PhpMyAdmin to correctly export and import large databases. I generally just do a mysqldump via commandline. Let me know if you have any questions about how to do that.

Julia

Backup/Migrate

cdragin's picture

My plan was to have a full backup of the site before I made any changes to it...installing Backup and Migrate being #1 on the list. May go ahead and do it anyway.

Oh, and I also tried the

cdragin's picture

Oh, and I also tried the command line approach, only to find my ftp password didn't work on ssh. But I may try that again once the client returns.

The mysqldump tool is

kwinters's picture

The mysqldump tool is usually the most reliable if it's available. You can tar up a dump to cut down on file size as needed.

One important note about backup & migrate - make sure you export all table definitions, and exclude data (if anything) on the log tables. Watchdog, etc. data doesn't need to be transferred, but you will error out if the table definitions are wrong.

Ken Winters

www.coalmarch.com

Ken Winters

triDUG

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: