Could not run backup because the source 'db' is missing.

I see the same issue.

Yes, I had the same problem after updating to 7.x-2.7 - reverting back to the previous version fixed the problem, that is Backup and Migrate could find the Default db again and the backup ran OK

I have the same issue after upgrading. Reverting to previous version.

As the OP notes, "SOURCE" shows as "missing" in the table of profiles. Creating a new profile also shows "SOURCE" as "missing".

maybe related? similar issue

aitala. Are you sure both websites are running 2.7 version.

I tested that on 3 different websites on 3 different hosts. I have that problem with all of them.

Regards,

Alex

I have two exact setups on the same hosting company. 1 works the other does not.

Those of you with similar setups where one works and the other doesn't, could you compare the contents of the backup_migrate_* db tables and see if there are interesting differences?

Exactly the same problem here. Installed version 7.x.2.7 and the 'Backup from' select stayed empty causing the error described above.

Reverted to the previous installed version on my development machine (was version 7.x.2.4) and everything was working flawlessly again.

(Before, i did a reinstall, cleared the cache, but problem stayed the same)

This has to have been caused by the following commit: http://drupalcode.org/project/backup_migrate.git/commit/ef90a5a7ed97464f... which was merely intended to do some error checking so that the module wouldn't choke when a broken or missing db was defined. Either I screwed something up with the error checking, or there is some error which isn't preventing Drupal from accessing the db but is causing the main db to be unavailable to Backup and Migrate.

I've attached a patch that reverses that 1 commit. Can people having this problem try it on the latest dev and tell me if it is indeed the cause of the issue.

I applied your reversal patch, and backup_migrate works again. The connection attempt in _db_get_connection in destinations.db.inc is throwing an exception in your newly added try block. I added a debug($e) in the catch and have attached its output (sanitized). I haven't tried to work through the changes in destinations.db.mysql.inc yet to see what's provoking this.

I can confirm that the patch in #13 almost resolved the issue described. Nothing else seemed to resolve it (clearing cache, cron, rebuild registry, disable/uninstall/reinstall module, etc).

EDIT:
I spoke too soon. The source reappears, but I'm unable to back up with drush. Not sure if this is related, though, since I can now backup via the UI.

Setting this back to needs review since my RTBC was a bit premature.

Patch from #13 resolves the issue for me.

#13 fixed this for me.

Any estimate on the release of an updated module? Sorry, but I am a newbie and do not know how to apply a patch (even after reading the "How to apply a patch" article).

TIA.

Unless there is a feature that you have to have, the easiest solution is to go back to the earlier version by going to the bottom of the project page and look for "View all releases". Download the previous version from there till there is a fix.

This bug should be be flagged as a 'known issue' against the 2.7 release to warn others that their backups might fail

I've rolled back the offending code in dev. I have no idea how the MySQL connection could be access denied but still actually works. If any body has any idea what might be happening here I'd love to have more info.

Not sure what's wrong
I run some multicore websites ( basically they are all the same with different content but do have the same modules enabled, use the same codebase and use the same database server ( different databases for most part ).

On about half of the websites I get the error missing db on the other half it just works fine...

Cleared cache on all sites just to be sure.

Only thing I can think of is a different setting or something??

very strange.. hope this helps...

@ #11

Posted by aitala on May 24, 2013 at 3:28pm
The only difference I see is the one that works with 7.x-2.7 did not have compression enabled and the one that failed had GZip compression enabled.

I have multiple sites (looked at 2) ( same codebase, db server etc ) both use Gzip compression as backup setting one works the other doesn't. Think we can exclude GZip compression as the cause.

@scuba_fly: are you still having issues with the latest dev release from june 14 or later?

I experienced this issue with backup_migrate 7.x-3.x-dev. Uninstalled the BAM tables, set up "from scratch" still had error. Ran patch #13, restored BAM functionality.

...apologies this is for 7.x-2.7 and not dev version.

Could not run restore because the source 'db' is missing.
Could not perform the restore.

Strange this error only occurs on 1 of 5 sites running off the same code base in both dev and live environments.

---

to add: just noticed on live environment that after upgrade, the dropdown box, "Backup from..." is blank, where on dev environment it = "Default Database"

only on the one site that is causing an error.

---

Under "Destinations" the "Default Database" is not listed on live but listed in dev.

so when importing database with phpmyadmin, it still does not correct the issue on live site

I also need to report that backup is not working because "db" is missing. I see this error in version 2.4, 2.5 and 2.7. After installing the patch the error message changes a little bit to "Could not run backup because the source '' is missing." I also tried the "dev" version. There I get some different error. Is there any workaround for this issue. The settings.php file has the right path to the SQLite DB.

Same error with 7.27. Works in my local environment, doesn't work on the live site. Exported the local database & imported it onto the live database, error remains!

Moving to 7.3.dev fixed the error

ye ol de-automation

I have same issues. source db is missing. restoring version 7.x-2.5 resolved my issue.

I've been through the same issues.

On a new blank drupal installation, the Backup and Migrate module could not find the db.

Then I uninstalled and installed again, but it didn't find again.

So, a changed the password of the mysql user, and it worked.
It showed some warnings, but I believe its related at multiple times I tried to restore the db.

The old password had some 'strange' characters that may be the cause of the problem.
The old password: Tn@t+VzQl3MP

I've using the 7.x-2.7 version

(sorry for my english)

nice find nimbfire! Your english is good :)

This corrected my issue also by changing the password to common characters.

This also explains why it works in local development using username "root" with no password and it does not on live site using a password.

The old password I was using for the one site that was not working: hrf=TNo}+!+I

Common characters of yours and mine is the "+" character.

I experience the same issue. Clean Drupal installation with Backup & Migrate 7.x-2.7. My password does contain the character '%'.

I'm also experiencing this issue. I have 7.x-2.7 installed. The patch in #13 also worked for me.

Password containing characters "+" or "!" don't work either!

Found the same issue on one of my sites, but couldn't replicate the issue on 4 other sites running the module. It may have to do with the password character issue mentioned in above posts. Also tried flushing the caches, running update.php, and even deleting the 7.x-2.7 version of the module and reinstalling. I got it fixed by installing the latest dev module (7.x-3.x dev). As soon as I had installed it, and run the DB updates, all was good again.

Knowing that dev releases still need to be run by the security team, is there any ETA on when 7.x-3.x will be live?

This version of backup & Migrate resolved my problem also, you should try it. -> https://drupal.org/node/686904

Upgrade or patch from #13 fixes the problem.

I have the same Problem.

I work with Commerce Kickstart 2.9

#39 has fixed the Problem. It works fine.

Greetings from Germany
Frank

To nimbfire (post #33) > THANK YOU SO MUCH !! your solution was right, it worked for me. Just had to change the password in sites/default/settings.php and of course on mysql database and ^^miracle ^^ !!

I encountered the same db missing problem, after applying the latest dev as @ronan #13 committed the patch. Confirmed it works and everything is back to normal. Thanks @Ronan !

#39
thanks it work for me :)

Changing the DB password worked for me too. My password contained the + character which prevented it from working. Just to note * and = can be used in a password

I have 2 sites both running 7.27

Works on one site and not the other. Tried changing the password the same as the site that was working and that did not solve the problem.
The configuration and destination are the same on both sites.

change the password to not include special characters to see if works

The tab which i have highlighted in the attachment is not visible on my website........Kindly help me out .....On priority .....

Thanks in advance.....

Try nimbfires post #33. That tab won't show because the default database is missing.

FYI, the only thing that's needed is to urlencode the parameters:

diff --git a/sites/all/modules/contrib/backup_migrate/includes/destinations.db.mysql.inc b/sites/all/modules/contrib/backup_migrate/includes/destinations.db.mysql.inc
index ffde3f5..283bfa6 100644
--- a/sites/all/modules/contrib/backup_migrate/includes/destinations.db.mysql.inc
+++ b/sites/all/modules/contrib/backup_migrate/includes/destinations.db.mysql.inc
@@ -49,7 +49,7 @@ class backup_migrate_destination_db_mysql extends backup_migrate_destination_db
         // Only mysql/mysqli supported by this destination.
         $key = $db_key . ':' . $tgt_key;
         if ($info['driver'] === 'mysql') {
-          $url = $info['driver'] . '://' . $info['username'] . ':' . $info['password'] . '@' . $info['host'] . (isset($info['port']) ? ':' . $info['port'] : '') . '/' . $info['database'];
+          $url = $info['driver'] . '://' . $info['username'] . ':' . urlencode($info['password']) . '@' . $info['host'] . (isset($info['port']) ? ':' . $info['port'] : '') . '/' . $info['database'];
           if ($destination = backup_migrate_create_destination('mysql', array('url' => $url))) {
             // Make sure the connection is valid.
             if ($destination->_get_db_connection()) {

#53 doesn't work for me

@Pramod Edathil this should be fixed in the 2.x-dev. Please try that before reopening this ticket.

Hi all,

Can confirm #34 and #35... "backup and migrate" 2.7 .... has issues with the + sign in db password.

Same here

Kind regards,

Eno