NSR_LAYOUT(5)NSR_LAYOUT(5)NAMEnsr_layout - NetWorker file layout
SYNOPSIS
type: NSR layout
DESCRIPTION
The NetWorker server filesystem has a directory called /nsr that con‐
tains log files, on-line indexes, and configuration information. This
directory can be created in any filesystem with /nsr set up as a sym‐
bolic 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/nsrdb.
/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 corre‐
spond 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 element is the db6 directory which contains the
NetWorker save records and access indexes to those records. The
disk space utilized by the index 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. There are no practical limits on the maximum size of an
online index, except that it must reside entirely within a sin‐
gle file system.
The format of the db6 directory is subject to change, and is
accessible only through an RPC interface to nsrindexd(8). How‐
ever, the nsrls(8) command can be used to obtain some useful
statistics from this directory. The nsrck(8) command is used
for checking and rebuilding index files as well as recovering
index files from backup media.
The data in the files in the db6 directory are stored in plat‐
form-independent order, so these files may be migrated from one
NetWorker server to another. Moving the media database from one
NetWorker server to another of unlike architecture is not cur‐
rently supported.
The files in the db6 directory include the files listed below.
Note that these files are for the internal use of the server and
are not to be modified or changed for any purposes.
<savetime>.rec
These files contain the index records for each file saved
at the savetime, where <savetime> is a hexadecimal repre‐
sentation of the time.
<savetime>.k0
These files contain the keys on the <savetime>.rec file
based on file name.
<savetime>.k1
These files contain the keys on the <savetime>.rec file
based on inode. These may be zero length files if the
client file index is for a windows client.
<savetime>.sip
This is a save-in-process file and only exists when a
save has been started and is not yet complete. Once the
save is complete, this file is renamed to <savetime>.rec.
v6hdr This file contains a summary of all the <savetime>.rec
files that exist in a client's db6 directory.
v6journal
This file contains updates to the v6hdr file that are
waiting to be merged into the v6hdr file. Any index
operation includes the entries here as well as the ones
in the v6hdr.
v6ck.lck
This file is a lock that nsrck uses to ensure that only
one nsrck operates on a client's index at any given time.
v6hdr.lck
This file locks the v6hdr for reading and the v6journal
for reading and writing.
v6tmp.ptr
This file refers to the working directory in which con‐
version and recovery will take place.
tmprecov
This is a working directory in which conversion and
recovery take place.
recovered
This directory contains intermediate results of an index
that has been converted or recovered. The results here
are complete and will be integrated into the file index
when nsrck is run against this client file index.
/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 contain any device drivers for use with Net‐
Worker.
/nsr/tmp
This directory contains temporary files used by the NetWorker
system.
The executables for the NetWorker system are usually installed in the
/usr/etc or /usr/bin, directories though alternate locations may be
chosen when the nsr_ize(8) installation script is run. 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 archi‐
tectures are normally installed.
/export/exec/arch/etc
Where NetWorker executables for non-native archi‐
tectures are normally installed.
/usr/bin, /usr/sbin, /usr/lib/nsr
Where NetWorker executables for Solaris 2.x are
normally installed.
SEE ALSOnsrck(8), nsrindexd(8), nsrls(8), nsrmm(8), mminfo(8), nsr_ize(8).
NetWorker 7.3.2 Aug 23, 06 NSR_LAYOUT(5)
