Quantum Portable Media Storage 6 00360 15 User Guide
Installation Guide Installation Guide Installation Guide Installation Guide  
StorNext® 3.1.3  
6-00360-15  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Contents  
Chapter 1  
Installing StorNext File System and Storage Manager  
1
Storage Manager System Requirements......................................................... 2  
Operating System Requirements.............................................................. 2  
Hardware Requirements ........................................................................... 2  
LAN Requirements..................................................................................... 4  
Getting Ready to Install .................................................................................... 5  
Configuring Storage Devices .................................................................... 5  
Planning for LUNs Larger than 1 TB....................................................... 5  
Installing the Linux Kernel Source Code ................................................ 7  
Verifying Hostname Length...................................................................... 7  
Pre-Installation Script........................................................................................ 8  
Before You Begin......................................................................................... 8  
Running snPreInstall.................................................................................. 9  
Interpreting snPreInstall Output............................................................ 10  
StorNext Installation Script ............................................................................ 12  
Launching the StorNext Installation Script........................................... 12  
Changing Installation Configuration Options...................................... 14  
Performing an Installation Operation.................................................... 17  
Chapter 2  
Installing StorNext File System  
18  
File System Requirements............................................................................... 19  
Operating System Requirements............................................................ 19  
StorNext 3.1.3 Installation Guide  
iii  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Contents  
Hardware Requirements ......................................................................... 20  
LAN Requirements................................................................................... 20  
Getting Ready to Install .................................................................................. 21  
Configuring Storage Devices .................................................................. 21  
Planning for LUNs Larger than 1 TB..................................................... 22  
Installing the Linux Kernel Source Code .............................................. 23  
Installing StorNext File System on Linux or Unix ...................................... 24  
Launching the SNFS Installation Script................................................. 24  
Changing Installation Configuration Options...................................... 25  
Performing an Installation Operation.................................................... 26  
Installing StorNext File System on Windows.............................................. 27  
Removing a Previous Version of StorNext ........................................... 28  
Running the Setup Wizard...................................................................... 29  
Restoring a Previous Client Configuration........................................... 33  
Chapter 3  
Installing the StorNext Client  
36  
Client System Requirements .......................................................................... 37  
Operating System Requirements............................................................ 37  
Hardware Requirements ......................................................................... 38  
Downloading the StorNext Client Software ................................................ 39  
Installing the StorNext Client on Linux or Unix ......................................... 42  
Installing the StorNext Client on Linux................................................. 42  
Installing the StorNext Client on Sun Solaris ....................................... 44  
Installing the StorNext Client on HP-UX .............................................. 46  
Installing the StorNext Client on IBM AIX ........................................... 47  
Installing the StorNext Client on SGI IRIX ........................................... 49  
Installing the StorNext Client on Windows................................................. 51  
Removing a Previous Version of StorNext ........................................... 51  
Running the Setup Wizard...................................................................... 52  
Restoring a Previous Client Configuration........................................... 56  
Chapter 4  
Configuring StorNext  
59  
StorNext GUI .................................................................................................... 60  
Accessing the StorNext GUI.................................................................... 60  
Configuration Wizard ..................................................................................... 62  
Displaying the Configuration Wizard................................................... 63  
Using the Configuration Wizard............................................................ 63  
Configuring a Distributed LAN Client Server ............................................ 67  
StorNext 3.1.3 Installation Guide  
iv  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Contents  
Configuring a Distributed LAN Client on Linux................................. 68  
Configuring a Distributed LAN Server on Linux................................ 68  
Windows Configuration Utilities .................................................................. 72  
Client Configuration................................................................................. 73  
Disk Device Labeler.................................................................................. 83  
License Identifier....................................................................................... 86  
Simple File System Configuration.......................................................... 86  
Start File System Services ........................................................................ 88  
Stop and Remove File System Services ................................................. 88  
Stop File System Services......................................................................... 88  
Version Information ................................................................................. 88  
Check (Read-Only) a File System........................................................... 89  
File System Startup List ........................................................................... 89  
Re-initialize a File System........................................................................ 91  
Repair a File System ................................................................................. 91  
Server Administration.............................................................................. 91  
Server Configuration................................................................................ 97  
Appendix A  
Appendix B  
Uninstalling StorNext  
108  
Uninstalling StorNext on Unix and Linux ................................................. 108  
Uninstalling SNSM and SNFS .............................................................. 109  
Uninstalling the StorNext Client Software ......................................... 110  
Uninstalling StorNext on Windows............................................................ 111  
StorNext Administration Tasks  
112  
Sharing a Library Between Applications.................................................... 112  
Manually Modifying Storage Manager Configuration ............................ 114  
fs_sysparm_override Configuration File............................................. 114  
filesize.config Configuration File ......................................................... 115  
log_params Configuration File............................................................. 115  
Connecting to a StorNext Network Using Xsan 1.4.2............................... 116  
Mounting SNFS on the OSx Computer ............................................... 116  
Creating the automount.plist File ........................................................ 118  
Connecting to a StorNext Network Using Xsan 2..................................... 119  
Mounting SNFS on the Mac OS X Computer..................................... 119  
Viewing a Fibre Channel Device ................................................................. 122  
StorNext Log Rolling Administration......................................................... 123  
Changing Log Rolling Times ................................................................ 123  
StorNext 3.1.3 Installation Guide  
v
Download from Www.Somanuals.com. All Manuals Search And Download.  
Contents  
Log Rolling Options ............................................................................... 123  
Avoiding Poor System Performance........................................................... 124  
Appendix C  
Appendix D  
StorNext Files  
125  
The example.cfg File...................................................................................... 125  
Commonly Used SNFS Files ........................................................................ 132  
Quality of Service Guide  
135  
Overview......................................................................................................... 136  
Active vs. Passive.................................................................................... 136  
Supported Platforms .............................................................................. 136  
Configuration ................................................................................................. 137  
Unit of I/O............................................................................................... 137  
Converting MB/sec to I/O/sec............................................................ 137  
Real-time I/O.................................................................................................. 142  
SetRtio....................................................................................................... 143  
Oversubscription .................................................................................... 143  
Handles .................................................................................................... 143  
Ungated files............................................................................................ 144  
Calculating Available RTIO .................................................................. 145  
Callbacks ......................................................................................................... 145  
Callback Failures..................................................................................... 147  
Tokens ...................................................................................................... 148  
Failure Semantics.................................................................................... 149  
FSM Failures............................................................................................ 150  
Client Failures ......................................................................................... 150  
Client Token Releases ............................................................................ 151  
Monitoring ...................................................................................................... 151  
Sharing Disk Resources................................................................................. 152  
StorNext 3.1.3 Installation Guide  
vi  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Figures  
Figure 1  
Figure 2  
Figure 3  
Figure 4  
Figure 5  
Figure 6  
Figure 7  
Figure 8  
Figure 9  
Pre-Installation Script ................................................................ 10  
StorNext Installation Script....................................................... 13  
Configuration Menu .................................................................. 15  
StorNext Installation Status ...................................................... 17  
SNFS Installation Script............................................................. 25  
Configuration Menu .................................................................. 26  
StorNext Installation Status ...................................................... 27  
StorNext Installation Window: Remove StorNext ................ 28  
StorNext Installation Window: Install StorNext.................... 29  
Figure 10 SNFS Setup: Welcome ............................................................... 30  
Figure 11 SNFS Setup: End-User License Agreement............................ 30  
Figure 12 SNFS Setup: Customer Information ........................................ 31  
Figure 13 SNFS Setup: Choose Setup Type.............................................. 31  
Figure 14 SNFS Setup: Ready to Install .................................................... 32  
Figure 15 SNFS Setup: Finish..................................................................... 32  
Figure 16 StorNext Installation Window: Configure StorNext............. 33  
Figure 17 StorNext Configuration Window............................................. 34  
StorNext 3.1.3 Installation Guide  
vii  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Figures  
Figure 18 Import/Export Client Configuration Window...................... 35  
Figure 19 Select Platform Window............................................................ 40  
Figure 20 Download Client Software Window ....................................... 41  
Figure 21 StorNext Installation Window: Remove StorNext ................ 52  
Figure 22 StorNext Installation Window: Install StorNext.................... 53  
Figure 23 SNFS Setup: Welcome ............................................................... 53  
Figure 24 SNFS Setup: End-User License Agreement............................ 54  
Figure 25 SNFS Setup: Customer Information ........................................ 54  
Figure 26 SNFS Setup: Choose Setup Type.............................................. 55  
Figure 27 SNFS Setup: Ready to Install .................................................... 55  
Figure 28 SNFS Setup: Finish..................................................................... 56  
Figure 29 StorNext Installation Window: Configure StorNext............. 57  
Figure 30 StorNext Configuration Window............................................. 57  
Figure 31 Import/Export Client Configuration Window...................... 58  
Figure 32 StorNext Home Page: File System and Storage Manager .... 61  
Figure 33 StorNext Home Page: File System Only ................................. 61  
Figure 34 StorNext Configuration Wizard: Storage Manager............... 62  
Figure 35 StorNext Configuration Wizard: File System Only............... 63  
Figure 36 sndpscfg Configuration Utility ................................................ 69  
Figure 37 Client Configuration: Drive Mappings................................... 74  
Figure 38 Client Configuration: FS Name Servers.................................. 76  
Figure 39 Client Configuration: Authentication ..................................... 77  
Figure 40 Client Configuration: Mount Options..................................... 79  
Figure 41 Client Configuration: Syslog Level.......................................... 80  
Figure 42 Client Configuration: Cache Parameters ................................ 81  
Figure 43 Client Configuration: Distributed LAN.................................. 82  
Figure 44 Disk Device Labeler ................................................................... 84  
Figure 45 Disk Labeler Dialog Box............................................................ 85  
Figure 46 Simple File System Configuration ........................................... 87  
StorNext 3.1.3 Installation Guide  
viii  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Figures  
Figure 47 File System Startup List............................................................. 90  
Figure 48 Server Administration ............................................................... 92  
Figure 49 Server Administration: File System Properties...................... 93  
Figure 50 Server Administration: Stripe Group Properties................... 94  
Figure 51 Server Administration: Quota Properties............................... 96  
Figure 52 Configuration Administrator ................................................... 98  
Figure 53 Server Configuration: Global Settings..................................... 99  
Figure 54 Server Configuration: Disk Types.......................................... 102  
Figure 55 Server Configuration: Enter New Disk Type ....................... 103  
Figure 56 Server Configuration: Disk Definitions................................. 104  
Figure 57 Server Configuration: Stripe Groups..................................... 105  
Figure 58 StorNext Remove Main Menu................................................ 110  
Figure 59 Sharing Access to Files............................................................. 144  
Figure 60 Callback Flow for Initial RTIO Request ................................ 146  
Figure 61 Callback Retraction Example.................................................. 147  
Figure 62 Non-Real-time Token Adjustments....................................... 149  
StorNext 3.1.3 Installation Guide  
ix  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Tables  
Table 1  
Table 2  
Table 3  
Table 4  
Table 5  
Table 6  
Table 7  
Table 8  
Table 9  
Table 10  
Table 11  
Table 12  
Table 13  
Table 14  
Table 15  
Table 16  
Table 17  
Storage Manager Supported Platforms.................................... 2  
Storage Manager Hardware Requirements.............................. 3  
Required Disk LUN Labels......................................................... 6  
StorNext Support Directories ..................................................... 8  
Pre-Installation Script Recommendation Types .................... 11  
StorNext Installation Main Menu Options ............................. 14  
File System Supported Platforms............................................ 19  
File System Hardware Requirements...................................... 20  
Required Disk LUN Labels....................................................... 22  
SNFS Installation Main Menu Options ................................... 25  
StorNext Client Supported Platforms .................................... 37  
Distributed LAN Server Parameters ....................................... 70  
Distributed LAN Client and Server Commands ................... 71  
Client Configuration: Drive Mappings................................... 74  
Client Configuration: FS Name Servers.................................. 76  
Client Configuration: Authentication ..................................... 77  
Client Configuration: Distributed LAN.................................. 82  
StorNext 3.1.3 Installation Guide  
x
Download from Www.Somanuals.com. All Manuals Search And Download.  
Tables  
Table 18  
Table 19  
Table 20  
Table 21  
Table 22  
Table 23  
Table 24  
Table 25  
Table 26  
Table 27  
Table 28  
Disk Labeler Dialog Box............................................................ 85  
Simple File System Configuration ........................................... 87  
File System Startup List............................................................. 90  
Server Administration: File System Properties...................... 93  
Server Administration: Stripe Group Properties................... 95  
Server Administration: Quota Properties............................... 96  
Server Configuration: Global Settings..................................... 99  
Server Configuration: Enter New Disk Type ....................... 103  
Server Configuration: Disk Definitions................................. 104  
Server Configuration: Stripe Groups..................................... 106  
QOS Configuration Keywords ............................................... 138  
StorNext 3.1.3 Installation Guide  
xi  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Preface  
StorNext provides high performance data sharing and intelligent  
archiving that is compatible with an industry-leading range of operating  
systems, server platforms, and storage devices.  
StorNext includes two main components:  
• StorNext File System (SNFS) is high performance data sharing  
software that lets applications on multiple operating systems access a  
single data set.  
• StorNext Storage Manger (SNSM) is an intelligent, policy-based data  
mover that automatically moves and locates data across multiple  
storage tiers.  
You can choose to install both StorNext File System and Storage Manager,  
or install StorNext File System only. In addition, StorNext includes client  
software that allows client systems to mount and work with StorNext file  
systems.  
StorNext 3.1.3 Installation Guide  
xii  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Preface  
Audience  
Audience  
This document is intended for service professionals and system  
administrators who install StorNext software. The installer should have  
strong familiarity with the operating system on which StorNext is  
installed.  
Only service professionals, experienced StorNext users, or individuals  
who have successfully completed StorNext training should configure  
StorNext. Attempting to configure StorNext without proper experience or  
training can affect system performance and may result in data loss.  
Purpose  
This document provides information about installing and configuring  
StorNext. The following topics are covered:  
• System requirements  
• Pre-installation tasks  
• Installation  
• Configuration  
• Uninstalling StorNext  
StorNext 3.1.3 Installation Guide  
xiii  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Preface  
Document Organization  
Document Organization  
This document contains the following chapters:  
• Chapter 1, “Installing StorNext File System and Storage Manager,”  
provides system requirements, pre-installation information, and  
instructions for installing StorNext File System and Storage Manger  
on a metadata controller (MDC).  
• Chapter 2, “Installing StorNext File System,” provides system  
requirements, pre-installation information, and instructions for  
installing StorNext File System (without Storage Manager) on a  
metadata controller (MDC).  
• Chapter 3, “Installing the StorNext Client,” provides system  
requirements, pre-installation information, and instructions for  
installing the StorNext client software.  
• Chapter 4, “Configuring StorNext,” describes how to use the  
StorNext configuration wizard and the Windows configuration  
utilities to create a basic StorNext configuration, and how to  
configure a distributed LAN client or server.  
• Appendix A, “Uninstalling StorNext,” describes how to remove  
StorNext software from a server or client system.  
StorNext 3.1.3 Installation Guide  
xiv  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Preface  
Notational Conventions  
Notational Conventions  
This manual uses the following conventions:  
Convention  
Example  
./install.stornext  
User input is shown in Arial regular  
font.  
User input variables are enclosed in  
angle brackets and are shown in  
Arial italic font.  
mkdir -p <mount point>  
For UNIX and Linux commands, the ./install.stornext  
command prompt is implied.  
is the same as  
# ./install.stornext  
File and directory names, menu  
commands, button names, and  
window names are shown in Arial  
bold font.  
/stornext/snfs1  
Admin > Download Client  
Software  
Menu names separated by arrows  
indicate a sequence of menus to be  
navigated.  
The following formats indicate important information:  
Note: Notes emphasize important information related to the main  
topic.  
Tech Tip: Tech Tips provide technical information which may be  
helpful in performing the procedure.  
Caution: Cautions indicate potential hazards to equipment and are  
included to prevent damage to equipment.  
StorNext 3.1.3 Installation Guide  
xv  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Preface  
Related Documents  
Warning: Warnings indicate potential hazards to personal safety and  
are included to prevent injury.  
Related Documents  
Documents related to StorNext are shown below:  
Quantum StorNext Documentation  
0
Document No. Document Title  
Document Description  
6-01658-06  
StorNext User’s Guide  
Provides in-depth  
information about using  
StorNext to create and  
manage StorNext File  
Systems.  
6-01376-10  
6-01620-09  
6-01688-06  
StorNext File System  
Tuning Guide  
Provides information for  
maximizing file system  
performance.  
StorNext Upgrade  
Guide  
Provides procedures for  
upgrading from earlier  
versions of StorNext.  
StorNext CLI Reference Provides procedures for  
Guide  
performing common tasks  
using the command line  
interface.  
StorNext 3.1.3 Installation Guide  
xvi  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Preface  
Contacting Quantum  
Document No. Document Title  
Document Description  
6-01564-02  
AMASS Conversion  
Guide  
Provides information about  
migrating systems running  
AMASS to StorNext.  
6-00431-23  
StorNext 3.1.3 Release  
Notes  
Includes the latest product  
information, fixes, and  
issues.  
Contacting Quantum  
More information about this product is available on the Quantum Service  
and Support website at www.quantum.com/ServiceandSupport. The  
Quantum Service and Support website contains a collection of  
information, including answers to frequently asked questions (FAQs).  
You can also access software, firmware, and drivers through this site.  
To request a software upgrade, visit www.quantum.com/  
ServiceandSupport/Upgrade/Index.aspx. For further assistance, or if  
training is desired, contact Quantum Global Services:  
+1 800-284-5101 Option 5  
00800 9999 3822  
North America  
EMEA  
www.quantum.com/OSR  
Online Service and  
Support  
www.quantum.com/ServiceandSupport  
World Wide Web  
(Local numbers for specific countries are listed on the Quantum Service  
and Support Website.)  
StorNext 3.1.3 Installation Guide  
xvii  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 1  
1Installing StorNext File System  
and Storage Manager  
This chapter describes how to install StorNext File System (SNFS) and  
StorNext Storage Manager (SNSM) on a metadata controller (MDC).  
Install both SNFS and SNSM for storage systems that require policy-  
based data movement (for example, systems that include tape drives or  
libraries).  
To ensure successful operation, do the following tasks before installing  
StorNext:  
• Make sure the MDC meets all operating system and hardware  
requirements (see Storage Manager System Requirements).  
• Make sure all storage devices are correctly configured and are visible  
to the MDC (see Getting Ready to Install on page 5)  
• (Optional) Run the pre-installation script to check for available disk  
space and view recommended locations for support directories (see  
Pre-Installation Script on page 8).  
When you are ready to install StorNext File System and Storage Manager  
on the MDC, run the installation script (see StorNext Installation Script  
on page 12).  
Note: To install only StorNext File System (without Storage  
Manager), see Chapter 2, “Installing StorNext File System.” To  
install the StorNext client software, see Chapter 3, “Installing  
the StorNext Client.”  
StorNext 3.1.3 Installation Guide  
1
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 1 Installing StorNext File System and Storage Manager  
Storage Manager System Requirements  
Storage Manager System Requirements  
To run StorNext File System and Storage Manager, the metadata  
controller must meet all operating system, hardware, and LAN  
requirements.  
Operating System  
Requirements  
The operating systems, kernel versions, and hardware platforms  
supported by StorNext SNFS and SNSM are presented in Table 1. Make  
sure the MDC uses a supported operating system and platform, and if  
necessary update to a supported kernel version before installing  
StorNext.  
1
Table 1 Storage Manager  
Supported Platforms  
Operating System  
Kernel  
Platform  
Red Hat Enterprise  
Linux 4  
2.6.9-55.EL (Update 5)  
2.6.9-67.EL (Update 6)  
2.6.9-78.EL (Update 7)  
x86 32-bit  
x86 64-bit  
Itanium 64-bit  
Red Hat Enterprise  
Linux 5  
2.6.18-53.EL (Update 1)  
2.6.18-92.EL (Update 2)  
x86 64-bit  
SUSE Linux Enterprise 2.6.16.21-0.8  
Server 10  
x86 32-bit  
x86 64-bit  
Itanium 64-bit  
2.6.16-46-0.12 (SP1)  
2.6.16-60-0.27 (SP2)  
Generic 120011-14  
Sun Solaris 10  
SPARC 64-bit  
The minimum amount of RAM and available hard disk space required to  
run StorNext SNFS and SNSM are presented in Table 2. Because support  
files (such as database and journal files) are stored on the MDC, the  
amount of local disk space that is required increases with the number of  
data files stored on StorNext file systems.  
Hardware Requirements1  
If necessary, upgrade the RAM and local disk storage in the MDC to meet  
the minimum requirements before installing StorNext.  
StorNext 3.1.3 Installation Guide  
2
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 1 Installing StorNext File System and Storage Manager  
Storage Manager System Requirements  
Note: The RAM requirements in Table 2 are for running StorNext  
File System and Storage Manager only. Running additional  
software (including the StorNext client software) requires  
additional RAM.  
Table 2 Storage Manager  
Hardware Requirements  
File Systems  
RAM  
Disk Space  
1–4*  
2 GB  
4 GB  
• For application binaries, log files,  
and documentation: up to 30GB  
(depending on system activity)  
5–8**  
• For support directories: 3 GB per  
million files stored  
• For metadata: 25GB minimum  
*
Two CPUs recommended for best performance.  
** Two CPUs required for best performance.  
Note: If a file system uses deduplicated storage disks (DDisks), note  
the following additional requirements:  
• Requires 2 GB RAM per DDisk in addition to the base RAM  
noted in Table 2.  
• Requires an additional 5GB of disk space for application  
binaries and log files.  
• Deduplication is supported only for file systems running on  
a Linux operating system (x86 32-bit or x86 64-bit).  
• An Intel Pentium 4 or later processor (or an equivalent  
AMD processor) is required. For best performance,  
Quantum recommends an extra CPU per blockpool.  
StorNext 3.1.3 Installation Guide  
3
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 1 Installing StorNext File System and Storage Manager  
Storage Manager System Requirements  
Partitioning Local Hard Disks  
StorNext can be installed on any local file system (including the root file  
1
system) on the MDC. However, for optimal performance, as well as to aid  
disaster recovery, follow these recommendations:  
• Avoid installing StorNext on the root file system.  
• Partition local hard disks so that the MDC has four available local file  
systems (other than the root file system) located on four separate  
hard drives.  
Note: You can run the pre-installation script to help determine the  
estimated size of and optimal location for StorNext support  
directories. For more information, see Pre-Installation Script  
on page 8.  
The following LAN requirements must be met before installing StorNext  
on the MDC:  
LAN Requirements  
1
• In cases where gigabit networking hardware is used and maximum  
StorNext performance is required, a separate, dedicated switched  
Ethernet LAN is recommended for the StorNext metadata network. If  
maximum StorNext performance is not required, shared gigabit  
networking is acceptable.  
• A separate, dedicated switched Ethernet LAN is mandatory for the  
metadata network if 100 Mbit/s or slower networking hardware is  
used.  
• The MDC and all clients must have static IP addresses.  
Verify network connectivity with pings, and also verify entries in the  
/etc/hosts file.  
• If using Gigabit Ethernet, disable jumbo frames and TOE (TCP  
offload engine).  
Note: StorNext does not support file system metadata on the same  
network as iSCSI, NFS, CIFS, or VLAN data when 100 Mbit/s  
or slower networking hardware is used.  
StorNext 3.1.3 Installation Guide  
4
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 1 Installing StorNext File System and Storage Manager  
Getting Ready to Install  
Getting Ready to Install  
Before installing StorNext SNFS and SNSM, complete the following tasks  
to ensure successful installation:  
• Correctly configure all storage devices (see Configuring Storage  
Devices).  
• If using LUNs larger than 1 TB, decide on a label type and install any  
necessary operating system patches (see Planning for LUNs Larger  
than 1 TB).  
• (Linux only) Install the kernel source code (see Installing the Linux  
Kernel Source Code on page 7).  
Configuring Storage  
Devices  
Before installing StorNext SNFS and SNSM, make sure that all LUNs are  
visible to the MDC. (A LUN, or logical unit number, is a logical device  
that corresponds to one or more disks, drives, or storage devices.)  
1
If there are any connection issues, resolve them before installing  
StorNext. For assistance in configuring storage devices, refer to the  
documentation that came with the storage device, or contact the  
manufacturer.  
Note: LUNs that you plan to use in the same stripe group must be  
the same size. Consider this when configuring storage devices.  
(For more information about stripe groups, see the StorNext  
3.1.3 User’s Guide.)  
Caution: StorNext does not support the connection of multiple  
devices through fibre channel hubs. Multiple devices must  
be connected using fibre channel switches.  
Planning for LUNs Larger  
StorNext supports LUNs greater than 1 TB in size if they are allowed by  
the operating system. To enable support for 1 TB or larger LUNs, all  
StorNext LUNs must be correctly labeled according to the requirements  
than 1 TB  
1
StorNext 3.1.3 Installation Guide  
5
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 1 Installing StorNext File System and Storage Manager  
Getting Ready to Install  
of the operating system running on the MDC as well as the operating  
system running on all connected clients. Disk LUNs can have one of three  
labels: VTOC, EFI, or sVTOC (short VTOC).  
Required disk LUN label settings based on operating system and LUN  
size are presented in Table 3. Before installing StorNext, decide what  
label type will be used, and then install any required operating system  
patches or updates (for both MDC and client) as indicated in the notes for  
Table 3.  
Note: After labeling a disk LUN, you must reboot systems running  
Solaris before they can access the disk LUN.  
Table 3 Required Disk LUN  
Labels  
Operating  
System  
Label for  
LUNs < 1 TB  
Label for  
LUNs 1–2 TB  
Label for  
LUNs > 2 TB  
a
Windows XP  
VTOC, EFI  
VTOC, EFI  
VTOC, EFI  
VTOC, EFI  
EFI, sVTOC  
EFI, sVTOC  
Windows 2003  
Server  
Linux 2.6  
Kernel  
VTOC, EFI  
VTOC, EFI  
VTOC, EFI  
VTOC, EFI  
EFI, sVTOC  
Linux 2.4  
Kernel  
Not supported  
b
Solaris 9  
VTOC, EFI  
VTOC, EFI  
VTOC, EFI  
VTOC, EFI  
VTOC  
EFI  
Not supported  
EFI  
c
Solaris 10  
EFI  
a
HP-UX  
VTOC, EFI  
VTOC, EFI  
VTOC  
EFI, sVTOC  
EFI, sVTOC  
Not supported  
EFI, sVTOC  
d
IBM AIX  
SGI IRIX  
Apple Xsan 1.3 VTOC, EFI  
(MacOS X 10.4  
VTOC, EFI  
Tiger)  
Apple Xsan 1.3 VTOC, EFI  
(MacOS X 10.3  
Panther)  
VTOC, EFI  
EFI, sVTOC  
a
StorNext 3.1.3 Installation Guide  
6
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 1 Installing StorNext File System and Storage Manager  
Getting Ready to Install  
Operating  
System  
Label for  
LUNs < 1 TB  
Label for  
LUNs 1–2 TB  
Label for  
LUNs > 2 TB  
Apple Xsan  
1.2  
VTOC  
VTOC  
sVTOC  
a
a. Supports only the first 2 TB of LUNs larger than 2 TB.  
b. Support for EFI labels requires the Multiterabyte Disk Support patch.  
c. Support for 2 TB or larger LUNs requires Solaris 10 Update 2 (06/06).  
d. Supports only LUNs of 2.2 TB or less.  
Note: For best results, Quantum recommends using persistent  
binding for disk LUNs. For more information, contact the  
vendor of your HBA (host bus adapter).  
Installing the Linux  
Kernel Source Code  
For management servers running Red Hat Enterprise Linux version 4 or  
5, before installing SNFS and SNSM you must first install the kernel  
header files (shipped as the kernel-devel or kernel-devel-smp RPM,  
depending on your Linux distribution).  
1
For servers running SUSE Linux Enterprise Server, you must install the  
first kernel source code (shipped as the kernel-source RPM). StorNext  
will not operate correctly if these packages are not installed. You can  
install the kernel header files or kernel source RPMs by using the  
installation disks for your operating system.  
Verifying Hostname  
Length  
The maximum hostname length for a StorNext server is limited to 25  
characters. Before you begin the installation, verify that the destination  
hostname is not longer than 25 characters. (The hostname is read during  
the installation process, and if the hostname is longer than 25 characters  
the installation process could fail.)  
1
StorNext 3.1.3 Installation Guide  
7
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 1 Installing StorNext File System and Storage Manager  
Pre-Installation Script  
Pre-Installation Script  
The StorNext pre-installation script (snPreInstall) is included on the  
StorNext installation CD. When you run snPreInstall, you are prompted  
for information about your system. The pre-installation script uses this  
information to estimate the amount of local disk space required for SNFS  
and SNSM support directories. In addition, the script recommends the  
optimal locations for support directories.  
StorNext uses five directories to store application support information.  
These directories are stored locally on the metadata controller, except for  
the Backup directory, which is stored on the managed file system.  
The StorNext support directories are described in Table 4.  
Table 4 StorNext Support  
Directories  
Support Directory  
Description  
Database  
Records information about where and how  
data files are stored.  
/adic/database  
Journal  
Records changes made to the database.  
/adic/database_jnl  
Mapping  
Contains index information that enables quick  
searches on the file system.  
/adic/mapping_dir  
Metadata  
Stores metadata dumps (backups of file  
metadata).  
/adic/database_meta  
Backup  
Contains configuration files and support data  
required for disaster recovery.  
/backup  
Before running the pre-installation script, be prepared to answer the  
following questions:  
Before You Begin  
1
• Is this an upgrade installation?  
• What local file systems can be used to store support information?  
• Which version of StorNext will be installed?  
StorNext 3.1.3 Installation Guide  
8
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 1 Installing StorNext File System and Storage Manager  
Pre-Installation Script  
• What is the maximum number of directories expected (in millions)?  
• What is the maximum number of files expected (in millions)?  
• How many copies will be stored for each file?  
• How many versions will be retained for each file?  
Note: Keep in mind that storage needs typically grow rapidly.  
Consider increasing the maximum number of expected  
directories and files by a factor of 2.5x to ensure room for  
future growth.  
Note: The pre-installation script ignores unmounted file systems.  
Before running snPreInstall, be sure to mount all local file  
systems that will hold StorNext support information.  
To run the pre-installation script, use the StorNext installation CD.  
Running snPreInstall  
1
1 Log on to the MDC as root.  
2 Mount the StorNext installation CD and change to the CD root  
directory.  
3 List the installation directories on the CD. At the command prompt,  
type:  
ls -l  
4 Identify the correct installation directory for your operating system  
and hardware platform, and then change to that directory.  
For example, for Red Hat Linux 4 running on an x86 64-bit platform,  
change to the RedHat40AS_26x86_64 directory.  
5 Run the script. At the command prompt, type:  
./snPreInstall  
The pre-installation script runs (figure 1).  
StorNext 3.1.3 Installation Guide  
9
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 1 Installing StorNext File System and Storage Manager  
Pre-Installation Script  
Figure 1 Pre-Installation Script  
6 Follow the onscreen instructions, and answer each question when  
prompted.  
The script outputs results based on the information you entered.  
Interpreting snPreInstall  
Output  
After you enter all requested information, the pre-installation script  
outputs the following results:  
1
• Estimated disk space required for each support directory.  
• Recommended file system location for each support directory.  
Tech Tip: For optimal performance, each support directory  
(other than the Backup directory) should be located on  
its own local file system, and each local file system  
should reside on a separate physical hard disk in the  
MDC.  
There are three types of directory recommendations, as indicated by the  
text preceding the recommendation. The three types of recommendations  
are described in Table 5.  
StorNext 3.1.3 Installation Guide  
10  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 1 Installing StorNext File System and Storage Manager  
Pre-Installation Script  
Table 5 Pre-Installation Script  
Recommendation Types  
Type  
Description  
RECOMMEND  
NOTE  
The suggested directory locations will result in  
optimal system performance.  
The suggested directory locations are valid but  
system performance will not be optimal.  
SPACE  
Additional hard disk space is required to store  
the required support directories.  
The pre-installation script bases directory location recommendations on  
the following criteria:  
• To aid disaster recovery, the Database and Journal directories should  
be located on different file systems.  
• For optimal performance, the Metadata directory should not be  
located on the same file system as (in order of priority) the Journal,  
Database, or Mapping directory.  
Note: Do not change the location of support directories manually.  
Instead, use the installation script to specify the location for  
support directories. For more information, see StorNext  
Installation Script.  
StorNext 3.1.3 Installation Guide  
11  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 1 Installing StorNext File System and Storage Manager  
StorNext Installation Script  
StorNext Installation Script  
When you are ready to install StorNext, use the StorNext installation  
script to install StorNext File System and Storage Manager on the  
metadata controller. The installation script also installs the client software  
on the MDC.  
Launching the StorNext  
Installation Script  
The StorNext installation script lets you choose installation configuration  
options and install StorNext. To launch the script, use the correct  
StorNext installation CD for your operating system.  
1
1 Log on to the MDC as root.  
2 Mount the StorNext installation CD and change to the CD root  
directory.  
Note: When you mount a CD in a Red hat 4 or 5 system, CDs are  
mounted by default with a noexec (non-executable) option  
which prevents you from proceeding with the installation.  
For Red Hat users only, before proceeding you must  
remount the CD by typing mount -o remount, exec ...  
3 List the installation directories on the CD. At the command prompt,  
type:  
ls -l  
4 Identify the correct installation directory for your operating system  
and hardware platform, and then change to that directory.  
For example, for Red Hat Linux 4 running on an x86 64-bit platform,  
change to the RedHat40AS_26x86_64 directory.  
5 Run the script. At the command prompt, type:  
./install.stornext  
The installation script runs (figure 2).  
StorNext 3.1.3 Installation Guide  
12  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 1 Installing StorNext File System and Storage Manager  
StorNext Installation Script  
Figure 2 StorNext Installation  
Script  
StorNext 3.1.3 Installation Guide  
13  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 1 Installing StorNext File System and Storage Manager  
StorNext Installation Script  
6 Type the number corresponding to a menu option and press <Enter>.  
Installation menu options are described in Table 6.  
Table 6 StorNext Installation  
Main Menu Options  
Menu Option  
Description  
1
Change installation options, including the  
location of application directories and the  
default media type (see Changing Installation  
Configuration Options).  
2
Install StorNext using the installation options  
specified on the Configuration Menu (see  
Performing an Installation Operation on page  
17).  
3
4
View the status of an installation operation that  
is currently in progress.  
Exit the StorNext installation script.  
Changing Installation  
Configuration Options 1  
Use the Configuration Menu to change StorNext installation options. You  
can specify the location of application and support directories and change  
the default media type for storage devices.  
On the Main Menu, type 1 and press <Enter>. The Configuration Menu  
appears (figure 3).  
StorNext 3.1.3 Installation Guide  
14  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 1 Installing StorNext File System and Storage Manager  
StorNext Installation Script  
Figure 3 Configuration Menu  
Changing Application Directory Locations  
1
When you first enter the Configuration Menu, it displays recommended  
locations for StorNext application directories based on the available file  
systems detected by the installation script. To accept the recommended  
directory locations and return to the Main Menu, press <Enter>.  
Alternately, customize the installation by specifying the file systems  
where application and support files are stored.  
1 On the Configuration Menu, type the number that corresponds to the  
directory location you want to customize (1–14), and then press  
<Enter>.  
A list of available local file systems is shown.  
2 To change the file system where the directory is located, type the  
name of the file system and press <Enter>.  
StorNext 3.1.3 Installation Guide  
15  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 1 Installing StorNext File System and Storage Manager  
StorNext Installation Script  
3 To confirm the change, type yes and press <Enter>.  
To customize additional directory locations, repeat steps 1–3.  
4 When you are done customizing the installation, press <Enter> to  
return to the Main Menu.  
Note: To help determine the optimal location for StorNext support  
directories, use the StorNext pre-installation script. For more  
information, see Pre-Installation Script on page 8.  
Changing the Default Media Type  
1
If you do not specify a different media type, the StorNext installation  
script selects LTO as the default media type for storage devices. If storage  
devices in your system use a different media type, change the default  
media type before installing StorNext.  
1 On the Configuration Menu, type 15 and press <Enter>.  
A list of valid default media types is shown. The valid media types  
are: DDISK, SDISK, LTO, LTOW, 3590, 3592, 9840, 9940, AITW, AIT,  
DLT4, and T10K.  
Note: The DDISK option is available only for MDCs running  
x86 (32-bit or 64-bit) versions of Linux.  
2 Type the correct default media type for storage devices in your  
system and press <Enter>.  
3 To confirm the change, type yes and press <Enter>.  
4 When you are done customizing the installation, press <Enter> to  
return to the Main Menu.  
Note: For multiple libraries or systems with mixed media types,  
specify the media type used in the primary backup.  
StorNext 3.1.3 Installation Guide  
16  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 1 Installing StorNext File System and Storage Manager  
StorNext Installation Script  
Performing an  
Installation Operation  
To install StorNext using the options specified on the Configuration  
Menu, perform an installation operation.  
1
1 On the Main Menu, type 2 and press <Enter>.  
The StorNext installation script runs (figure 4). The script displays  
the current progress of the installation.  
Figure 4 StorNext Installation  
Status  
2
When the installation is complete, press <Enter> to return to the Main  
Menu.  
3 To exit the installation script, type 4 and press <Enter>.  
Note: The script displays the URL at which the MDC can be  
accessed. Make a note of this information.  
You can now access StorNext File System and Storage Manager, and run  
the configuration wizard. For more information, see Chapter 4,  
“Configuring StorNext.”  
StorNext 3.1.3 Installation Guide  
17  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 2  
2Installing StorNext File System  
This chapter describes how to install StorNext File System (SNFS) on a  
metadata controller (MDC). Install SNFS to create data sets that can be  
shared by clients and applications running on multiple operating  
systems.  
To ensure successful operation, do the following tasks before installing  
StorNext:  
• Make sure the MDC meets all operating system and hardware  
requirements (see File System Requirements).  
• Make sure all storage devices are correctly configured and are visible  
to the MDC (see Getting Ready to Install on page 21).  
When you are ready, install StorNext File System on the MDC using the  
appropriate method for your operating system (see Installing StorNext  
File System on Linux or Unix on page 24 or Installing StorNext File  
System on Windows on page 27).  
Note: To install both StorNext File System and StorNext Storage  
Manager, see Chapter 1, “Installing StorNext File System and  
Storage Manager.” To install the StorNext client software, see  
Chapter 3, “Installing the StorNext Client.”  
StorNext 3.1.3 Installation Guide  
18  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 2 Installing StorNext File System  
File System Requirements  
File System Requirements  
To run StorNext File System, the metadata controller must meet all  
operating system and hardware requirements.  
Operating System  
Requirements  
The operating systems, releases and kernels, and hardware platforms  
supported by StorNext SNFS are presented in Table 7. Make sure the  
MDC uses a supported operating system and platform, and if necessary  
update to a supported release or kernel version before installing  
StorNext.  
2
Table 7 File System  
Supported Platforms  
Operating System  
Release or Kernel  
Platform  
Windows 2003 Server  
SP2  
x86 32-bit  
x86 64-bit  
Windows 2008 Server  
SP1  
x86 32-bit  
x86 64-bit  
Red Hat Enterprise  
Linux 4  
2.6.9-55.EL (Update 5)  
2.6.9-67.EL (Update 6)  
2.6.9-78.EL (Update 7)  
x86 32-bit  
x86 64-bit  
Itanium 64-bit  
Red Hat Enterprise  
Linux 5  
2.6.18-53.EL (Update 1)  
2.6.18-92.EL (Update 2)  
x86 64-bit  
SUSE Linux Enterprise 2.6.16.21-0.8  
Server 10  
x86 32-bit  
x86 64-bit  
Itanium 64-bit  
2.6.16.46-0.12 (SP1)  
2.6.16-60-0.27 (SP2)  
Generic 120011-14  
Sun Solaris 10  
SPARC 64-bit  
StorNext 3.1.3 Installation Guide  
19  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 2 Installing StorNext File System  
File System Requirements  
The minimum amount of RAM and available hard disk space required to  
run StorNext SNFS are presented in Table 8.  
Hardware Requirements2  
If necessary, upgrade the RAM and local disk storage in the MDC to meet  
the minimum requirements before installing StorNext.  
Note: The RAM requirements in Table 8 are for running StorNext  
File System only. Running additional software (including the  
StorNext client software) requires additional RAM.  
File Systems  
RAM  
Disk Space  
Table 8 File System Hardware  
Requirements  
1–4*  
2 GB  
4 GB  
2 GB  
4 GB  
5–8**  
*
Two CPUs recommended for best performance.  
** Two CPUs required for best performance.  
Note: On 32-bit versions of Windows, for best performance, run  
SNFS on a dedicated system. Do not run other applications on  
the MDC.  
The following LAN requirements must be met before installing StorNext  
on the MDC:  
LAN Requirements  
2
• In cases where gigabit networking hardware is used and maximum  
StorNext performance is required, a separate, dedicated switched  
Ethernet LAN is recommended for the StorNext metadata network. If  
maximum StorNext performance is not required, shared gigabit  
networking is acceptable.  
• A separate, dedicated switched Ethernet LAN is mandatory for the  
metadata network if 100 Mbit/s or slower networking hardware is  
used.  
• The MDC and all clients must have static IP addresses.  
Verify network connectivity with pings, and also verify entries in the  
/etc/hosts file.  
StorNext 3.1.3 Installation Guide  
20  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 2 Installing StorNext File System  
Getting Ready to Install  
• If using Gigabit Ethernet, disable jumbo frames and TOE (TCP  
offload engine).  
Note: StorNext does not support file system metadata on the same  
network as iSCSI, NFS, CIFS, or VLAN data when 100 Mbit/s  
or slower networking hardware is used.  
Getting Ready to Install  
Before installing StorNext SNFS, complete the following tasks to ensure  
successful installation:  
• Correctly configure all storage devices (see Configuring Storage  
Devices on page 21).  
• If using LUNs larger than 1 TB, decide on a label type and install any  
necessary operating system patches (see Planning for LUNs Larger  
than 1 TB on page 22).  
• (Linux only) Install the kernel source code (see Installing the Linux  
Kernel Source Code on page 23).  
Configuring Storage  
Devices  
Before installing StorNext SNFS, make sure that all LUNs are visible to  
the MDC. (A LUN, or logical unit number, is a logical device that  
corresponds to one or more disks, drives, or storage devices.)  
2
If there are any connection issues, resolve them before installing  
StorNext. For assistance in configuring storage devices, refer to the  
documentation that came with the storage device, or contact the  
manufacturer.  
Note: LUNs that you plan to use in the same stripe group must be  
the same size. Consider this when configuring storage devices.  
(For more information about stripe groups, see the StorNext  
3.1.3 User’s Guide.)  
StorNext 3.1.3 Installation Guide  
21  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 2 Installing StorNext File System  
Getting Ready to Install  
Caution: StorNext does not support the connection of multiple  
devices through fibre channel hubs. Multiple devices must  
be connected using fibre channel switches.  
Planning for LUNs Larger  
StorNext supports LUNs greater than 1 TB in size if they are allowed by  
the operating system. To enable support for 1 TB or larger LUNs, all  
StorNext LUNs must be correctly labeled according to the requirements  
of the operating system running on the MDC as well as the operating  
system running on all connected clients. Disk LUNs can have one of three  
labels: VTOC, EFI, or sVTOC (short VTOC).  
than 1 TB  
2
Required disk LUN label settings based on operating system and LUN  
size are presented in Table 9. Before installing StorNext, decide what  
label type will be used, and then install any required operating system  
patches or updates (for both MDC and client) as indicated in the notes for  
Table 9.  
Note: After labeling a disk LUN, you must reboot systems running  
Solaris before they can access the disk LUN.  
Table 9 Required Disk LUN  
Labels  
Operating  
System  
Label for  
LUNs < 1 TB  
Label for  
LUNs 1–2 TB  
Label for  
LUNs > 2 TB  
a
Windows XP  
VTOC, EFI  
VTOC, EFI  
VTOC, EFI  
VTOC, EFI  
EFI, sVTOC  
EFI, sVTOC  
Windows 2003  
Server  
Linux 2.6  
Kernel  
VTOC, EFI  
VTOC, EFI  
VTOC, EFI  
VTOC, EFI  
EFI, sVTOC  
Linux 2.4  
Kernel  
Not supported  
b
Solaris 9  
VTOC, EFI  
VTOC, EFI  
VTOC, EFI  
EFI  
Not supported  
EFI  
c
Solaris 10  
EFI  
a
HP-UX  
VTOC, EFI  
EFI, sVTOC  
StorNext 3.1.3 Installation Guide  
22  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 2 Installing StorNext File System  
Getting Ready to Install  
Operating  
System  
Label for  
LUNs < 1 TB  
Label for  
LUNs 1–2 TB  
Label for  
LUNs > 2 TB  
d
IBM AIX  
VTOC, EFI  
VTOC  
VTOC, EFI  
VTOC  
EFI, sVTOC  
Not supported  
EFI, sVTOC  
SGI IRIX  
Apple Xsan 1.3 VTOC, EFI  
(MacOS X 10.4  
VTOC, EFI  
Tiger)  
Apple Xsan 1.3 VTOC, EFI  
(MacOS X 10.3  
Panther)  
VTOC, EFI  
VTOC  
EFI, sVTOC  
sVTOC  
a
Apple Xsan  
1.2  
VTOC  
a
a. Supports only the first 2 TB of LUNs larger than 2 TB.  
b. Support for EFI labels requires the Multiterabyte Disk Support patch.  
c. Support for 2 TB or larger LUNs requires Solaris 10 Update 2 (06/06).  
d. Supports only LUNs of 2.2 TB or less.  
Note: For best results, Quantum recommends using persistent  
binding for disk LUNs. For more information, contact the  
vendor of your HBA (host bus adapter).  
Installing the Linux  
Kernel Source Code  
For MDCs running Red Hat Linux or SUSE Linux Enterprise Server you  
must install the kernel source code as well as all tools required to compile  
the kernel before installing SNFS. StorNext will not operate correctly if  
the kernel source code is not installed.  
2
The kernel source code can be installed using the installation disks for  
your operating system.  
StorNext 3.1.3 Installation Guide  
23  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 2 Installing StorNext File System  
Installing StorNext File System on Linux or Unix  
Installing StorNext File System on Linux or Unix  
When you are ready to install StorNext, use the SNFS installation script to  
install StorNext File System on a metadata controller running Linux or  
Unix. The installation script also installs the client software on the MDC.  
StorNext can be installed on any local file system (including the root file  
system) on the MDC. However, for optimal performance, avoid installing  
StorNext on the root file system.  
Launching the SNFS  
Installation Script  
The SNFS installation script lets you choose installation configuration  
options and install StorNext. To launch the script, use the correct  
StorNext installation CD for your operating system.  
2
1 Log on to the MDC as root.  
2 Mount the StorNext installation CD and change to the CD root  
directory.  
Note: When you mount a CD in a Red hat 4 or 5 system, CDs are  
mounted by default with a noexec (non-executable) option  
which prevents you from proceeding with the installation.  
For Red Hat users only, before proceeding you must  
remount the CD by typing mount -o remount, exec ...  
3 List the installation directories on the CD. At the command prompt,  
type:  
ls -l  
4 Identify the correct installation directory for your operating system  
and hardware platform, and then change to that directory.  
For example, for Red Hat Linux 4 running on an x86 64-bit platform,  
change to the RedHat40AS_26x86_64 directory.  
5 Run the script. At the command prompt, type:  
./install.snfs  
The installation script runs (figure 5).  
StorNext 3.1.3 Installation Guide  
24  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 2 Installing StorNext File System  
Installing StorNext File System on Linux or Unix  
Figure 5 SNFS Installation  
Script  
6 Type the number corresponding to a menu option and press <Enter>.  
Installation menu options are described in Table 10.  
Table 10 SNFS Installation  
Main Menu Options  
Menu Option  
Description  
1
Change installation options for the location of  
application directories (see Changing  
Installation Configuration Options on page 25).  
2
Install StorNext using the installation options  
specified on the Configuration Menu (see  
Performing an Installation Operation on page  
26).  
3
4
View the status of an installation operation that  
is currently in progress.  
Exit the SNFS installation script.  
Changing Installation  
Configuration Options 2  
Use the Configuration Menu to change the location of application  
directories.  
On the Main Menu, type 1 and press <Enter>. The Configuration Menu  
appears (figure 6).  
StorNext 3.1.3 Installation Guide  
25  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 2 Installing StorNext File System  
Installing StorNext File System on Linux or Unix  
Figure 6 Configuration Menu  
When you first enter the Configuration Menu, it displays recommended  
locations for StorNext application directories based on the available file  
systems detected by the installation script. To accept the recommended  
directory locations and return to the Main Menu, press <Enter>.  
Alternately, customize the installation by specifying the file systems  
where application and support files are stored.  
1 On the Configuration Menu, type the number that corresponds to the  
directory location you want to customize (1–6), and then press  
<Enter>.  
A list of available local file systems is shown.  
2 To change the file system where the directory is located, type the  
name of the file system and press <Enter>.  
3 To confirm the change, type yes and press <Enter>.  
To customize additional directory locations, repeat steps 1–3.  
4 When you are done customizing the installation, press <Enter> to  
return to the Main Menu.  
Performing an  
Installation Operation  
To install StorNext using the options specified on the Configuration  
Menu, perform an installation operation.  
2
1 On the Main Menu, type 2 and press <Enter>.  
The installation script runs (figure 7). The script displays the current  
progress of the installation.  
StorNext 3.1.3 Installation Guide  
26  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 2 Installing StorNext File System  
Installing StorNext File System on Windows  
Figure 7 StorNext Installation  
Status  
2
When the installation is complete, press <Enter> to return to the Main  
Menu.  
3 To exit the installation script, type 4 and press <Enter>.  
Note: The script displays the URL at which the MDC can be  
accessed. Make a note of this information.  
You can now access StorNext File System and run the configuration  
wizard. For more information, see Chapter 4, “Configuring StorNext.”  
Installing StorNext File System on Windows  
The StorNext setup wizard guides you through the process of installing  
StorNext File System on a metadata controller running Windows 2003  
Server. (The installation wizard also installs the client software on the  
MDC.)  
Before installing StorNext, remove any previously installed versions (see  
Removing a Previous Version of StorNext on page 28).  
When you are ready, use the setup wizard to install StorNext (see  
Running the Setup Wizard on page 29).  
(Optional) After installation, restore the previous client configuration (see  
Restoring a Previous Client Configuration on page 33).  
StorNext 3.1.3 Installation Guide  
27  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 2 Installing StorNext File System  
Installing StorNext File System on Windows  
Note: You must log on as an Administrator to install StorNext.  
Removing a Previous  
Version of StorNext  
If a previous version of StorNext exists on the system, you must remove it  
before installing the new version.  
2
1 Insert the StorNext installation CD.  
2 Browse to the root directory of the installation CD and double-click  
the file SnfsSetup32.exe (32-bit systems) or SnfsSetup64.exe (64-bit  
systems).  
The StorNext Installation window appears (figure 8).  
Figure 8 StorNext Installation  
Window: Remove StorNext  
3 Click Remove StorNext.  
A dialog box appears informing you that the current client  
configuration has been saved.  
4 Note the name and location of the saved configuration file, and then  
click OK.  
5 If prompted, click Yes to continue, and then click OK to finish the  
removal.  
6 When the removal is complete, click Yes to reboot the system.  
StorNext 3.1.3 Installation Guide  
28  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 2 Installing StorNext File System  
Installing StorNext File System on Windows  
Note: After installing the new version of StorNext, you can restore  
the saved client configuration (see Restoring a Previous Client  
Configuration on page 33).  
Running the Setup  
Wizard  
To launch the setup wizard, use the correct StorNext installation CD for  
your operating system.  
2
1 Insert the StorNext installation CD.  
2 Browse to the root directory of the installation CD and double-click  
the file SnfsSetup32.exe (32-bit systems) or SnfsSetup64.exe (64-bit  
systems).  
The StorNext Installation window appears (figure 9).  
Figure 9 StorNext Installation  
Window: Install StorNext  
3 Click Install StorNext to begin installation.  
The StorNext setup wizard appears (figure 10).  
StorNext 3.1.3 Installation Guide  
29  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 2 Installing StorNext File System  
Installing StorNext File System on Windows  
Figure 10 SNFS Setup:  
Welcome  
4 Click Next to continue.  
The License Agreement window appears (figure 11).  
Figure 11 SNFS Setup: End-  
User License Agreement  
5 Click the option to accept the license agreement, and then click Next  
to continue.  
The Customer Information window appears (figure 12).  
StorNext 3.1.3 Installation Guide  
30  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 2 Installing StorNext File System  
Installing StorNext File System on Windows  
Figure 12 SNFS Setup:  
Customer Information  
6 Type your name and the name of your company or organization in  
the boxes, and then click Next to continue.  
The Choose Setup Type window appears (figure 13).  
Figure 13 SNFS Setup:  
Choose Setup Type  
7 Click an installation option:  
•
Typical: (Recommended) Installs StorNext File System, client  
software, and help files in the default location (C:\Program  
Files\StorNext).  
StorNext 3.1.3 Installation Guide  
31  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 2 Installing StorNext File System  
Installing StorNext File System on Windows  
•
•
Custom: Lets you choose which components to install and specify  
an installation location. When ready, click Next.  
Complete: Same as a typical installation.  
The Ready to Install window appears (figure 14).  
Figure 14 SNFS Setup: Ready  
to Install  
8 Click Install to continue.  
Wait while the setup wizard installs StorNext. When installation is  
complete, the Finish window appears (figure 15).  
Figure 15 SNFS Setup: Finish  
StorNext 3.1.3 Installation Guide  
32  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 2 Installing StorNext File System  
Installing StorNext File System on Windows  
9 Click Finish to close the setup wizard.  
10 On the StorNext Installation window, click Exit.  
You are prompted to reboot the system.  
11 Click Yes to reboot.  
You can now configure StorNext File System. For more information, see  
Chapter 4, “Configuring StorNext.” Or, to restore a previous client  
configuration, see the next section.  
Restoring a Previous  
Client Configuration  
If you saved a client configuration file (for example, when removing a  
previous version of StorNext), you can import it after installing StorNext.  
This configures StorNext using the same settings as the previous  
installation.  
2
1 Insert the StorNext installation CD.  
2 Browse to the root directory of the installation CD and double-click  
the file SnfsSetup32.exe (32-bit systems) or SnfsSetup64.exe (64-bit  
systems).  
The StorNext Installation window appears (figure 16).  
Figure 16 StorNext Installation  
Window: Configure StorNext  
3 Click Configure StorNext.  
The StorNext Configuration window appears (figure 17).  
StorNext 3.1.3 Installation Guide  
33  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 2 Installing StorNext File System  
Installing StorNext File System on Windows  
Figure 17 StorNext  
Configuration Window  
4 Click Import/Export Client Settings.  
The Import/Export Client Configuration window appears (figure 18).  
StorNext 3.1.3 Installation Guide  
34  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 2 Installing StorNext File System  
Installing StorNext File System on Windows  
Figure 18 Import/Export Client  
Configuration Window  
5 Under Import, click Browse. Locate the client configuration (*.reg) file  
to import, and then click Open.  
Client configuration files saved during removal of a previous version  
of StorNext are located in one the following directories:  
•
•
C:\SNFS\config\  
C:\Program Files\StorNext\config\  
6 Click an option for handling current configuration settings:  
•
Merge with current configuration: The imported configuration is  
merged with the current configuration settings.  
•
Replace current configuration: The imported configuration  
overwrites the current configuration settings.  
7 Click Import, and then click Yes to confirm.  
A message appears informing you the configuration settings were  
successfully added to the registry.  
8 Click OK, and then click Quit to close the Import/Export Client  
Configuration window.  
StorNext 3.1.3 Installation Guide  
35  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 3  
3Installing the StorNext Client  
This chapter describes how to install the StorNext client software. The  
StorNext client software lets you mount and work with StorNext file  
systems.  
To ensure successful operation, make sure the client system meets all  
operating system and hardware requirements (see Client System  
Requirements).  
To install the StorNext client software, first download the client software  
from the metadata controller (MDC) (see Downloading the StorNext  
Client Software on page 39).  
After downloading the client software, install and configure it using the  
appropriate method for your operating system (see Installing the  
StorNext Client on Linux or Unix on page 42 or Installing the StorNext  
Client on Windows on page 51).  
Note: Before installing the StorNext client software, you must install  
and configure StorNext on an MDC. For more information, see  
Chapter 1, “Installing StorNext File System and Storage  
Manager” or Chapter 2, “Installing StorNext File System.”  
StorNext 3.1.3 Installation Guide  
36  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 3 Installing the StorNext Client  
Client System Requirements  
Client System Requirements  
To run the StorNext client software, the client system must meet all  
operating system and hardware requirements.  
Operating System  
Requirements  
The operating systems, releases and kernels, and hardware platforms  
supported by the StorNext client software are presented in Table 11.  
Make sure the client system uses a supported operating system and  
platform, and if necessary update to a supported release or kernel version  
before installing StorNext.  
3
Table 11 StorNext Client  
Supported Platforms  
Operating System  
Release or Kernel  
Platform  
Windows XP  
SP2  
SP3  
x86 32-bit  
x86 64-bit  
Windows 2003 Server  
Windows Vista  
SP2  
x86 32-bit  
x86 64-bit  
SP1  
x86 32-bit  
x86 64-bit  
Red Hat Enterprise  
Linux 4  
2.6.9-55.EL (Update 5)  
2.6.9-67.EL (Update 6)  
2.6.9-78.EL (Update 7)  
x86 32-bit  
x86 64-bit  
Itanium 64-bit  
Red Hat Enterprise  
Linux 5  
2.6.18-53.EL (Update 1)  
2.6.18-92.EL (Update 2)  
x86 64-bit  
SUSE Linux Enterprise 2.6.16.21-0.8  
Server 10  
x86 32-bit  
x86 64-bit  
Itanium 64-bit  
2.6.16-46-0.12 (SP1)  
2.6.16-60-0.27 (SP2)  
—
Sun Solaris 9  
SPARC 64-bit  
StorNext 3.1.3 Installation Guide  
37  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 3 Installing the StorNext Client  
Client System Requirements  
Operating System  
Release or Kernel  
Platform  
Sun Solaris 10  
Generic 120011-14  
Generic 127128-11  
SPARC 64-bit  
Opteron and  
Intel x86 64-bit  
HP-UX  
11i v2  
5.3  
Itanium 64-bit  
IBM AIX  
64-bit Power  
Architecture  
SGI-IRIX  
6.5.30  
64-bit MIPS  
x86 32-bit  
Apple MacOS X 10.5  
With Xsan 1.4.2 or Xsan  
2.1.1  
To install and run the StorNext client software, the client system must  
meet the following minimum hardware requirements.  
Hardware Requirements3  
For SAN (FC-attached) clients or for distributed LAN clients:  
• 1 GB RAM  
• 500 MB available hard disk space  
For SAN clients acting as a distributed LAN server:  
• 2 GB RAM  
• 500 MB available hard disk space  
Note: Distributed LAN servers may require additional RAM  
depending on the number of file systems, distributed LAN  
clients, and NICs used. See the StorNext 3.1.3 Release Notes for  
distributed LAN server memory tuning guidelines.  
StorNext 3.1.3 Installation Guide  
38  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 3 Installing the StorNext Client  
Downloading the StorNext Client Software  
Downloading the StorNext Client Software  
The StorNext client software can be downloaded from a metadata  
controller. (To download the client software, the client system must have  
network access to the MDC.)  
Note: You can download the client software only from MDCs  
running Linux or Unix.  
1 On the client system, point a web browser to the URL (host name and  
port number) of the MDC. For example, http://servername:81  
Use one of the following web browsers to access the MDC (make sure  
pop-up blockers are turned off):  
•
•
Internet Explorer 6.0 or later (including 7.0)  
Mozilla Firefox 1.5 or later (including 2.0 or later)  
2 When prompted, type the username and password for the MDC, and  
then click OK. (The default value for both username and password is  
admin.)  
The StorNext home page appears.  
3 Do one of the following:  
•
For a MDC running SNFS and SNSM: On the Admin menu, click  
Download Client Software.  
•
For a MDC running SNFS only: On the home page, click  
Download Client Software.  
The Select Platform window appears (figure 19).  
StorNext 3.1.3 Installation Guide  
39  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 3 Installing the StorNext Client  
Downloading the StorNext Client Software  
Figure 19 Select Platform  
Window  
4 In the list, click the operating system running on the client system,  
and then click Next.  
The Download Client Software window appears (figure 20).  
StorNext 3.1.3 Installation Guide  
40  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 3 Installing the StorNext Client  
Downloading the StorNext Client Software  
Figure 20 Download Client  
Software Window  
5 Click the download link that corresponds to your operating system  
version and hardware platform. (Depending on the operating  
system, you may have only one choice.)  
For example, for Red Hat Linux 4 running on an x86 64-bit platform,  
click Linux Redhat AS 4.0 (Intel 64bit).  
6 When prompted, click Save or OK to download the file to the client  
system.  
Make sure to note the file name and the location where you save the  
file.  
7 After the download is complete, click Cancel to close the Download  
Client Software window.  
Do not follow the onscreen installation instructions. Instead, continue  
with the correct procedure for your operating system:  
•
•
Installing the StorNext Client on Linux or Unix on page 42  
Installing the StorNext Client on Windows on page 51.  
StorNext 3.1.3 Installation Guide  
41  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Linux or Unix  
Installing the StorNext Client on Linux or Unix  
After downloading the StorNext client software from the metadata  
controller, install it on the client system using the correct procedure for  
your operating system:  
• Installing the StorNext Client on Linux on page 42  
• Installing the StorNext Client on Sun Solaris on page 44  
• Installing the StorNext Client on HP-UX on page 46  
• Installing the StorNext Client on IBM AIX on page 47  
• Installing the StorNext Client on SGI IRIX on page 49  
Installing the StorNext  
Client on Linux  
To run the StorNext client software on Red Hat Linux or SUSE Linux  
Enterprise, first install the client software package, and then configure the  
client.  
3
Caution: Before installing the StorNext client software, you must  
install the kernel source code. You can install the kernel  
source code by using the installation disks for your  
operating system.  
1 Log on to the client system as root.  
2 Change to the directory where the client software archive file you  
downloaded from the MDC is located.  
3 Extract the software archive file. At the command prompt, type:  
tar xf <archive name>  
where <archive name> is the name of the software archive file you  
downloaded from the MDC.  
4 List the packages extracted from the software archive file. At the  
command prompt, type:  
ls -l  
Identify the correct package to install. The correct package begins  
with snfs-client and ends with the .rpm file name extension.  
StorNext 3.1.3 Installation Guide  
42  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Linux or Unix  
Note: The file that ends with .rpm.md5sum is a checksum file, not  
the client software package.  
5 Install the client software package. At the command prompt, type:  
rpm -ivh <package name>  
where <package name> is the name of the client software package you  
identified in step 4.  
6 Configure the boot order for system services. Do one of the following:  
•
For Red Hat Linux, at the command prompt, type:  
chkconfig --level 3456 cvfs on  
•
For SUSE Linux Enterprise, at the command prompt, type:  
chkconfig -s raw 235  
chkconfig -s cvfs 345  
7 Edit the /usr/cvfs/config/fsnameservers text file to contain the IP  
address of the MDC the client will connect to.  
The fsnameservers file on the client must be exactly the same as on  
the MDC. If the fsnameservers file does not exist, use a text editor to  
create it.  
Note: The fsnameservers file only needs to contain the name of  
the MDC. For example, if the MDC is named snserver, then  
the fsnameservers file should contain a single line with a  
single word: snserver  
8 Create a mount point for the file system. At the command prompt,  
type:  
mkdir -p <mount point>  
chmod 777 <mount point>  
where <mount point> is the directory path where you want the file  
system to be mounted. For example: /stornext/snfs1  
StorNext 3.1.3 Installation Guide  
43  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Linux or Unix  
9 Configure the file system to automatically mount after reboot. To do  
this, edit the /etc/fstab file so that it contains the following line:  
<file system> <mount point> cvfs verbose=yes 0 0  
where <file system> is the name of the StorNext file system and <mount  
point> is the directory path created in step 8.  
10 Reboot the client system.  
After reboot, the StorNext file system is mounted at the mount point  
you specified.  
Note: To manually mount a file system, at the command prompt,  
type:  
mount -t cvfs <file system> <mount point>  
where <file system> is the name of the StorNext file system and  
<mount point> is the directory path where you want the file  
system to be mounted.  
Installing the StorNext  
Client on Sun Solaris  
To run the StorNext client software on Sun Solaris, first install the client  
software package, and then configure the client.  
3
1 Log on to the client system as root.  
2 Change to the directory where the client software archive file you  
downloaded from the MDC is located.  
3 Extract the software archive file. At the command prompt, type:  
tar xf <archive name>  
where <archive name> is the name of the software archive file you  
downloaded from the MDC.  
4 Install the client software package. At the command prompt, type:  
pkgadd -d .  
5 Type 1 to select the ADICsnfs package.  
6 Type y to confirm installation of the ADICsnfs package. When  
installation is complete, type q to quit the installation program.  
StorNext 3.1.3 Installation Guide  
44  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Linux or Unix  
7 Edit the /usr/cvfs/config/fsnameservers text file to contain the IP  
address of the MDC the client will connect to.  
The fsnameservers file on the client must be exactly the same as on  
the MDC. If the fsnameservers file does not exist, use a text editor to  
create it.  
Note: The fsnameservers file only needs to contain the name of  
the MDC. For example, if the MDC is named snserver, then  
the fsnameservers file should contain a single line with a  
single word: snserver  
8 Create a mount point for the file system. At the command prompt,  
type:  
mkdir -p <mount point>  
chmod 777 <mount point>  
where <mount point> is the directory path where you want the file  
system to be mounted. For example: /stornext/snfs1  
9 Configure the file system to automatically mount after reboot. To do  
this, edit the /etc/vfstab file so that it contains the following line:  
<file system> - <mount point> cvfs 0 auto rw  
where <file system> is the name of the StorNext file system and <mount  
point> is the directory path created in step 8.  
10 Reboot the client system.  
After reboot, the StorNext file system is mounted at the mount point  
you specified.  
Note: To manually mount a file system, at the command prompt  
type:  
mount -F cvfs <file system> <mount point>  
where <file system> is the name of the StorNext file system and  
<mount point> is the directory path where you want the file  
system to be mounted.  
StorNext 3.1.3 Installation Guide  
45  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Linux or Unix  
Installing the StorNext  
Client on HP-UX  
To run the StorNext client software on HP-UX, first install the client  
software package, and then configure the client.  
3
1 Log on to the client system as root.  
2 Change to the directory where the client software archive file you  
downloaded from the MDC is located.  
3 Extract the software archive file. At the command prompt, type:  
tar xf <archive name>  
where <archive name> is the name of the software archive file you  
downloaded from the MDC.  
4 List the packages extracted from the software archive file. At the  
command prompt, type:  
ls -l  
Identify the correct package to install. The correct package begins  
with snfs-client and ends with the .depot file name extension.  
5 Install the client software package. At the command prompt, type:  
swinstall -s <package path and name> -x mount_all_filesystems=false \*  
where <package path and name> is the full path and name of the client  
software package you identified in step 4.  
6 Edit the /usr/cvfs/config/fsnameservers text file to contain the IP  
address of the MDC the client will connect to.  
The fsnameservers file on the client must be exactly the same as on  
the MDC. If the fsnameservers file does not exist, use a text editor to  
create it.  
Note: The fsnameservers file only needs to contain the name of  
the MDC. For example, if the MDC is named snserver, then  
the fsnameservers file should contain a single line with a  
single word: snserver  
StorNext 3.1.3 Installation Guide  
46  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Linux or Unix  
7 Create a mount point for the file system. At the command prompt,  
type:  
mkdir -p <mount point>  
chmod 777 <mount point>  
where <mount point> is the directory path where you want the file  
system to be mounted. For example: /stornext/snfs1  
8 Configure the file system to automatically mount after reboot. To do  
this, edit the /etc/fstab file so that it contains the following line:  
<mount point> <mount point> cvfs rw,fsname=<file system> 0 0  
where <mount point> is the directory path created in step 7 and <file  
system> is the name of the StorNext file system.  
9 Reboot the client system.  
After reboot, the StorNext file system is mounted at the mount point  
you specified.  
Note: To manually mount a file system, at the command prompt,  
type:  
mount -F cvfs <mount point> <mount point>  
where <mount point> is the directory path where you want the  
file system to be mounted.  
Installing the StorNext  
Client on IBM AIX  
To run the StorNext client software on IBM AIX, first install the client  
software package, and then configure the client.  
3
1 Log on to the client system as root.  
2 Change to the directory where the client software archive file you  
downloaded from the MDC is located.  
3 Extract the software archive file. At the command prompt, type:  
tar xf <archive name>  
where <archive name> is the name of the software archive file you  
downloaded from the MDC.  
StorNext 3.1.3 Installation Guide  
47  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Linux or Unix  
4 List the packages extracted from the software archive file. At the  
command prompt, type:  
ls -l  
Identify the correct package to install. The correct package begins  
with snfs and ends with the .bff file name extension.  
5 Install the client software package. At the command prompt, type:  
installp -ac -d <package name> all .  
where <package name> is the name of the client software package you  
identified in step 4.  
6 Edit the /usr/cvfs/config/fsnameservers text file to contain the IP  
address of the MDC the client will connect to.  
The fsnameservers file on the client must be exactly the same as on  
the MDC. If the fsnameservers file does not exist, use a text editor to  
create it.  
Note: The fsnameservers file only needs to contain the name of  
the MDC. For example, if the MDC is named snserver, then  
the fsnameservers file should contain a single line with a  
single word: snserver  
7 Create a mount point for the file system. At the command prompt,  
type:  
mkdir -p <mount point>  
chmod 777 <mount point>  
where <mount point> is the directory path where you want the file  
system to be mounted. For example: /stornext/snfs1  
8 Configure the file system to automatically mount. At the command  
prompt, type:  
crfs -v cvfs -d <file system> -a verbose=yes -a type=cvfs -A yes -m <mount  
point>  
where <file system> is the name of the StorNext file system and <mount  
point> is the directory path created in step 7.  
The StorNext file system is mounted at the mount point you  
specified.  
StorNext 3.1.3 Installation Guide  
48  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Linux or Unix  
Note: To manually mount a file system, at the command prompt,  
type:  
mount <mount point>  
where <mount point> is the directory path where you want the  
file system to be mounted.  
Installing the StorNext  
Client on SGI IRIX  
To run the StorNext client software on SGI IRIX, first install the client  
software package, and then configure the client.  
3
1 Log on to the client system as root.  
2 Change to the directory where the client software archive file you  
downloaded from the MDC is located.  
3 Extract the software archive file. At the command prompt, type:  
tar xf <archive name>  
where <archive name> is the name of the software archive file you  
downloaded from the MDC.  
4 Install the client software package. At the command prompt, type:  
inst -f .  
5 Type go to confirm installation. When installation is complete, type  
quit to quit the installation program.  
6 Configure the boot order for system services. At the command  
prompt, type:  
chkconfig cvfs on  
chkconfig verbose on  
7 Edit the /usr/cvfs/config/fsnameservers text file to contain the IP  
address of the MDC the client will connect to.  
The fsnameservers file on the client must be exactly the same as on  
the MDC. If the fsnameservers file does not exist, use a text editor to  
create it.  
StorNext 3.1.3 Installation Guide  
49  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Linux or Unix  
Note: The fsnameservers file only needs to contain the name of  
the MDC. For example, if the MDC is named snserver, then  
the fsnameservers file should contain a single line with a  
single word: snserver  
8 Create a mount point for the file system. At the command prompt,  
type:  
mkdir -p <mount point>  
chmod 777 <mount point>  
where <mount point> is the directory path where you want the file  
system to be mounted. For example: /stornext/snfs1  
9 Configure the file system to automatically mount after reboot. To do  
this, edit the /etc/fstab file so that it contains the following line:  
<file system> <mount point> cvfs verbose=yes 0 0  
where <file system> is the name of the StorNext file system and <mount  
point> is the directory path created in step 8.  
10 Reboot the client system.  
After reboot, the StorNext file system is mounted at the mount point  
you specified.  
Note: To manually mount a file system, at the command prompt,  
type:  
mount -t cvfs <file system> <mount point>  
where <file system> is the name of the StorNext file system and  
<mount point> is the directory path where you want the file  
system to be mounted.  
StorNext 3.1.3 Installation Guide  
50  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Windows  
Installing the StorNext Client on Windows  
The StorNext setup wizard guides you through the process of installing  
the StorNext client software on Windows XP, Windows 2003 Server, or  
Windows Vista.  
Before installing StorNext, remove any previously installed versions (see  
Removing a Previous Version of StorNext on page 51).  
When you are ready, use the setup wizard to install StorNext (see  
Running the Setup Wizard on page 52).  
(Optional) After installation, restore the previous client configuration (see  
Restoring a Previous Client Configuration on page 56).  
Note: You must log on as an Administrator to install StorNext.  
If you are installing on Windows Vista, answer Yes to any  
messages asking if you want to run the installation process  
with administrative privileges.  
Removing a Previous  
Version of StorNext  
If a previous version of StorNext exists on the system, you must remove it  
before installing the new version.  
3
1 Unzip the client software archive file you downloaded from the  
MDC.  
2 Open the unzipped folder and double-click the client software  
installer file. This file is named SnfsSetup32.exe (32-bit systems) or  
SnfsSetup64.exe (64-bit systems).  
The StorNext Installation window appears (figure 21).  
StorNext 3.1.3 Installation Guide  
51  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Windows  
Figure 21 StorNext Installation  
Window: Remove StorNext  
3 Click Remove StorNext.  
A dialog box appears informing you that the current client  
configuration has been saved.  
4 Note the name and location of the saved configuration file, and then  
click OK.  
5 If prompted, click Yes to continue, and then click OK to finish the  
removal.  
6 When the removal is complete, click Yes to reboot the system.  
Note: After installing the new version of StorNext, you can restore  
the saved client configuration (see Restoring a Previous Client  
Configuration on page 56).  
Running the Setup  
Wizard  
To launch the setup wizard, use the correct StorNext installation CD for  
your operating system, or use the client software installer you  
downloaded from the MDC.  
3
1 If necessary, unzip the client software archive file you downloaded  
from the MDC.  
2 Open the unzipped folder and double-click the client software  
installer file. This file is named SnfsSetup32.exe (32-bit systems) or  
SnfsSetup64.exe (64-bit systems).  
The StorNext Installation window appears (figure 22).  
StorNext 3.1.3 Installation Guide  
52  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Windows  
Figure 22 StorNext Installation  
Window: Install StorNext  
3 Click Install StorNext to begin installation.  
The StorNext setup wizard appears (figure 23).  
Figure 23 SNFS Setup:  
Welcome  
4 Click Next to continue.  
The License Agreement window appears (figure 24).  
StorNext 3.1.3 Installation Guide  
53  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Windows  
Figure 24 SNFS Setup: End-  
User License Agreement  
5 Click the option to accept the license agreement, and then click Next  
to continue.  
The Customer Information window appears (figure 25).  
Figure 25 SNFS Setup:  
Customer Information  
6 Type your name and the name of your company or organization in  
the boxes, and then click Next to continue.  
The Choose Setup Type window appears, (figure 26).  
StorNext 3.1.3 Installation Guide  
54  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Windows  
Figure 26 SNFS Setup:  
Choose Setup Type  
7 Click an installation option:  
•
•
•
Typical: (Recommended) Installs the StorNext client software and  
help files in the default location (C:\Program Files\StorNext).  
Custom: Lets you choose which components to install and specify  
an installation location. When ready, click Next.  
Complete: Same as a typical installation.  
The Ready to Install window appears (figure 27).  
Figure 27 SNFS Setup: Ready  
to Install  
StorNext 3.1.3 Installation Guide  
55  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Windows  
8 Click Install to continue.  
Wait while the setup wizard installs StorNext. When installation is  
complete, the Finish window appears (figure 28).  
Figure 28 SNFS Setup: Finish  
9 Click Finish to close the setup wizard.  
10 On the StorNext Installation window, click Exit.  
You are prompted to reboot the system.  
11 Click Yes to reboot.  
You can now configure StorNext File System. For more information, see  
Chapter 4, “Configuring StorNext.”  
Restoring a Previous  
Client Configuration  
If you saved a client configuration file (for example, when removing a  
previous version of StorNext), you can import it after installing StorNext.  
This configures StorNext using the same settings as the previous  
installation.  
3
1 If necessary, unzip the client software archive file you downloaded  
from the MDC.  
2 Open the unzipped folder and double-click the client software  
installer file. This file is named SnfsSetup32.exe (32-bit systems) or  
SnfsSetup64.exe (64-bit systems).  
The StorNext Installation window appears (figure 29).  
StorNext 3.1.3 Installation Guide  
56  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Windows  
Figure 29 StorNext Installation  
Window: Configure StorNext  
3 Click Configure StorNext.  
The StorNext Configuration window appears (figure 30).  
Figure 30 StorNext  
Configuration Window  
4 Click Import/Export Client Settings.  
The Import/Export Client Configuration window appears (figure 31).  
StorNext 3.1.3 Installation Guide  
57  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 3 Installing the StorNext Client  
Installing the StorNext Client on Windows  
Figure 31 Import/Export Client  
Configuration Window  
5 Under Import, click Browse. Locate the client configuration (*.reg) file  
to import, and then click Open.  
Client configuration files saved during removal of a previous version  
of StorNext are located in one the following directories:  
•
•
C:\SNFS\config\  
C:\Program Files\StorNext\config\  
6 Click an option for handling current configuration settings:  
•
Merge with current configuration: The imported configuration is  
merged with the current configuration settings.  
•
Replace current configuration: The imported configuration  
overwrites the current configuration settings.  
7 Click Import, and then click Yes to confirm.  
A message appears informing you the configuration settings were  
successfully added to the registry.  
8 Click OK, and then click Quit to close the Import/Export Client  
Configuration window.  
StorNext 3.1.3 Installation Guide  
58  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4  
4Configuring StorNext  
This chapter describes how to configure StorNext after installation. To  
configure StorNext, enter license information and create one or more file  
systems. In addition, on metadata controllers (MDCs) running StorNext  
Storage Manager, you can add storage devices and media, create storage  
policies, and set up e-mail notifications. In addition, Linux or Windows  
SAN clients can be configured as a distributed LAN client or a distributed  
LAN server.  
For system running Unix or Linux, use the web-based GUI (graphical  
user interface) to access StorNext running on an MDC (see StorNext  
GUI).  
The first time you log on to StorNext, the Configuration Wizard appears.  
The wizard guides you through the process of setting up StorNext (see  
Configuration Wizard on page 62).  
To configure a StorNext client as a distributed LAN client or server, edit  
the distributed LAN configuration file (see Configuring a Distributed  
LAN Client Server on page 67).  
For systems running Windows, use the Windows-based configuration  
utilities to set up server and client features (see Windows Configuration  
Utilities on page 72).  
StorNext 3.1.3 Installation Guide  
59  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
StorNext GUI  
StorNext GUI  
The StorNext GUI provides access to StorNext features and displays  
system status information. Use the StorNext GUI to create and work with  
file systems. In addition, on metadata controllers running Storage  
Manager, you can use the StorNext GUI to configure storage devices and  
media, and to set up storage policies.  
Note: The StorNext GUI is available only for MDCs running on Unix  
or Linux. For MDCs running on Windows, use the  
configuration utilities to configure StorNext (see Windows  
Configuration Utilities on page 72).  
Accessing the StorNext  
GUI  
To log on to the StorNext GUI, use a web browser running on the MDC,  
or on any system that has network access to the MDC.  
4
1 Point a web browser to the URL of the MDC.  
The URL consists of the host name or IP address of the MDC  
followed by the port number at which StorNext can be reached. (The  
default port number is 81.) For example: http://servername:81  
Use one of the following web browsers to access the MDC (make sure  
pop-up blockers are turned off):  
•
•
Internet Explorer 6.0 or later (including 7.0)  
Mozilla Firefox 1.5 or later (including 2.0 or later)  
2 When prompted, type the user name and password for the MDC, and  
click OK. (The default value for both user name and password is  
admin.)  
The StorNext home page appears. The appearance of the home page  
differs depending on if both Storage Manager and File System are  
installed on the MDC, or if File System only is installed.  
The StorNext home page for an MDC running File System and  
Storage Manager is shown in figure 32. The StorNext home page for  
an MDC running File System only is shown in figure 33.  
StorNext 3.1.3 Installation Guide  
60  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
StorNext GUI  
Figure 32 StorNext Home  
Page: File System and Storage  
Manager  
Figure 33 StorNext Home  
Page: File System Only  
StorNext 3.1.3 Installation Guide  
61  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Configuration Wizard  
Configuration Wizard  
The first time you log onto the StorNext GUI, the Configuration Wizard  
appears. The wizard guides you step-by-step through the process of  
configuring StorNext.  
The appearance of the wizard differs depending on if both Storage  
Manager and File System are installed on the MDC, or if File System only  
is installed.  
The Configuration Wizard for an MDC running File System and Storage  
Manager is shown in figure 34. The Configuration Wizard for an MDC  
running File System only is shown in figure 35.  
Figure 34 StorNext  
Configuration Wizard: Storage  
Manager  
StorNext 3.1.3 Installation Guide  
62  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Configuration Wizard  
Figure 35 StorNext  
Configuration Wizard: File  
System Only  
Displaying the  
Configuration Wizard  
The Configuration Wizard appears each time you log on to StorNext until  
all steps of the wizard are completed. You can also control the wizard  
manually:  
4
• To set the Configuration Wizard to not appear the next time you log  
in, select the Don’t Show CW Again check box.  
• To display the Configuration Wizard at any time, on the Config  
menu, click Configuration Wizard.  
Using the Configuration  
Wizard  
The Configuration Wizard consists of eight steps. (If Storage Manager is  
not installed on the MDC, only the first two steps appear.) The wizard  
lets you navigate between steps and tracks your progress as you  
complete each step.  
4
• To go to the next step, click Next.  
• To return to a previous step, click the step in the list.  
• To start the wizard over from the beginning, click Reset.  
• To exit the wizard, click Done.  
StorNext 3.1.3 Installation Guide  
63  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 4 Configuring StorNext  
Configuration Wizard  
The following sections describe each step of the Configuration Wizard.  
Each step consists of a separate wizard that guides you through a task. To  
complete a task, follow the onscreen instructions. To see more detailed  
instructions for completing a task, refer to the indicated section in the  
StorNext User’s Guide.  
Note: Using the Configuration Wizard to configure StorNext is  
optional. All configuration tasks can be accessed at any time  
using the StorNext main menu, as described in the following  
sections.  
Step 1: Enter License  
4
The Enter License Wizard guides you through the steps of entering a  
license string. A license string must be entered before you can configure  
or use StorNext.  
You can generate a temporary license that is valid for 30 days. To obtain a  
permanent license, contact the Quantum Technical Assistance center at  
licenses@quantum.com and provide the following information:  
• The product serial number from the StorNext box or CD.  
• The number of client machines connecting to the MDC.  
• The StorNext Server ID number. (This number can be found on the  
Enter License String window of the Enter License Wizard.)  
To display the Enter License Wizard at any time, on the Config menu,  
click Enter License. For more information about entering a license, see  
Chapter 4, “Common StorNext Tasks,” in the StorNext User’s Guide.  
Step 2: Add File System  
4
The Add New File System Wizard guides you through the steps of  
creating and configuring a new file system. The wizard also lets you  
establish a mount point for the file system, specify disk block size, and  
customize stripe groups.  
A file system is a shared data pool that can be accessed by client systems  
and applications. Each file system contains one or more stripe groups. (A  
stripe group is a logical volume that consists of one or more disks.)  
StorNext 3.1.3 Installation Guide  
64  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 4 Configuring StorNext  
Configuration Wizard  
To display the Add New File System Wizard at any time, on the Config  
menu, click Add File System. For more information about adding file  
systems, see Chapter 6, “Managing the File System,” in the StorNext  
User’s Guide.  
Step 3: Add Library  
4
The Add Library wizard guides you through the steps of adding and  
configuring a tape library or vault. The wizard lets you specify the type of  
library (SCSI, ACSLS, DAS, or vault) and set the appropriate parameters  
for that library type.  
To display the Add Library Wizard at any time, on the Config menu, click  
Add Library. For more information about adding libraries, see Chapter 7,  
“Managing Libraries,” in the StorNext User’s Guide.  
Step 4: Add Tape Drive  
4
The Add Drive Wizard guides you through the steps of adding and  
configuring tape drives. The wizard lets you associate hardware devices  
with libraries and, if necessary, map them to slots.  
To display the Add Drive Wizard at any time, on the Config menu, click  
Add Tape Drive. For more information about adding tape drives, see  
Chapter 8, “Managing Drives and Disks,” in the StorNext User’s Guide.  
Step 5: Add Media  
4
The Add Media Wizard guides you through the steps of adding media to  
a configured library. The wizard lets you specify a media type and, for  
vaults, specify media IDs. (Before adding media, make sure no tape  
drives contain media.)  
To display the Add Media Wizard at any time, on the Config menu, click  
Add Media. For more information about adding media, see Chapter 9,  
“Managing Media,” in the StorNext User’s Guide.  
StorNext 3.1.3 Installation Guide  
65  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 4 Configuring StorNext  
Configuration Wizard  
Step 6: Add Storage Disks  
4
The Add Storage Disk wizard guides you through the steps of adding  
external storage disks to a managed system. The wizard lets you specify  
which file systems to define as storage disks. Once defined, storage disks  
can be used as a target media type when creating storage policies.  
To display the Add Storage Disk Wizard at any time, on the Config menu,  
click Add Storage Disk. For more information about adding storage disks,  
see Chapter 10, “Managing Storage Disks,” in the StorNext User’s Guide.  
Step 7: Add Storage Policy  
4
The Add New Storage Policy Wizard guides you through the steps of  
adding disk-to-disk policy classes to a managed system. Storage policies  
allow data to be intelligently moved between disks (stripe groups)  
without affecting the file name space.  
To display the Add New Storage Policy Wizard at any time, on the Config  
menu, click Add Storage Policy. For more information about adding  
storage policies, see Chapter 11, “Data Migration Management,” in the  
StorNext User’s Guide.  
Step 8: E-Mail Notification  
4
The E-mail Notification Wizard guides you through the steps of setting  
up e-mail notifications on the MDC. The wizard lets you specify the  
SMTP server to use for outgoing e-mail, and the addresses to which  
system alerts and notifications are sent. (Make sure the SMTP server is  
configured before setting up e-mail notifications.)  
To display the E-mail Notification Wizard at any time, on the Config  
menu, click E-Mail Notification. For more information about setting up  
e-mail notifications disks, see Chapter 4 “Common StorNext Tasks,” in  
the StorNext User’s Guide.  
StorNext 3.1.3 Installation Guide  
66  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 4 Configuring StorNext  
Configuring a Distributed LAN Client Server  
Configuring a Distributed LAN Client Server  
Traditional StorNext SAN clients access data disks using a high  
throughput, low-latency fibre channel connection. In addition, using the  
distributed LAN client and server feature, StorNext clients can access  
data disks over a network instead of directly accessing disks.  
A StorNext client running on Linux or Windows can be configured as a  
distributed LAN client or a distributed LAN server. (This is a licensed  
feature.)  
• Distributed LAN Server: A distributed LAN server has direct access to  
data disks (using fibre channel) and makes the shared storage pool  
available to distributed LAN clients over a network.  
• Distributed LAN Client: A distributed LAN client does not have direct  
access to data disks and instead accesses the shared storage pool by  
connecting to a distributed LAN server over a network. (Distributed  
LAN clients have full StorNext client functionality.)  
Note: A StorNext client configured as a distributed LAN server  
requires a dedicated system. Do not run other applications or  
services on a system configured as a distributed LAN server.  
To configure a Linux client as a distributed LAN client, see Configuring a  
Distributed LAN Client on Linux. To configure a Linux client as a  
distributed LAN server, see Configuring a Distributed LAN Server on  
Linux.  
To configure a Windows client as a distributed LAN server or a  
distributed LAN client, use the Windows Client Configuration utility. For  
more information, see Client Configuration on page 73 and Distributed  
LAN on page 81.  
StorNext 3.1.3 Installation Guide  
67  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4 Configuring StorNext  
Configuring a Distributed LAN Client Server  
Configuring a Distributed  
To configure a StorNext client as a distributed LAN client, edit mount  
options in the /etc/fstab file.  
LAN Client on Linux  
4
1 Stop the StorNext client. At the command prompt, type:  
/etc/init.d/cvfs stop  
2 Configure the client to mount a file system as a distributed LAN  
client. To do this, edit the /etc/fstab file so that it contains the  
following line:  
<file system> <mount point> cvfs rw,diskproxy=client 0 0  
where <file system> is the name of the StorNext file system and <mount  
point> is the directory path where the file system is mounted.  
3 Start the StorNext client. At the command prompt, type:  
/etc/init.d/cvfs start  
Configuring a Distributed  
To configure a StorNext client as a distributed LAN server, edit mount  
options in the /etc/fstab file, and then configure distributed LAN server  
options.  
LAN Server on Linux  
4
1 Stop the StorNext client. At the command prompt, type:  
/etc/init.d/cvfs stop  
2 Configure the client to mount a file system as a distributed LAN  
server. To do this, edit the /etc/fstab file so that it contains the  
following line:  
<file system> <mount point> cvfs rw,diskproxy=server 0 0  
where <file system> is the name of the StorNext file system and <mount  
point> is the directory path where the file system is mounted.  
3 Change to the /usr/cvfs/bin/ directory.  
4 Launch the StorNext distributed LAN server configuration utility. At  
the command prompt, type:  
./sndpscfg -e  
Note: To get help for the sndpscfg utility, at the command  
prompt, type: ./sndpscfig -h  
The distributed LAN server configuration utility appears (figure 36).  
StorNext 3.1.3 Installation Guide  
68  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Configuring a Distributed LAN Client Server  
Figure 36 sndpscfg  
Configuration Utility  
5 Edit the default distributed LAN server configuration:  
• (Required) Uncomment (delete the # next to) the line that  
corresponds to the network interface used by the distributed LAN  
server when connecting to distributed LAN clients. (For best  
performance, do not choose the network used for metadata.)  
• (Optional) To change a tunable parameter from the default value,  
uncomment the parameter, and then specify a new value. Table 12  
describes the tunable parameters.  
Note: The distributed LAN server configuration utility uses the  
default text editor. If a default text editor has not been  
specified, the utility uses the vi editor.  
StorNext 3.1.3 Installation Guide  
69  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4 Configuring StorNext  
Configuring a Distributed LAN Client Server  
Table 12 Distributed LAN  
Server Parameters  
Field / Button  
Description  
tcp_window_size_kb  
The TCP window size (in KB) used by the  
distributed LAN server. (Default: 64)  
transfer_buffer_size_kb  
transfer_buffer_count  
The transfer buffer size (in KB) used by the  
distributed LAN server. A larger buffer may  
increase performance for larger files.  
(Default: 256)  
The number of transfer buffers used by the  
distributed LAN server. This parameter is  
used only by Windows servers and clients.  
Linux servers pass the value of this  
parameter to Windows clients. (Default: 16)  
server_buffer_count  
daemon_threads  
The number of I/O buffers allocated for  
each network interface on the distributed  
LAN server. This parameter is used only by  
Linux servers. (Default: 8)  
The maximum number of daemon threads  
used by the distributed LAN server.  
(Default: 8)  
6 When you are done making edits, type :x to save and close the  
configuration file.  
The configuration is saved in the file dpserver in the /user/cvfs/config/  
directory.  
Note: To edit this file at a later date, you can run the sndpscfg  
utility again or edit the dpserver file directly.  
7 Start the StorNext client. At the command prompt, type:  
/etc/init.d/cvfs start  
StorNext 3.1.3 Installation Guide  
70  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4 Configuring StorNext  
Configuring a Distributed LAN Client Server  
Creating an Override Configuration  
4
By default, the settings specified in the dpserver configuration file are  
used for all file systems mounted by the distributed LAN server. To use  
different settings for a file system, create an override configuration file for  
that file system. At the command prompt, type:  
./sndpscfg -E <file system>  
where <file system> is the name of the file system to which the override  
settings apply. Edit the configuration file, and then save and exit. A new  
configuration file with the name dpserver.<file system> is created in the  
/user/cvfs/config/ directory.  
Using Distributed LAN Client and Server Commands  
4
Use the cvadmin commands described in Table 13 to see information  
about distributed LAN servers and clients. (For more information about  
using cvadmin commands, see the CLI Reference Guide.)  
Table 13 Distributed LAN  
Client and Server Commands  
Command  
Description  
proxy  
Lists all distributed LAN servers for the  
currently selected file system.  
proxy long  
Lists all distributed LAN servers for the  
currently selected file system, as well as  
tunable parameters and attached disks.  
proxy who <distributed LAN  
client>  
Lists distributed LAN servers connected  
to the specified distributed LAN client, as  
well as current I/O statistics.  
proxy who <distributed LAN  
server>  
Lists distributed LAN clients connected to  
the specified distributed LAN server, as  
well as current I/O statistics.  
StorNext 3.1.3 Installation Guide  
71  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Windows Configuration Utilities  
To configure StorNext File System or the StorNext client software on  
Windows operating systems, use the Windows configuration utilities.  
The configuration utilities let you set up a Windows-based metadata  
controller, configure a StorNext client, and work with StorNext file  
systems.  
To run a configuration utility, on the Windows Start menu, click All  
Programs > StorNext File System, and then click the utility.  
The StorNext client software includes the following configuration  
utilities:  
• Client Configuration on page 73  
• Disk Device Labeler on page 83  
• License Identifier on page 86  
• Simple File System Configuration on page 86  
• Start File System Services on page 88  
• Stop and Remove File System Services on page 88  
• Stop File System Services on page 88  
• Version Information on page 88  
StorNext File System server includes all the configuration utilities  
installed by the client software as well as the following additional  
utilities:  
• Check (Read-Only) a File System on page 89  
• File System Startup List on page 89  
• Re-initialize a File System on page 91  
• Repair a File System on page 91  
• Server Administration on page 91  
• Server Configuration on page 97  
StorNext 3.1.3 Installation Guide  
72  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
The Client Configuration utility lets you view and modify properties for  
the StorNext client software. Use the utility to add name servers, map file  
systems to drives, and configure a distributed LAN server or a  
distributed LAN client.  
Client Configuration  
4
To run the Client Configuration utility, on the Windows Start menu, click  
All Programs > StorNext File System > Client Configuration.  
The Client Configuration utility includes six tabs:  
• Drive Mappings on page 73  
• FS Name Servers on page 75  
• Authentication on page 76  
• Mount Options on page 78  
• Syslog Level on page 79  
• Cache Parameters on page 80  
• Distributed LAN on page 81  
Click a tab to view or modify StorNext client properties. After making  
changes on one or more tabs, click OK to save the changes. A message  
appears prompting you to restart the system. Click Yes. Most changes do  
not take affect until the system is restarted.  
Drive Mappings  
4
To access a StorNext file system, it must be mapped to a local drive letter  
on the client system.  
Use the Drive Mappings tab (figure 37) to map file systems to local drives.  
Table 14 describes the fields on the Drive Mappings tab.  
Note: You must specify a file system name server on the FS Name  
Servers tab before mapping drives.  
StorNext 3.1.3 Installation Guide  
73  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Note: You must disable the Windows Recycle Bin for each local  
drive that is mapped to a file system. Right click the Recycle  
Bin icon and click Properties. On the Global tab, click Configure  
Drives Independently. On the appropriate Local Disk tab, select  
the Do not move files to the Recycle Bin check box, and then  
click OK.  
Figure 37 Client Configuration:  
Drive Mappings  
Table 14 Client Configuration:  
Drive Mappings  
Field / Button  
Description  
Map Drive - Drive  
Select a local drive letter to associate with a  
file system.  
Map Drive - File  
System  
Type or select the name of the file system to  
associate with the selected local drive letter.  
Map Drive - Map  
Click to associate the selected local drive letter  
with the selected file system.  
StorNext 3.1.3 Installation Guide  
74  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Field / Button  
Description  
Select Drive - Drive  
Select the mapped drive to configure on the  
other tabs of the Client Configuration utility.  
Unmap Drive  
Unmap  
Select a drive to unmap.  
Click to unmap the selected drive.  
Display File System  
Critical Events to  
Desk Top  
Select to display a notification dialog box if a  
critical event occurs.  
(Because the dialog box must be manually  
dismissed, clear this check box for unattended  
client systems.)  
Disable SNFS ONC  
Portmapper Process  
Select to disable the SNFS portmapper service.  
(Disable this service only if a product that  
provides equivalent functionality is installed,  
for example, the portmapper installed with  
Microsoft Services for Unix).  
Don’t Register with  
ONC Portmapper (port  
111)  
Select to not register with the SNFS  
portmapper service.  
FS Name Servers  
4
To access a file system, you must first specify the name server (StorNext  
host) where the file system is located. The first host in the list is the  
primary name server. Additional hosts are backups for use in the event of  
a failover.  
Use the FS Name Servers tab (figure 38) to specify the primary StorNext  
host. Table 15 describes the fields on the FS Name Servers tab.  
Note: Make sure the host list is the same for all clients on the SAN.  
An incorrect or incomplete host list may prevent the client  
from connecting to the file system.  
StorNext 3.1.3 Installation Guide  
75  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Figure 38 Client Configuration:  
FS Name Servers  
Table 15 Client Configuration:  
FS Name Servers  
Field / Button  
Add  
Description  
Click to add the name server entered in the  
box.  
Remove  
Click to remove the name server selected in  
the list.  
Move Up  
Move Down  
Click to move the selected name server up in  
the list.  
Click to move the selected name server down  
in the list.  
Authentication  
4
If a Windows client accesses file systems that are also accessed by non-  
Windows clients, you must specify an authentication method: Active  
Directory, PCNFSD, or NIS. This method is used to map the Windows  
StorNext 3.1.3 Installation Guide  
76  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
user to a user ID and group on the SAN. (Changes are applied when you  
click Apply. You do not need to restart the client system.)  
Use the Authentication tab (figure 39) to specify an authentication  
method. Table 16 describes the fields on the Authentication tab.  
Note: If your StorNext installation is Windows-only and you do not  
plan to add non-Windows clients, you do not need to specify  
an authentication method.  
Figure 39 Client Configuration:  
Authentication  
Table 16 Client Configuration:  
Authentication  
Field / Button  
Windows User  
Description  
Select the Windows user to map to a user ID  
and group on the SAN.  
StorNext 3.1.3 Installation Guide  
77  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Field / Button  
Description  
Use Active Directory  
Click to use LDAP to obtain the Active  
Directory/Services for UNIX (SFU) mapping  
for the selected user. (The client system must  
be part of an Active Directory domain.)  
User Name  
PCNFSD  
Type the user name that should be sent to the  
authentication server. (PCNFSD and NIS  
methods only.)  
Click to use a PCNFSD server for  
authentication.  
PCNFSD - Server  
NIS  
Type the IP address of the PCNFSD server.  
Click to use an NIS server for authentication.  
Type the name of the NIS server.  
NIS - Server  
NIS - Domain Name  
Type the domain name of the NIS server.  
File Creation  
Permissions  
Select the default UNIX permissions for new  
files created by the selected user. (PCNFSD  
and NIS methods only.)  
Apply  
Click to Apply changes. (You do not need to  
restart the client system.)  
Mount Options  
4
The Mount Options tab (figure 40) displays the mount options for the  
drive currently selected on the Drive Mappings tab.  
Caution: Changing the values on the Mount Options tab can affect  
system performance and stability. Do not change mount  
options unless instructed to do so by the Quantum  
Technical Assistance Center.  
StorNext 3.1.3 Installation Guide  
78  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Figure 40 Client Configuration:  
Mount Options  
Note: Selecting the Read Only check box has no effect. This feature  
has been disabled.  
Syslog Level  
4
The system log level determines the types of messages the file system  
records in the system event log.  
Use the Syslog Level tab (figure 41) to specify the system log level. The  
None level setting provides the least amount of logging and the Debug  
level provides the most. The default level is Info.  
StorNext 3.1.3 Installation Guide  
79  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Figure 41 Client Configuration:  
Syslog Level  
Cache Parameters  
4
The Cache Parameters tab (figure 42) displays performance values that  
control how many file system lookup names are kept in memory.  
Caution: Changing the values on the Cache Parameters tab can  
affect system performance and stability. Do not change  
cache parameters unless instructed to do so by the  
Quantum Technical Assistance Center.  
StorNext 3.1.3 Installation Guide  
80  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Figure 42 Client Configuration:  
Cache Parameters  
Distributed LAN  
4
A StorNext client running on Windows can be configured as a distributed  
LAN client or a distributed LAN server. (This is a licensed feature.)  
• Distributed LAN Server: A distributed LAN server has direct access to  
data disks (using fibre channel) and makes the shared storage pool  
available to distributed LAN clients over a network.  
• Distributed LAN Client: A distributed LAN client does not have direct  
access to data disks and instead accesses the shared storage pool by  
connecting to a distributed LAN server over a network. (Distributed  
LAN clients have full StorNext client functionality.)  
Note: A StorNext client configured as a distributed LAN server  
requires a dedicated system. Do not run other applications or  
services on a system configured as a distributed LAN server.  
StorNext 3.1.3 Installation Guide  
81  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Use the Distributed LAN tab (figure 43) to configure a distributed LAN  
server or a distributed LAN client. Table 17 describes the fields on the  
Distributed LAN tab.  
Figure 43 Client Configuration:  
Distributed LAN  
Table 17 Client Configuration:  
Distributed LAN  
Field / Button  
Enable Client  
Description  
Select to configure the StorNext client as a  
distributed LAN client. The StorNext client  
will connect to all available distributed LAN  
servers.  
(If you select this check box, all other fields on  
the tab become unavailable.)  
Enable Server  
Select to configure the StorNext client as a  
distributed LAN server. The StorNext client  
will make the disks for this file system  
available to distributed LAN clients over the  
specified LAN.  
StorNext 3.1.3 Installation Guide  
82  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Field / Button  
Description  
Number of Transfer  
Buffers  
Type the number of transfer buffers used by  
the distributed LAN server. (Default: 16)  
Transfer Buffer Size  
(kb)  
Type the transfer buffer size (in KB) used by  
the distributed LAN server. A larger buffer  
may increase performance for larger files.  
(Default: 256)  
TCP Window Size (kb)  
Max Daemon Threads  
Type the TCP window size (in KB) used by  
the distributed LAN server. (Default: 64)  
Type the maximum number of daemon  
threads used by the distributed LAN server.  
(Default: 8)  
Server Interfaces  
Select the server interface (network interface  
card) to use when connecting to distributed  
LAN clients. If a network interface has more  
than one address configured, you must select  
one of the addresses to use for distributed  
LAN connections. (For best performance, do  
not choose the network used for metadata.)  
The Disk Device Labeler utility lets you configure StorNext File System  
storage area network (SAN) disks. Use the Disk Device Labeler to create a  
list of disk labels, associated device names, and (optional) the sectors to  
use.  
Disk Device Labeler  
4
Note: Run the Disk Device Labeler on a system that has visibility to  
all disk devices on the SAN.  
The file system uses the volume labels to determine which disk drives to  
use. The label name written to a disk device must match the disk name  
specified in the Server Configuration utility. For more information, see  
Server Configuration on page 97.  
StorNext 3.1.3 Installation Guide  
83  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Caution: Modifying the label of a system disk may render the  
system inoperable and require you to repair the volume.  
Only label disk devices that are intended for use with the  
StorNext File System SAN.  
To run the Disk Device Labeler utility, on the Windows Start menu, click  
All Programs > StorNext File System > Disk Device Labeler. The Disk  
Labeler window (figure 44) appears.  
Figure 44 Disk Device Labeler  
On the Disk Labeler window, do one of the following:  
• Click Label to write a volume label to the selected device(s) (see  
Labeling Disks below).  
• Click UnLabel to remove the existing volume label from the selected  
device(s).  
• Click Exit to quit the Disk Device Labeler utility.  
• Click Probe Disk(s) to pulse the activity light of the selected device(s).  
Use this feature to correctly identify disks before labeling them.  
• Click Clear Selections to deselect all devices in the list.  
StorNext 3.1.3 Installation Guide  
84  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Labeling Disks  
4
When you select one or more disks and click Label, a confirmation screen  
appears asking if you are sure you want to proceed. Click OK to continue.  
The Disk Labeler dialog box appears (figure 45). Table 18 describes the  
fields on the on the Disk Labeler dialog box.  
Figure 45 Disk Labeler Dialog  
Box  
Table 18 Disk Labeler Dialog  
Box  
Field / Button  
Description  
New Disk Label  
New Sectors  
Type the label for the disk.  
(Optional) Type the number of sectors on the  
disk.  
Create Label  
Skip Disk  
Cancel  
Write the new label to the disk and proceed to  
the next selected disk.  
Do not write a label to the disk and proceed to  
the next selected disk.  
Close the Disk Labeler dialog box.  
StorNext 3.1.3 Installation Guide  
85  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Use the License Identifier utility to display the host license identifier. The  
host license identifier is required to obtain a permanent license for  
StorNext.  
License Identifier  
4
To run the License Identifier utility, on the Windows Start menu, click All  
Programs > StorNext File System > License Identifier. A dialog box  
displays the host license identifier. Record this information.  
To obtain a license, use the Configuration Wizard. For more information,  
see Using the Configuration Wizard on page 63. Alternately, you can  
manually copy a license file to the StorNext Configuration directory.  
To obtain a permanent license, contact the Quantum Technical Assistance  
center at licenses@quantum.com and provide the following information:  
• The product serial number from the StorNext box or CD.  
• The number of client machines connecting to the MDC.  
• The host license identifier you recorded.  
A Quantum support representative will send you a license.dat file. Copy  
the file to the C:\Program Files\StorNext\config directory. (If there is a  
temporary license file, overwrite the file.)  
Simple File System  
Configuration  
The Simple File System Configuration utility can be used instead of the  
Server Configuration utility to configure a basic StorNext file system with  
a single stripe group.  
4
Note: Before configuring a file system, you should label disk devices.  
For more information, see Disk Device Labeler on page 83.  
To run the Simple File System Configuration utility, on the Windows  
Start menu, click All Programs > StorNext File System > Simple File System  
Configuration. The Simple Configuration Setup window appears  
(figure 46). Table 19 describes the fields on the Simple Configuration Setup  
window.  
To configure a simple file system, select the disks to use in the  
configuration. Specify settings (file system name, block size, stripe size,  
and maximum connections), and then click Configure.  
StorNext 3.1.3 Installation Guide  
86  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Figure 46 Simple File System  
Configuration  
Table 19 Simple File System  
Configuration  
Field / Button  
Clear Selections  
Select All  
Description  
Click to deselect all devices in the list.  
Click to select all devices in the list.  
File System Name  
Type the name of the file system. This is the  
name used by clients when establishing a  
mount point for the file system.  
File System Block  
Size  
Select the file system block size (in bytes). This  
is the minimum allocation size used by the file  
system.  
Stripe Size in Blocks  
Select the stripe size (in blocks). This is the  
number of file system blocks to write before  
switching to the next disk in the stripe group.  
Maximum  
Connections  
Type the maximum number of clients that can  
simultaneously mount the file system. (This  
value may be overridden by values in your  
product license code.)  
Configure  
Exit  
Click to save the configuration using the  
current settings. The configuration file is  
saved in the StorNext configuration directory.  
Click to quit the Simple File System  
Configuration utility.  
StorNext 3.1.3 Installation Guide  
87  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Start File System  
Services  
The Start File System Services utility starts all StorNext services on an  
MDC or StorNext client.  
4
The StorNext services must be running on the MDC for file systems to be  
active and available. In addition, the StorNext services must be running  
to use the StorNext configuration utilities and to mount file systems using  
the client software.  
To start StorNext File System services, on the Windows Start menu, click  
All Programs > StorNext File System > Start File System Services.  
Stop and Remove File  
System Services  
The Stop and Remove File System Services utility stops all StorNext  
services on an MDC or StorNext client, and also removes registry entries  
that automatically start the services on bootup.  
4
To stop and remove StorNext File System services, on the Windows Start  
menu, click All Programs > StorNext File System > Stop and Remove File  
System Services.  
To start the StorNext services again, you must use the Start File System  
Services utility. Rebooting the system will not restart services. For more  
information, see Start File System Services.  
Stop File System  
Services  
The Stop File System Services utility stops all StorNext services on an  
MDC or StorNext client.  
4
To stop StorNext File System services, on the Windows Start menu, click  
All Programs > StorNext File System > Stop System Services.  
To start the StorNext services again, reboot the system or use the Start File  
System Services utility. For more information, see Start File System  
Services.  
The Version Information utility displays information about the currently  
installed version of the StorNext server and/or client software, such as  
the version number, build number, and platform.  
Version Information  
4
To run the Version Information utility, on the Windows Start menu, click  
All Programs > StorNext File System > Version Information. A dialog box  
displays version information for the StorNext server and/or client  
software installed on your system.  
StorNext 3.1.3 Installation Guide  
88  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Check (Read-Only) a File  
The Check (Read-Only) a File System utility allows you to check a  
System  
4
StorNext file system for metadata corruption (due to a system crash, bad  
disk, or other failure). Run the utility on an MDC that contains the file  
system you want to check.  
To check a file system, on the Windows Start menu, click All Programs >  
StorNext File System > Check (Read-Only) a File System. Type the number  
that corresponds to the file system you want to check, and then press  
<Enter>.  
Because the file system check is run in read-only mode, any problems that  
exist are not repaired. If the utility identifies errors or corruption in  
metadata, you must repair the file system (see Repair a File System on  
page 91).  
The File System Startup List utility lets you modify the File System  
Manager (FSM) services list and set file system priority.  
File System Startup List 4  
The File System Manager is a process that manages the name space,  
allocations, and metadata coherency for a file system. Each file system  
uses its own FSM process. When there are multiple file systems (and  
therefore multiple FSM processes), the FSM services list controls which  
FSM processes are run when the server starts up, and also sets the  
priority for each file system (for failover configurations).  
To run the File System Startup List utility, on the Windows Start menu,  
click All Programs > StorNext File System > File System Startup List. The  
FSM Services List window appears (figure 47). Table 20 describes the  
fields on the FSM Services List window.  
StorNext 3.1.3 Installation Guide  
89  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Figure 47 File System Startup  
List  
Table 20 File System Startup  
List  
Field / Button  
New  
Description  
Click to add a file system to the FSM services  
list. Type the name of the file system and click  
OK.  
Delete  
Click to remove the selected file system from  
the FSM services list.  
Host Name  
Priority  
(Optional) Type the name of the host on  
which the file system is running.  
(Optional) Select the priority for the selected  
file system. This priority is used for failover  
configurations. 0 is highest priority and 9 is  
lowest priority.  
OK  
Click to save changes to the FSM services list.  
Cancel  
Click to quit the File System Startup List  
utility without saving changes.  
StorNext 3.1.3 Installation Guide  
90  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Re-initialize a File  
System  
The Re-initialize a File System utility allows you to initialize an existing  
file system. Initializing a file system prepares it for use.  
4
Caution: Re-initializing a file system will destroy all data on the file  
system.  
To initialize a file system, on the Windows Start menu, click All Programs  
> StorNext File System > Re-initialize a File System. Type the number that  
corresponds to the file system you want to re-initialize, and then press  
<Enter>.  
The Repair a File System utility lets you repair corrupted metadata on a  
file system. Repair a file system if errors were identified when checking  
the file system (see Check (Read-Only) a File System on page 89).  
Repair a File System  
4
The file system must be inactive in order to be repaired. To stop a file  
system, use the Server Administration utility (see Server Administration).  
To repair a file system, on the Windows Start menu, click All Programs >  
StorNext File System > Repair a File System. Type the number that  
corresponds to the file system you want to repair, and then press <Enter>.  
The Server Administration utility lets you view and modify stripe group  
properties and set quotas. A stripe group is a logical storage unit made  
up of one or more disks. A quota is a space limit that is set for specified  
users or groups.  
Server Administration  
4
To run the Server Administration utility, on the Windows Start menu,  
click All Programs > StorNext File System > Server Administration. The  
Administrator window appears (figure 48). The left pane shows file  
systems running on the currently connected MDC. Expand a file system  
to see stripe groups, quotas, and other properties.  
StorNext 3.1.3 Installation Guide  
91  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Figure 48 Server  
Administration  
On the Administrator window, do one of the following:  
• To connect to an MDC, click File > Connect to. Type the host name  
and click OK. File systems on the server appear in the left pane.  
• To start a file system, click it in the left pane. Click File > Start File  
System, and then click Start.  
• To activate a file system, click it in the left pane. Click File > Activate  
File System, and then click Activate.  
• To stop a file system, click it in the left pane. Click File > Stop File  
System, and then click Stop.  
• To update the list of file systems in the left pane, click View > Refresh.  
For more information about viewing and modifying file system  
properties and quotas, see the following sections:  
• File System Properties on page 93  
• Stripe Group Properties on page 94  
• Quota Properties on page 95  
• Quality of Service Information on page 97  
• Clients Information on page 97  
Note: Do not change settings on the Debug Settings dialog box  
unless directed to do so by the Quantum Technical Assistance  
Center.  
StorNext 3.1.3 Installation Guide  
92  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
File System Properties  
4
To view or change file system properties, click a file system in the left  
pane, and then click the file system name in the right pane. The File  
System Properties dialog box appears (figure 49). Table 21 describes the  
fields on the File System Properties dialog box.  
After making changes, click OK. (Not all fields can be modified on this  
dialog box.)  
Figure 49 Server  
Administration: File System  
Properties  
Table 21 Server  
Administration: File System  
Properties  
Field / Button  
Active Clients  
Description  
The number of active clients on the file  
system.  
Msg Buffer Size  
Fs Block Size  
Disk Devices  
Stripe Groups  
The size of the message buffer.  
The file system block size.  
The number of disk devices in the file system.  
The number of stripe groups in the file  
system.  
File System Quotas  
Select to enable file system quotas.  
StorNext 3.1.3 Installation Guide  
93  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Field / Button  
Description  
Distributed Locking  
Indicates if distributed locking is enabled or  
disabled.  
Windows Security  
Global Superuser  
Quality-of-Service  
Usage  
Indicates if Windows security is enabled or  
disabled.  
Indicates if the global superuse is enabled or  
disabled.  
Indicates if Quality of Service is enabled or  
disabled.  
Displays the amount of used and free storage  
space in the file system.  
Stripe Group Properties  
4
To view or change stripe group properties, expand a file system in the left  
pane, click Stripe Groups, and then click the stripe group name in the  
right pane. The Stripe Group Properties dialog box appears (figure 50).  
Table 22 describes the fields on the Stripe Group Properties dialog box.  
After making changes, click OK. (Not all fields can be modified on this  
dialog box.)  
Figure 50 Server  
Administration: Stripe Group  
Properties  
StorNext 3.1.3 Installation Guide  
94  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Table 22 Server  
Administration: Stripe Group  
Properties  
Field / Button  
Description  
Stripe Group Name  
Status  
The name of the stripe group.  
Shows the current status of the stripe group.  
Click Up to make the stripe group active or  
click Down to make the strip group inactive.  
Stripe Breadth  
The number of file system blocks to write  
before switching to the next disk in the stripe  
group.  
Stripe Depth  
Exclusive  
The number of disks in the stripe group.  
Indicates if only specified file types  
(associated with the stripe group affinities)  
can be stored on the stripe group.  
Metadata  
Journal  
Indicates if file system metadata can be stored  
on the stripe group.  
Indicates if the file system logging journal can  
be stored on the stripe group.  
Realtime  
(no longer supported)  
Multi-Path Method  
Indicates the method the file system uses to  
access the disk: round, static, or sticky.  
Usage  
Displays the amount of used and free storage  
space in the stripe group.  
Quota Properties  
4
Quotas define the amount of storage space a specified user or group is  
allowed to own. You can set hard or soft quota limits.  
To view or change quota properties, expand a file system in the left pane,  
and then click Quotas. The Quota Properties dialog box appears  
(figure 51). There are two tabs:  
• Set quotas for users on the User Quotas tab.  
• Set quotas for groups on the Group Quotas tab.  
StorNext 3.1.3 Installation Guide  
95  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Table 23 describes the fields on the User Quotas and Group Quotas tabs.  
After making changes, click OK. (Not all fields can be modified on this  
dialog box.)  
Figure 51 Server  
Administration: Quota  
Properties  
Table 23 Server  
Administration: Quota  
Properties  
Field / Button  
Description  
User Name / Group  
Name  
Type the name of the user or group to set a  
quota for.  
Usage  
Displays the percentage of the quota that has  
been used.  
Hard Limit  
Specify an amount in B, KB, MB, GB, or TB, or  
EB. This is the maximum amount of space the  
specified user or group can use.  
Soft Limit  
Specify an amount in B, KB, MB, GB, or TB, or  
EB. Once the user or group uses this amount  
of space, a warning is sent. (Typically this is  
80% of the hard limit.)  
StorNext 3.1.3 Installation Guide  
96  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Field / Button  
Time Limit  
Description  
Specify the amount of time it takes for the soft  
limit to turn into a hard limit.  
Get Quota  
Set Quota  
Click to get quota settings for the specified  
user or group.  
Click to set a quota for the specified user or  
group using the current settings.  
Quality of Service Information  
4
To view Quality of Service (QOS) information for a file system, expand a  
file system in the left pane, and then click QOS. Quality of Service  
information appears in the right pane, including stripe group, real-time  
limit, non-real-time reserve, committed RTIO, and the number of non-  
real-time clients.  
Clients Information  
4
To view information about clients connected to the file system, expand a  
file system in the left pane, and then click Clients. Information about the  
currently connected clients appears in the right pane, including client ID,  
type, location, up time, and when the client license expires.  
The Server Configuration utility lets you view and modify properties for  
an MDC. Use this utility to create a new server configuration or modify  
an existing configuration.  
Server Configuration  
4
To run the Server Configuration utility, on the Windows Start menu, click  
All Programs > StorNext File System > Server Configuration. The  
Configuration Administrator window appears (figure 52).  
StorNext 3.1.3 Installation Guide  
97  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Figure 52 Configuration  
Administrator  
On the Configuration Administrator window, do one of the following:  
• Click New to create a new configuration file.  
• Click Modify to edit an existing configuration file. Browse for the  
configuration (*.cfg) file and click Open.  
• Click Exit to close the Configuration Administrator window.  
When you create a new configuration file or open an existing  
configuration file for editing, the StorNext File System Configuration  
window appears. This window includes four tabs:  
• Global Settings on page 99  
• Disk Types on page 101  
• Disk Definitions on page 103  
• Stripe Groups on page 105  
Click a tab to view or modify StorNext File System properties. After  
making changes on one or more tabs, click OK to save the changes.  
Specify a name and a location for the *.cfg file, and then click Save.  
Note: Before configuring a file system, you should label disk devices.  
For more information, see Disk Device Labeler on page 83.  
StorNext 3.1.3 Installation Guide  
98  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Global Settings  
4
Use the Global Settings tab (figure 53) to specify general file system  
properties. Table 24 describes the fields on the Global Settings tab.  
Figure 53 Server  
Configuration: Global Settings  
Table 24 Server Configuration:  
Global Settings  
Field / Button  
Description  
Global Superuser  
(Optional) Select to allow a user with  
superuser privileges to have global access  
rights on the file system.  
Windows Security  
(Optional) Select to use Windows Security  
Reference Monitor (ACLs) on Windows  
clients.  
StorNext 3.1.3 Installation Guide  
99  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Field / Button  
Quotas  
Description  
(Optional) Select to enforce file system quotas  
and track storage usage for individual users  
and groups.  
Cluster File Locking  
(Optional) Select to send a warning when a  
user attempts to access a file that is locked or  
already in use.  
File Size Dynamic  
Expansion - Minimum  
Type the minimum number (in blocks) to  
allocate when a file is created.  
File Size Dynamic  
Expansion - Increment  
Type the initial increment (in blocks) by  
which a file is expanded.  
File Size Dynamic  
Expansion - Maximum  
Type the maximum increment (in blocks) by  
which a file is expanded.  
File System Block  
Size  
Select the file system block size (in bytes).  
Buffer Cache Size  
Journal Log Size  
Inode Cache Size  
Type the amount of memory (in MB) used for  
general metadata information caching.  
Type the maximum size (in MB) for the  
journal log.  
Type the number of entries in the inode cache.  
Maximum Debug Log  
Size  
Type the maximum size (in MB) for the debug  
log.  
Thread Pool Size  
Type the number of threads the FSS uses  
when reading and storing files.  
Maximum  
Connections  
Type the maximum number of simultaneous  
connections (SNFS clients and Administrative  
Tap clients) allowed by the FSS.  
StorNext 3.1.3 Installation Guide  
100  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Field / Button  
Description  
Allocation Strategy  
Select the method of allocation for new disk  
blocks:  
• Round: Alternate between similar stripe  
groups. (Default)  
• Fill: Fill the first stripe group before using  
the second.  
• Balance: Use the stripe group with the most  
free space.  
“Nobody” UID  
“Nobody” GID  
Type the Windows user ID to use when no  
user ID can be found using Active Directory.  
Type the Windows group ID to use when no  
group ID can be found using Active  
Directory.  
Default File Mode  
Type the permission mode to use when  
creating files.  
Default Directory  
Mode  
Type the permission mode to use when  
creating directories.  
Use Fabricated IDs  
Select if the metadata controller is running on  
Apple MacOS X.  
Disk Types  
4
Use the Disk Types tab (figure 54) to define disk types used in the file  
system.  
StorNext 3.1.3 Installation Guide  
101  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Figure 54 Server  
Configuration: Disk Types  
On the Disk Types tab, do one of the following:  
• To add a new disk type, click New.  
• To modify a disk type, select the disk type in the list and click Edit.  
• To delete a disk type, select it in the list and click Delete.  
When you add or modify a disk type, the Enter New Disk Type dialog box  
appears (figure 55). Table 25 describes the fields on the Enter New Disk  
Type dialog box.  
Note: The Sector and Sector Size fields are populated with values  
from the Disk Device Labeler utility. For more information, see  
Disk Device Labeler on page 83.  
StorNext 3.1.3 Installation Guide  
102  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Figure 55 Server  
Configuration: Enter New Disk  
Type  
Table 25 Server Configuration:  
Enter New Disk Type  
Field / Button  
Description  
Disk Type  
Sectors  
Type a descriptive name for the disk.  
Type the number of physical sectors on the  
disk.  
Sector Size  
OK  
Type the size of sectors on the disk.  
Click to create the new disk type with the  
specified properties.  
Cancel  
Click to close the Enter New Disk Type dialog  
box without saving changes.  
Disk Definitions  
4
Use the Disk Definitions tab (figure 56) to create disk definitions and  
modify disk specifications. Table 26 describes the fields on the Disk  
Definitions tab.  
StorNext 3.1.3 Installation Guide  
103  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Figure 56 Server  
Configuration: Disk Definitions  
Table 26 Server Configuration:  
Disk Definitions  
Field / Button  
Description  
Disks Available - New  
Click to create a new disk definition. Type a  
name for the disk and click OK.  
Disks Available -  
Delete  
Click to delete the selected disk definition.  
Status: Up  
Select to enable the selected disk definition.  
When enabled, the defined disk is available to  
the configured file system for I/O.  
Disk Type  
Select a disk type for the selected disk  
definition. (Disk types are defined on the Disk  
Types tab.)  
Device Names - New  
Click to add a device name to the disk  
definition. Type a device name and click OK.  
StorNext 3.1.3 Installation Guide  
104  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Field / Button  
Description  
Click to delete the selected device name.  
Device Names - Delete  
Stripe Groups  
4
Use the Stripe Groups tab (figure 57) to define stripe groups. (A stripe  
group is a logical storage unit consisting of one or more disk drives.)  
Table 27 describes the fields on the Stripe Groups tab.  
Figure 57 Server  
Configuration: Stripe Groups  
StorNext 3.1.3 Installation Guide  
105  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Table 27 Server Configuration:  
Stripe Groups  
Field / Button  
Description  
Stripe Groups  
Available - New  
Click to create a new stripe group. Type a  
name for the stripe group and click OK.  
Stripe Groups  
Available - Delete  
Click to delete the selected stripe group.  
Status: Up  
Select to enable the selected stripe group.  
When enabled, the stripe group is available to  
the configured file system for I/O.  
Exclusive  
Select to allow only file types associated with  
the affinities specified under Affinities to be  
stored on the stripe group.  
MetaData  
Select to allow file system metadata to be  
stored on the stripe group.  
Journal  
Select to allow the file system logging journal  
to be stored on the stripe group.  
Affinities - New  
Click to add a new affinity to the stripe group.  
Type the name of the new affinity and click  
OK. (Affinity names cannot be longer than  
eight characters.)  
Affinities - Delete  
Pathing Method  
Click to the delete the selected affinity.  
Select a method for how the file system  
accesses the disk:  
• Rotate: Chooses an I/O path based on load.  
• Static: Always uses the same I/O path.  
• Sticky: Chooses an I/O path based on the  
identity of the target file.  
Rtios  
Type the number of disk I/O operations per  
second available to real-time applications  
using the Quality of Service (QOS) API.  
RtiosReserve  
Type the minimum number of disk I/O  
operations per second reserved for non-real-  
time applications.  
StorNext 3.1.3 Installation Guide  
106  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4 Configuring StorNext  
Windows Configuration Utilities  
Field / Button  
RtTokenTimeout  
Description  
Type the number of seconds to wait for clients  
to respond to a token callback.  
Rtmb  
Type the number of MBs per second available  
to real-time applications using the Quality of  
Service (QOS) API.  
RtmbReserve  
Modify Drive List  
Type the minimum number of MBs per  
second reserved for non-real-time  
applications.  
Click to add or remove disks for the selected  
stripe group. Use the left and right arrows to  
add or remove disks in the Primary Disks list,  
and then click OK.  
Caution: When adding a disk to an existing stripe group, make sure  
the disk is added to the bottom of the Drive List. If the disk  
is inserted in the middle of the list, the file system behaves  
as if files on the file system are corrupted.  
StorNext 3.1.3 Installation Guide  
107  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix A  
AUninstalling StorNext  
If you no longer need to use StorNext, uninstall the software to remove it  
from your system. To uninstall StorNext, use the appropriate method for  
your operating system:  
• Uninstalling StorNext on Unix and Linux on page 108  
• Uninstalling StorNext on Windows on page 111  
Uninstalling StorNext on Unix and Linux  
To uninstall StorNext on a metadata controller (MDC), use the  
installation script (see Uninstalling SNSM and SNFS on page 109).  
To uninstall the StorNext client software, use the appropriate method for  
your operating system (see Uninstalling the StorNext Client Software on  
page 110).  
StorNext 3.1.3 Installation Guide  
108  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Appendix A Uninstalling StorNext  
Uninstalling StorNext on Unix and Linux  
Uninstalling SNSM and  
SNFS  
To uninstall StorNext File System and Storage Manager on an MDC  
running Unix or Linux, run the installation script with the -remove option.  
To launch the script, use the correct StorNext installation CD for your  
operating system.  
1
1 Log on to the MDC as root.  
2 Mount the StorNext installation CD and change to the CD root  
directory.  
Note: When you mount a CD in a Red hat 4 or 5 system, CDs are  
mounted by default with a noexec (non-executable) option  
which prevents you from proceeding with the installation.  
For Red Hat users only, before proceeding you must  
remount the CD by typing mount -o remount, exec ...  
3 List the installation directories on the CD. At the command prompt,  
type:  
ls -l  
4 Identify the correct installation directory for your operating system  
and hardware platform, and then change to that directory.  
For example, for Red Hat Linux 4 running on an x86 64-bit platform,  
change to the RedHat40AS_26x86_64 directory.  
5 Do one of the following:  
•
To uninstall StorNext Storage Manager and File System, at the  
command prompt, type:  
./install.stornext -remove  
•
To uninstall StorNext File System, at the command prompt, type:  
./install.snfs -remove  
The installation script runs (figure 58).  
StorNext 3.1.3 Installation Guide  
109  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Appendix A Uninstalling StorNext  
Uninstalling StorNext on Unix and Linux  
Figure 58 StorNext Remove  
Main Menu  
6 Type 2 and press <Enter>.  
7 After the uninstall process is complete, type 4 and press <Enter> to  
exit the installation script.  
Uninstalling the StorNext  
To uninstall the StorNext client software, unmount all file systems and  
stop StorNext software. Then remove the client software package using  
the appropriate command for your operating system.  
Client Software  
1
Note: This procedure removes the client software only. To uninstall  
StorNext File System and Storage Manager, see Uninstalling  
SNSM and SNFS on page 109.  
1 Unmount all file systems. To unmount a file system, at the command  
prompt, type:  
umount <mount point>  
where <mount point> is the location where the file system is mounted.  
2 Stop the StorNext client software. At the command prompt, type:  
/etc/init.d/cvfs fullstop  
3 Remove the StorNext software package using the correct commands  
for your operating system.  
• Linux:  
rpm -e <package name>  
where <package name> is the name of the client software package  
that was installed.  
• Solaris:  
pkgrm ADICsnfs  
• HP-UX:  
StorNext 3.1.3 Installation Guide  
110  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Appendix A Uninstalling StorNext  
Uninstalling StorNext on Windows  
swremove –x mount_all_filesystems=false snfsclient  
• IBM AIX:  
installp –u <package name>  
where <package name> is the name of the client software package  
that was installed.  
• SGI IRIX:  
Inst  
remove cv_base  
remove cv_clnt  
go  
Note: If you do not know the package name, you can download  
the client software for your operating system and check  
the package name (see Downloading the StorNext Client  
Software on page 39).  
Uninstalling StorNext on Windows  
To uninstall StorNext (server or client) on a Windows system, use the  
Add or Remove Programs control panel.  
1 Open the Windows Control Panel, and then double-click Add or  
Remove Programs.  
The Add or Remove Programs window appears.  
2 In the list of currently installed programs, click StorNext File System,  
and then click Remove.  
3 Click Yes to confirm the removal.  
4 After the uninstall process is complete, reboot the system.  
StorNext 3.1.3 Installation Guide  
111  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Appendix B  
BStorNext Administration  
Tasks  
Use the following information to perform specific file system  
configuration tasks that do not apply to a typical StorNext set up.  
Sharing a Library Between Applications  
If two or more software applications (on one or multiple machines), are  
configured to use the same library, then you must use the following  
procedure to enable the library to be shared and to prevent media being  
overwritten when these applications are used. This task must be  
performed when the Configuration Wizard (CW) is run during initial  
StorNext setup and configuration. For more information on using the  
CW, refer to the StorNext Installation Guide.  
Note: For library sharing to be effective, the steps in the following  
procedure must be performed in the order in which they are  
presented.  
You must have root privileges to perform this task.  
StorNext 3.1.3 Installation Guide  
112  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Appendix B StorNext Administration Tasks  
Sharing a Library Between Applications  
1 When you match hardware devices to their correct slots on the  
Matched Devices With Slots screen (you will see this screen during the  
execution of Step 4 of the Configuration Wizard, Add Tape Drive),  
only configure the tape drives that your software application will  
use. You do not need to configure all tape drives listed as part of the  
library.  
2 Once the tape drives are added and configured in Step 4 of the CW  
(Add Tape Drive), but before continuing to Step 5 of the CW (Add  
Media), go to a metadata controller and perform these steps:  
a Change directory to the config directory. Type:  
cd /usr/adic/MSM/internal/config  
b List all files in the config directory. Type:  
ls -l  
c Using a text editor, edit the media_file_<library_name> file. For  
example:  
vi media_file_<library_name>  
The media_file contains a filter for barcode labels that are read by  
StorNext. This action is performed by using regular expressions.  
(A regular expression provides a mechanism to select strings  
from a set of character strings. In the above example, the  
character strings refer to the barcode labels.) In the example  
above, <library_name> is the library that was configured in Step 3,  
Add Library, of the CW.  
d Set up the pattern matching of the media file.  
Multiple entries may exist in the media file. Read the examples in  
the file to learn how to set up pattern matching.  
These are examples of pattern matching:  
scsi_archive 1111.. (brings in all media with the 1111 prefix)  
scsi_archive AB9... (brings in all six-character media labels with  
the AB9 prefix)  
scsi_archive CLN1.. (brings in all media that have the CLN1 prefix)  
3 Continue to the Add Media section of the Configuration Wizard.  
StorNext 3.1.3 Installation Guide  
113  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix B StorNext Administration Tasks  
Manually Modifying Storage Manager Configuration  
Manually Modifying Storage Manager Configuration  
StorNext employs global parameters that define the Storage Manager  
configuration. Although the default values in these files are sufficient for  
most installations, you can edit the files to customize the StorNext  
software for your specific installation. This section provides a procedure  
that can be used to modify the following StorNext configuration files:  
• /usr/adic/TSM/config/fs_sysparm_override  
• /usr/adic/TSM/config/filesize.config  
• /usr/adic/TSM/logs/log_params  
fs_sysparm_override  
Configuration File  
The fs_sysparm_override configuration file is used to tune items related to  
system administration, drives and media, media manager interface, and  
other miscellaneous items. For more information about the parameters  
that can be placed into the fs_sysparm_override configuration file, refer to  
the fs_sysparm.README file.  
2
Caution: Incorrect modification of the fs_sysparm_override  
configuration file can cause a serious, adverse effect on  
StorNext functionality. Before modifying this file,  
Quantum recommends that you contact Quantum Global  
Services.  
Caution: If you have files larger than 100GB and are using LTO2  
media, the MED_SEG_OVER_LTO parameter may be  
modified to a value less than or equal to 190G to reduce  
file fragmentation. This has the adverse effect of reducing  
the potential for parallel I/O for multiple file segments.  
Setting the MED_SEG_OVER_LTO parameter to a value  
larger than 190GB may result in allocation failures that  
prevent file movement to tape.  
StorNext 3.1.3 Installation Guide  
114  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Appendix B StorNext Administration Tasks  
Manually Modifying Storage Manager Configuration  
filesize.config  
Configuration File  
The filesize.config configuration file is used to control the file steering  
feature and has these characteristics:  
2
• Allows the placement of files on different media types, based on the  
size of the files  
• Specifies which drive pool a policy class should use when storing  
data  
• Contains specific syntax and usage information  
• Enables the system administrator to make changes without recycling  
the Tertiary Manager software  
log_params  
Configuration File  
The log_params configuration file is used to control various levels of trace  
logging. The file specifies each log level and how to enable and/or  
disable it.  
2
Use the following procedure to modify the fs_sysparm_override,  
filesize.config, or log_params configuration files.  
1 Use a text editor to open one of the following configuration files:  
•
•
•
/usr/adic/TSM/config/fs_sysparm_override  
/usr/adic/TSM/config/filesize.config  
/usr/adic/TSM/logs/log_params  
2 Locate the parameter you want to modify and replace the setting  
with a new, valid value.  
When editing a file, be sure to follow the format used by entries in the  
file. For example, in the fs_sysparm_override and filesize.config files,  
all entries must be in the format: name=value;  
3 Recycle the Tertiary Manager software.  
a Stop the software by typing TSM_control stop  
b Restart the software by typing TSM_control start  
StorNext 3.1.3 Installation Guide  
115  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Appendix B StorNext Administration Tasks  
Connecting to a StorNext Network Using Xsan 1.4.2  
Connecting to a StorNext Network Using Xsan 1.4.2  
If you are using Apple Xsan 1.4.2, follow the procedure below to connect  
to a StorNext network. The procedure consists of mounting the StorNext  
file system onto the OSx computer, and then creating an automount.plist  
to enable mounting the StorNext file system whenever the Macintosh is  
rebooted.  
Do not use the procedure if you are using Xsan2, which has a slightly  
different procedure described in Connecting to a StorNext Network  
Using Xsan 2 on page 119.  
Mounting SNFS on the  
OSx Computer  
Follow this procedure to mount the StorNext file system.  
2
1 Connect the Apple computer to the SAN's metadata Ethernet and  
Fibre Channel networks.  
2 Install Xsan 1.4.2 software on the Apple computer.  
3 After Xsan 1.4.2 is installed, follow these steps to configure the  
software:  
a On the Apple client, open Xsan Admin, which is located under  
the Finder > Applications > Server folder, and then connect to  
the Apple computer.  
b Select the SAN in the SAN Components list.  
c Click Setup, and then click Computers.  
d Double-click the client in the list (located in the center of the  
window).  
e Enter the Xsan serial number (printed on a sticker on the Xsan  
Installation disc sleeve).  
f Click Save, and then quit Xsan Admin.  
4 Navigate to an existing StorNext client on the SAN and print a copy  
of its fsnameservers file.  
On Unix: the fsnamerservers file is located at /usr/cvfs/config/.  
StorNext 3.1.3 Installation Guide  
116  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Appendix B StorNext Administration Tasks  
Connecting to a StorNext Network Using Xsan 1.4.2  
On Windows: the fsnamerservers file is located at  
\%cvfsroot%\config\ (where %cvfsroot% is the directory where the  
StorNext software is installed). This directory is usually located in  
C:\Program Files\Stornext\config\.  
5 Create a new plaintext file called fsnameservers in the /Library/  
FileSystems/Xsan/config/ directory. Populate the file with the content  
of the StorNext file you printed in the previous step.  
Note: If the content of the fsnameservers file specifies the  
metadata controller by its fully qualified domain name  
(FQDN), you must convert this to the metadata controller's  
IP address by using the command host <FQDN>  
6 Type the command sudo rm /Library/Filesystems/Xsan/config/  
.auth_secret to remove the .auth_secret file from the Macintosh OS X  
client.  
Caution: If you do not remove the .auth_secret file from the  
Macintosh OS X client, the metadata controller  
server and the client will be unable to  
communicate and FSMPM could fail.  
7 Restart the Macintosh OS X system by typing on the terminal sudo  
reboot. Alternatively, you can restart by selecting Restart in the  
Apple menu.  
8 Verify that the file system has started by typing in the terminal  
/Library/FileSystems/Xsan/bin/cvadmin. You should see a list of file  
systems that contain the StorNext filesystem. If the file system does  
not appear in the list, repeat step 3.  
9 Create a mount point for the file system by creating a new folder at  
/Volumes where the file system will be mounted. The name of this  
directory should be the name of the file system. In the terminal type  
the following commands:  
mkdir -p /Volumes/file_system_name  
chmod -R 777 /Volumes/file_system_name  
10 Mount the StorNext FS file system to the mount point by typing the  
following command in the terminal:  
StorNext 3.1.3 Installation Guide  
117  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix B StorNext Administration Tasks  
Connecting to a StorNext Network Using Xsan 1.4.2  
sudo mount -t acfs fsname /Volumes/fsname (where <fsname> is the  
name of the file system). The SNFS filesystem should now be  
mounted on the OS X computer.  
Creating the  
automount.plist File  
In order to mount the StorNext file system whenever the Macintosh client  
is rebooted, configure the automount.plist file. Xsan 1.4.2 uses the  
automount.plist file to mount SAN volumes.  
2
1 Use the command vi /Library/Filesystems/Xsan/config/automount.plist  
to create the automount.plist file.  
2 Copy and paste the text from the automount.plist template below into  
the file you just created.  
3 Change Volume_name to the name of your mounted file system.  
The automount.plist Template  
2
Copy and paste the text from the following template into the  
automount.plist file as described in step 2 above.  
<?xml version=”1.0” encoding="UTF-8”?>  
<!DOCTYPE plist PUBLIC “-//Apple Computer//DTD PLIST 1.0//EN”  
“http://www.apple.com/DTDs/PropertyList-1.0.dtd”>  
<plist version=”1.0?>  
<dict>  
<key>Volume_name</key>  
<dict>  
<key>AutoMount</key>  
<string>rw</string>  
<key>MountOptions</key>  
<dict/>  
</dict>  
<key>Another_volume_name</key>  
<dict>  
<key>AutoMount</key>  
<string>rw</string>  
<key>MountOptions</key>  
<dict/>  
</dict>  
</dict>  
</plist>  
StorNext 3.1.3 Installation Guide  
118  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Appendix B StorNext Administration Tasks  
Connecting to a StorNext Network Using Xsan 2  
Connecting to a StorNext Network Using Xsan 2  
If you are using Apple Xsan 2.2 or earlier, follow the procedure below to  
connect to a StorNext network. The procedure consists of mounting the  
StorNext file system onto the Mac OS X computer, and then creating an  
automount.plist to enable mounting the StorNext file system whenever  
the Macintosh is rebooted.  
Do not use the procedure if you are using Xsan 1.4.2, which has a slightly  
different procedure described in Connecting to a StorNext Network  
Using Xsan 1.4.2 on page 116.  
Mounting SNFS on the  
Mac OS X Computer  
Follow this procedure to mount the StorNext file system.  
2
1 Connect the Apple computer to the SAN's metadata Ethernet and  
Fibre Channel networks.  
2 Install Xsan 2 software on the Apple computer. (Xsan 2.1.1 is  
supported only by the Leopard operating system. Snow Leopard  
operating systems require Xsan 2.2.)  
3 Create the file /etc/systemserialnumbers/xsan using that Macintosh’s  
Xsan serial number.  
You must create the directory /etc/systemserialnumbers if it doesn't  
already exist. The format of the serial number file is a two-line file:  
XSAN-020-XXX-XXX-X-XXX-XXX-XXX-XXX-XXX-XXX-X  
registered to|organization  
Note: The file does not have a trailing return on the last line. Use  
the following:  
cat > /etc/systemserialnumbers/xsan and end with ^D^D (where  
^D^D is control-D control-D)  
If you are unable to browse to the systemserialnumbers directory, use  
the cat or echo commands to insert information into the Xsan file  
under that directory.  
4 Copy from the following template and paste into the file to create the  
file config.plist in /Library/Filesystems/Xsan/config/.  
StorNext 3.1.3 Installation Guide  
119  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Appendix B StorNext Administration Tasks  
Connecting to a StorNext Network Using Xsan 2  
Note: Items in red indicate data you should enter which applies  
to your configuration. Do not enter the literal red text  
shown in the template.  
For example, for <string>My IP Address</string> you would  
enter the netmask in the format X.Y.Z.0/24 (for example,  
<string>10.65.182.0/24</string>) not the words “My IP  
Address.”  
<?xml version="1.0" encoding="UTF-8"?>  
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://  
www.apple.com/DTDs/PropertyList-1.0.dtd">  
<plist version="1.0">  
<dict>  
<key>computers</key>  
<array/>  
<key>metadataNetwork</key>  
<string>My IP Address</string>  
<key>ownerEmail</key>  
<string>me@mycompany.com</string>  
<key>ownerName</key>  
<string>My Name</string>  
<key>role</key>  
<string>CLIENT</string>  
<key>sanName</key>  
<string>My SAN name</string>  
<key>serialNumbers</key>  
<array>  
<dict>  
<key>license</key>  
<string>xsan client license number</string>  
<key>organization</key>  
<string>organization name</string>  
<key>registeredTo</key>  
<string>registered to name</string>  
</dict>  
</array>  
</dict>  
</plist>  
5 Copy from the following template and paste into the file to create an  
automount.plist file located in /Library/Filesystems/Xsan/config/.  
StorNext 3.1.3 Installation Guide  
120  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix B StorNext Administration Tasks  
Connecting to a StorNext Network Using Xsan 2  
Note: Items in red indicate data you should enter which applies  
to your configuration. Do not enter the red text shown in  
the template.  
For example, for <key>file system</key> you would enter  
the name of your file system, not “file system.”  
<?xml version="1.0" encoding="UTF-8"?>  
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://  
www.apple.com/DTDs/PropertyList-1.0.dtd">  
<plist version="1.0">  
<dict>  
<key>file system</key>  
<dict>  
<key>AutoMount</key>  
<string>rw</string>  
<key>MountOptions</key>  
<dict/>  
</dict>  
</plist>  
6 Navigate to an existing StorNext server on the SAN and copy the  
fsnameservers file to your Macintosh client in /Library/Filesystems/Xsan/  
config/. This file should contain the IP addresses of the name server  
machines.  
On Unix: the fsnameservers file is located at /usr/cvfs/config/.  
On Windows: the fsnameservers file is located at \%cvfsroot%\config\  
(where %cvfsroot% is the directory where the StorNext software is  
installed). This directory is usually located in C:\Program  
Files\Stornext\config\.  
Note: If the content of the fsnameservers file specifies a fully  
qualified domain name (FQDN), you must convert this to  
the metadata controller's IP address by using the  
command host <FQDN>.  
7 Run RegisterSeRV in Terminal to ensure that the serial number is  
recognized. Text will be returned if the serial number is not  
recognized. (No messages are displayed if the serial number is  
successfully registered.)  
StorNext 3.1.3 Installation Guide  
121  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix B StorNext Administration Tasks  
Viewing a Fibre Channel Device  
8 Run the following in Terminal to update Xsan with the new file  
system information:  
launchctl unload /System/Library/LaunchDaemons/com.apple.xsan.plist  
launchctl load /System/Library/LaunchDaemons/com.apple.xsan.plist  
Note: Unload will fail if plist is not loaded.  
If the file system does not mount automatically, manually mount the  
StorNext file system. In the Terminal type xsanctl mount <fsname> Where  
<fsname> is the file system name displayed in cvadmin. The SNFS file  
system should now be mounted on the Mac OS X computer.  
Viewing a Fibre Channel Device  
Use this procedure to add a Fibre Channel (FC) device. Before adding a  
FC device, first configure the Host Bus Adapter (HBA) card so you can  
view the device. Use the fs_scsi -p command to make sure you can view  
your devices over FC. FC devices include tape libraries, individual  
drives, or RAID disk.  
Note: The fs_scsi -p command is only available if the storage  
manager is installed on the FSM server.  
1 Type the /usr/adic/TSM/util/fs_scsi -p command to make sure that the  
necessary devices can be viewed over FC.  
• To view tape libraries, access the StorNext GUI to view your tape  
libraries.  
• To view individual drives or RAID LUNs, access either the StorNext  
or SNFS GUI.  
To add a disk, see Chapter 6, “Managing the File System,” in the StorNext  
User’s Guide. To add a tape drive to a configured library, see Chapter 8,  
“Managing Drives and Disks,” in the StorNext User’s Guide.  
StorNext 3.1.3 Installation Guide  
122  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Appendix B StorNext Administration Tasks  
StorNext Log Rolling Administration  
StorNext Log Rolling Administration  
Use the following procedures to configure StorNext log rolling options.  
Changing Log Rolling  
Times  
Use this procedure to change the frequency of rolling the StorNext logs.  
This process requires that you edit the tldm crontab to set log times. Use  
this procedure to edit tdlm crontab.  
2
1 Log on as root.  
2 Edit the tdlm crontab and update the sn_log_update script.  
Below is an example crontab:  
0 1,7,13,19 * * * /usr/adic/www/bin/cmdwrap /usr/adic/util/sn_log_update /usr/  
adic  
where 0 1,7,13,19 * * * designates the times when logs run.  
In this release of StorNext the sn_log_update information is overwritten  
and no longer contains the $DEF_SIZE or the $DEF_LOGS variables. These  
entries are now contained in the sn_log_update.cfg file  
Log Rolling Options  
2
You can change these options to optimize log rolling.  
• -s: This option sets the directory where logs are saved (copied) to as  
they are rolled. This directory is typically a managed directory. For  
example:  
sn_log_update [-s <dir>]  
where <dir> is the directory where you want the logs to reside.  
• $DEF_SIZE = 2000000: This is the default size at which logs are rolled.  
Edit this entry in the /usr/adic/util/sn_log_update.cfg file if you want  
the log sizes to be larger or smaller.  
• $DEF_LOGS = 28: This is the default number of logs that are saved  
before they are deleted. Edit this entry in the /usr/adic/util/  
sn_log_update.cfg file if you want to save less than 28 logs or are  
saving the logs to a managed directory.  
StorNext 3.1.3 Installation Guide  
123  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Appendix B StorNext Administration Tasks  
Avoiding Poor System Performance  
Avoiding Poor System Performance  
Most systems run administrator scripts to rebuild namespace databases  
and/or to remove certain files. Unfortunately, running these scripts can  
degrade StorNext performance. It is recommended that you review  
administrator scripts to determine if they may adversely affect your  
StorNext installation and its performance.  
For example, many UNIX systems have a find command in the root  
crontab that traverses the entire directory hierarchy while searching for  
old temporary and core files. Typically, the find commands are configured  
only to run on the local file system. However by default, these commands  
do not skip StorNext file systems because they are considered to be local,  
even though the file system manager may be running remotely. StorNext  
performance can be dramatically degraded when these commands visit a  
StorNext file system if the system contains a large number of files.  
If StorNext performance is degraded to an unacceptable level due to the  
operation of administrator scripts, you can modify them to skip StorNext  
file systems. A sample command (original and modified is shown below:  
On IRIX, by default, the root crontab contains the following find  
command:  
find / -local -type f '(' -name core -o -name dead.letter ')' -atime +7 -mtime + 7  
-exec rm -f '{}' ';'  
To prevent the find command from searching in StorNext file systems,  
modify it as shown:  
'(' -type d -fstype cvfs -prune ')' -o  
The modified find command looks like this:  
find / -local '(' -type d -fstype cvfs ')' -o -type f '(' -name core -o -name  
dead.letter ')' -atime +7 –mtime +7 -exec rm -f '{}' ';'  
StorNext 3.1.3 Installation Guide  
124  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Appendix C  
CStorNext Files  
StorNext creates a series of files that are used and modified to configure a  
file system. This section includes an expanded example.cfg file and a  
listing of the most commonly used StorNext files with descriptions and  
locations for each.  
The example.cfg File  
The following is listing of the configuration file created by StorNext. This  
file is modified during the configuration of a file system. The location for  
this file is: /usr/cvfs/examples/example.cfg  
# *************************************************************************  
# A global section for defining file system-wide parameters.  
#
# For Explanations of Values in this file see the following:  
#
# UNIX Users: man cvfs_config  
# Windows Users: Start > Programs > StorNext File System > Help >  
# Configuration File Internal Format  
StorNext 3.1.3 Installation Guide  
125  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Appendix C StorNext Files  
The example.cfg File  
# *************************************************************************  
GlobalSuperUser  
Systems ##  
Yes ## Must be set to Yes for SNMS Managed File  
WindowsSecurity  
Quotas  
No  
No  
No  
FileLocks  
DataMigration  
InodeExpandMin  
InodeExpandInc  
InodeExpandMax  
FsBlockSize  
No  
32K  
## SNMS Managed File Systems Only ##  
128K  
8M  
16K  
16M  
Round  
32  
JournalSize  
AllocationStrategy  
MaxConnections  
ForceStripeAlignment Yes  
Debug  
0x0  
4M  
MaxLogSize  
MaxLogs  
4
#
# Globals Defaulted  
#
# ThreadPoolSize  
# InodeCacheSize  
# BufferCacheSize  
# StripeAlignSize  
64 # default 16, 2 MB memory per thread  
32K # 800-1000 bytes each, default 8K  
64M # default 32MB  
2M # auto alignment, default MAX(StripeBreadth)  
50 # in MBs, default 100MB reserved per client  
300 # default 180 secs  
# MaxMBPerClientReserve  
# OpHangLimitSecs  
# DataMigrationThreadPoolSize 128 # Managed only, default 8  
# *************************************************************************  
# A disktype section for defining disk hardware parameters.  
*************************************************************************  
StorNext 3.1.3 Installation Guide  
126  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix C StorNext Files  
The example.cfg File  
[DiskType MetaDrive] ##1+1 Raid 1 Mirrored Pair##  
Sectors XXXXXXXX ## Sectors Per Disk From Command "cvlabel -l" ##  
SectorSize 512  
[DiskType JournalDrive] ##1+1 Raid 1 Mirrored Pair##  
Sectors XXXXXXXX  
SectorSize 512  
[DiskType VideoDrive] ##8+1 Raid 5 Lun for Video##  
Sectors XXXXXXXX  
SectorSize 512  
[DiskType AudioDrive] ##4+1 Raid 3 Lun for Audio##  
Sectors XXXXXXXX  
SectorSize 512  
[DiskType DataDrive] ##4+1 Raid 5 Lun for Regular Data##  
Sectors XXXXXXXX  
SectorSize 512  
# *************************************************************************  
# A disk section for defining disks in the hardware configuration.  
*************************************************************************  
[Disk CvfsDisk0]  
Status UP  
Type MetaDrive  
[Disk CvfsDisk1]  
Status UP  
Type JournalDrive  
[Disk CvfsDisk2]  
StorNext 3.1.3 Installation Guide  
127  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix C StorNext Files  
The example.cfg File  
Status UP  
Type VideoDrive  
[Disk CvfsDisk3]  
Status UP  
Type VideoDrive  
[Disk CvfsDisk4]  
Status UP  
Type VideoDrive  
[Disk CvfsDisk5]  
Status UP  
Type VideoDrive  
[Disk CvfsDisk6]  
Status UP  
Type VideoDrive  
[Disk CvfsDisk7]  
Status UP  
Type VideoDrive  
[Disk CvfsDisk8]  
Status UP  
Type VideoDrive  
[Disk CvfsDisk9]  
Status UP  
Type VideoDrive  
[Disk CvfsDisk10]  
Status UP  
Type AudioDrive  
StorNext 3.1.3 Installation Guide  
128  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix C StorNext Files  
The example.cfg File  
[Disk CvfsDisk11]  
Status UP  
Type AudioDrive  
[Disk CvfsDisk12]  
Status UP  
Type AudioDrive  
[Disk CvfsDisk13]  
Status UP  
Type AudioDrive  
[Disk CvfsDisk14]  
Status UP  
Type DataDrive  
[Disk CvfsDisk15]  
Status UP  
Type DataDrive  
[Disk CvfsDisk16]  
Status UP  
Type DataDrive  
[Disk CvfsDisk17]  
Status UP  
Type DataDrive  
# *************************************************************************  
# A stripe section for defining stripe groups.  
# *************************************************************************  
[StripeGroup MetaFiles]  
StorNext 3.1.3 Installation Guide  
129  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix C StorNext Files  
The example.cfg File  
Status UP  
MetaData Yes  
Journal No  
Exclusive Yes  
Read Enabled  
Write Enabled  
StripeBreadth 256K  
MultiPathMethod Rotate  
Node CvfsDisk0 0  
[StripeGroup JournFiles]  
Status UP  
Journal Yes  
MetaData No  
Exclusive Yes  
Read Enabled  
Write Enabled  
StripeBreadth 256K  
MultiPathMethod Rotate  
Node CvfsDisk1 0  
[StripeGroup VideoFiles]  
Status UP  
Exclusive Yes##Exclusive StripeGroup for Video Files Only##  
Affinity VidFiles  
Read Enabled  
Write Enabled  
StripeBreadth 4M  
MultiPathMethod Rotate  
Node CvfsDisk2 0  
Node CvfsDisk3 1  
Node CvfsDisk4 2  
Node CvfsDisk5 3  
StorNext 3.1.3 Installation Guide  
130  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix C StorNext Files  
The example.cfg File  
Node CvfsDisk6 4  
Node CvfsDisk7 5  
Node CvfsDisk8 6  
Node CvfsDisk9 7  
[StripeGroup AudioFiles]  
Status UP  
Exclusive Yes##Exclusive StripeGroup for Audio File Only##  
Affinity AudFiles  
Read Enabled  
Write Enabled  
StripeBreadth 1M  
MultiPathMethod Rotate  
Node CvfsDisk10 0  
Node CvfsDisk11 1  
Node CvfsDisk12 2  
Node CvfsDisk13 3  
StripeGroup RegularFiles]  
Status UP  
Exclusive No##Non-Exclusive StripeGroup for all Files##  
Read Enabled  
Write Enabled  
StripeBreadth 256K  
MultiPathMethod Rotate  
Node CvfsDisk14 0  
Node CvfsDisk15 1  
Node CvfsDisk16 2  
Node CvfsDisk17 3  
StorNext 3.1.3 Installation Guide  
131  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix C StorNext Files  
Commonly Used SNFS Files  
Commonly Used SNFS Files  
The following is a list of commonly used SNFS files and provides the  
name and location of the files installed during a SNFS installation. Each  
entry also includes a brief description of the file’s utility in SNFS  
functionality.  
• /usr/cvfs/bin/  
cvadmin — Allows you to view and modify the active SNFS system(s).  
cvaffinity — Associates a stripe group with a media type.  
cvcp — A high-speed file copy utility.  
cvdb — A client debugging tool.  
cvdbset — A wrapper for cvdb.  
cvfsck — A utility to check and repair a SNFS file system.  
cvfsd — SNFS server daemon launched at mount time.  
cvfsdb — A metadata debugging tool.  
cvfsid — Provides the SNFS site identifier  
cvlabel — Lists and labels SNFS drives.  
cvmkdir — Associates an affinity with a directory.  
cvmkfile — Pre-allocates space and attributes for a file.  
cvmkfs — Initializes a SNFS file system  
cvupdatefs — Modifies the configuration of an existing SNFS file  
system.  
cvversions — Lists SNFS version information.  
fsm — A SNFS server daemon.  
fsmpm — A SNFS portmapper daemon.  
mount_cvfs — A mount helper for SNFS.  
snfsdefrag — Defragments files and file systems.  
• /usr/cvfs/config/  
fsmlist — A list of SNFS file systems that have been serviced.  
StorNext 3.1.3 Installation Guide  
132  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Appendix C StorNext Files  
Commonly Used SNFS Files  
fsnameservers — Identifies the SNFS name service coordinators.  
license.dat — The SNFS license file.  
• /usr/cvfs/data/<FS Name>/log/  
Cvlog — debug and runtime messages  
• /usr/cvfs/debug/  
cvfsd.out — Displays debug and status messages from cvfsd.  
fsmpm.out — Displays debug and status messages from fsmpm.  
mountall.out — Displays debug and status messages from mount_cvfs.  
nssdbg.out — Displays debug and status messages from fsmpm.  
• /usr/cvfs/CLIENTS/ — The following are client installation files for  
various operating systems.  
sn_dsm_aix52_client.tar  
sn_dsm_irix65f_client.tar  
sn_dsm_irix65m_client.tar  
sn_dsm_linuxRH_80i386smp_client.tar  
sn_dsm_linuxRH_80i386up_client.tar  
sn_dsm_linuxRH_AS_3i386smp_client.tar  
sn_dsm_linuxRH_AS_3ia64smp_client.tar  
sn_dsm_linuxSuSE_81i386smp_client.tar  
sn_dsm_linuxSuSE_81i386up_client.tar  
sn_dsm_solaris58sparc64_client.tar  
sn_dsm_solaris59sparc64_client.tar  
sn_dsm_win2k_client.exe  
sn_dsm_winnt_client.exe  
• /usr/cvfs/docs/  
external_api.pdf — Documentation for the SNFS API.  
• /usr/cvfs/examples/ — The following are examples of files that are  
present in certain file system configurations. For example, the  
cvfail.example will be in the configuration file of a system running  
failover.  
cvfail.example  
StorNext 3.1.3 Installation Guide  
133  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix C StorNext Files  
Commonly Used SNFS Files  
cvlabels.example  
cvpaths.example  
example.cfg  
fsmlist.example  
fsnameservers.example  
fsports.example  
fsroutes.example  
• /usr/cvfs/lib/  
cvextapi.a — A SNFS API library.  
• libcvfsdmapi.a — A SNFS DMAPI library.  
• /usr/cvfs/src/  
cvapi.c — A sample API application.  
StorNext 3.1.3 Installation Guide  
134  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix D  
DQuality of Service Guide  
This appendix describes how to configure and use the StorNext File  
System (SNFS) Quality of Service (QOS) feature. QOS allows real-time  
applications to reserve some amount of bandwidth on the storage system.  
This is known as real-time I/O (RTIO). SNFS gates (that is, throttles) non-  
real-time applications so their I/O accesses do not interfere with the real-  
time application.  
QOS is a passive implementation in that it does not actively monitor a  
process’ activity and then schedule the process so that it receives the  
bandwidth it has requested. It is up to real-time applications to gate their  
own I/O requests to the desired rate. SNFS QOS provides a “get out of  
the way” gating for non-real-time I/O requests so they do not hinder the  
real-time requests.  
QOS is fully functional in SNFS version 2.1.2 and later. Earlier versions of  
SNFS do not support QOS. If a pre-QOS client connects, the file system  
manager (FSM) logs a message to syslog. If the pre-QOS client connects  
while real-time I/O is in progress, the message is logged at the critical  
event level.  
The remainder of this document explains the client and server  
configuration settings for QOS; describes the use of tokens and callbacks  
for gating non-real-time I/O; describes setting real-time I/O on a file; and  
discusses the performance monitoring tools that are available for  
diagnosis.  
StorNext 3.1.3 Installation Guide  
135  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Appendix D Quality of Service Guide  
Overview  
Overview  
QOS is stripe-group centric; all configuration and operations act on a  
specific stripe group. This allows stripe groups with differing access  
characteristics to use different real-time settings. When a client requests a  
certain amount of real-time I/O, the FSM informs all connected clients of  
the amount remaining and available for non-real-time I/O accesses.  
This information is encapsulated in a token. Think of the token as a  
capability that enables the client to perform I/O without contacting the  
FSM. When the amount of real-time I/O on a stripe group changes, the  
FSM informs all connected clients about the change via a callback.  
In both the client and the server, QOS is implemented as a state machine.  
Each state has a set of events and allowable actions. In this document, the  
term state thusly refers to the internal state machine.  
QOS is a passive, not active implementation of real-time I/O. In an active  
implementation (such as the SGI IRIX guaranteed rate I/O known as  
GRIO), the scheduler is tightly coupled with the I/O subsystem. The  
qualities of the disk subsystem are well known so the scheduler can  
guarantee that a process will be scheduled such that it will receive the  
required amount of bandwidth. Since SNFS is a cross-platform file  
system that does not have hooks in the operating system scheduler, it  
cannot provide such a guarantee.  
Active vs. Passive  
4
In a passive implementation, a real-time process gates its I/O according  
to some outside metric (such as a frame rate for specific video formats).  
The file system then gates all other non-real-time I/O so they do not  
interfere.  
These differences cannot be over-stressed. It is a misconception to think  
that QOS, despite its name, guarantees a specific amount of real-time I/O  
to a process.  
QOS has been tested on Windows XP, Linux, IRIX, and Solaris. In the  
Windows world, an application gets a handle to a file to perform I/O,  
usually via the Win32 CreateFile() API. In the UNIX world, an application  
receives a file descriptor (fd) via the open(2) system call. In this document,  
“handle” is synonymous with fd.  
Supported Platforms  
4
StorNext 3.1.3 Installation Guide  
136  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Appendix D Quality of Service Guide  
Configuration  
Configuration  
The primary configuration for QOS is in the FSM configuration file. No  
client configuration is required, although there is a QOS tuning  
parameter that can be specified when the file system is mounted.  
Real-time I/O is based on well-formed I/O. This means that for the  
purposes of determining bandwidth rates, well-formed I/O is  
characterized as being a stripe width in size. This makes the best  
utilization of the disks in the stripe group and maximizes the transfer  
rate. Internally, non-real-time I/O is tracked by number of I/O  
operations per second. An I/O operation is a minimum of a file system  
block size, and a maximum of the file system block size multiplied by the  
stripe breadth  
Unit of I/O  
4
(FsBlocksize * StripeBreadth).  
FsBlockSize <= I/O <= (FsBlocksize * StripeBreadth)  
Converting MB/sec to I/O/  
sec  
Typically, it is easier to qualify an I/O subsystem in terms of MB/sec that  
can be sustained. However, internally the file system tracks everything  
on an I/O/sec basis. Note that the file system tracks only non-real-time I/  
O (that is, it gates only non-real-time I/O). An I/O is a minimum of the  
file system block size, and is typically the point at which the file system  
hands the request off to the disk driver (IoCallDriver in Windows, or a  
strategy call in UNIX).  
4
The file system counts the number of I/Os that have taken place during a  
given second. If the number exceeds that which is allotted, the request is  
pended until I/O becomes available (typically in the next second). I/O is  
honored in FIFO fashion; no priority is assigned.  
To convert between I/Os and MB/sec, SNFS uses a somewhat unique  
formula that quantifies I/O as well-formed. The rationale behind this is  
due to the way in which many video applications make real-time I/O  
requests. To optimize the disk subsystem, real-time I/Os are well-formed  
so they saturate the disks. In SNFS terminology, this would be an I/O  
that covers all of the disks in a stripe. This can be expressed as follows:  
StorNext 3.1.3 Installation Guide  
137  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Appendix D Quality of Service Guide  
Configuration  
ios_sec = mb_sec /  
(stripe_breadth * stripe_depth *fs_blocksize)  
For example, with a file system blocksize of 4k, a stripe_breadth of 384, and  
a stripe_depth of four, the equivalent number of I/Os/sec for each well-  
formed I/O would be 216 Mb/sec / (384 * 4 * 4k). This is equivalent to  
221184 k/sec / 6144k= 36 I/O/sec.  
Server Configuration  
4
All storage subsystems are different, so users must qualify the I/O  
subsystem and determine the maximum amount of I/O bandwidth  
available. SNFS relies on the correct setting in the configuration file; if the  
storage system changes (for example, because of a new disk array,) the  
user must re-qualify the I/O subsystem to determine the amount of  
bandwidth available. This amount will be specified in the FSM  
configuration file. The user can also specify the minimum amount of  
bandwidth to be provided to non-real-time applications.  
There are five keywords controlling QOS that can be specified in the  
stripe group section of the FSM configuration file. Not all keywords need  
be present. Typically, the user specifies the RTIO bandwidth in terms of  
either number of I/O operations per second (rtios) or megabytes per  
second (rtmb). Keywords are not case sensitive.  
For a minimum configuration, only the real-time limit (either rtios or rtmb)  
need be specified. All other configuration variables default to reasonable  
values.  
Table 28 QOS Configuration  
Keywords  
Name  
Description  
Default  
Rtios  
The maximum number of real-  
time I/Os allowed in a stripe  
group during any one-second  
period.  
0 (no real-time)  
Rtmb  
Maximum amount of real-time  
MB/sec allowed on the stripe  
group during any one-second  
period.  
0 (no real-time)  
StorNext 3.1.3 Installation Guide  
138  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Appendix D Quality of Service Guide  
Configuration  
Name  
Description  
Default  
RtiosReserve  
Amount of reserve in I/Os/sec  
from the maximum allowed for  
non-real-time I/Os. Must be  
greater than the equivalent to  
1MB/sec or the amount that can  
be transferred to a single stripe  
line.  
Equivalent to  
1MB/sec  
RtmbReserve  
Amount to reserve in MB/sec  
from the maximum allowed for  
non-real-time I/O.  
Must be  
greater than 1.  
1MB/sec  
RtTokenTimeout  
Time in seconds to wait for clients 2 seconds  
to respond to a token callback.  
RTIO Upper Bound  
4
The limit will be specified in terms of I/Os per second (parameter Rtios)  
or in terms of MB/sec (parameter Rtmb). Case is not sensitive. Note that  
I/Os per second are I/Os of any size to the disk subsystem. Either or both  
may be specified. If both are specified, the lower limit is used to throttle  
I/O. If neither is specified, no real-time I/O is available on the stripe  
group. These parameters are applied to a stripe group definition.  
[StripeGroup MyStripeGroup]  
Rtios 2048  
Rtmb 10  
The above example specifies that the storage system can support a  
maximum of 2048 I/Os per second at any instant, aggregate among all  
the clients, or 10 MB/sec, whichever is lower.  
Most real-time I/O requests will be a stripe line at a time to maximize  
performance. Non-real-time I/Os will be a minimum of a file system  
block size.  
StorNext 3.1.3 Installation Guide  
139  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix D Quality of Service Guide  
Configuration  
Note: It is important to realize that the rtios and rtmb settings refer to  
the total amount of sustained bandwidth available on the disk  
subsystem. Any I/O, either real-time or non-real-time, will  
ultimately be deducted from this overall limit. The  
calculations of available real-time and non-real-time are  
discussed later.  
Specifying rtmb in the FSM configuration file is only  
recommended if all I/Os are well formed (that is, a full stripe  
width). Otherwise, the conversion between MB/sec and I/Os/  
sec using the well-formed I/O calculation could lead to  
unexpected results.  
Reserve  
4
To prevent deadlock, the QOS implementation never allows zero I/O/  
sec for non-real-time I/O. Otherwise, a system could block with many  
critical file system resources held waiting for I/O to become available.  
This is especially true via flush-on-close I/O via the buffer cache. It  
becomes extremely difficult to diagnose system hangs because no I/O is  
available. For this reason, QOS always reserves some amount of I/O for  
non-real-time I/O.  
The minimum amount of non-real-time I/O reserved for non-real-time  
applications is one MB/sec. This can be changed via the stripe group  
section parameters (again, case is not sensitive). If both are specified, the  
lower of the two amounts is chosen. This amount is shared by all non-  
real-time applications on each client.  
[StripeGroup MyStripeGroup]  
RtiosReserve 256  
RtmbReserve 2  
StorNext 3.1.3 Installation Guide  
140  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix D Quality of Service Guide  
Configuration  
Token Timeouts  
4
The RtTokenTimeout parameter controls the amount of time the FSM waits  
for clients to respond to callbacks. In most normal SANs, the default two-  
second setting is sufficient. This value may need to be changed for a SAN  
that has a mixture of client machine types (Linux, NT, IRIX, etc.) that all  
have different TCP/IP characteristics. Also, large numbers of clients  
(greater than 32) may also require increasing the parameter.  
For example, if the FSM should ever fail, the clients will attempt to  
reconnect. When the FSM comes back online, the amount of time the  
clients take to re-establish their TCP/IP connection to the FSM can differ  
wildly. To avoid unnecessary timeouts, the RtTokenTimeout parameter can  
be increased, meaning the FSM waits longer for callback responses.  
If a client times out on a token retraction, the original requestor receives  
an error from the FSM that includes the IP address of the offending client.  
This error is logged to syslog, and alternatively to the desktop on  
Windows clients. This can help in diagnosing reconnect failures, and in  
determining if the token time value should be increased.  
Client Configuration  
4
When a client obtains a non-real-time I/O token from the FSM, the token  
allows the client a specific amount of non-real-time I/O. If the client is  
inactive for a period of time, the token is relinquished and the non-real-  
time I/O released back to the FSM for distribution to other clients. The  
timeout period is controlled by the nrtiotokenhold mount option on UNIX  
platforms, and the QOS Token Hold Time parameter in the mount options  
tab of the SNFS control panel on Windows platforms. The default is sixty  
(60) seconds.  
This means that after sixty seconds without non-real-time I/O on a stripe  
group, the non-real-time token for that stripe group is released. The  
parameter should be specified in five (5) second increments. If it is not, it  
will be silently rounded up to the next five-second boundary. If the  
syslog level is set to debug, the file system dumps out its mount  
parameters so the value can be seen.  
StorNext 3.1.3 Installation Guide  
141  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Appendix D Quality of Service Guide  
Real-time I/O  
Real-time I/O  
A process requests real-time (ungated) I/O by using the SNFS External  
API SetRtio call (F_SETRIO ioctl). A library function is included in the  
External API sample source code that provides all the required cross-  
platform handling.  
As an example, assume that a video playback application requires a  
constant rate of 186 MB/sec to correctly display images without dropping  
any frames. The application gates itself; that is, it requests I/O at a rate to  
satisfy the requirements of correctly displaying an image. QOS provides a  
mechanism so other I/O requests do not perturb the real-time display.  
In the following example, assume the I/O subsystem has been qualified  
at 216 MB/sec. The file system block size is 4k. The disk subsystem is  
actually a large RAID array that internally maps many drives to a single  
LUN. There are four LUNs in the stripe group; each LUN is optimized for  
a 1.5 MB transfer. This corresponds to the following in the fsm  
configuration file:  
[StripeGroup MyStripeGroup]  
StripeBreadth 384  
Node CvfsDisk0 0  
Node CvfsDisk1 1  
Node CvfsDisk2 2  
Node CvfsDisk3 3  
Rtmb 216  
Also, assume there is only one stripe group for user data in the file  
system. As recommended by Quantum, there may be other stripe groups  
for metadata and journal that are not shown.  
StorNext 3.1.3 Installation Guide  
142  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Appendix D Quality of Service Guide  
Real-time I/O  
Initially, all stripe groups in the file system are in non-real-time mode.  
Clients make their requests directly to the I/O subsystem without any  
gating. In our example, the process requires 186 MB/sec and the system  
designers know there will never be a need to support more than one  
stream at 186 MB/sec.  
SetRtio  
4
The SetRtio request has a number of flags and parameters to control its  
operation. These are all documented in the external_api.pdf file that  
describes the external API in detail. For this example, set the handle for  
the indicated stripe group using the RT_SET parameter.  
In most cases, system designers ensure that the amount of rtio is not  
oversubscribed. This means that processes will not ask for more rtio than  
is specified in the configuration file. However, it is possible to request  
more rtio than is configured. The API uses the RT_MUST flag to indicate  
that the call must succeed with the specified amount. If the flag is clear,  
the call allocates as much as it can. In both cases, the amount allocated is  
returned to the caller.  
Oversubscription  
4
4
The SetRtio call accepts two different types of handles. The first is a  
handle to the root directory. In this mode the stripe group is put into real-  
time mode, but no specific file handle is tagged as being ungated. Real-  
time I/O continues on the stripe group until it is explicitly cleared with a  
SetRtio call on the root directory that specifies the RT_CLEAR flag; the file  
system is unmounted; or the system is rebooted. It is up to the application  
to make a subsequent call to EnableRtio (F_ENABLERTIO) on a specific  
handle.  
Handles  
If the handle in the SetRtio call refers to a regular file, it is the equivalent  
of a SetRtio call on the root directory followed by an EnableRtio call. The  
file handle will be ungated until it is closed, cleared (RT_CLEAR in a  
SetRtio call), or disabled (DisableRtio). When the handle is closed, the  
amount of real-time I/O is released back to the system. This causes the  
FSM to readjust the amount of bandwidth available to all clients by  
issuing a series of callbacks.  
The client automatically issues a call to the FSM with the RT_CLEAR flag  
specifying the amount of real-time I/O set on the file. If multiple handles  
are open on the file—each with a different amount of real-time I/O—only  
the last file close triggers the releasing action; all aggregate rtio are  
released.  
StorNext 3.1.3 Installation Guide  
143  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Appendix D Quality of Service Guide  
Real-time I/O  
This automatic clearing of real-time I/O is carried out in the context of  
the process that is closing the file. If the FSM cannot be reached for some  
reason, the request is enqueued on a daemon and the process closing the  
file is allowed to continue. In the background, the daemon attempts to  
inform the FSM that the real-time I/O has been released.  
Different processes can share the same file in real-time and non-real-time  
mode. This is because the level of gating is at the handle level, not the file  
level. This allows a real-time process to perform ingest of material (video  
data) at the same time as non-real-time processes are performing other  
operations on the file.  
Figure 59 Sharing Access to  
Files  
In Figure 59, Process A has ungated access to file foo. Processes B and C  
also are accessing file foo, but the client gates their I/O accesses. If  
multiple handles are open to the same file and all are in real-time mode,  
only the last close of the handle releases the real-time I/O back to the  
system. This is because on most platforms the file system is informed  
only on the last close of a file.  
It is also possible to denote using the RT_NOGATE flag that a handle  
should not be gated without specifying any amount of real-time I/O. This  
is useful for infrequently accessed files (such as index files) that should  
not be counted against the non-real-time I/O. System designers typically  
allow for some amount of overage in their I/O subsystem to account for  
non-gated files.  
Ungated files  
4
StorNext 3.1.3 Installation Guide  
144  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Appendix D Quality of Service Guide  
Callbacks  
Calculating Available  
RTIO  
When the FSM receives a request for rtio, it takes the amount reserved  
into consideration. The reserve amount functions as a soft limit beyond  
which the FSM will not traipse. The calculation for rtio is as follows:  
4
avail_rtio = rtio_limit - rtio_current  
avail_rtio -= rtio_reserve  
All internal calculations are done in terms of I/O/sec.  
Callbacks  
The cornerstones of the communications between the FSM and the client  
are callbacks and tokens. A callback is an unsolicited message from the  
FSM to the client requesting that the client adjust its real-time I/O  
parameters. The callback contains a token that specifies the amount of  
non-real-time I/O available on a stripe group.  
Initially, all stripe groups in a file system are in non-real-time (ungated)  
mode. When the FSM receives the initial request for real-time I/O, it first  
issues callbacks to all clients informing them that the stripe group is now  
in real-time mode. The token accompanying the message specifies no I/O  
is available for non-real-time I/O. Clients must now obtain a non-real-  
time token before they can do any non-real-time I/O.  
After sending out all callbacks, the FSM sets a timer based on the  
RtTokenTimeout value, which by default is set to five seconds. If all clients  
respond to the callbacks within the timeout value the rtio request  
succeeds, and a response is set to the requesting client.  
StorNext 3.1.3 Installation Guide  
145  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Appendix D Quality of Service Guide  
Callbacks  
Figure 60 Callback Flow for  
Initial RTIO Request  
In the above diagram, a process on client A requests some amount of  
RTIO in Step 1. Since this is the first request, the FSM issues callbacks to all  
connected clients (Steps 2-5) informing them that the stripe group is now  
in real-time mode. The clients respond to the FSM in Steps 6-9. After all  
the clients have responded, the FSM responds to the original requesting  
client in Step 10.  
If the timer expires and one or more clients have not responded, the FSM  
must retract the callbacks. It issues a response to the requesting client  
with the IP number of the first client that did not respond to the callback.  
This allows the requesting client to log the error with the IP number so  
system administrators have a chance of diagnosing the failure. It then  
sends out callbacks to all the clients to which it first sent the callbacks,  
retracting them to the original state. In our example, it would set the  
stripe group back to non-real-time mode.  
After sending out the callbacks, the FSM waits for a response using the  
RtTokenTimeout value as before. If a client again does not respond within  
the timeout value, the callbacks are retracted and sent out again. This  
repeats until all clients respond. During this time of token retractions,  
real-time requests cannot be honored and will only be enqueued.  
StorNext 3.1.3 Installation Guide  
146  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Appendix D Quality of Service Guide  
Callbacks  
The FSM must handle a case where a client does not respond to a callback  
within the specified timeout period (RtTokenTimeout). If a client does not  
respond to a callback, the FSM must assume the worst: that it is a rogue  
that could wreak havoc on real-time I/O. It must retract the tokens it just  
issued and return to the previous state.  
Callback Failures  
4
As mentioned earlier, the original requestor will receive an error  
(EREMOTE) and the IP address of the first client that did not respond to  
the callback. The FSM enters the token retraction state, and will not honor  
any real-time or token requests until it has received positive  
acknowledgement from all clients to which it originally sent the  
callbacks.  
Figure 61 Callback Retraction  
Example  
In Figure 61, Client A requests some amount of rtio as in Figure 60.  
However, assume that Client C did not respond to the initial callback in  
time (step 7). The FSM will return a failure to Client A for the initial rtio  
request, then send out callbacks to all clients indicating the stripe group is  
no longer real-time (steps 11-14). In the example, Client C responds to the  
second callback, so the FSM will not send out any more callbacks. The  
stripe group is back in non-real-time mode.  
Note that this can have interesting repercussions with file systems that  
are soft mounted by default (such as Windows). When the caller times  
out because other clients are not responding and then gives up and  
returns an error to the application, if at some point the FSM is able to  
process the rtio request it may result in the stripe group being put into  
StorNext 3.1.3 Installation Guide  
147  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Appendix D Quality of Service Guide  
Callbacks  
real-time mode after the original caller has received an error code. Both  
the FSM and clients log their actions extensively to syslog, so if this  
situation arises it can be detected.  
In Figure 61, if the stripe group were already in real-time mode the FSM  
would only send out callbacks to those clients that already have tokens.  
Once all clients responded to the token callbacks, the stripe group would  
be back in its original state.  
A token grants a client some amount of non-real-time I/O for a stripe  
group. Tokens are encapsulated in callback messages from the FSM.  
Initially, no tokens are required to perform I/O. Once a stripe group is  
put into real-time mode, the FSM sends callbacks to all clients informing  
them that they will need a token to perform any non-real-time I/O. The  
first I/O after receiving the callback will then request a non-real-time I/O  
token from the FSM.  
Tokens  
4
The FSM calculates the amount of non-real-time bandwidth using the  
following formula:  
avail_nrtio = rtio_limit - rtio_current;  
avail_nrtio /= current_num_nonrtio_clients + 1  
In the above calculation, the amount of existing real-time I/O (rtio_current)  
has already been adjusted with the reserve parameter. As each client  
requests a non-real-time I/O token, the number of clients increases  
(current_num_nonrtio_clients in the above formula) and the amount of  
available non-real-time I/O decreases.  
Each time there is a change in the amount of non-real-time I/O available,  
the FSM sends callbacks to the clients with tokens. It is important to note  
that unlike the initial set of callbacks where the FSM sent callbacks to all  
connected clients, it is now only necessary to send callbacks to those  
clients that have an existing token.  
Once a client has a token, it can perform as much I/O per second as is  
allowed by that token. It does not need to contact the FSM on every I/O  
request. The FSM will inform the client whenever the token changes  
value.  
StorNext 3.1.3 Installation Guide  
148  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Appendix D Quality of Service Guide  
Callbacks  
Figure 62 Non-Real-time  
Token Adjustments  
In Figure 62, assume the stripe group is already in real-time mode as a  
result of an rtio request from client A. Clients B and D are doing non-real-  
time I/O to the stripe group and have a token that specifies the amount of  
non-real-time I/O available. Client C then requests a non-real-time I/O  
token in Step 1. The FSM calls back to Clients B and D and specifies the  
new token amount in Steps 2-3. The clients respond in Steps 4-5,  
acknowledging the new token amount. The FSM then responds to Client  
C with the new token in Step 6.  
There are two major failures that affect QOS: FSM crashes and client  
crashes. These can also be loss of communication (network outages). For  
client and server failures, the system attempts to readjust itself to the pre-  
failure state without any manual intervention.  
Failure Semantics  
4
StorNext 3.1.3 Installation Guide  
149  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Appendix D Quality of Service Guide  
Callbacks  
If the FSM crashes or is stopped, there is no immediate affect on real-time  
(ungated) I/O. As long as the I/O does not need to contact the FSM for  
some reason (attribute update, extent request, etc.), the I/O will continue.  
From the standpoint of QOS, the FSM being unavailable has no affect.  
FSM Failures  
4
Non-real-time I/O will be pended until the FSM is re-connected. The  
rationale for this is that since the stripe group is in real-time mode, there  
is no way to know if the parameters have changed while the FSM is  
disconnected. The conservative design approach was taken to hold off all  
non-real-time I/O until the FSM is reconnected.  
Once the client reconnects to the FSM, the client must re-request any real-  
time I/O it had previously requested. The FSM does not keep track of  
QOS parameters across crashes; that is, the information is not logged and  
is not persistent. Therefore, it is up to the clients to inform the FSM of the  
amount of required rtio and to put the FSM back into the same state as it  
was before the failure.  
In most cases, this results in the amount of real-time and non-real-time I/  
O being exactly the same as it was before the crash. The only time this  
would be different is if the stripe group is oversubscribed. In this case,  
since more rtio had been requested than was actually available, and the  
FSM had adjusted the request amounts, it is not deterministically possible  
to re-create the picture exactly as it was before. Therefore, if a  
deterministic picture is required across reboots, it is advisable to not over-  
subscribe the amount of real-time I/O.  
The process of each client re-requesting rtio is exactly the same as it was  
initially; once each client has reestablished its rtio parameters, the non-  
real-time I/O is allowed to proceed to request a non-real-time token. It  
may take several seconds for the SAN to settle back to its previous state.  
It may be necessary to adjust the RtTokenTimeout parameter on the FSM to  
account for clients that are slow in reconnecting to the FSM.  
When a client disconnects either abruptly (via a crash or a network  
partition,) or in a controlled manner (via an unmount), the FSM releases  
the client's resources back to the SAN. If the client had real-time I/O on  
the stripe group, that amount of real-time I/O is released back to the  
system. This causes a series of callbacks to the clients (all clients if the  
stripe group is transitioning from real-time to non-real-time,) informing  
them of the new amount of non-real-time I/O available.  
Client Failures  
4
If the client had a non-real-time I/O token, the token is released and the  
amount of non-real-time I/O available is recalculated. Callbacks are sent  
StorNext 3.1.3 Installation Guide  
150  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Appendix D Quality of Service Guide  
Monitoring  
to all clients that have tokens informing them of the new amount of non-  
real-time I/O available.  
While it is not a failure case, the handling of a client token release is  
exactly the same as in the case where the client disconnected. All clients  
retain non-real-time tokens for a fixed amount of time. The default is 60  
seconds. This can be controlled via the nrtiotokentimeout mount option.  
After the specified period of inactivity (i.e., no non-real-time I/O on the  
stripe group), the client will release the token back to the FSM. The FSM  
will re-calculate the amount of non-real-time bandwidth available, and  
send out callbacks to other clients.  
Client Token Releases 4  
Therefore, if a situation exists where a periodic I/O operation occurs  
every 70 seconds, it would be beneficial to set the nrtiotokentime mount  
option to something greater than or equal to 70 seconds to cut down on  
system and SAN overhead.  
Monitoring  
The current real-time statistics are available via the cvadmin utility. The  
show long command has been enhanced to provide information as to the  
current limit, the minimum amount reserved for non-real-time I/O, the  
number of active clients, the amount currently committed, and the  
amount a non-real-time application could hope to get when requesting  
I/O.  
Whenever the stripe group status changes (such as from non-real-time to  
real-time mode), an event is logged to syslog (system event log on  
Windows platforms).  
On the NT platform, real-time performance is also available via the  
perfmon utility. There are counters for both the client (SNFS Client) and  
FSM (SNFS File System Server [FSS]). In the client, a number of rtio_xxx  
counters are available to track the number of real-time I/Os/sec, number  
of non-real-time I/O requests, non-real-time I/O starvation, and other  
counters. A full explanation of each counter is provided with the perfmon  
utility by clicking Explain. In the FSM, information about the number of  
outstanding non-real-time clients, available rtio, and other QOS  
information is available.  
StorNext 3.1.3 Installation Guide  
151  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Appendix D Quality of Service Guide  
Sharing Disk Resources  
Performance counters are not enabled by default in the client. To enable  
them, you must execute cvdb -P ; this toggles the state of collection. To  
turn off the perfmon counters, do another cvdb -P. To re-enable, again do  
cvdb -P, and so on. To clear all client counters to zero, disable, then re-  
enable the counters with cvdb -P.  
Sharing Disk Resources  
As a final example, consider the case of a full-featured disk subsystem  
(Redundant Array of Very Expensive Disks, or RAVED) using a very  
high speed interconnect. Many clients can share these disk arrays, but it is  
sometimes desirable to limit a client's access to the array. QOS provides a  
mechanism for political bandwidth management so that no one client can  
consume all the bandwidth of the channel interconnects.  
In such a scenario, the stripe group would always be in real-time mode.  
Each client would have a token specifying the number of I/Os/sec  
permissible. In the current version of QOS, it is unfortunately not possible  
to assign different non-real-time limits to different clients.  
The foundation of such an approach is a simple program that puts the  
stripe group into real-time mode as soon as the FSM is up and servicing  
requests. An example of such a program is included in the source code for  
the External API.  
Once the stripe group is in real-time mode, the bandwidth as specified in  
the FSM configuration file is shared by all clients. In cases such as this, the  
real-time limit (rtios or rtmb) is calculated to be the total bandwidth  
desired to each client times the number of possible clients.  
As each client attempted to access the disk subsystem, it would obtain a  
token. The FSM would send out callbacks adjusting down the amount of  
bandwidth available. No one client would be allowed to exceed the  
threshold specified in the non-real-time token. This assures fairness  
among all the clients.  
StorNext 3.1.3 Installation Guide  
152  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 

Radica Games Nail Gun 75031 User Guide
RCA Flat Panel Television RCR160TKLM1 User Guide
RCA MP3 Player M63 User Guide
Remington Hair Dryer D 3510is User Guide
Renesas Computer Hardware M38C29T 64LCA User Guide
Ricoh Digital Camera L753 2911 User Guide
Samsung Car Video System GH15ES User Guide
Samsung Flat Panel Television UN85HU8550 User Guide
Schumacher Battery Charger MSC 2405 User Guide
Sears Rowing Machine 35 1215B User Guide