This topic explains automatic failover in the Episerver DXC Service. Automatic failover lets customers with business critical websites maintain high availability in the event of an outage in an infrastructure component in a datacenter, or even an entire datacenter region. Failover is an optional component which you can add to your DXC Service instance.
Failover prevents websites from going down in the event of a server failure. Through automatic detection, an error on a primary server is detected, and traffic is automatically routed to a backup server in a secondary geographically redundant location within the same delivery region.
Failover in DXC Service is fully automatic, with no manual intervention. Geo-replication is included by default, meaning that in case of a datacenter outage, traffic is sent to a backup server in a different location, providing redundancy across geographical regions.
The setup includes two application environments, where storage is replicated from the primary to the secondary (failover) environment. Episerver ensures that the failover web app is always in the same state as the primary one.
The web app endpoints are continuously checked for responses. If one of them stops responding, traffic is moved over to the secondary web app. When the primary web app is working again, traffic is directed back again. You can display a message informing that the site is in read-only mode.
DXC Service includes built-in endpoint monitoring and automatic endpoint failover. To use failover, you need to update the websites configuration to either handle all hosts (*), and/or add the failovers hostname. This is done in the Episerver Admin view. See example below.
Note: When the site is in failover state, the used storage will be read-only.
Last updated: Oct 03, 2017