Security Considerations
The NIS+ principal performing this operation must have modify rights to the domain's directory object.
Prerequisites
The domain must have already been configured and have a master server up and running.
The new replica server must already be configured as an NIS+ server, as described in "Setting Up an NIS+ Server".
The new replica server must by configured as a replica, as described in "Using NIS+ Commands to Configure a Replica Server".
Using nisping to Load Data on to a Replica Server -- Task Map
Table 7-3 Using nisping to Load Data on to a Replica Server
Task | Description | For Instructions, Go To | |
---|---|---|---|
Using nisping to Load Data on to a Replica Server | Use nisping to load data on to a replica server |
How to Load Namespace Data--nisping Method
Normally, the loading for namespace data is automatically initiated by the master server. If that does not occur, run the nisping command as described below.
This step sends a message (a "ping") to the new replica, telling it to ask the master server for an update. If the replica does not belong to the root domain, be sure to specify its domain name. (The example below includes the domain name only for completeness. Since the example used throughout this task adds a replica to the root domain, the doc.com. domain name in the example below is not necessary.)
master1# nisping doc.com. master1# nisping org_dir.doc.com. master1# nisping groups_dir.doc.com. |
You should see results similar to these:
master1# nisping doc.com. Pinging replicas serving directory doc.com. : Master server is master1.doc.com. No last update time Replica server is replica1.doc.com. Last update seen was Wed Nov 18 11:24:32 1992 Pinging ... replica2.doc.com. |
If your namespace is large, this process can take a significant amount of time. For more information about nisping, see Chapter 18, Administering NIS+ Directories.
Server Configuration Summary
Table 7-5 and Table 7-4 provide a summary of the tasks described in this chapter. They assume the simplest cases, so be sure you are familiar with the more thorough task descriptions before you use this summary as a reference. This summary does not show the server's responses to each command.
Table 7-4 Adding a Replica Named replica2 to doc.com.: Command Summary
Tasks | Commands |
---|---|
Log in as superuser to domain master. | master1% su |
Designate the new replica. | # nismkdir -s replica2 doc.com. # nismkdir -s replica2 org_dir.doc.com. # nismkdir -s replica2 groups_dir.doc.com. |
Ping the replica. | # /usr/lib/nis/nisping doc.com. # /usr/lib/nis/nisping org_dir.doc.com. # /usr/lib/nis/nisping groups_dir.doc.com. |
Note - Rather than using nisping to transfer data to the new replica, as shown in the example above, an easier method is to use the NIS+ backup and restore capability, as described in "Using nisrestore to Load Data on to a Replica Server".
Table 7-5 Starting Up a Non-root Master Server: Command Summary
Tasks | Commands |
---|---|
Log in to the server as root. | server%su |
NIS-compat only: Start daemon with -Y -B | server# rpc.nisd -Y - B |
Change to EMULYP= -Y -B. | server# vi /etc/inet.d/rpc |
NIS+-Only: Start daemon. | server# rpc.nisd |