On 5/14/07, Hans-Werner Hilse <[EMAIL PROTECTED]> wrote:
Hi, On Mon, 14 May 2007 15:42:45 -0300 "Daniel van Ham Colchete" <[EMAIL PROTECTED]> wrote: > Thinking about other options, does anyone have any other tip for me? Am I > going in the right direction? The two options you've mentioned are quite different. One gives console access, the other basically cures HD fails. The latter is clearly a job for your hosting company, I think. And there's an old, proven way for the task "console access": forget about that graphics output on that computer and learn to trust in good ol' serial connections :-) certainly cheaper than KVM-over-IP. Another option would be for the servers to default to netbooting and fall back to HD on boot. Then you were able to switch on the service offering the netboot images on some fall-back servers on-demand. I think this is somewhat like your USB idea. Or generally use netboot (w/ redundant servers) and forget about the HD fails alltogether (i.e., have some remote login program in your initrd). All these options still won't give you the opportunity to power-cycle your machines, which might be the only option left under some circumstances. A hw watchdog can probably reduce the impact of that problem a lot. -hwh -- [EMAIL PROTECTED] mailing list
Hi Hans! Yeah! Direct netboot is a very nice idea too... I can't to it with one kind of server I'll have but with the clustered ones that I'll be nice! To improve reliability I could make a copy of a healthy image to the node's hard drive every time it boots, so it's not dependent on a NFS server all the time (just to boot). Best Daniel
