.\" $Id: nsr_layout.5,v 1.3 2003/07/10 17:53:32 btompkin Exp $ Copyright (c) 2003, Legato Systems, Incorporated" .\" Copyright (c) 2003, Legato Systems, Incorporated. .\" All rights reserved. .TH NSR_LAYOUT 5 "Aug 23, 06" "StorEdge EBS 7.3.2" .SH NAME nsr_layout - Sun StorEdge EBS file layout .SH SYNOPSIS type: NSR layout .SH DESCRIPTION The Sun StorEdge EBS server filesystem has a directory called .B /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: .LP .IP "\fB/nsr/logs\fR" Contains server logging messages. The files in this directory are in ASCII format. .IP "\fB/nsr/res\fR" Contains the configuration files for various components of the Sun StorEdge EBS server. For example, the server stores configuration files in .BR /nsr/res/nsrdb . .IP "\fB/nsr/mm\fR" Contains the media index. Information about the contents of this index file can be printed with the .BR nsrls (8) command. See the .BR nsrmm (8) and .BR mminfo (8) manual pages on how to view and manipulate the media index information. .IP "\fB/nsr/index\fR" This directory contains subdirectories with names that correspond to the Sun StorEdge EBS clients that have saved files. Each index directory contains files that allow the Sun StorEdge EBS server to provide an on-line database of the client's saved files. The most important element is the .B db6 directory which contains the Sun StorEdge EBS save records and access indexes to those records. The disk space utilized by the index grows with the number of files saved by the Sun StorEdge EBS 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 single file system. .IP The format of the .B db6 directory is subject to change, and is accessible only through an RPC interface to .BR nsrindexd (8). However, the .BR nsrls (8) command can be used to obtain some useful statistics from this directory. The .BR nsrck (8) command is used for checking and rebuilding index files as well as recovering index files from backup media. .IP The data in the files in the .B db6 directory are stored in platform-independent order, so these files may be migrated from one Sun StorEdge EBS server to another. Moving the media database from one Sun StorEdge EBS server to another of unlike architecture is not currently supported. .IP The files in the .B 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. .RS .IP "\fB.rec\fR" These files contain the index records for each file saved at the savetime, where .B is a hexadecimal representation of the time. .RE .RS .IP "\fB.k0\fR" These files contain the keys on the .B .rec file based on file name. .RE .RS .IP "\fB.k1\fR" These files contain the keys on the .B .rec file based on inode. These may be zero length files if the client file index is for a windows client. .RE .RS .IP "\fB.sip\fR" 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 .B .rec. .RE .RS .IP "\fBv6hdr\fR" This file contains a summary of all the .B .rec files that exist in a client's .B db6 directory. .RE .RS .IP "\fBv6journal\fR" This file contains updates to the .B v6hdr file that are waiting to be merged into the .B v6hdr file. Any index operation includes the entries here as well as the ones in the .B v6hdr. .RE .RS .IP "\fBv6ck.lck\fR" This file is a lock that .B nsrck uses to ensure that only one .B nsrck operates on a client's index at any given time. .RE .RS .IP "\fBv6hdr.lck\fR" This file locks the .B v6hdr for reading and the .B v6journal for reading and writing. .RE .RS .IP "\fBv6tmp.ptr\fR" This file refers to the working directory in which conversion and recovery will take place. .RE .RS .IP "\fBtmprecov\fR" This is a working directory in which conversion and recovery take place. .RE .RS .IP "\fBrecovered\fR" 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 .B nsrck is run against this client file index. .RE .IP "\fB/nsr/cores\fR" Contains directories that correspond to the Sun StorEdge EBS server daemons and certain executables. Each directory may contain core files from Sun StorEdge EBS server daemons or executables that have abnormally terminated. .IP "\fB/nsr/drivers\fR" This directory may contain any device drivers for use with Sun StorEdge EBS. .IP "\fB/nsr/tmp\fR" This directory contains temporary files used by the Sun StorEdge EBS system. .LP The executables for the Sun StorEdge EBS system are usually installed in the .B /usr/etc or .BR /usr/bin , directories though alternate locations may be chosen when the .BR nsr_ize (8) installation script is run. See .BR pkgadd (1M) for details on alternate executable locations for Solaris 2.x. .LP When executables for more than one architecture are installed, the non-native architectures are by default put in the directory \fB/export/exec/\fIarch\fB/etc\fR, where .I arch refers to a given architecture name. A different location to install non-native executables can be chosen at installation time. .LP .SH FILES .TP 20 .B /nsr Sun StorEdge EBS indexes, log files, and configuration information. .TP .B "/usr/etc, /usr/bin" Where Sun StorEdge EBS executables for the native architectures are normally installed. .TP \fB/export/exec/\fIarch\fB/etc\fR Where Sun StorEdge EBS executables for non\-native architectures are normally installed. .TP .B "/usr/bin, /usr/sbin, /usr/lib/nsr" Where Sun StorEdge EBS executables for Solaris 2.x are normally installed. .SH SEE ALSO .BR nsrck (8), .BR nsrindexd (8), .BR nsrls (8), .BR nsrmm (8), .BR mminfo (8), .BR nsr_ize (8).