Irrespective of PHP upload/download limit and compression settings, a medium to large db size (~20MB or greater) seems to cause BM to begin dumping the db to /temp every 10 minutes, until disk space is filled.

This may be caused by another factor; not fully tested.

BM also seems to pass the write through the apache daemon process, resulting in very high load to server-- 100% of one of our 2G processors, in this case, which is highly likely to *at least* slog, if not hang many servers for the duration of 3-5 minutes. (Spawning a mysqldump or such would seem a better method.)

Thanks!

Comments

ronan’s picture

ronan commented

Are you running cron every 10 minutes? It sounds like an issue which cropped up before but should be solved in the most recent versions (which should be deleting temp files from failed attempts more consistently). If this is still happening, I'd really like to fix this ASAP. Any help you can give me to reproduce it would be much appreciated.

As for running through apache, the module is designed to run in any environment under the assumption that if you have permission to run mysqldump on your server then you would probably just do that and have no need for the module. It's certainly not the most efficient way to perform a db backup but it is universally deployable.

1kenthomas’s picture

1kenthomas commented
Status: Active » Closed (fixed)

I'm going to close this; didn't see your reply in time to test, and don't have a good reason to go back and try to duplicate-- doesn't look like too many people are affected.

As for mysqldump, that seems like an unnecessary assumption. Why not check for its presence, and use it if possible?