By mompadaddy on

I want to clone an older version of my site: mysite.com. I have all of the files and database backed up from the same day, at the same time so they should match perfectly.

I created a new database and imported the old data into it.

I copied all of the files into the new directory (a subdomain of the main site: subdomain.mysite.com.)

I changed the settings.php to point to the new database and new site.

I am running URL aliases., so I changed the .htaccess settings for the new site. It is in the directory subdomain.mysite.com, the same relationship the original .htaccess has to the original site.

The home page comes up perfectly on subdomain.mysite.com, but every other page comes up 'Page not found'.

Anyone know what I did wrong or didn't do that I should have?

Thanks

⋅ Categories: Drupal 6.x

Comments

mompadaddy’s picture

mompadaddy commented

For some reason, the .htaccess from the original site doesn't work in the subdomain/cloned site.

This .htaccess file does work:

http://drupal.org/node/480908

vako’s picture

vako commented

Here's the best way that worked for me on 6 sites that I migrated so far:
- Backup the /default/files folder or the entire /sites folder and any other custom files that you have
- Install and use the Backup & Migrate module: http://drupal.org/project/backup_migrate
- Save the site with this module and then do the restore on the new site.
- Restore the files directory.

Do not use ver. 2 of the module for now, it's still in development. But once it's final, will also backup the files folder for you in one easy step.

vallab444’s picture

vallab444 commented

I thought the B&M module only copies the DB tables and nothing more. SO, is it necessary to keep the files folder aside?

I' trying to restore my site onto another server, with the B & M backup. The new site does not replicate the old one in terms of contrib modules. When I run the restore process on the new server, it comes out of that after some time, without showing neither the restore success status nor any errors. Apparently, it does nothing.

What could be going wrong? my old site's Db is named 'sitename_736', while the new one is 'sitename'

-Vallab

vm’s picture

vm commented

SO, is it necessary to keep the files folder aside?

yes, if there are already files that have been uploaded into it