Visvanath Ratnaweera

Scraping 90+ GB from the Moodle application and packing that to a single file is something. Still a 8 vCPU, 32 GB RAM VM must be able to do that without maxing out - when it is idle. I would thoroughly investigate whether another party, or the system administrator of the host are involved. 2 am is a time when a machine should be idle. But if two people think the same, you know what happens. ;)

It could also explain why not everyday. It happens only when the two jobs overlap.

In fact, single thread processes don't max out the CPU, because waiting for the I/O system automatically throttle the process. My feeling.

To go deeper other than ask everybody who is involved, you need a good monitoring system which take a record, graphs, of many matrices in the machine. See for example How do you monitor your Moodle server? General information are in the forum documentation - Performance and Performance FAQ.

Home of the script that lives at get.docker.com and test.docker.com!

The purpose of the install script is for a convenience for quickly installing the latest Docker-CE releases on the supported linux distros. It is not recommended to depend on this script for deployment to production systems. For more thorough instructions for installing on the supported distros, see the install instructions.

This repository is solely maintained by Docker, Inc.
Usage:

From https://get.docker.com:

curl -fsSL https://get.docker.com -o get-docker.sh
sh get-docker.sh

From https://test.docker.com:

curl -fsSL https://test.docker.com -o test-docker.sh
sh test-docker.sh

From the source repo (This will install latest from the stable channel):

sh install.sh

Testing:

To verify that the install script works amongst the supported operating systems run:

make shellcheck

 

=== https://github.com/docker/docker-install?tab=readme-ov-file

 

Apparently this works for CentOS, Debian, Fedora, Raspberry Pi OS 32 bit, RHEL, SLES, Ubunty and "binaries" various combinations of architectures x86_64/amd64, arm64/aarch, arm 32 bit, ppc64le and S390!

 

Ref. https://docs.docker.com/engine/install/ 

I wasn't clear about the "virtual keyboards" or "soft keyboards" at the operating system level. Of course they are there. This is how one gets the "on-screen keyboard" as they call it on a Linux Mint with the Gnome-based Cinnamon Desktop: https://help.gnome.org/users/gnome-help/stable/keyboard-osk.html.en.

Trying to understand what you say:

a. You have a (good) backup of /var/lib/mysql and /etc/mysql
Those are enough to restore the database.

 

A SQL dump would have been easier, but I understand that you haven't taken a database dump.

b. What about moodledata/ directory, specifically moodledata/filedir/?

This had to be taken as you backed up the database in a).

c. What about the moodle code directory, usually just called moodle/?

Ideally backed up at the same time with a) and b). The code is not something changes continuously. So a backup from roughly the same time is good enough.

 

The whole story is documented in Site backup.

Once you have those three things, to restore the Moodle site follow Site restore.