Results 11 to 14 of 14
Actually, after a discussion with the AD guy, the only part of it that he is concerned with is the replication. This is simply a redundancy thing; the server(s) are ...
- 06-26-2003 #11
Actually, after a discussion with the AD guy, the only part of it that he is concerned with is the replication. This is simply a redundancy thing; the server(s) are constantly updating each other. It is the only thing keeping him from letting me rebuild his WebFarm with Linux. It seems to me that this functionality would have been around long before the GUI (or what was in that day refered to as the WIMP(Windows, Icons, Mice, Pointers)) systems.
Any ideas?
- 06-26-2003 #12Linux Guru
- Join Date
- Oct 2001
- Location
- Täby, Sweden
- Posts
- 7,578
NIS has very mature support for setting up a master server and having slave servers replicating from it. I believe that there can only be one master server for each map, though.
- 06-26-2003 #13
So can you set NIS up to know to set a new master in the event that the existing master has some catastrophic failure?
- 06-26-2003 #14Linux Engineer
- Join Date
- Jan 2003
- Location
- Lebanon, pa
- Posts
- 994
If the master goes down or is running to slow for the request, the client will automaticly contact the slave. I guess if you did not backup the master at all and you lose all data, you could convert the slave to a master since the nis databases would be stored on it. Though I recommend running backups on your master server


Reply With Quote