1 of 1 people found this helpful
If there is no any issue with load balancing and Network bandwidth, you may direct all clients from ATL to NYC, but in this case if your ePo goes down both NYC and ATL will not be updated by ePo, In your current senairo, apart from load balancing and Network babdwidth impact one important thing is that, your AH is a backup for your ATL.If server goes down, AH will be serving to ATL.And as soon as ePo comes back it will fetch updtes again and distribute to all clients.
Ok, thanks for the information.
That means that the Agent Handler can serve as a backup for all the client connections even if there is no connection to the ePO server DB, right? I assume it caches everything to serve the client as long as the ePO server is back up?!
I have found following in the Agent Handler white paper:
Page 7, chapter "Failover"
"As long as the agent handler is connected to the database it can continue serving agents, including any policy or task modifications that result from agent properties or from user modifications prior to the application server being taken offline."
Does this mean that our Agent Handler will not be able to serve client request while the ePO server including its database is down? You have to know that the database is installed on the ePO server.
Message was edited by: dhierholzer on 2/6/13 12:15:15 PM CST
Agreed, If DB is also down then AH will not be able to server clients requests, If you have your SQl DB on the same server t, AH will not be serving your clients. So in your case your AH is serving as "Request Handler only if connected to DB".I would suggest you to set a "Repository" instead of AH.