The deployment model illustrated below can be implemented to ensure both High Availability and Disaster Recovery. This configuration requires a good network connectivity between the datacenters, which are located in different geographical areas.
The model can also be implemented on premises. For cloud deployment, you need to pick different regions for the primary and secondary locations.
Both Orchestrator nodes are active and the Load Balancer directs traffic to them in a Round Robin algorithm.
In order to provide High Availability for the Network Load Balancer (if the NLB machine is located in the Primary Datacenter), a secondary NLB can be provided in the Disaster Recovery Datacenter. The two NLBs need to be placed in a Primary-Secondary (or Master-Slave) configuration. The same NLB can be used, with different interfaces (VIPs), to optimally distribute loads to Orchestrator and Elasticsearch nodes.
The Always On Availability Group feature can be composed of minimum 2 machines:
- Primary DB in the first data center;
- Secondary DB in the second datacenter.
Minimum three nodes are required for Elasticsearch - two of them are placed in the first data center and the third one in the second data center.
If the Always On Availability Group feature is not an option, then the classical Windows Failover Cluster with one Active node, one Passive node and External Storage for database files, can be used.
|About Physical Deployment|
|Web Server on a Single Machine|
|Deployment in the Cloud|
|Disaster Recovery - Active/Passive|