When creating a new "File Directory", BAM let me create one using the URL of a remote file storage (for instance s3://
). However, this does not work as source. Trying to create a backup result in the following error messages:
- Directory does not exist.
- No files available.
- Could not complete the backup.
This is caused by the usage of drupal_realpath()
in backup_migrate_destination_filesource
. Real path only make sense for local filesystems.
BAM should either prevent creation of a "File Directory" source usign a remote file storage (on validation, if drupal_realpath()
returns FALSE. Or add support for remote file storage in backup_migrate_destination_filesource
. IMHO, support for remote file storage is probably best be left to additional module.
Comments
Comment #2
pbuyle CreditAttribution: pbuyle at Floe design + technologies commentedA quick test shows that
Archive_Tar::addModify()
used inbackup_migrate_destination_filesource::_backup_to_file_php()
supports remote file storage (tested with the Amazon S3 module stream wrapper).Comment #3
pbuyle CreditAttribution: pbuyle at Floe design + technologies commentedHere is a class that implements a working remote file storage source. I'm posting this since I'm note sure I will have time to continue working on this.
Notes
Comment #4
pbuyle CreditAttribution: pbuyle at Floe design + technologies commentedI finally adopted an alternative approach, creating backup of only managed files, it is available as a separated module: Backup and Migrate - Managed Files Source. Please note that the BAM issue is still relevant. Use should be prevented from creating a "File Directory" for a remote wrapper location, or support for remote file wrapper should be added.
Comment #5
couturier CreditAttribution: couturier as a volunteer commentedSounds like you found a manual work-around. Please be aware that most of the new development work is taking place now in the 8.x branch.