The nisrestore command recreates NIS+ directory objects to match the data stored in backup files created with the nisbackup command. This command can be used to restore NIS+ servers, replace directory objects that have become corrupted, or down load NIS+ data on to a new NIS+ server.
In order to use nisrestore the target machine that will be receiving the NIS+ data from nisrestore must have already been set up as an NIS+ server. (See Solaris Naming Setup and Configuration Guide for a detailed description of setting up NIS+ servers.) This means that:
The machine must have already been initialized as an NIS+ client.
If the machine will be running in NIS-compatibility mode and support DNS forwarding, it must have a properly configured /etc/resolv.conf file.
If you are using nisrestore on a server while other servers in the namespace are up and running, nisrestore will verify with those other servers that this server is configured to serve the backed up NIS+ objects that you are restoring to it. If no other servers are up and running in your namespace, then you must run nisrestore with the -f option. In other words, if there are other servers that nisrestore can check with, you do not need to use the -f option. If no other servers are available, for example if you are restoring a single master server and there are no functioning replica servers, then you must use the -f option.
In addition to the three pre-requisites listed above, the rpc.nisd daemon must not be running on the machine. If necessary, you must kill rpc.nisd before running nisrestore.
The nisrestore command uses the following syntax:
nisrestore [-fv][-a][-t] backupdir [directory_objects] |
Where:
Backupdir is the directory containing the backup files to be used to restore the NIS+ objects. For example, /var/master1_bakup.
Directory_objects are the NIS+ directory objects that you want to restore. For example, org_dir.doc.com. Multiple NIS+ directory objects can be listed separated by spaces. (If you run nisrestore with the -a option, you do not specify specific directory objects.)
The nisrestore command takes the following options:
Table 15-2 Options for the nisbackup Command
Option |
Purpose |
---|---|
-a |
All. Restores all of the NIS+ directory objects contained in the backup directory. |
-f |
Forces the restoration without validating that the server is listed in the directory object's serving list. This option must be used when restoring a root master server or if you get an "unable to lookup object" type of error. |
-v |
Verbose mode. This mode provides additional information |
-t |
This option lists all of the NIS+ directory objects stored in the backup directory. No restoration of objects takes place. |
To restore NIS+ data from NIS+ backup files, use the nisrestore command.
For example, to restore the org_dir.doc.com. directory object on the replica1 server, you would log in as root on replica1, make sure that the prerequisites described in "Prerequisites to Running nisrestore " have been met and then run nisrestore as shown below:
replica1# nisrestore /var/master1_bakup org_dir.doc.com. |
The following points apply to nisrestore:
Damaged namespace. To restore a damaged or corrupted NIS+ namespace, the nisrestore command must be run on all of the servers for the NIS+ directory objects you are restoring.
Lookup error. If you get an error message telling you that nisrestore cannot verify or look up needed data, then you must use the -f option.
For example, to reload NIS+ data on a root master server named master1, you would enter:
master1# nisrestore -f -a /var/master1_bakup |