On Fri, Mar 22, 2013 at 12:56 PM, Ken Cornetet <[email protected]> wrote: > We used to have that sort of mentality, but I've found over the years that, > in general, HA options tend to create more down time than they are designed > to eliminate. Personally, I'd recommend just doing an occasional clone of > your web server and broker (they don't have any critical volatile > information), which you probably want to do anyway for DR purposes.
OK, I will put that to my boss. I seriously doubt he will agree to it, and I will have to try for HA on the connection broker / web access. I am guessing that each component should be isolated - by which I mean, the session host should *only* be the session host, and not also the web access or connection broker. So I would want, at minimum, 1 connection broker, 1 web access, and multiple session hosts. I imagine I can remove the connection broker and web access from the session host without issue, as long as I have added a broker and web access server ahead of time? More - should I? I have added a 2nd Win2012 server, and added it as a web access server, so now it shows 2 - the web access server, and the original server which is also the session host and connection broker. And if I can remove the broker and web access from the session host, where do I connect to - do I put the web URL of the web access server into a client web browser, or do I put the web URL of the broker server in the client web browser? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
