EMC Legato NetWorker Commands Reference

nsrindexd

SYNOPSIS

       nsrindexd

DESCRIPTION

       The  nsrindexd  daemon  is  started  by  the server nsrd(1) daemon.  It
       should not be started manually.  The daemon provides an RPC-based  ser-
       vice  to  the server nsrd(1) 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(1) 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
       question.

       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 db.SCAVENGE to synchro-
       nize their access to an index.

FILES

       /nsr/index/clientname/db
                             This file is where the client's index records are
                             stored and accessed.

       /nsr/index/clientname/db.SCAVENGE
                             When  this  file exists and nsrindexd is not run-

       waiting for lock on filename.
              This message indicates that another  program  is  accessing  the
              same file that is required by this daemon.  The daemon will wait
              for the advisory lock to be cleared.

       lock on filename acquired.
              This is an informative message that eventually follows the wait-
              ing for lock on filename message.

ADVERTISEMENT