by Ken Task.
Scheduled reboot daily?!!!! Uhhh ... Errr ... GRRRRR!!! ... that kinda reminds me of NT 4.0 days, when about the only way to solve issues was to reboot! Image may be NSFW.
Clik here to view. That's somewhat hard on DB as well as server, I would think - Virtual or not. Is it Windows?
About an all-in-one-box ... depends ... Percona folks (well known for their MySQL expertise) say (in blogs I've read) that it's 'best' if the DB server can use about 80% of the memory of the machine ... ie, no swap space. IF ... notice I said IF ... one were able to reach that on an all in one box, then that takes away from Apache (if running workers) and other operating system processes that must run. Matter of fact, MySQLtuner will report the total memory the config of MySQL could consume and it's possible to have MySQL configured so that it would try to use more memory than the box has ... bad news ... swap space.
So if one has a large site and it's used like a K12 entity would use in a 1-1 or BYOD situation, it might be best to have a dedicated DB server. If a corp/college/Higher Ed, where the users are NEVER brought into a training with an instructor in a F-2-F situation (in other words, Moodle is used in a true asynchronous situation), then one could get away with an all-in-one although it would be wise to make sure one has at least 8 Gig ... that seems to be a 'sweet spot' on servers with which I've had experience. One exception to that ... Staff Development - might be F-2-F and Moodle used - but, have noticed that K12 entities, as an example, can use their F-2-F SD time for other things and provide supplemental/culminating, etc. types of things with Moodle ... which means entire staff isn't hitting server at the same time (but traffic is higher than normal).
Bottom line ... you have to know how your Moodle is used!
Sooooo ... does that offer some food for though? ;)
'spirit of sharing', Ken