We are trying to create a "lightweight" failover setup, consisting of a failover CD instance with the core + web database being replicated (Azure SQL failovergroup). Additionally, that means adding an Azure Traffic Manager infront of the two CDs. I call this a lightweight setup, since I just want the CD site to be available in case any outages in our primary Azure region.
What we tried
We tried to setup the two CD instances, lets call them:
as endpoints in the traffic manager (e.g. my.trafficmanager.net). We also added these two instances as valid hostnames in the Sitecore config.
Both endpoints appear with "online" status in the traffic manager.
I verified that the trafficmanager binding "my.trafficmanager.net" appears on both app service bindings in the Azure Portal.
Our website is a multi-site solution, with configuration like this: (for CD site)
<sites env:require="TestCD"> <site name="site1"> <patch:attribute name="targetHostName">tst-site1.contoso.com</patch:attribute> <patch:attribute name="hostName">tst-site1.contoso.com|north-europe.azurewebsites.net|west-europe.azurewebsites.net</patch:attribute> </site> <site name="site2"> <patch:attribute name="targetHostName">tst-site2.contoso.com</patch:attribute> <patch:attribute name="hostName">tst-site2.contoso.com</patch:attribute> </site> </sites>
When I browse the my.traffimanager.net, I expected to see my Sitecore application from either of the endpoints (depending on which the traffic manager selected). However, it seems that Sitecore always resolves to the scheduler site. Do I also need to add the trafficmanager (my.trafficmanager.net) as hostname for each Sitecore site or did I misconfigure something?