by Ken Task.
"It is strongly suggested that in the process of backup, in case it gets
stuck due to some reason, a indication be provided so that the
particular part may be excluded from the backup."
I agree ... but programmers will say that's kinda already done with the plans ... and stages of the plan ... to make the backup. Were there any log files larger than 0 bytes in moodledata/temp/backup/ ? Is so, what did they contain?
Could be that your timeouts need to be increases in PHP. Fact that it gets to the 90's % might mean you were close!
Did you turn on debugging to see what else moodle might be complaining about?
Quizzes are heavy processing ... rather than disabling ALL quizzes, how about say 1/3 of them included. It might be an issue with just one quiz!
In older versions of Moodle there used to be a health check tool that has now been removed in 4.2! ![sad]( "sad")
That health check used to find issues with Quizzes and provide suggested SQL solutions if it could.
'SoS', Ken