Wow! Making me work to support! Images hard to read in some cases and to point out things in them can't copy text ... anyhoo!
Wonder what:
fgrep '$release' version.php looks at top level of core code.
uname -an
php -v
php -m
free -h
df -h
.log files in moodledata/temp/backup/ that are 0 byte size indicate successful.
.log files with any size are failures and show the stage of the backup plan ... 700,800,900,1000 ... normally 1000 is highest and indicates success ... and the log file should be zeroed out - ie, contains nothing!
The .log file with the larger red line next to it is the largest in size.
Might try watching that files size: ls -l nameoflogifle.log ... several times ... To see if there any change in size.
If there is none ... process is no longer working and the log file is evidence of that.
The long named directories are the directories being used to build the backups.
If a backup is successful, there should be a moodle_backup.xml file present which is the road map for contents in the course. There are other .xml files .. files.xml maps to files directory. A large questions.xml file indicates a lot of quizzes.
If there is no activity in the long named directories then they should be cleaned up as soon as your moodle figures out it failed ... there several task for cleaning up:
run from code/admin/cli/
php ./scheduled_task.php --execute="\block_recent_activity\task\cleanup"
php ./scheduled_task.php --execute="\editor_atto\task\autosave_cleanup_task"
php ./scheduled_task.php --execute="\logstore_standard\task\cleanup_task"
php ./scheduled_task.php --execute="\core\task\automated_backup_report_task"
php ./scheduled_task.php --execute="\core\task\backup_cleanup_task"
php ./scheduled_task.php --execute="\core\task\cache_cleanup_task"
php ./scheduled_task.php --execute="\core\task\context_cleanup_task"
php ./scheduled_task.php --execute="\core\task\file_temp_cleanup_task"
php ./scheduled_task.php --execute="\core\task\file_trash_cleanup_task"
php ./scheduled_task.php --execute="\core\task\session_cleanup_task"
php ./scheduled_task.php --execute="\core\task\task_lock_cleanup_task"
php ./scheduled_task.php --execute="\core\task\task_log_cleanup_task"
php ./scheduled_task.php --execute="\tool_recyclebin\task\cleanup_category_bin"
php ./scheduled_task.php --execute="\tool_recyclebin\task\cleanup_course_bin"
The running of cron from command line shows it errors on select id, category from (course) where id=? .... no id.
select id,category,fullname,shortname from mdl_course;
in admin/cli/ run:
php fix_course_sequence.php -c *
What does this query look like:
select id,fullname,shortname from mdl_course;
If one were to make a backup ... not copy ... of this one course, how large is the backup (.mbz file)?
There is a backup.php script in code/admin/cli/ that could use ... think I'd save the .mbz file to specified location.
Did you notice the cron run from command line looped 180 times on the adhoc_task ... and that reported 0 task!
So which table did you not truncate?
And finally, my turn for sharing images ... from a 4.4.1+ (Build: 20240802) and server where I tested a course copy ... difference probably is I waited on the copy screen until the status changed.
'SoS', Ken