As the task is running in the background, it's difficult to see what's happening. The course I restored yesterday, finished with progress code 1000 in table mdl_backup_controllers, and it took 3:20 hours. I inspected the temporary backup folder and only an empty log file was there (with the backupid of the restore). We're investigating our network traffic at the moment, because our content scanner is having problems with the Moodle content (.mbz files and it's content). We focus on that issue first.
Alain Raap
Các bài đăng được tạo bởi Alain Raap
Hi Ken,
I found a record in the mdl_backup_controllers table referring to the restore process of the course. What I also see are two directories with the unpacked mbz file in the temporary backup folder of Moodle. I don't understand the process of a restore inside a course itself with a backup file from the Private back-upzone, is the backup transferred over the network to the webserver? How is the process working? It seems complicated to me
This restore process shouldn't take a lot of hours (even days), or am I wrong? The size of the backup is 111 MB, so this shouldn't be a problem.
I found a record in the mdl_backup_controllers table referring to the restore process of the course. What I also see are two directories with the unpacked mbz file in the temporary backup folder of Moodle. I don't understand the process of a restore inside a course itself with a backup file from the Private back-upzone, is the backup transferred over the network to the webserver? How is the process working? It seems complicated to me
This restore process shouldn't take a lot of hours (even days), or am I wrong? The size of the backup is 111 MB, so this shouldn't be a problem.
I can't see anything on the site itself, only the message that the restore process is running. Debugging is not possible, it's on our productie site.
We try to restore courses on the restore page on our site and it takes a lot of time (days) before the restore is finished. The course is restored in an existing course and I see a directory with the unpacked .mbz file on our server in the temporary backup folder, but how can I find out why this restore takes such a long time? Is there a table in the database where I can find and follow the status of the restore?
We are using Moodle 4.1.x and also files are scanned with a virusscanner in our network when files are uploaded via the network.
Moodle in English -> Backup and restore -> [4.4.2]Error on automated backup, core\task\course_backup_task,array_key_exists(): Argument #2 ($array) must be of type array, null given -> Re: [4.4.2]Error on automated backup, core\task\course_backup_task,array_key_exists(): Argument #2 ($array) must be of type array, null given
Bởi Alain Raap -
Hi Richard,
When I look in the tgz_packer.php file, it is the writing of a file to system :
$written += gzwrite($gz, $data);
Maybe a problem with your data storage that fails to write?
The class is handling this function:
* Utility class - handles all packing/unpacking of .tar.gz files.
When I look in the tgz_packer.php file, it is the writing of a file to system :
$written += gzwrite($gz, $data);
Maybe a problem with your data storage that fails to write?
The class is handling this function:
* Utility class - handles all packing/unpacking of .tar.gz files.