Hi All,
We are trying to upgrade our customer ADFS 2.0 infra to ADFS 3.0 . Below are few points which we have considered for upgrade approach however customer has DR requirement for ADFS for which we have suggested few solutions however we want suggestions so that we can have more robust infra without much hiccups.
Scenario 1. With Global Load Balancing Active – Active setup
a.) All servers added to same one farm
b.) Dallas Datacenter is down.
c.) As we have Global Load Balancing, request will start hitting New york server
d.) No change required on External and Internal DNS
Scenario 2. With local Load Balancing Active – Passive setup
a.) Two setups are created one in Dallas which is Production and one is New york as DR
b.) Dallas goes down
c.) Both Internal and External DNS IP have to be changed to bring Passive setup online
d.) Would require some changes at SQL level also ... I think
Scenario 3. With local load balancing at both sites with all servers added to same farm Active - Active
a.) All servers added to same farm
b.) Have New york NLB IP added to Public DNS (Requests are distributed among both the sides)
c.) Dallas goes down
d.) All request hits New york
e.) Have to check on SQL Replication and will it work without restoring SQL configuration ?
Scenario 4. Not sure about this if we can have two farms with same name and serve two sites separately.
Also is there way to control traffic from Internet going to which ADFS site - (ADFS Proxy-ADFS-AD=SQL) ...I believe Internal Active Directory Sites and Service will take care of.
SQL Mirroring would be recommended or SQL Cluster .
(ADFS Proxy-ADFS-AD=SQL)
(ADFS Proxy-ADFS-AD=SQL)
Any suggestions would be really helpfull