I'm getting the following message wikt the latest dev (Jun 3) release. I got it with the previous dev release too. Prior to that all has been working for several months.

warning: fopen(/home/xxxxxx/public_html/tmp/backup_migrate_4a2675a3ecfc9.mysql) [function.fopen]: failed to open stream: No such file or directory in /home/xxxxxx/public_html/sites/all/modules/backup_migrate/includes/filters.compression.inc on line 110.

The database is set, in a profile, to be GZipped.

I went through the "Advanced Backup" option and after turning compression off I got the following message

Profile setting saved: Normal 
Site backed up successfully. 
Database backup file BackupFileName-2009-06-03T14-36-09 saved to destination Manual Backups Directory.

warning: rename(/home/xxxxx/public_html/tmp/backup_migrate_4a267c49ea1d8.mysql,sites/default/files/backup_migrate/manual/BackupFileName-2009-06-03T14-36-09.mysql) [function.rename]: No such file or directory in /home/xxxxx/public_html/sites/all/modules/backup_migrate/includes/destinations.file.inc on line 30.

Upon checking destination Manual Backups Directory the backed up file was NOT there.

Checking the automatic backups which happen hourly confirms that no backups are being saved.

Earlier I also had the problem reported in http://drupal.org/node/479224 - Call to undefined function _backup_migrate_temp_files_delete() - but that seems to have been fixed.

Ade Atobatele

Comments

ronan’s picture

ronan commented

Hmm... very strange. It appears that the temporary file is getting garbage collected before being moved to the backup folder. I'll look through my changes and see if there's anything that may be causing this. Thanks for the detailed report.

Is anyone else having this problem?

Nigeria’s picture

Nigeria commented

Just updated with the latest dev,

now in addition I'm getting to the previous messages I'm getting in Apache error logs

[Sat Jun 06 09:37:35 2009] [error] [client xxx.xxx.xxx.xxx] PHP Fatal error: require_once() [function.require]: Failed opening required './sites/all/modules/backup_migrate/includes/files.inc' (include_path='.:/usr/share/pear:/usr/share/php') in /home/xxxxxx/public_html/sites/all/modules/backup_migrate/backup_migrate.module on line 921, referer: http://mysite.com/admin/content/backup_migrate

btw the file 'files.inc.' does exist in the sites/all/modules/backup_migrate/includes directory

netlite’s picture

netlite commented

I have this problem too.

I change the permissions in the directory "tmp" to 755 and try backup with the advanced option admin/content/backup_migrate/export/advanced

I only backup with the advanced option

teebo’s picture

teebo commented

I am also having the same errors.
No backup available whether I use the option to Download the backup or to save the backup to a directory.

bobmarchman’s picture

bobmarchman commented

To add #3’s comment:

If you are using MAMP or MAMP Pro for local development but experience issues when you migrate to a staging or production server, check admin/settings/file-system and be sure the path to your tmp directory is correct for the server the site is being hosted on. By default, MAMP uses its own tmp directory (usually located at /Applications/MAMP/tmp/php).

I was getting the errors mentioned above when I realized I had probably forgotten to check that path on the production site. Once Drupal could find my server’s tmp directory, I was able to restore again. One more thing I believe I will script Drush to handle for me when I migrate sites.

I imagine a lot of issues for this module spawn from either 1) erroneous or absent file system settings or 2) incorrect file permissions. I have been using this module since it’s earliest 5.x days, and every issue I can remember having with it I can trace back to one of those two possibilities.

Love this module. Great work.

Nigeria’s picture

Nigeria commented

The lastest dev release has sorted the original problem but introduced another:

[Tue Jul 07 12:12:59 2009] [error] [client xxx.xxx.xxx.xxx] PHP Fatal error: Cannot use object of type backup_migrate_profile as array in /home/xxxxxx/public_html/sites/all/modules/backup_migrate/includes/filters.statusnotify.inc on line 70

The effect of this is that the database is backed up EVERY cron run, which in our case is every 5 minutes.

ronan’s picture

ronan commented
Status: Active » Fixed

Glad the original problem got fixed. I've pushed a fix for the fatal error you found.

Thanks
Ronan

Status: Fixed » Closed (fixed)

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