Thread Starter
wpprup
(@wppraesenz)
Hi Daniel,
I use tophoster, here in Germany.
Please don’t say Strato. Than i know the problem 😉
Thread Starter
wpprup
(@wppraesenz)
no, it isn´t…. but what now? 🙂
Something to change in the settings anywhere?
I use the plugin on many sites. BackWPup always slows very much down at about 80% compressing. The other website´s backup processes do not actually hang but the websites are very much smaller than the one which displays this chronic error. Perhaps this is the difference and the reason behind it?
I have got the same problem. And I am with Strato.
Daniel, you seem to know about problems with Strato, so, what would be the solution?
Sorry with Strato there isst a good solution. The Problem is, that you can there only create files with a MAximum of 64MB with PHP. That is not enoth for archives.
The never Version https://github.com/inpsyde/backwpup/releases/download/3.2.0-rc1/backwpup-3.2.0-rc1.zip will output a error message if that happends.
Ulf can you test it two. So that we can see if ther a error message two.
Ok, so as a solution for Strato and other limited hosters, I would have to try to use several backup jobs to keep the archive’s size under 64 MB?
Will test the new version at the weekend.
Ok, tried it just now:
FEHLER: Signal “SIGXFSZ” wurde an das Script geschickt!
Not sure, if that is what you were looking for.
SIGXFSZ is the hint that the limit is reached.
Thread Starter
wpprup
(@wppraesenz)
So, is there something I can tell my hoster to change in the settings? And if so, how is it called exactly? I am not a server expert…
Thanks.
