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
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, Roger arelem@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/ ]
Have you cleared the cache before taking database dump ? Have you heard about Migraine? Here is the presentation from my college : http://bit.ly/c1Qj1v
On Thu, Oct 21, 2010 at 8:06 AM, Maurice Mengel mauricemengel@gmail.comwrote:
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, Roger arelem@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/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
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/ ]
One thing I have noticed moving back and forth is I usually have to go into the file system option on site configuration and update where my files are. My Acquia installation has a slightly different path than the "standard" Drupal install on my server.
Also in anticipation of moving from a temporary domain name to the final domain name I've been doing some scans on the MySQL dump inside the Backup-Migrate zip file. It appears that some modules can store full paths (which in my case would be the temporary domain name).
Gregg
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Michelle Ziegmann Sent: Thursday, October 21, 2010 6:53 AM To: support@drupal.org Subject: Re: [support] Backing up and migrating a drupal site
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/ ]
On 21/10/2010 04:29, Roger 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.
Incorrect. The Backup and Migrate module on the server backs up your entire Drupal database. Nothing else.
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.
After you you have backed up your Drupal database on the server you need to backup your entire public_html or www directory on the server. Store both your database backup and your public_html or www directory backup locally somewhere safe on your local machine.
You only need those two components to create an image of your Drupal site on your localhost.
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.
Install a fresh copy of drupal on your local machine using the latest Drupal version from Drupal.org. However, when you install it use the same database name and database password you used on the server. This is important.
Next, drop your newly created database on your local machine. Now, import the server database backup you created from your server to your local machine through phpmyadmin, from the same place where you dropped it.
Now copy the database backup of your public_html or www folder and replace it all together (not overwrite), whatever is in the htdocs folder on your local machine.
Next, you need to perform an update of your local Drupal database on the local machine to the latest version. You can do this in a couple of ways. If you are using Drush then execute the commands drush pm_update and updatedb consecutively following the appropriate instructions.
Now your Drupal site from the server should be correctly installed locally. Only this time its up to date with Drupal according to the latest Drupal version, not the version you used on the server.
To migrate your Drupal site from the local machine back to the server where it came from, follow the reverse process.
If there are any mistakes or better methods to the method I use, please let me know.
Regards, Moses
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
-
Amit Vyas -
Gregg Marshall -
Maurice Mengel -
Michelle Ziegmann -
Moses Elias (2) -
Roger