Possible scenarios for availability zones in Azure which work? We are wanting redundancy and HA between the servers if possible. :
1) A scale set configured with more than one availability zone configured (ie zone 1, zone 2, zone 3) However when I go to provision SQL there is only one option to choose a availability zone (ie zone 1). I cannot choose two avail zones for SQL. Noticed I can choose a standard sku LB which allows for redundancy,... can we control which avail zone is migrated to if the datacenter is destroyed? We want the scale sets and SQL to be in the same avail zone.
2) Can we configure two IaaS behind a LB (same availability set) with each IaaS configured for a different availability zone? For example, IaaS A(avail zone 1); IaaS B(avail zone 2); IaaS A and IaaS B are in avail set 3 ?-- is this possible to have a availability set span two different avail zones (1 and 2).
3) What happens if scale set is configured for default avail zone ( no avail zones chosen)?
4) What happens if we use a API instead of LB in option 2 above?
5) Also we want a entire system (IaaS A w avail set 3; IaaS B w avail set 3; SQL AG w/ 2 replicas,1 internal LB, avail set 4 all to migrate together to the same availability zone. How would we do this?,... can we configure all IaaS to move to the same regional zone in case the original regional zone is destroyed? Is it possible to have a LB migrate between availability zones?
dsk