Hi,
like some others on this board GoDaddy have forced me off their servers by claiming high CPU usage and shutting off my site.
Only now I find I cannot access mysql database. I have managed to download a 'sqlbackup.tar'.
If I make a fresh install nother server, is the 'sqlbackup.tar' enough to enable me to restore my blog?
Thanks.
Moving from GoDaddy
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Re: Moving from GoDaddy
Hi!
That depends on the contents of your sqlbackup.tar package. Did you look into it, does it contain a complete SQL dump with all of your data?
If you load that to a new server, you'll have your database intact. You will still need all the extra files you possibly had on your old blog: Media files (images, documents) and possibly custom plugins (if you uploaded them previously) or custom templates/modifications. You'll need to get those via FTP as well.
Then you can upload a usual serendipity release to your blog, and manually create a serendipity_config_local.inc.php file. It should look like this:
You must there enter the right database access details to your new imported database, and you must enter the versionInstalled number of the serendipity version you had on your old host.
Feel free to ask for specific details if you're having problems.
Regards,
Garvin
That depends on the contents of your sqlbackup.tar package. Did you look into it, does it contain a complete SQL dump with all of your data?
If you load that to a new server, you'll have your database intact. You will still need all the extra files you possibly had on your old blog: Media files (images, documents) and possibly custom plugins (if you uploaded them previously) or custom templates/modifications. You'll need to get those via FTP as well.
Then you can upload a usual serendipity release to your blog, and manually create a serendipity_config_local.inc.php file. It should look like this:
Code: Select all
<?php
$serendipity['versionInstalled'] = '1.3-alpha1';
$serendipity['dbName'] = 'serendipity';
$serendipity['dbPrefix'] = 'serendipity10_';
$serendipity['dbHost'] = '127.0.0.1';
$serendipity['dbUser'] = 'root';
$serendipity['dbPass'] = 'pass';
$serendipity['dbType'] = 'mysql';
$serendipity['dbPersistent'] = false;
?>
Feel free to ask for specific details if you're having problems.
Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
Hi Garvin
My '2007-10-10-22-37_sqlbackup.tar' contains 32 sql files. Does that sound right?
One has INSERT_serendpity_emtries.sql etc... and is about 1MB
However when I extract it, it makes a new 'last_backup' direcrory which contains much smaller files and not all the data.
On my new server can I upload the uncompressed '2007-10-10-22-37_sqlbackup.tar'?
Thanks.
My '2007-10-10-22-37_sqlbackup.tar' contains 32 sql files. Does that sound right?
One has INSERT_serendpity_emtries.sql etc... and is about 1MB
However when I extract it, it makes a new 'last_backup' direcrory which contains much smaller files and not all the data.
On my new server can I upload the uncompressed '2007-10-10-22-37_sqlbackup.tar'?
Thanks.
I've had good luck importing SQL data with BigDump when not having access to the shell.
http://www.ozerov.de/bigdump.php
http://www.ozerov.de/bigdump.php