Hello,
I can’t create a backup of the course — neither through the website nor via the console.
How can I complete the backup in the end?
moodle 4.5.5.
This happened after 2 hours... incredibly long.
Please delete the topic.
Please delete the topic.
So back was successful? Uhhh ... postings aren't deleted.
Did you fix your issues with the .so's not loading?
If your site isn't large, php's opcache would be ok - don't need those .so's.
Was the course backup .mbz file large?
For large courses I've had to put a 'no hang up' wrapper on the command line backup.
nohup php commandto backup &
That puts the command into a background process in shell and starts a nohup.out log at location where command was issued.
Came in handy once with a course that was 130Gig plus! :|
'SoS', Ken
I created a course backup.
The process ended up completing after two hours.
The website backup was only 85 MB in .mbz format. Suspicious.
Your method is truly worth considering. Thank you!
"85 MB in .mbz format" is a fairly large course and would take time to backup ... not sure about 2 hours though ... and that was via GUI or command line? I have a few courses around that size and it takes minutes via command line with no wrapper and via a weekly cron job that points to a bash shell script which uses just the admin/cli/ php backup.php script with a destination outside of moodledata.
And again, I'll mention that acpu and memcache are old - server errors said server could find the .so files for those. You do need to check admin config of your moodle to make sure those are not set to be active. And if you think you site needs caching, OpCache might be all that's needed. If you do need more/better caching, the recommendation is Redis.
'SoS, Ken