"WARNING: Job restart due to inactivity for more than 5 minutes."

whatever I try, I always get the Inactivity-Warning when doing my backups. I already splitted up my backups in several parts. But I have a very old blog with just a lot of entries and images. (the wp-content-Folder is 470MB large).

Can you please help me, solving that problem?

I could easily post any logs here, but I think, you do have enough logs like mine.

Memory seems not to be the problem (see the following timeline). Maybe some timeouts? Maybe false memory-calculations?

Here is some kind of a timeline, what follows:

(1) Backup starts without any problems.
(2) Really fast, I get the following line within the console-ouput of the backup-plugin: “Komprimiere Dateien als Tar. Bitte habe einen Moment Geduld.” … in English something link: “Compressing files as tar. Please be patient.” …
(3) Parallel to the Compression, I get a folder under …/wp-content/uploads/backwpup-*****-temp (the stars indicate the unique identifier). In that folder, I do have a tar-file, which is 223 MB large (and rising).
(4) I first get the following linke within the console-output of the backup-plugin: “[05-Jan-2014 19:00:37] WARNUNG: Auftrag durch Inaktivität von mehr als 5 Minuten neu gestartet” … in English something like: “Warning: Job restart due to inactivity for more than 5 Minutes.”
(5) The size of the tar-file within the temp-Folder is still rising, now exceeding the above mentioned 256 MB. 429 MB large (and rising)
(6) I now get the following message within the console-output of the backup-plugin: “2. Versuche, Backup zu erstellen …” … in English: “Trying to make a backup for the 2nd time”.
(7) The size of the tar-file within the temp-Folder is still rising, now exceeding 531 MB large (and rising)
(8) I now get the following message within the console-output of the backup-plugin: “3. Versuche, Backup zu erstellen …” … in English: “Trying to make a backup for the 3rd time”.
(9) The size of the tar-file within the temp-Folder is still rising, now exceeding 634 MB large (and rising). It is now rising very incremental. Everytime I go on “reload” the size increases a bit. This has not been during the other stages mentioned above.
(10) I now get the following message within the console-output of the backup-plugin: “4. Versuche, Backup zu erstellen …” … in English: “Trying to make a backup for the 4th time”.
(11) … I get the following message: “Backup wurde erstellt.” … “backup created”.
(12) … now, the plugin tries to upload the file (666.2 MB on my FTP, 635,37 MB stated in the console log) to the dropbox, previously connected.
(13) within the console of the plugin, I get the statement: “11386 Dateien mit 631,86 MB in Archiven.” … 631,86 MB … third statement to the size of my archive. And none of them fits to the other.
(14) within the console of the plugin, I get the statement, that the upload just started.

(16) Whatever the following statement means, I get it in the console of the plugin:(400) False offset will corrected
(17) After a very long time, I just get the following statement in the console of the plugin:

I do have 100 GB at my Dropbox-Account. so memory may not be the problem at all. Now my Dropbox syncs with my local laptop. So the tar-file may find its way. But nevertheless, I got the timout-warning 8 times. And I got a strange error-message in addition to that.

If your folder/files is 470mb the compressed version should not be 600+. I have seen that the new version (3.1.1) has changed the backup location and is therefore backing up all the old saved backups. You may want to look into that and make sure you are not including all your old backups. The new location is in the wp-content/uploads. In my case the old location was /wp-content/backwpup-backups and since that was not the current location was not being excluded.

Also maybe split up your files and database to separate backups (two separate jobs) could help as well.

I just checked the mentioned issues (1. backing up backups and 2. folder-change) before. Both issues are no reason for the problems. I posted only sizes of the compressed files. So I have never mentioned any differences between compressed and uncompressed files. … This might not be the problem, too.

And I already splitted up the backups. My database is 22 MB large. The rest is the content. …

Hello!
Thank you Daniel for the response. I used to have the same 5 min inactivity issue but after I set a value of 30 in the max script execution time as you said, it seems to have done the trick and now the jobs are done. However the logs have these [STRICT NOTICE: is_a(): Deprecated. Please use the instanceof operator.]….. which I don’t know I should be worried about?