[Plugin: BackWPup] Memory Exhausted

This is an interesting out of memory error. 256MB should be more than adequate for nearly any WordPress site…
However, the file size is too big for e-mail. Most SMTP services will limit mail to under 10MB (many are even more limited). But why it’s showing up as a server “out of memory” error is puzzling.
I am going to stick my neck out here and say even if you increased php memory limit to 400MB, the mail will still not get sent

So I just upgraded and am getting the exact same message. The “Jobs” panel only shows the log file. If I look at it through FTP the file was created and I can download it at least ??

alan

Im experiencing the same using the dropbox-option:

2012/08/22 10:40.27: [INFO]: BackWPup version 2.1.15, WordPress version 3.3.2 Copyright ? 2012 Daniel Hüsken
2012/08/22 10:40.27: [INFO]: BackWPup comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions.
2012/08/22 10:40.27: [INFO]: BackWPup job: 3. Filer; FILE
2012/08/22 10:40.27: [INFO]: BackWPup job started manualy
2012/08/22 10:40.27: [INFO]: PHP ver.: 5.3.14; cgi-fcgi; Linux
2012/08/22 10:40.27: [INFO]: MySQL ver.: 5.1.63-0+squeeze1
2012/08/22 10:40.27: [INFO]: curl ver.: 7.21.0; OpenSSL/0.9.8o
2012/08/22 10:40.27: [INFO]: Temp folder is:
2012/08/22 10:40.27: [INFO]: Backup file is:
2012/08/22 10:40.27: 1. try for make list of files to backup….
2012/08/22 10:40.45: 7502 files with 97.8 MB to backup
2012/08/22 10:40.45: 1. try to create backup zip (PclZip) archive…
2012/08/22 10:41.14: [ERROR]Allowed memory size of 83886080 bytes exhausted (tried to allocate 131072 bytes)
2012/08/22 10:41.14: 1. Script stop! Will started again now!
2012/08/22 10:41.14: 2. try to create backup zip (PclZip) archive…
2012/08/22 10:41.39: [ERROR]Allowed memory size of 83886080 bytes exhausted (tried to allocate 131072 bytes)
2012/08/22 10:41.39: 2. Script stop! Will started again now!
2012/08/22 10:41.39: 3. try to create backup zip (PclZip) archive…
2012/08/22 10:41.39: [ERROR]Allowed memory size of 83886080 bytes exhausted (tried to allocate 131072 bytes)
2012/08/22 10:41.39: 2. Script stop! Will started again now!
2012/08/22 10:41.39: 3. try to create backup zip (PclZip) archive…
2012/08/22 10:42.08: [ERROR]Allowed memory size of 83886080 bytes exhausted (tried to allocate 131072 bytes)
2012/08/22 10:42.08: 3. Script stop! Will started again now!
2012/08/22 10:42.08: [ERROR] Step arborted has too many trys!
2012/08/22 10:42.09: 1. Try to sending backup file to DropBox…
2012/08/22 10:42.10: Authed with DropBox from Mark Schiller
2012/08/22 10:42.10: 1.54 GB free on DropBox
2012/08/22 10:42.10: Upload to DropBox now started…
2012/08/22 10:42.45: Backup transferred to https:
2012/08/22 10:42.45: Job done in 138 sec.

SQL-backup works like a charm – but filebackup gives the error above …….

Any help would be highly appreciated ??

TIA

/Mark

[ERROR]Allowed memory size of 270532608 bytes exhausted (tried to allocate 125829120 bytes)

I had similar problem and here is how I fixed it.
First I thought, something was wrong with the backup-plugin so i tested other backup plugins but same php out of memory error. For example

“Database error MySQL server has gone away for query”

or

“Cannot allocate sufficient memory”

So I thought something wrong with php memory. Then some articles suggested to edit wordpress’s .db files or some other files in cpanel, to increase memory or time limit, but those tricks didnot work out.

Finally I came to know that one of the possible reason for memory error is, your mySQL file is too big (something like more than 200MB) That’s why memory runs out while doing things like backup. The culprits are following plugins-

You may be using one or both of following plugins
1. Better WordPress security
2. Akismet spam remover

both of them create ‘logfiles’ in your MYSQL file and over the time, because of them, the SQL file becomes very huge.
So, you’ve to goto phpmyadmin >> empty the tables that contain those logfiles.
Then try to take backup again and it’ll run smoothly.

In my case, Better WordPress Security alone had huge logfile of 480MB inside mysql. When I emptied the “wp_bwps_log”, the size of mysql file was reduced to barely 47MB (for 700 posts and 3000 comments on my site.)
And then I tried to take backup using “BackWPup” plugin and it worked smoothly without any problem.

That’s nice.

But the two example listed above are FILE only backups.

alan

@alanpae: backups sending by mal neds many php memory. i think i have found a solution but that will come with version 3.

@markschiller: please try to use a tar archive it not need so many memory on creation time.

The same error happens to me with a db and table backup on local filesystem.

I’ve tryed to use tar.gz archive instead of zip and the error disappear but…another strange thing:

in the backup window appear the backup file (with correct size) and also an index.php file.

Trying to download the backup file, the file is 0 byte (corrupted)

AnY idea?

TIA