We are moving to running all our monitoring services in (VMWare) virtual machines. The vm's are backed up each night to a NAS share.

If the physical server dies, no big deal I can just start the vm on another host connected to the same SAN. If the SAN dies (unlikely), I can restore the vm from the backup on some other host.

We also run Sitescope, which alerts us if BigBrother/Hobbit dies (and vice versa).

-- Scott Kelley, Disney Enterprise IT Platform Services

-----Original Message----- From: hobbit-return-2800-Scott.Kelley=disney.com at hswn.dk [mailto:hobbit-return-2800-Scott.Kelley=disney.com at hswn.dk] On Behalf Of Lowery, Michael Sent: Tuesday, June 21, 2005 9:13 AM To: hobbit at hswn.dk Subject: [hobbit] Redundant Hobbit Servers

I'm interested in knowing what everyone is doing for redundancy. I currently have 2 hobbit servers and each one performs the same tests as the other.

I find this to be a bit wasteful and am looking for the active/passive type of configuration that has been talked about on this list before.

This configuration works fine, except for alerting. In order to not be overwhelmed by messages, I only have one hobbit server performing the alerting task, the other only sends alerts on the other hobbit host.

I have considered using the "depends=" test, but then I have to maintain two separate bb-hosts files, rather than copying and pasting from one to the other.

Is there a better way than what I'm doing? My goal is to have both servers configured the same, as much as possible, and have only one of them at a time send me alerts.

I'd love to know what you guys are doing to get around these limits. I could easily have missed something in the newest update that solves this problem, but I haven't seen it yet.

Thanks for your thoughts on this subject.

Michael

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk