Non-Redundant / Simplex Mode Deployment
| Include Page |
|---|
| Non-Redundant / Simplex Mode Deployment |
|---|
| Non-Redundant / Simplex Mode Deployment |
|---|
|
High Availability (HA) / Duplex Deployment
| Include Page |
|---|
| DAW:Deployment Architecture |
|---|
| DAW:Deployment Architecture |
|---|
|
Failover scenarios
| Failover Scenario | Behavior |
|---|
| 1 | When one of the VMs/nodes are down | The VIP will route the traffic to the secondary VM. All read/write operations will continue to work. |
| 2 | When both of the VMs are down | All read/write operations will fail and a manual intervention will be required. |
Out of Scope
- Component-Level Failover: Failover of individual components is not supported.
- Network-level failover support: The internal network/link between the VMs (or the Docker network) is assumed to be working all the time. DB Cluster:
Assumptions
- Both VMs must be on the same subnet. Otherwise, the failover won't work.
- Setting up the DB cluster for MS SQL Server lies under the Customer responsibility.
- Manual intervention will be required when both VMs are down.
Failover scenarios
...
