Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.When I try to restore a file to the database, it gives me the following error
# Unable to restore from file sites/default/files/backup_migrate/manual/ because a file can't be restored to this database.
You can notice there's not the filename appended to the path. I dsm'd some variables to find out why but I couldn't find where the error comes from.
The POST url seems correct : /admin/content/backup_migrate/destination/list/restorefile/manual/backup-2009-12-07T12-29-36.mysql.bz
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | backup_migrate.module.diff | 608 bytes | garphy |
Comments
Comment #1
garphy CreditAttribution: garphy commentedOk, I think this is fixed in CVS.
Here's a quick patch for the 6.x-2.1.
Comment #2
garphy CreditAttribution: garphy commentedClose.
Comment #3
smoothify CreditAttribution: smoothify commented[Edit - the patch just above fixes it for me too]
Comment #4
entrepreneur27 CreditAttribution: entrepreneur27 commentedI am having this exact same problem with 2.1 downloaded at 6pm San Francisco time on Dec 7th. I got the impression from this thread that the download is meant to be correct but it seems not to be. Am I supposed to patch it? And, if so, would it be possible to release a working version soon, please as I am uncomfortable patching.
Comment #5
garphy CreditAttribution: garphy commentedThe HEAD (6.x-2.x-dev) version seems to be fixed but the whole function seems rewritten. I prefer stay with this tiny patch as it's much more auditable than switching on devel version ;).
Maybe it justifies to release a 2.1.1 patched version based on 2.1 rather than on HEAD.
Comment #6
ronan CreditAttribution: ronan commentedThis patch has been committed. If the latest dev (which should be packaged today sometime) works for everybody I'll roll a new release.
Thanks everybody.
Comment #8
FreeFox CreditAttribution: FreeFox commentedMaybe this helps someone ^^
For migration I have to backup (zipped) => transfer file to local => unzip => edit the file (changing domains, file locations, etc...) => re-zip => upload to new server and than I try to restore:
Unable to restore from file ... because a file can't be restored to this database
I found out that when the file is renamed like db_testdomain-2010-02-04T16-16-02.migrated.zip, you'll see it in the list, can click "restore" and than get the error.
Renaming the file to db_testdomain-2010-02-04T16-16-02.mysql.zip did the trick.
Could the code be corrected to allow other names as well?
Thanks in advance
Jan
Comment #9
ronan CreditAttribution: ronan commentedYep, the module requires the mysql file ending to know what kind of file it is (it can also export tarballs of files and someday postgres dumps too).