On Wed, Dec 23, 2009 at 10:33 PM, CHAPLIN, JAMES (CTR) <james.chap...@associates.dhs.gov> wrote:
> We want to create a central location for all zLinux server's user home > directory located on a common server (using NFS?) with some method of > failover if that server is down. Is there a file system that crosses > different servers that can be mounted by one system as the user home > file system, and then can fail over to another system if that (NFS > holding the Home Directories) server goes down? You would need that central location to be as highly available than the rest... But even then, it may not be nice to always require that central location for everything you do. Along those lines, in a CSE environment I prefer production services not depend on a remote resource. Local resource for anything that keeps the system running, possibly remote resource for things that can be postponed, planned or worked around. For our Linux setup, we decided on a slightly different route where each user gets a home directory on temporary space, but has his central "own" directory mounted R/O within that temporary home directory (eg as ~/homedir ) The files in the temporary space were discarded after 2 weeks or so. This worked well for coming back a few times when diagnosing problems or doing things on some system. Also, when you don't share the actual home directory there's no risk of mixing things up. Only on the NFS host itself, the user got that as his home directory to make updates (you can use scp to put something there). The reason for R/O was that our developers had root access on their own sandbox systems. We don't want them to use that to plant a trojan horse into someone's home directory that would be invoked on a production system again. Rob ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
