nsrd man page on DigitalUNIX

Man page or keyword search:  
man Server   12896 pages
apropos Keyword Search (all sections)
Output format
DigitalUNIX logo
[printable version]

NSRD(8)								       NSRD(8)

       nsrd - daemon providing the NetWorker service

       nsrd [ -k virtual-service-name ]

       ansrd [ commentary ]

       The  nsrd  daemon provides an RPC-based save and recover service.  This
       service allows users to save, query for, and recover their files across
       a network.  The RPC program number provided by nsrd is 390103.

       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 dae‐
       mons 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(8)),
       and  sufficient disk space for the index daemons, (see nsrindexd(8) and
       nsrmmdbd(8)) 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 valida‐
       tion 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.

       -k virtual-service-name
	      Instructs nsrd to start up in cluster failover mode  using  vir‐
	      tual-service-name as its hostname/identity.  This option is used
	      by the NetWorker cluster control script which starts NetWorker.

		 The file to which  nsrd  and  other  NetWorker	 daemons  send
		 information about various error conditions that cannot other‐
		 wise be logged using the NetWorker event mechanism.

		 Information  describing  the  NetWorker   service   and   its
		 resources (See nsr_service(5)).

		 If  this  file exists in the directory containing NetWorker's
		 daemons, it indicates that  the  NetWorker  server  has  been
		 installed as a cluster service.

       nsr(8), nsr_service(5), nsrmmd(8), nsrmmdbd(8), nsrindexd(8), ps(1),

NetWorker 7.3.2			  Aug 23, 06			       NSRD(8)

List of man pages available for DigitalUNIX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
Vote for polarhome
Free Shell Accounts :: the biggest list on the net