Hi!
First have to say big thx for the great LTSP environment, works like a charm!;)
Now, I'm on the way of upgrading my LTSP server and would like to setup a second one (identical hw), for ha purposes.
Even with solid server hw, hotplugable hw RAID disks, there's always the possibility of some part breaking. Users shouldn't need anymore then switching their tc off and on again to boot from the second server.
Things I thought already about:
Using DHCP fail over looks like the easiest way to obtain automatic fail over to the second LTSP server.
Problem remaining, how to keep /home in sync. One way would be a dedicated link via crossover and using rsync from cron to keep files the same. Might need some tweaking, if you need to sync in both directions, case you got for one or another reason, thin clients on both systems at the same time.
Another idea would be using GFS on shared SAN storage, which should resolve any of the above problems. Is there anyone out there using GFS (sistina) with LTSP? How did he redundant multi-path hbas used?
Then there's ENBD which might do the same, but requires a third system.
What do you think?
Thx for reading and special thx to Jim McQuillan for making LTSP possible!
Michael Heiming
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
