Hello,
I have copied my whole site to my local computer (running ubuntu & lamp). There I have drupal 5.9 installed and the module backup and migrate enabled. I did a backup of my production site with backup and migrate and imported that file into my local site. It appears that the configuration settings are not being copied. What am I missing? Where is that information stored?
What is the best way of creating an identical backup of the production site to my local computer? Is this documented somewhere?
Is it necessary to name the local database the same as on the production site (I appears to me that backup and migrate does not backup that information, so it should matter or does it anyhow)?
Kind regards,
Frank
Comments
...
Make sure you are signed up to the Security notification list drupal.org/security
Update to 5.10 :) -> Test.
Clear the sites cache table.
Turn off clean url's
Backup your database (I use mysqldump)
Backup all the files in the web directory.
Restore your database to the new destination
Restore your files to the new destination.
Ensure that the web server knows the site by name
Check correct information in settings.php
Make sure you got the .htaccess file and it does not need to be adjusted for any differences in the new servers configuration.
Misc stuff exists: http://drupal.org/search/node/move+site+type%3Abook
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
Mysqldump
Thank you Steven!
You mentioned mysqldump. I had looked into it, but couldn't figure out how to use it on my ISP (I don't have shell access).
In all I read I got the impression that there are at least two different products by the same name.
Would you mind telling me, if the one you are using is possibly suitable for my situation (and where to find it) and maybe even some instructions on how to use it?
Kind regards,
Frank
PS: Thanks for the link. For one result (http://drupal.org/node/252969) which seemed to cover the situation. I got the error "You are not authorized to access this page. " even though I am logged-in. What am I supposed to make of that?
You may want to look at the
Do you use a web-based control panel to administer your domain? Do you have access to phpMyAdmin? That's another way to do it. Frankly, though, I've found it faster just to use backup/migrate for that particular task. I, too, develop on a local machine, and all I do is import the backup created by the backup/migrate module and edit my settings.php file. If that isn't working for you, though, you may want to talk to your host about your database backup options.
Rob Hamm
http://www.sage-comics.com
You don't need shell access,
You don't need shell access, but you need some kind of user tools to manage and backup your database. Many hosters (even $5/month ones) include in their control panel some database backup tools and/or phpmyadmin. If not, you can upload to your site phpMyBackupPro, backupDB or another similar tool.
Also, there is a very compact and convenient tool called Sypex Dumper - but its user interface is currently available only in Russian.
(Actually, there is a non-official English version of Sypex Dumper, too --
see http://ztz.110mb.com/dumper.en.zip).
Good news ...
Thanks GN, that is good news ...
Hello, I have created a copy
Hello,
I have created a copy of my live drupal site by moving the files and copying the database over to localhost. I have also updated the settings.php file to the new database location and all that. The site runs.
However, sometimes it justs into the livesite instead of just on localhost. Especially with SSL pages...i cant see any SSL pages on the local host...and by default, it goes to the live site without even running the localhost first....
why is this>? anyone else have success in backing up their ecommerce site?
Have you cleared the cache of
Have you cleared the cache of your site before backing up the data base?
You may also clear the seach tables if you need to reduce the file size, but that is a side issue.
Also, check if any of your links include the full domain name.