We have a building with 25 LTSP clients. We will open another location across town. I need to choose to design the network.
A few topologies come to mind: (1) to keep servers in building A and login from building B. However, if there is a problem with the Internet, then all the computers in building B, are down. (2) to have servers in both buildings; but synchronization may be problematic. (And will take bandwidth) (3) to take a hybrid approach. Remote login as in topology (1); however, each night 'Copy/Rsync/Unison' building A to building B. This way in the event of Internet failure, building B can run locally. So there I have nicely synchronized files, offsite backup, low bandwidth usage. note: (mainServer has dual Xeon processor and 8gb ram w/ raid drives) So please cast your vote for 1, 2 or 3. Or make your own suggestion. many thanks. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _____________________________________________________________________ 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
