Replicating FNS Service

On large or mission-critical networks where performance and reliability of FNS naming is of vital importance, FNS service should be replicated.

Replicating FNS Service — Task Map

How to Replicate FNS Under NIS+

After the FNS namespace has been set up on the master server, additional replicas can be added in each domain to serve the domain's ctx_dir directory. Replicas enhance availability and performance of the servers.

1. Run the nismkdir command on the FNS master server to add a replica for the ctx_dir directory.

   For example, establish the machine fnsrserver as an FNS replica for the doc.com. domain:

   # nismkdir -s fnsrserver ctx_dir.doc.com.

2. Checkpoint the ctx_dir directory with the nisping command.

   # /usr/lib/nis/nisping -C ctx_dir.doc.com.

   FNS replicas should be checkpointed at regular intervals. The recommended period is every few days. The period you choose depends on how frequently changes are made to the FNS namespace.

How to Replicate FNS Under NIS

After the FNS namespace has been set up on the domain master server, additional slave servers can be added to enhance availability and performance of the servers.

1. As root, edit the /etc/hosts file on the slave server to add the name and IP addresses of all the other NIS servers.

2. Change directory to /var/yp on the slave server.

3. To initialize the slave server as a client, type the following:

   # /usr/sbin/ypinit -c

   The ypinit command prompts you for a list of NIS servers. Enter the name of the local slave you are working on first, then the master server, followed by the other NIS slave servers in your domain in order, from the physically closest to the furthest (in network terms).

   ---

   Note –

   You must first configure the new slave server as an NIS client so that it can get the NIS maps from the master for the first time. (See “Setting Up and Configuring NIS Service” in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for details.)

   ---

4. To determine if ypbind is running, type:

   # ps -ef | grep ypbind

   If a listing is displayed, ypbind is running.

5. If ypbind is running, stop it by typing:

   # /usr/lib/netsvc/yp/ypstop

6. Type the following to restart ypbind:

   # /usr/lib/netsvc/yp/ypstart

7. To initialize this machine as a slave, type the following:

   # /usr/sbin/ypinit -s master

   Where master is the machine name of the existing NIS master server.

8. Stop yp processes on the Slave Server:

   # /usr/lib/netsvc/yp/ypstop

9. Restart yp service:

   # /usr/lib/netsvc/yp/ypstart

   Alternatively, you can reboot the slave server and allow daemons to start automatically.

How to Replicate FNS Under Files-Based Naming

There is no server replication when your primary naming service is files-based.