RDS Broker

hi

i have a questions:

with using dns round robin , broker. fault detection? everywhere best practices setting broker talks of using dns rr broker load balancing.

so if have 4 records rdsfarm (10.0.0.1 / 10.0.0.2 / 10.0.0.3 / 10.0.0.4)

if 10.0.0.1 down , client resolves 10.0.0.1, whether there 3 other clients , active broker........

how ha? or viable load balancing solution @ all?

rgs

hi,

first need decide how balance initial connection rd connection broker servers.  can done using different methods hardware load balancer, dns rr, nlb, etc.  once client makes initial connection rdcb redirect user rd session host server have existing connection or rdsh least load.  if rdsh server goes down, rd connection broker (after short time) detect , not redirect users down server.

if use dns rr balance initial connections need understand ramifications when rd connection broker server goes down.  normal behavior rd client try first ip address received dns server, , if not response try next address, etc.  how long process takes depends on tcp settings, network configuration/architecture, latency, rdp-tcp security layer setting, etc.

if servers , clients on same lan expect see delay in ballpark of 30 seconds connect if first rdcb server ip address returned via dns down, second rdcb server in list up.  delay vary.

for dns rr workable please consider ttl settings on rd deployment records (the fqdn points rdcb servers).  may want make them smaller amount of time, example, 10 minutes.  way if rdcb server goes down can delete failed server's record , clients stop attempting use bad server initial connections within 10 minutes.  not want make ttl short because may cause clients potentially retrieve bad server ip address second time while attempting connect.  example, if made ttl 15 seconds, client attempt connect bad server, when not response re-query dns (because ttl expired), potentially receiving same bad ip address again.

using dns rr load balancing initial connection not ideal, inexpensive , easy configure.  if know , understand limitations can decide if acceptable solution.  if know going take down rdcb server can delete record , wait ttl expire first.

second, did not mention sql server.  in order have ha rd connection broker configuration need sql server instance rdcb servers can use.  should have ha sql server configuration well.  if have ha sql server in environment should consider using since additional load rdms database should not much.

thanks.

-tp

Windows Server  >  Remote Desktop Services (Terminal Services)