timecheck00

Thank you. I appreciate the informed reply. I rather naively just installed w3 total cache based on someone’s recommendation that a cache manager would help my performance. Didn’t do any research other than number of stars. Now I see that in your installation notes and FAQs you do have a warning:

Optional:?On the “Database Cache” tab, the recommended settings are preset. If using a shared hosting account use the “disk” method with caution, the response time of the disk may not be fast enough, so this option is disabled by default. Try object caching instead for shared hosting.

I suggest modifying it as follows:

Optional:?On the “Database Cache” tab, the recommended settings are preset. If using a shared hosting account use the “disk” method with caution, the response time of the disk may not be fast enough and it will generate 1000s of files, possibly maxing our your allowed file limit so this option is disabled by default. Try object caching instead for shared hosting.

I found that my problem was due to w3 total cache almost by chance. The problem I had for several months was that UpdraftPlus would very rarely finish a backup. It would stop with various errors, or no errors. It turns out that when the file limit is hit, Godaddy doesn’t give an error, just whatever process was trying to write a file fails. We thought it was Cron failures, etc.

However, I found from the cpanel that the file limit had been hit, and at that time talking with support on how to find what was generating so many files, that their level 2 support said w3 total cache could generate many files. Then I found all the cached files, deinstalled the plugin and deleted all the cache files and got back to normal operations.

At this point I am just happy to be able to run backups and am not going to think about caching for awhile.

I just had a similar issue, and Bryle recommended that I go to settings – advanced and change the size limit from 400 to 100. That worked.

I first deleted all updraftplus files that I could find. There were a number left over from failed backups.

Then I changed the split size to 100MB, and that did work.

Thank you very much!