- Install B&M
- Configure backup directory to:
"Manual Backups Directory" "Server Directory" private://home/drupal/manual

Directory exists and is writable:
d130:/home/drupal # ls -l
drwxr-xr-x 2 wwwrun www 4096 2010-10-28 22:32 manual

Private directory setting at: admin/config/media/file-system
Path private file setting is empty.

The backup results:
Foutmelding
* Warning: is_dir(): Unable to find the wrapper "private" - did you forget to enable it when you configured PHP? in file_prepare_directory() (line 446 of /srv/www/htdocs/includes/file.inc).
* Warning: is_dir(): Unable to find the wrapper "private" - did you forget to enable it when you configured PHP? in file_prepare_directory() (line 446 of /srv/www/htdocs/includes/file.inc).
* Unable to create or write to the save directory 'private://home/drupal/manual'. Please check the file permissions that directory and try again.
* Could not run backup because the file could not be saved to the destination.

If I leave out the private:// extension in the Server directory:
Error message: Warning: rename(/tmp/backup_migrate_xsrvUp.mysql,): No such file or directory in backup_migrate_destination_files->save_file() (line 31 of /srv/www/htdocs/sites/all/modules/backup_migrate/includes/destinations.file.inc).

Status Default Database backed up successfully to TheSiteName-2010-10-28T23-05-13 in destination Manual Backups Directory in 455.06 ms.

The file exists, but has a '0' size:
d130:/home/drupal # ls -l /tmp/backup_migrate_xsrvUp*
-rw------- 1 wwwrun www 0 2010-10-28 23:05 /tmp/backup_migrate_xsrvUp

If I change to manual download mode, I get the backup downloaded so the actual back works.

Is this a B&M module bug, or a core Drupal bug?

Comments

jessesteele’s picture

jessesteele commented

I have the same problem with the same results.

It also doesn't send me an email, but it will download.

I am wondering if it is connected to several "undefined index" errors I get. Since I can't set a back-up file location of my own, I am wondering if this is some kind of file permission-write/access issue.

Does the Core need to allow the right files to be written to?

Here were some of the other errors I got that seem related enough to make me wonder if it's a core matter of allowing modules to modify the proper files and directories:

Notice: Undefined index: #title in template_preprocess_user_profile_item() (line 208 of /home/content/j/e/s/jessesteele/html/thepoint/modules/user/user.pages.inc).
Notice: Undefined index: #markup in template_preprocess_user_profile_item() (line 209 of /home/content/j/e/s/jessesteele/html/thepoint/modules/user/user.pages.inc).

Notice: Undefined index: name in _token_token_tree_format_row() (line 109 of /home/content/j/e/s/jessesteele/html/thepoint/modules/token/token.pages.inc).

[RE: Backup and Migrate email I was sent by the system after attempting a file-save backup on the server]
The site backup has failed with the following messages:
Site was taken offline.
Site was taken online.
Unable to create or write to the save directory 'private://backup_migrate/scheduled'. Please check the file permissions that directory and try again.
Could not run backup because the file could not be saved to the destination.

Notice: Undefined index: adaptivetheme in theme_update_report() (line 201 of /home/content/j/e/s/jessesteele/html/thepoint/modules/update/update.report.inc).

jochen wendebaum’s picture

jochen wendebaum commented

any news on this??

ronan’s picture

ronan commented
Status: Active » Fixed

You need to have created a private files directory for backup and migrate to save to the server. I have added a warning and disabled server backups if you don't have one set up. I don't love this solution so if anyone has ideas for a better user experience for this please let me know.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.