ADFS DR方法和解决方案 [英] ADFS DR Approach and Solution

查看:138
本文介绍了ADFS DR方法和解决方案的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

大家好,



我们正在努力将客户ADFS 2.0 infra升级到ADFS 3.0。以下是我们考虑升级方法的几点,但是客户对ADFS有DR要求我们已经提出了一些解决方案,但是我们需要建议,以便
我们可以拥有更强大的基础设施,而不会有太多的打嗝。


        




场景1. 使用全局负载平衡 主动 - 主动设置



a。)         所有服务器都添加到同一个服务器场中 

b。)         达拉斯 数据中心已关闭。

c。)         由于我们有全局负载平衡,请求将开始命中纽约服务器

d。)         外部和内部DNS无需更改 




场景2.使用本地负载均衡 主动 - 被动设置



a。)         在达拉斯创建了两个设置 这是生产,其中一个是纽约,因为DR¥b $ b b。)         达拉斯 下降了b $ b c。)         必须更改内部和外部DNS IP以在线启用被动设置

d。)         还需要在SQL级别进行一些更改......我认为这是



场景3.在两个站点都使用本地负载平衡所有服务器都添加到同一个服务器场 - 活动 



a。)添加到同一个服务器场的所有服务器 

b。)有新功能york NLB IP添加到公共DNS(请求在双方之间分配)

c。)达拉斯 降价 

d。)所有请求命中纽约

e。)必须检查SQL Replication并且它是否可以在不恢复SQL配置的情况下工作?



$ b b $ b场景4.如果我们可以有两个同名的农场并分别提供两个站点,则不确定。 



还有办法控制来自互联网的流量到哪个ADFS站点 - (ADFS代理-ADFS-AD = SQL)...我相信内部Active Directory站点和服务将负责。



建议使用SQL镜像或SQL Cluster。



(ADFS代理-ADFS-AD = SQL )b


(ADFS代理-ADFS-AD = SQL)



任何建议真的很有帮助

解决方案


大家好,



我们正在尝试将客户ADFS 2.0 infra升级到ADFS 3.0。以下是我们考虑升级方法的几点,但是客户对ADFS有DR要求我们已经提出了一些解决方案,但是我们需要建议,以便
我们可以拥有更强大的基础设施,而不会有太多的打嗝。


        




场景1. 使用全局负载平衡 主动 - 主动设置



a。)         所有服务器都添加到同一个服务器场中 

b。)         达拉斯 数据中心已关闭。

c。)         由于我们有全局负载平衡,请求将开始命中纽约服务器

d。)         外部和内部DNS无需更改 




场景2.使用本地负载均衡 主动 - 被动设置



a。)         在达拉斯创建了两个设置 这是生产,其中一个是纽约,因为DR¥b $ b b。)         达拉斯 下降了b $ b c。)         必须更改内部和外部DNS IP以在线启用被动设置

d。)         还需要在SQL级别进行一些更改......我认为这是



场景3.在两个站点都使用本地负载平衡所有服务器都添加到同一个服务器场 - 活动 



a。)添加到同一个服务器场的所有服务器 

b。)有新功能york NLB IP添加到公共DNS(请求在双方之间分配)

c。)达拉斯 降价 

d。)所有请求命中纽约

e。)必须检查SQL Replication并且它是否可以在不恢复SQL配置的情况下工作?



$ b b $ b场景4.如果我们可以有两个同名的农场并分别提供两个站点,则不确定。 



还有办法控制来自互联网的流量到哪个ADFS站点 - (ADFS代理-ADFS-AD = SQL)...我相信内部Active Directory站点和服务将负责。



建议使用SQL镜像或SQL Cluster。



(ADFS代理-ADFS-AD = SQL )b


(ADFS代理-ADFS-AD = SQL)



任何建议真的很有帮助



任何建议都非常有帮助



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

解决方案

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 helpful

Any suggestions would be really helpfull


这篇关于ADFS DR方法和解决方案的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆