NIS and redundancy
I have been scratching my head over this problem for a couple of days and have yet to come up with a elegant working solution.
I want to set up a network with redundant home directories for all the users and software, so that if the machine with the relevant disks goes down for whatever reason, there is a fallback that can take over.
My original idea was to set up two NIS master servers running on the same domain with a copy of the home directories on each machine. My reasoning was, that if I give each server a different passwd map pointing to the local home directories, fallover of one of the machines would cause the clients to use of the other master's maps, resulting in business as usual (home directories are sync'd on a regular basis).
I also tried the same thing, but with changes in auto.home, so the automounter maps from the different servers would use the same mount point for different home directories.
Neither of these schemes worked. Somehow the clients remember the last maps they used. Example, I am bound to NISmaster1 for which the user Joe's home directory is on /home1/joe. I restart the client binding to NISmaster2 where joe's home is at /home2/joe. The maps from the new binding does not overwrite the setting on the client, i.e. if I type cd ~joe, I still go to /home1/joe. Same thing for the autofs maps.
I suppose this is not so surprising, but it leaves me with little idea on how set up a backup file server without some kind of cluster-like heartbeat.
Any suggestions would be appreciated. Thanks.