I'm re-posting / updating my issue since I'm pretty sure it's a bug and it has not been addressed or solved here.

I'm running

Drupal core 6.17
Backup and Migrate 6.x-2.2
Backup and Migrate Files 6.x-1.x-dev (2010-Jul-11)

Both manual and scheduled DB backups work fine.

Neither Manual nor scheduled file back ups work at all.
If I have a file backup profile scheduled then my cron runs fail.

I believe I have PEAR and Archive installed correctly.

> which pear gives me /usr/local/bin/pear on my host

I have Tar.php uploaded to ./sites/all/modules/backup_migrate_files/includes/

Also, if I try to run a manual file back up I notice that Backup Migrate creates a tar file in my tmp directory, e.g. ./sites/default/files/tmp/backup_migrate_4c59c7cab443b.tar

The Tar file grows to about 325Mbytes but then I get a 500 Internal Server Error or a white screen.

I'm assuming that since I'm getting a temporary tar file that Tar.php is working OK and maybe the problem is when the file is getting handed off to gzip.

However I've tried with zip and no compression and still have the same problem.

Please can someone get backup migrate files working again?

It used to work just fine until a previous upgrade of BM and BMF

Comments

butler360’s picture

butler360 CreditAttribution: butler360 commented

Have you tried Backup and Migrate 6.x-2.x-dev?

riversidekid’s picture

riversidekid CreditAttribution: riversidekid commented

Seems I have the 'same' issue, except I don't get the WSOD, I get my normal "Page not found" error. The logs show 500.shtml Internal Server Error. I'm about to try 6.x-2.x-dev. ;)

I wanted to add that I performed a full files backup, then uploaded (image import) 8300 pictures, and the files backup after the import did not work. I know it's got a good bit more to do, but time out??? ouch.

riversidekid’s picture

riversidekid CreditAttribution: riversidekid commented

6.x-2.x-dev did not help :( The backup gets to about 700 MB and then records a 500.shtml and the user gets a 404 page. I have seen the WSOD a couple of times, but usually I get the 404 page.

I am on shared hosting so I can't change the timeout settings to 'never expire'.

Oh, I'm running
Drupal 6.19
Backup and Migrate 6.x-2.x-dev (2010-Sep-13)
Backup and Migrate Files 6.x-1.x-dev (2010-Jul-11)

riversidekid’s picture

riversidekid CreditAttribution: riversidekid commented

After applying "Backup and Migrate 6.x-2.x-dev (2010-Sep-13)" my cron jobs stopped working. Via Drupal I got "Cron Failed." and via my Drupal reports I saw that cron attempted to run while a prior cron job was still running. (I had it set to run one each hour.) Via my host's cron email notification I saw this error: "Cache-Control: store, no-cache, must-revalidate"

Reapplying "Backup and Migrate 6.x-2.2" solved the problem immediately.

riversidekid’s picture

riversidekid CreditAttribution: riversidekid commented

After Backup-Migrate 6.x-2.3 was released the other day I performed a full uninstall of both Backup-Migrate and Backup-Migrate-Files and installed both fresh. Backup-Migrate is working fine, both scheduled and manual, but Backup-Migrate-Files still errors with the 500.shtml in the recent hits and in it's own error log I see: (I wish I had found the log file before I deleted the folders!)

"[22-Oct-2010 03:38:40] PHP Warning: require_once(./sites/all/modules/cck/theme/theme.inc) [function.require-once]: failed to open stream: No such file or directory in /home/example/public_html/sites/all/modules/cck/content.module on line 177

[22-Oct-2010 03:38:40] PHP Fatal error: require_once() [function.require]: Failed opening required './sites/all/modules/cck/theme/theme.inc' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/example/public_html/sites/all/modules/cck/content.module on line 177"

I am using a different theme than Garland, I'm using the Twilight theme. Could it be that this theme isn't compatible?

ronan’s picture

ronan CreditAttribution: ronan commented
Status: Active » Postponed (maintainer needs more info)

Sounds like either a memory error or a timeout. Your files directory may be just too large to backup via the web. You may want to look at an offline solution if you can't up your timeout or memory any more.