Hello Moodle folk,
Firstly, I have been following this site for a few months extracting all the finer detail and building an environment that is a little different and where 1 or more threads don't quite give me the full confidence as this is more based on a LAMP model. So thankyou for all the snippets of information.
- 38 Disparate Sites
- 4000 Computers
- Windows Server Failover Clusters (WSFC) at each site in 2 Node Mirror
- Central Higher Bandwidth Site with 3 Node WSFC
- All different Subnets
- ALL SITES OPERATE RETROSPECTIVLY WETHER WAN LINK IS UP OR NOT * This is a must for continuance of training*
I have engineered successfully a single site (SITE TEMP) to have a full working access point for Moodle courseware to all the other 38 Sites. The network isn't by any means to latent and was done at a remote site so the Moodle administrator can add all the courses and look/feel etc locally.
So this consists of (Baring in mind it was just for development);
- Windows Server 2016 VM hosting;
The bigger plan is to have the ability to incorporate it into the 'Top Level' WSFC for high Availability and co-ordinate the \MoodleData folder over the network using DFS-R.
SQL VM's Split over 3 NODES within the cluster using Always ON Availability Groups (AG) *Standard Licencing*
IIS Application Request Routing (ARR) for Network Load Balancing (NLB) for the moodle wwwroot.
HAVE THE ABILITY TO ACCESS THE CONTENT LOCALLY USING NLB DIRECTED BY IIS SERVER OR IN THE EVENT OF TOP LEVEL SWITCH OR WAN LINK FALIURE AT ANY SITE.
I have like hundreds of ideas and plans in my head/on paper and trying to find common ground with them is haunting me as its all in the detail. A detail where Moodle is off topic for me as I have worked with Microsoft technologies for years.
Essentially I would like to know the best way to accomplish the Moodle aspect with regards to clustering, HA, offsite local replication and database responses for how Moodle would behave.
This is a fully enclosed domain with no external connectivity to the Internet. It operates within the confines of an Intranet.
I hope this was informative and all support is welcome.