nisrestore restores an existing backup of a NIS+ directory object that was created using nisbackup(1M). The backup-dir is the UNIX directory that contains the NIS+ backup on the server being restored. The nisrestore command can be used to restore a NIS+ directory object or a complete NIS+ database. It also can be used as an "out of band" fast replication for a new replica server being
initialized. The rpc.nisd(1M) daemon must be stopped before running nisrestore.
The first synopsis is used to restore a single directory object or a specified list of directory objects. The directory can be partially qualified or fully qualified. The server being restored will be verified against the list of servers serving the directory. If this server is not configured to
serve this object, nisrestore will exit with an error. The -f option will override this check and force the operation.
The second synopsis will restore all of the directory objects contained in the backup-dir. Again, the server will be validated against the serving list for each of the directory objects in the backup-dir. If one of the objects in the backup-dir are not served by this server, nisrestore will exit with an error. The -f option will override this check and force the operation.
The -a option will attempt to restore all NIS+ objects contained in the backup-dir. If any of these objects are not served by the server, nisrestore will exit with an error. If the backup-dir contains objects
that are not served by the server, nisrestore must be executed without the -a option and the specific directory objects listed.
The -f option will disable verification of the server being configured to serve the objects being restored. This option should be used with care, as data could be inadvertently restored to a server that doesn't serve the restored data. This option is required in the case of restoring
a single server domain (master server only) or if the other NIS+ servers are unavailable for NIS+ lookups.
The combination of options -f and -a should be used with caution, as no validation of the server serving the restored objects will be done.
New replicas can be quickly added to a namespace with the nisrestore command. The steps are as follows.
Configure the new replica on the master server (see nisserver(1M)):
|
master# nisserver -R -h replica
|
Kill the rpc.nisd server process on the new replica server:
|
replica# kill rpc.nisd-pid
|
Create a backup of the NIS+ database on the master, which will include the new replica information. See nisbackup(1M). The /backup will need to be exported to
the new replica. See share_nfs(1M).
|
master# nisbackup -a /backup
|
Restore the backup of the NIS+ database on the new replica. Use the -f option if nisrestore is unable to lookup the NIS+ objects being restored. The backup should be available through nfs or similar means. See share_nfs(1M).
|
replica# nisrestore -f -a //nfs-mnt/backup
|
Restart the rpc.nisd(1M) process on the new replica, and the server will immediately be available for service.
|