+1 to Emma's response ... but a question or two ... Was the restore attempt done during prime time use of server? Do you have command line access to your server? The second question suggestion ... such a large backup file will take time and the GUI method will take longer. CLI restore of course depends upon being able to see the .mbz file - knowing the path to the .mbz file. So third question .... are backups made of courses to a designated directory or 2 the sea of files in moodledata/filedir/? Best, me thinks, to a designated directory so one can see the size of the file etc. If designated directory, one could put the restore script in a nohup (no hang up wrapper) which puts the restore process in the background outside of the GUI. Example: nohup php ./restore.php blah & [ENTER] That begins a log file (nohup.out) at location of where command issued and then allows one to exit the shell. One can come back later to see the progress by viewing the nohup.out log file. Have been able to restore courses as large as 130G that way. A couple of things to investiate ... disk speed and health of DB as both of those would be involved in a restore. 'SoS', Ken
von Ken Task.