1854811 Members
20227 Online
104103 Solutions
New Discussion

Re: NIS Migration

 
SOLVED
Go to solution
Manoj Sivan
Regular Advisor

NIS Migration

Hi,

We are having two NIS servers( each having slaves seperately) under HP-Ux 11.11. We would like to consolidate as one server (and slave)

Can anyone guide me in migration, by steps (both master and slave side).

Thanks in advance

Manoj
3 REPLIES 3
Arunvijai_4
Honored Contributor

Re: NIS Migration

Hi Manoj,

These threads will help you,

http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=33869
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=128921

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
Manoj Sivan
Regular Advisor

Re: NIS Migration

Hi Arun,

Those doc links are not active now. I will explain my setup.

I do have

NIS Master-A NIS Master-B
NIS Slave-A NIS Slave-B

I want to remove NIS Servers-B from network as a part of server reduction. So i need to migrate all databases from B to A. SO i am requesting the procedure for that. Also what are the necessary changes i need to impliment at clinet side ?

Thanks and regards

Manoj
Mark Ellzey
Valued Contributor
Solution

Re: NIS Migration

Manoj,

I assume that these are two different NIS domains and are also on the same subnet. What you will need to do depends on how you have your NIS-B domain set up, with respect to your NIS-A domain.

At a minimum, you will need to make sure all the host, passwd, group and netgroup files on NIS-B are included in NIS-A. If you are also using auto.master, auto.direct, auto.indirect or auto.home maps on NIS-B, these will also have to be included in the appropriate NIS-A files.

Once that is done, you will have to run /var/yp/ypmake to create the new NIS maps. Then you would probably want to reboot the NIS-A master, or stop and start the ypserv daemon with /sbin/init.d/nis.server stop|start.

On the client side, you will need to update the /etc/rc.config.d/namesvrs file to the new NIS-A domain name. Then you can either reboot the clients, or execute /sbin/init.d/nis.client stop
/sbin/init.d/nis.client start

If you have any security set up in your /etc/exports file on any NFS servers that are specific to NIS-B, this will have to be updated on the NIS-A server as well. Then you would re-export all exported NFS filesystem on all NFS servers.

If all that goes well, your clients should connect to the NIS-A domain.

A valuable resource is the HP website: Administering NFS services. This is available at:

http://docs.hp.com/en/5991-1154/index.html

Regards,
Mark