MOVING SERVERS
- Login to post comments
Fri, 27/08/2010 - 18:47
i am about to attempt to move a ProsePoint site from a GoDaddy account to a BlueHost account. i am new to ProsePoint/Drupal... i'm assuming this is possible, right? any tips out there before i attempt this? BlueHost has SimpleScripts which can automatically install Drupal for you. this is something that i did before i realized that i should start with a clean slate because the ProsePoint installation includes Drupal. anything else i should be aware of? thank you, ProsePoint community! any help would be appreciated.
Tue, 31/08/2010 - 17:12
#2
recreating site
ok. thanks, beng! i'll try that. thanks for your quick response!
ardith
Tue, 31/08/2010 - 17:49
#3
instructions to move site
hi, beng.
as a newbie, i'm apprehensive about doing this database move. sounds easy enough with your instructions. when i do a search for supporting materials i get a lot of conflicting info on the drupal site. should i be concerned about this? there's a discussion there with detailed instructions. how would these drupal steps compare with what you've described above? http://drupal.org/node/46389
thanks for your time.
ardith
Thu, 02/09/2010 - 10:07
#4
...
Hi,
Firstly, that post you quoted is very old and applies for Drupal 4.x. ProsePoint is based on Drupal 6.x which is too generations newer. Digging out how much of 4.x still applies to 6.x is probably not worth the effort.
Secondly, the actual procedure for dumping and restoring a database depends on your hosting provider. They will usually provide some sort of gui (ie. phpmyadmin or another) to do this, so they would be the authorative reference for their hosting system. (I don't think I actually provide any specific instructions on dumping and restoring databases for that same reason.)
As long as you are restoring onto a totally empty database, that should be okay. Couldn't you conduct a test migration first before 'going live'?
- Login to post comments
Hi,
If you create a tarball (ie. a compressed archive) of the filesystem where your site is, and take a mysql dump of the database, that usually contains all the information needed to recreate a site on another server.
When you extract out the tarball onto the destination server, you may need to change the filesystem permissions (or filesystem owner) of the .../sites/default/files directory and all its subdirectories so that the web server of the destination server can write to them.
I think that's about it, really.