Hello,

I am migrating my dev site to production. I did the following but it did not restore as expected. I presumed that restoring would bring the new site to be exactly the same as the dev site.

I used the same version of drupal (6.16). Here is what I did:

1. copied the drupal files to www directory
2. replaced the new sites directory with the sites directory from the dev site
3. removed settings.php and created a new one using default.settings.php
4. created a new mySQL database
5. installed drupal using the new db
6. enabled backup and migrate module
7. performed the restore

None of the content was transfered and I am not sure why. Any help would be much appreciated. I guess I have missed a step. I did also go to file-system in the admin menu and clicked save. This still did not change anything. None of my views were migrated and most importantly, none of the content.

Thanks in advance.

Ren Gomez

Comments

rengomez’s picture

rengomez commented

Just checked, none of my content types were migrated either. Basically, it seems the restore did nothing. I checked the db in cPanel and the migration happened as the db size is the same as on my dev site.

Again, any help would be much appreciated.

Thanks very much.

apmsooner’s picture

apmsooner commented

Did you name the new database the same as the old? Thats part of the process just in case....

olkl’s picture

olkl commented

I've got exactly the same problem. Nothing is restored.

Owlbear’s picture

Owlbear commented

Hi all, I had this issue recently - is it possible that the Drupal install you're trying to migrate to has a different table prefix? In that case, the backup/migrate module is operating correctly (i.e. dropping all the tables in) but your Drupal install isn't using the tables. This would also explain why your database is the correct size!

If this is the case, you can fix it by changing the db_prefix variable in the /sites/default/settings.php file.

Hope this helps!

Cheers,

Harry

dentonlt’s picture

dentonlt commented

It's possible that your backup file size is greater than the PHP upload limit (2MB default?). If that's the case, backup_migrate doesn't necessarily give you an error message. It just chokes and returns to the backup_migrate page.

To get a smaller file, enable zip/gzip/etc when you export from backup_migrate.

ronan’s picture

ronan commented

I guess it could be what dentonlt describes in #5. If you access to phpMyAdmin (usually available in cpanel) try using the import feature there to restore the file. The DB can be blank if you do it this way so that would be a good way of seeing if anytihng's getting imported at all.

Mario2’s picture

Mario2 commented

same here, i changed php.ini upload limit to 128M and still the same. i did restart:)

alar’s picture

alar commented

My uncompressed backup file was 6 Mb the compressed one only 678 kb! Success with Backup & Migrate module :)

Steps to success
1 - truncate the cache tables
2- disable clean URLs
3- save/backup with Gzip compression

4- create new database (different name was ok) using same prefix
5- turn on module "backup and migrate" on new site
6 - restore from backup

Run update.php

Now to ftp the theme....
and run update.php again

nonoan’s picture

nonoan commented

I just spent some time trying to figure out why Backup & Migrate was not working. FIX: My two Drupal installations had different db_prefix. :-)

Could I suggest that this is something important to check that could be put in the README file of the module?

BTW Thanks for a great module!

ronan’s picture

ronan commented
Status: Active » Closed (duplicate)

Sounds like this may have been a db prefix issue.

gregor171’s picture

gregor171 commented

PS: im my case with multiple site installation tje problem was not using Gzip compression. Thx!