Also, when you restore using Backup-Migrate, make sure all of the files on the server you're migrating to are EXACTLY the same as the one you backed up from. I've found something as little as a different version of a module between sites will blow things up.
You definitely need 2 processes - Backup-Migrate takes care of your database, but also need to migrate all files.
Michelle
On 10/20/2010 7:36 PM, Maurice Mengel wrote:
I think you are on the right track. I use backup and migrate to get the db, then I get the files from the server and copy all to my home server. I bet the WSOD is due to something trivial like php memory settings or some rights issues (file system, or db) or the like. Anyways, it will pay off if you figure that out now! Did you search d.o for this problem?
On Wed, Oct 20, 2010 at 10:29 PM, Rogerarelem@bigpond.com wrote:
I have a development site on a remote server. I've installed the Backup_Migrate module and found that it only copies the Drupal code not the database, images, etc.
I do not want to continue developing on the remoter server site as the save times can frequently be 1 minute or so even after small changes to css code. So trialing css code changes can take a long time over all.
I tried cPanel on the server but the resultant mysql.tar.gz seems to produce only the same as the backup_migrate module produces.
When I used the b_m module to restore to my home pc it killed my Drupal installation, WSOD.
When I have all the drupal site and mysql database I can develop at home, fix issues then intend to migrate it back to the server but after the current experience am nervous.
I can find nothing to help understand the process or what I should or should not be doing in migrating a drupal system. Can someone please advise me. Thanks Roger -- [ Drupal support list | http://lists.drupal.org/ ]