Support » Plugins » WP-db-backup creates file, but no email is sent

  • Resolved galbaras


    After updating the plugin (twice) in the past couple of weeks, two of my blogs have stopped sending me the backup email. I’ve just checked their backup directories and backups were created, one was even compressed, but they weren’t sent.

    I’m using the WP Mail Queue plugin, if it makes any difference, but only on one of these blogs and it doesn’t explain why some backups aren’t even compressed.

Viewing 15 replies - 1 through 15 (of 19 total)
  • How big are the uncompressed backup files? If they’re huge it might be that your server times out before it can complete the compression.

    I’m not familiar with the WP Mail Queue plugin, but I wouldn’t be surprised if it caused the backup emails not to be sent.

    I’m having a similar problem in that it appears that the files are being created, but no email is being sent.

    I’m not using any mail-related plugins.

    At least, I think those are the right files. They’re .sql files that end in the date, then an underscore, then 3 more digits. The files are each ~ 19,600KB.

    Any ideas?

    19MB is pretty big for an attachment. I wouldn’t be surprised if your host’s email server was rejecting them. You should contact your host and ask if there’s a maximum allowed size in sent emails.

    Hi Austin. Thanks for such a speedy reply. 🙂

    I’m on a “dedicated virtual” server with Media Temple. According to their knowledge base, there’s no limitation on email size for DV users.

    Can you check the web server logs, then, and see if there are any error messages?

    Sorry, took a bit to figure out how/where to do that. 🙂

    I have this error message: PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 20115289 bytes) in /var/www/vhosts/ on line 1025, referer:

    Admittedly, I don’t really know what that means or what to do about it. I’m guessing it means you’re right re: email size. But is there any option at that point other than doing backups manually all the time?

    Your PHP memory size of ~33MB is really low for WordPress. I’m surprised you haven’t run into other problems. I would set that no lower than 128MB. Normally, you would do this by setting the line memory_limit = 128MB in php.ini, but I don’t know if there’s a control panel way of doing that for your virtual server.

    Looking around, I guess a number of people recommend 64MB for WP, but I would go higher if your system has the resources. 64MB might be sufficient for solving this issue, though. Basically the problem is that the server is trying to read that file into memory so it can make a gzipped version, and 19MB takes up the majority of the allotted 32MB, which is being used elsewhere.

    Sorry, took me a while again to figure out exactly what to do to set the memory limit higher.

    But…it worked! Thank you for your help. 😀



    I have the same problem – even when I manually do a backup, it will not sent to my email, though it says it has. I have unlimited memory limit allotment so not sure what to do now.

    mardi, if you say “unlimited memory” I think you must mean disk space, not server memory. PHP memory must be limited to something; your host should know what that number is.



    Thank you – I had my web person change the memory allocation and doubled it from 64 to 128. Backup worked!

    I think there is a way to compress files in chunks, see my post here:

    I use 64M on all my blogs, yet some of them fail (granted, it’s only the biggest one now) and most don’t.

    When gzipping manually, there’s no problem and the compressed file is fine.

    Do I also need to change the setting in wp-config.php?

    So now I’m on 128M and the scheduled backup worked OK. Maybe that’s what it was. Another blog that’s still on 64M produced nothing, although it updated its schedule.

    Austin, what about improving the logging of errors?

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘WP-db-backup creates file, but no email is sent’ is closed to new replies.