nsrindexd man page on DigitalUNIX

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


       nsrindexd - NetWorker file index daemon


       The  nsrindexd  daemon  is  started  by	the server nsrd(8) daemon.  It
       should not be started manually.	The daemon provides an RPC-based  ser‐
       vice  to	 the server nsrd(8) daemon; direct network access to this ser‐
       vice is not allowed.  The RPC program and version numbers  provided  by
       nsrindexd are 390105 and 4, respectively.

       The  service provided to the NetWorker system is designed for high per‐
       formance insertion and deletion of save	records	 into  indexes.	  This
       performance  is obtained by keeping information cached in the nsrindexd
       process address space.  When the NetWorker system wishes	 to  commit  a
       save  session's records, it notifies the nsrindexd daemon (via a remote
       procedure call) to flush its volatile state to its file(s).

       Since the daemon (or the server) may crash at any time, the index files
       may  be left in an inconsistent state.  Therefore, the maintenance pro‐
       gram, nsrck(8) is run automatically by the nsrd daemon before the  Net‐
       Worker service is started.

       When  the NetWorker service is started, it starts the process nsrindexd
       which will invoke nsrck -L 1 to perform a fast and efficient check  for
       each of the configured client file indexes. Only the consistency of the
       index header and journal files are checked. It is generally not	neces‐
       sary  (and  very	 time consuming) to check every record and key file in
       the client file index at startup. If a  problem	is  detected,  a  more
       thorough	 check will be automatically performed on client file index in

       If you believe an index may be corrupt, you can manually run  a	higher
       level check on the index, for example:

       nsrck -L 6

       Running nsrck -L 7 will not overwrite existing files in the client file
       index. So, if online client  file  index	 data  already	exists	for  a
       saveset	for a particular save time, it must be removed before nsrck -L
       7 can be used to restore it from the backup media.

       Since nsrindexd and nsrck are run at the same time, both	 programs  use
       an  advisory file-locking mechanism on the file v6ck.lck to synchronize
       their access to an index.

			     This directory is where the client's index header
			     file  and	journal	 files	are  stored. The index
			     record files (.rec)  and  the  corresponding  key
			     files  (.k0 and .k1) are stored in different sub‐
			     directories under db6 directory.

			     This is the name of the index header.

			     This is the name of the journal file.

			     This is the name of the lock file used  for  syn‐
			     chronizing	 access	 to  the index header file and
			     journal file.

       SEE ALSO
	      nsr_layout(5), nsr(8), nsrck(8),	nsrd(8),  nsrim(8),  nsrindex‐
	      asm(8), nsrls(8), nsrmm(8),

       Continuing without index header for client clientname
	      This  is an informative message to indicate that another program
	      is accessing the same file that is required by this daemon.  The
	      daemon  determined  that	it  can	 continue its operation safely
	      without the index header.

NetWorker 7.3.2			  Aug 23, 06			  NSRINDEXD(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