Hello --

I am an applications developer, not exactly a Linux "newbie," but don't spend most of my time at the $ or # prompt. I have "inherited" a Linux HA cluster - two servers running RedHat Enterprise, each with two NICS (there is a dedicated gigabit connection between the servers, and each server is on the network). Heartbeat and drbd are running on each. So one is primary, the other secondary. It looks to me like most of the work has been done on these servers, but since I took them over without benefit of talking to the person that left them (he passed away), I'm just not sure what might be missing! I've seen one or two articles on Linux HA using heartbeat and drbd, but would like some more in-depth reading or assistance. Are the drbd man pages my best bet? Can anyone point me in a helpful direction?

Thanks...C.Hawkins

Welcome to LQ chawkins. What question specifically are you trying to answer, or what specific problem are you trying to solve? From your description it appears that responsibility for these machines has now been assigned to you, but beyond that it isn't clear exactly what technical issue you are trying to investigate. (Is the server misbehaving in some way, are there error messages being generated, etc.)

If your main interest essentially is to gather more information about drbd, then I'd consider a basic Google search to be an excellent starting point. -- J.W.

Thanks for the reply, J.W. Yes, the servers are now my responsibility. I have no particular technical issue. I just don't know enough about this configuration (RedHat/Heartbeat/drbd) to know if my predecessor was really "done" configuring things, and was ready to put live data on the servers, or not. I don't know what I don't know, in other words. So I'm really looking for more in-depth coverage of the topic than I was able to find by Googling. I did find a Linux Magazine article ("Highly Affordable High Availability") that paints the "big picture." I'm looking for a resource (human or otherwise) that can lead me through some detailed checklist, some fail-over testing, etc., so I can see if the servers perform as they should. Am I making things clearer or worse? Thanks again, C.Hawkins.