Ok, that is probably the most reported issue here on this forum.
The iTSec plugin backup code definately has some room for optimization.
It stores the entire backup in memory before writing it to a file …
Luckily there are other solutions (that by the way do not always work).
There is an end to increasing the PHP memory limit …
I think it would be fair to say that increasing the PHP memory limit is just a way to postpone the issue …
Introducing a paging algorithm to the iTSec plugin Database Backup feature would be a more robust solution.
As it seems you have been able to identify the cause of this issue please mark this topic as ‘resolved’.
dwinden