NAME

NSR Layout - NetWorker file layout

DESCRIPTION

The NetWorker server filesystem has a directory called /nsr that contains log files, on-line indexes, and configuration information.  This directory can be created in any filesystem with /nsr set up as a symbolic link to the actual directory (this is determined at installation time).  The format of this directory is as follows:

/nsr/logs
Contains server logging messages. The files in this directory are in ASCII format.

/nsr/res
Contains the configuration files for various components of the NetWorker server. For example, the server stores configuration files in /nsr/res/nsr.res and /nsr/res/nsrjb.res. 

/nsr/mm
Contains the media index. Information about the contents of this index file can be printed with the nsrls(8) command.  See the nsrmm(8) and mminfo(8) manual pages on how to view and manipulate the media index information. 

/nsr/index
This directory contains subdirectories with names that correspond to the NetWorker clients that have saved files. Each index directory contains files that allow the NetWorker server to provide an on-line database of the client’s saved files. The most important file is the db file which contains the NetWorker save records and access indexes to those records.  This index file grows with the number of files saved by the NetWorker service.  Administrators should plan to use about 200 bytes per saved file instance placed in this index.  An index may grow to a maximum of 1GB in size, with the first 40KB allocated for internal use. 

The format of the db file is subject to change, and is accessible only through an RPC interface to nsrindexd(8).  However, the command nsrls(8) can be used to obtain some useful statistics from this file. 

The existence of the db.SCAVENGE file indicates that the associated db file may need to be checked.  The nsrck(8) command is used for checking and rebuilding index files.  While checking is taking place, the db.SCAVENGE file may contain the save records that will be used to rebuild db.  If the filesystem does not have enough free space to contain db.SCAVENGE, then the file will be a symbolic link to a temporary file in some other local filesystem. 

The file db.RECOVER is where nsrck “rebuilds” a fresh index.  Upon completion this file is renamed to db. 

/nsr/cores
Contains directories that correspond to the NetWorker server daemons and certain executables. Each directory may contain core files from NetWorker server daemons or executables that have abnormally terminated.

/nsr/drivers
This directory may contains any device drivers for use with NetWorker.

/nsr/tmp
This directory contains temporary files used by the Networker system.

The executables for the NetWorker system are usually installed in the directories /usr/etc or /usr/bin, though alternate locations may be chosen when the nsr_ize(8) installation script is run. Alternate locations are not available on SCO systems that install with custom(ADM).  See pkgadd(1M) for details on alternate executable locations for Solaris 2.x. 

When executables for more than one architecture are installed, the non-native architectures are by default put in the directory /export/exec/arch/etc, where arch refers to a given architecture name.  A different location to install non-native executables can be chosen at installation time. 

FILES

/nsr NetWorker indexes, log files, and configuration information. 

/usr/etc, /usr/bin Where NetWorker executables for the native architectures are normally installed. 

/export/exec/arch/etc
Where NetWorker executables for non−native architectures are normally installed.

/usr/bin, /usr/sbin, /usr/lib/nsr
Where NetWorker executables for Solaris 2.x are normally installed.

SEE ALSO

nsrck(8), nsrindexd(8), nsrls(8), nsrmm(8), mminfo(8), nsr_ize(8). 

NetWorker 4.1.2  —  Last change: May 1995