Hi guys,

Unfortunately I seem to have a weird one here. I can't restore backup db's from my local environment to my server exactly as I used to be able to (and have done for years) without problems. I.E. I always could create backups locally (Windows 7/XAMPP setup) and restore direct to server (Dreamhost VPSs) several times a day, either direction, as part of fulltime development work.

Today I've been completely flummoxed (for over 9 hours now) just trying to find any clues (logs, watchdog, error messages, anything) but each time there's a completely 'silent' fail. I can backup/restore local to local and remote to remote and remote to local but each and every time I try local to remote (today only that is) absolutely nothing happens, no log errors reported or anything, no data imported whatsoever.

Example steps/details below - but the above make sense? Does a silent failure of this kind point to something in particular?

Steps/details:
1. Local environment is Windows 7/XAMPP 1.8.2 (php 5.4, apache 2.4.4, mysql 5.0.10
2. Drupal 7.31 (also just patched today, locally and remote)
3. Backup Migrate 7.2.8 (first 6 hours) and 7.3.0

STOP THE PRESS/UPDATE (30 minutes later):
4. My restore files have suddenly kicked-in (after I reverted php to the previous version 5.3 and re-tested the restore).
5. No restore confirmation was received so it's difficult to see how long after the restore action was triggered - but this took maybe 15-30 minutes to restore.
6. The site is now covered in tons of Notice messages (Notice: Undefined index: 29 in user_node_load() (line 3641 of /home/peachypro/site/modules/user/user.module) on the admin pages and the homepage states: "Fatal error: Call to undefined function field_group_info_groups() in /home/peachypro/site/sites/all/modules/commerce_fieldgroup_panes/commerce_fieldgroup_panes.module on line 14".
7. I can browse the admin pages but none of the site pages.
8. Local version of the db has 66 tables and the remote has 54! (I also just spotted).

I'll post this now - thanks - in case there's an obvious error here (anyone can spot)?

Any feedback/help would be highly appreciated.

Q.

Comments

quantos’s picture

quantos commented

Update: I just found a similar issue here: https://www.drupal.org/node/1995044

This problem can occur if you've specified a database prefix in settings.php or via the installer and then restore from a database that did not use the same prefix.

Backup Migrate executes the SQL commands successfully, but you won't see any change if the prefix is different unless you change the prefix in settings.php to reflect the database you restore from

Referencing a further link here: Source : https://drupal.org/comment/4665038#comment-4665038

I'll check these and update/remove this ticket if it's a full duplicate issue. It was hard to search for in the first place, being such a generic issue.

Q.

ronan’s picture

ronan commented
Status: Active » Postponed (maintainer needs more info)

Do you have a db prefix in either your local or remote installs? If that is the case and they don't match then this is indeed a dupe. B&M (still) doesn't handle prefixes well. It's on my todo list but it's a complicated request and it never seems to become a priority.

quantos’s picture

quantos commented

Hi Ronan. Many thanks for the follow-ups and my apologies, I didn't see the earlier reply. I don't have or haven't attempted to use a db prefix but at least one of the problem sites was originally created with Commerce installer package - which I subsequently removed after local testing to make sure that wouldn't be an issue - which means you could have hit the bulls-eye with the installer comment. Does that sound a candidate explanation?

PS I'll test further on more sites that never used an installer profile - and will update back here.

Q.

quantos’s picture

quantos commented

Ronan: Test update: it does seem my problem is restricted to Commerce Installer Profiles (or something very similar). I've just tested local/remote restores on sites that don't have am Install profile and have had no problems. Phew.

I.E. I'll test further and let you know but the problem sites x 2 originally featured the Commerce Install profile but I removed the profile directories later to update the modules direct. I'll let you know again when I've had to chance to test that properly. Thanks again meantime.

Q.

couturier’s picture

couturier commented
Status: Postponed (maintainer needs more info) » Closed (outdated)

Closed due to non-response from the issue reporter.