RD Connection Broker Warm Standby Node
it's become necessary to implement rd connection broker in our environment. familiar article available on technet on setting rd connection broker on cluster (active/passive) however, moving away use of windows clustering practical , possible.
has used warm standby node (rdcb role service installed, service broker computer added, additional requirements met, etc.) in case there issue on node 1, node 2 can used? testing an approach where the rdcb has a dns alias configure rd hosts use rdcb server. so, in recovery scenario update dns alias of rd host farms point to. recovery time should minutes in case , confirm testing in pre-production environment.
additional information may impact responses includes follwoing: we use rd gateway, rd web (with sso) and rd hosts (multiple farms), highly available using hardware load balancer. not use virtual desktop resources in environment , have no plans in future so.
steven, here's i've tested far , appears work. consideration.
- setup rdcb role on 2 nodes xxxxrdcb1 & xxxxrdcb2
- add the 2 rdweb nodes xxxxrdweb1 & xxxxrdweb2 both rdcb nodes
- add the four rdsh farm nodes (2 per farm) for rdshfarm1 , rdshfarm2 session broker computers group on both rdcb nodes
- setup cname alias rdcb named xxxxrdcb, point xxxxrdcb1
- setup rdshfarm1 & rdshfarm2 servers to use rdcb xxxxrdcb (alias)
- configure rdweb use xxxxrdcb (alias) rdcb source
- test user access published application on both farms through rdweb sso. launch applications both farms.
- test 'failover' second rdcb node changing cname in dns point xxxxrdcb2, shut down xxxxrdcb1. let dns replication complete.
- test user access published application on both farms through rdweb sso. launch applications both farms.
Windows Server > Remote Desktop Services (Terminal Services)
Comments
Post a Comment