It isn't the job of a load balancer to read your event log. :-P That being said, all of them that I am aware of will do "live host" checks via ping, port tests, synthetic transactions, and external scripts - so if you want to write a script to read your event log, you can do that.
Typically speaking, ping, port, and synthetic transactions are the way to go. Ping detects complete server failure. Port checks verify that applications are listening on the expected ports. Synthetic transactions verify that the applications are working as expected (i.e., I send this HTTP request and I don't get an error back). On the low end, I've deployed Kemp Technologies and Coyote Point load balancers. They both work just fine, have a similar cost (at least in the US), and a similar feature set. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Oliver Marshall [mailto:oliver.marsh...@g2support.com] Sent: Wednesday, February 02, 2011 5:07 AM To: MS-Exchange Admin Issues Subject: Load balancer requirement and recommendations for DAG failover Hi, Recently we had a discussion on the list about whether a load balancer was *required* for running multiple exchange servers. If we did want a load balancer to automate the process can anyone recommend a unit they are using? What are the particular requirements of a load balancer? Clearly if the primary exchange server in our two Exchange server setup is dead then the load balancing role is fairly easy: if the server doesn't respond failover. But I'm guessing that the load balancer would also need to be able to handle more esoteric issues like users not being able to log on due to the Info Store being stopped, or 500 errors etc. Any comments/suggestions? Olly --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
