ansrd [ commentary ]
Normally nsrd is invoked from a startup shell script (for example rc.local, rc.boot) at boot-time, and should never need to be started directly by a user. After it is started, nsrd starts up the other daemons it needs to provide the NetWorker service.
The nsrd command must be run on a machine with appropriate resources. These resources include devices (for example, tape drives) which are under the control of the media multiplexor software (see nsrmmd(1m)), and sufficient disk space for the index daemons, (see nsrindexd(1m) and nsrmmdbd(1m)) to maintain the index of saved user files and volumes with corresponding files.
Each time a backup, recover, or another session begins, nsrd starts the program, ansrd, to process the requested session. The ansrd program is called an agent. The agent is in charge of monitoring that backup, recover, or another session, and automatically exits when a session completes. Using ps(1) or another process monitoring tool, you can inspect the subsequent parameters of ansrd to see what kind of session it is monitoring. If necessary, agents can be forcibly terminated to abort a backup or recover session. Agents cannot be run directly; they can only be started by nsrd.
When nsrd is started with the -k option, it checks to see whether it has been installed as a cluster service and that the virtual host which owns /nsr/res matches virtual-service-name. If either of these validation steps fails, nsrd exits immediately. (To check whether NetWorker has been installed as a cluster service, nsrd checks for a file called NetWorker.clustersvr in the directory containing the nsrd binary. To check that /nsr/res is owned by virtual-service-name, nsrd queries the cluster management software.)
If the -k option is not used when starting NetWorker in a cluster, the server assumes the identity of the virtual host which owns /nsr/res. If no virtual host owns /nsr/res, then nsrd will not start.