Quantum STORNEXT 3.5.2.1 User Manual

6-00360-21
StorNext® 3.5.2.1
StorNext
Installation Guide Installation Guide Installation GuideInstallation Guide
Document Title, 6-00360-21 Rev A, June 2010, Product of USA.
Quantum Corporation provides this publication “as is” without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability or fitness for a particular purpose. Quantum Corporation may revise this publication from time to time without notice.
COPYRIGHT STATEMENT
© 2010 Quantum Corporation. All rights reserved.
Your right to copy this manual is limited by copyright law. Making copies or adaptations without prior written authorization of Quantum Corporation is prohibited by law and constitutes a punishable violation of the law.
TRADEMARK STATEMENT
Quantum, the Quantum logo, DLT, DLTtape, the DLTtape logo, Scalar, and StorNext are registered trademarks of Quantum Corporation, registered in the U.S. and other countries.
Backup. Recovery. Archive. It’s What We Do., the DLT logo, DLTSage, DXi, DXi-Series, Dynamic Powerdown, FastSense, FlexLink, GoVault, MediaShield, Optyon, Pocket-sized. Well-armored, SDLT, SiteCare, SmartVerify, StorageCare, Super DLTtape, SuperLoader, and Vision are trademarks of Quantum.
LTO and Ultrium are trademarks of HP, IBM, and Quantum in the U.S. and other countries. All other trademarks are the property of their respective companies.
Specifications are subject to change without notice.

Contents

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Notational Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
Contacting Quantum. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Chapter 1 Installing StorNext File System and Storage Manager 1
Storage Manager System Requirements . . . . . . . . . . . . . . . . . . . . . . . . 2
Getting Ready to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Pre-Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
StorNext Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 2 Installing StorNext File System 17
File System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Getting Ready to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Installing StorNext File System on Linux or Unix . . . . . . . . . . . . . . . . . 22
StorNext 3.5.2.1 Installation Guide i
Contents
Installing StorNext File System on Windows . . . . . . . . . . . . . . . . . . . . 26
Chapter 3 Installing the StorNext Client 37
Client System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Client Installation Changes From Previous Releases . . . . . . . . . . . . . . . 41
Downloading the StorNext Client Software. . . . . . . . . . . . . . . . . . . . . 42
Installing the StorNext Client on Linux or Unix . . . . . . . . . . . . . . . . . . 45
Installing the StorNext Client on Windows . . . . . . . . . . . . . . . . . . . . . 52
Chapter 4 Configuring StorNext 61
StorNext GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Configuration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Configuring a Distributed LAN Client Server . . . . . . . . . . . . . . . . . . . . 68
Windows Configuration Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Installing Promise RAID Controller Software . . . . . . . . . . . . . . . . . . . 110
Appendix A Uninstalling StorNext 113
Uninstalling StorNext on Unix and Linux . . . . . . . . . . . . . . . . . . . . . . 113
Uninstalling StorNext on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Appendix B StorNext Administration Tasks 117
Sharing a Library Between Applications . . . . . . . . . . . . . . . . . . . . . . 117
Manually Modifying Storage Manager Configuration . . . . . . . . . . . . 119
Connecting to a StorNext Network Using Xsan 1.4.2 . . . . . . . . . . . . 120
Connecting to a StorNext Network Using Xsan 2 . . . . . . . . . . . . . . . 123
Viewing a Fibre Channel Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
StorNext Log Rolling Administration . . . . . . . . . . . . . . . . . . . . . . . . . 127
Avoiding Poor System Performance. . . . . . . . . . . . . . . . . . . . . . . . . . 128
Contents
Appendix C StorNext Files 131
The example.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Cluster-Wide Central Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Commonly Used SNFS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Appendix D Quality of Service Guide 145
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Real-time I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Non-Realtime I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Callbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Sharing Disk Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
StorNext 3.5.2.1 Installation Guide iii
Contents

Figures

Figure 1 Pre-Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Figure 2 StorNext Installation Script . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 3 Configuration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 4 SNFS Installation Script. . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 5 Configuration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 6 StorNext Installation Window: Remove StorNext . . . . . . . 28
Figure 7 StorNext Installation Window: Install StorNext. . . . . . . . . 29
Figure 8 SNFS Setup: Welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 9 SNFS Setup: End-User License Agreement . . . . . . . . . . . . 30
Figure 10 SNFS Setup: Customer Information . . . . . . . . . . . . . . . . . 30
Figure 11 SNFS Setup: Choose Setup Type . . . . . . . . . . . . . . . . . . . . 31
Figure 12 SNFS Setup: Ready to Install . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 13 SNFS Setup: Finish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 14 StorNext Installation Window: Configure StorNext. . . . . . 33
Figure 15 StorNext Configuration Window . . . . . . . . . . . . . . . . . . . 34
Figure 16 Import/Export Client Configuration Window . . . . . . . . . . 35
Figure 17 Select Platform Window . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 18 Download Client Software Window . . . . . . . . . . . . . . . . . 44
StorNext 3.5.2.1 Installation Guide v
Figures
Figure 19 StorNext Installation Window: Remove StorNext . . . . . . . 53
Figure 20 StorNext Installation Window: Install StorNext. . . . . . . . . 55
Figure 21 SNFS Setup: Welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 22 SNFS Setup: End-User License Agreement . . . . . . . . . . . . 56
Figure 23 SNFS Setup: Customer Information . . . . . . . . . . . . . . . . . 56
Figure 24 SNFS Setup: Choose Setup Type . . . . . . . . . . . . . . . . . . . . 57
Figure 25 SNFS Setup: Ready to Install . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 26 SNFS Setup: Finish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 27 StorNext Installation Window: Configure StorNext. . . . . . 59
Figure 28 StorNext Configuration Window . . . . . . . . . . . . . . . . . . . 59
Figure 29 Import/Export Client Configuration Window . . . . . . . . . . 60
Figure 30 StorNext Home Page: File System and Storage Manager . 63
Figure 31 StorNext Home Page: File System Only . . . . . . . . . . . . . . . 63
Figure 32 StorNext Configuration Wizard: Storage Manager . . . . . . 64
Figure 33 StorNext Configuration Wizard: File System Only . . . . . . . 65
Figure 34 sndpscfg Configuration Utility . . . . . . . . . . . . . . . . . . . . . 71
Figure 35 Client Configuration: Mount Point . . . . . . . . . . . . . . . . . . 75
Figure 36 Client Configuration: Distributed LAN . . . . . . . . . . . . . . . 77
Figure 37 Client Configuration: Advanced Mount Options. . . . . . . . 79
Figure 38 Client Configuration: Advanced Cache Options . . . . . . . . 83
Figure 39 Disk Device Labeler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Figure 40 Disk Labeler Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Figure 41 Simple File System Configuration . . . . . . . . . . . . . . . . . . . 90
Figure 42 File System Startup List. . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 43 Server Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Figure 44 Server Administration: File System Properties. . . . . . . . . . 96
Figure 45 Server Administration: Stripe Group Properties . . . . . . . . 98
Figure 46 Server Administration: Quota Properties. . . . . . . . . . . . . . 99
Figure 47 Configuration Administrator. . . . . . . . . . . . . . . . . . . . . . 101
Figures
Figure 48 Server Configuration: Global Settings. . . . . . . . . . . . . . . 102
Figure 49 Server Configuration: Disk Types . . . . . . . . . . . . . . . . . . 105
Figure 50 Server Configuration: Enter New Disk Type. . . . . . . . . . . 106
Figure 51 Server Configuration: Disk Definitions . . . . . . . . . . . . . . 107
Figure 52 Server Configuration: Stripe Groups . . . . . . . . . . . . . . . . 108
Figure 53 Windows Boot Manager Screen 1. . . . . . . . . . . . . . . . . . 111
Figure 54 Windows Boot Manager Screen 2. . . . . . . . . . . . . . . . . . 111
Figure 55 Advanced Boot Options Screen . . . . . . . . . . . . . . . . . . . 112
Figure 56 StorNext Remove Main Menu . . . . . . . . . . . . . . . . . . . . . 114
Figure 57 Sharing Access to Files . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 58 Callback Flow for Initial RTIO Request. . . . . . . . . . . . . . . 158
Figure 59 Callback Retraction Example. . . . . . . . . . . . . . . . . . . . . . 159
Figure 60 Non-Real-time Token Adjustments . . . . . . . . . . . . . . . . . 161
StorNext 3.5.2.1 Installation Guide vii
Figures

Ta b l e s

Table 1 Storage Manager Supported Platforms . . . . . . . . . . . . . . . 2
Table 2 Storage Manager Hardware Requirements . . . . . . . . . . . . . 3
Table 3 Required Disk LUN Labels . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Table 4 StorNext Support Directories . . . . . . . . . . . . . . . . . . . . . . . 8
Table 5 Pre-Installation Script Recommendation Types . . . . . . . . . 11
Table 6 StorNext Installation Main Menu Options. . . . . . . . . . . . . 13
Table 7 File System Supported Platforms . . . . . . . . . . . . . . . . . . . 18
Table 8 File System Hardware Requirements. . . . . . . . . . . . . . . . . 19
Table 9 Required Disk LUN Labels . . . . . . . . . . . . . . . . . . . . . . . . . 21
Table 10 SNFS Installation Main Menu Options . . . . . . . . . . . . . . . 24
Table 11 StorNext Client Supported Platforms. . . . . . . . . . . . . . . . 38
Table 12 Default Memory Consumed by cachebufsize . . . . . . . . . . 40
Table 13 Distributed LAN Server Parameters . . . . . . . . . . . . . . . . . . 71
Table 14 Distributed LAN Client and Server Commands . . . . . . . . . 73
Table 15 Client Configuration: Mount Point . . . . . . . . . . . . . . . . . . 76
Table 16 Client Configuration: Distributed LAN . . . . . . . . . . . . . . . 77
Table 17 Client Configuration: Advanced Mount Options. . . . . . . . 80
Table 18 Client Configuration: Advanced Cache Options . . . . . . . . 84
StorNext 3.5.2.1 Installation Guide ix
Tables
Table 19 Disk Labeler Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Table 20 Simple File System Configuration . . . . . . . . . . . . . . . . . . . 90
Table 21 File System Startup List. . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Table 22 Server Administration: File System Properties. . . . . . . . . . 96
Table 23 Server Administration: Stripe Group Properties . . . . . . . . 98
Table 24 Server Administration: Quota Properties. . . . . . . . . . . . . 100
Table 25 Server Configuration: Global Settings. . . . . . . . . . . . . . . 103
Table 26 Server Configuration: Enter New Disk Type. . . . . . . . . . . 106
Table 27 Server Configuration: Disk Definitions . . . . . . . . . . . . . . 107
Table 28 Server Configuration: Stripe Groups . . . . . . . . . . . . . . . . 108
Table 29 QOS Configuration Keywords . . . . . . . . . . . . . . . . . . . . . 149

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.

Audience

This document is intended for service professionals and system administrators who install StorNext software. The installer should have
StorNext 3.5.2.1 Installation Guide xi
Preface Purpose

Purpose

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.
This document provides information about installing and configuring StorNext. The following topics are covered:
• System requirements
• Pre-installation tasks
• Installation
• Configuration
• Uninstalling StorNext

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).
Preface

Notational Conventions

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.
Appendix B, StorNext Administration Tasksdescribes how to perform file system tasks that do not apply to a typical StorNext setup.
Appendix C, StorNext Filesdescribes the files used and modified to configure a file system.
Appendix D, Quality of Service Guidedescribes how to configure and use the StorNext File System (SNFS) Quality of Service (QOS) feature.
Notational Conventions
This manual uses the following conventions:
Convention Example
User input is shown in Arial regular font.
User input variables are enclosed in angle brackets and are shown in Arial italic font.
For UNIX and Linux commands, the command prompt is implied.
File and directory names, menu commands, button names, and window names are shown in Arial bold font.
StorNext 3.5.2.1 Installation Guide xiii
./install.stornext
mkdir -p
./install.stornext
is the same as
# ./install.stornext
/stornext/snfs1
<mount point>
Preface Related Documents
Convention Example
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
Caution: Cautions indicate potential hazards to equipment and are
WARNING: Warnings indicate potential hazards to personal safety

Related Documents

Admin > Download Client Software
topic.
included to prevent damage to equipment.
and are included to prevent injury.
Documents related to StorNext are shown below:

Quantum StorNext Documentation

Document No. Document Title Document Description
6-01658-12 StorNext User’s
Guide
6-01376-16 StorNext File System
Tuning Guide
Provides in-depth information about using StorNext to create and manage StorNext File Systems.
Provides information for maximizing file system performance.

Contacting Quantum

Document No. Document Title Document Description
Preface
6-01620-15 StorNext Upgrade
6-01688-12 StorNext CLI
6-00431-30 StorNext 3.5.2.1
Contacting Quantum
More information about StorNext is available on the Service and Support website at 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.
Provides procedures for
Guide
Reference Guide
Release Notes
www.quantum.com/support. The Service and
upgrading from earlier versions of StorNext.
Provides procedures for performing common tasks using the command line interface.
Includes the latest product information, fixes, and issues.
For further assistance, or if training is desired, contact Quantum:
Quantum Technical Assistance Center in the USA:
For additional contact information:
To open a Service Request:
For the most updated information on Quantum Global Services, please visit:
www.quantum.com/support
StorNext 3.5.2.1 Installation Guide xv
+1 800-284-5101
www.quantum.com/support
www.quantum.com/osr
Preface Contacting Quantum
Chapter 1
Installing 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
• Make sure all storage devices are correctly configured and are visible to the MDC (see
Storage Manager System Requirements).
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 on page 11).
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.5.2.1 Installation Guide 1
StorNext Installation Script
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

Table 1 Storage Manager Supported Platforms
The operating systems, kernel versions, and hardware platforms supported by StorNext SNFS and SNSM are presented in sure the MDC uses a supported operating system and platform, and if necessary update to a supported kernel version before installing StorNext.
Operating System Kernel Platform
Red Hat® Enterprise
®
Linux
4
Red Hat Enterprise Linux 5
SUSETM Linux Enterprise Server 10
Sun SolarisTM 10
2.6.9-89 EL (Update 8) x86 64-bit
2.6.18-53.EL (Update 1)
2.6.18-92.EL (Update 2)
2.6.18-128.EL (Update 3)
2.6.18-164.EL (Update 4)
2.6.16-46-0.12 (SP1)
2.6.16-60-0.27 (SP2)
2.6.16.60-0.54.5 (SP3)
Generic 120011-14 Sparc 64-bit
Ta bl e 1. Make
x86 64-bit
x86 64-bit

Hardware Requirements

The minimum amount of RAM and available hard disk space required to run StorNext SNFS and SNSM are presented in 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.
If necessary, upgrade the RAM and local disk storage in the MDC to meet the minimum requirements before installing StorNext.
Ta bl e 2. Because support
Chapter 1: Installing StorNext File System and Storage Manager
Storage Manager System Requirements
Note: The RAM requirements in Ta bl e 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 • For application binaries, log files,
5–8** 4 GB
and documentation: up to 30GB (depending on system activity)
• 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. †For non-managed file systems, the requirement is 1GB per million files
stored.
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
Ta bl e 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.
• 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.5.2.1 Installation Guide 3
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 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.

LAN Requirements The following LAN requirements must be met before installing StorNext

on the MDC:
• 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. Alternatively, telnet or ssh between machines to verify
connectivity.
• 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 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
than 1 TB).
• (Linux only) Install the kernel source code (see Installing the Linux
Kernel Source Code on page 7).
Chapter 1: Installing StorNext File System and Storage Manager
Getting Ready to Install
Planning for LUNs Larger

Configuring Storage Devices

Planning for LUNs Larger than 1 TB

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.)
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
Guide
.)
Caution: StorNext does not support the connection of multiple
devices through fibre channel hubs. Multiple devices must be connected using fibre channel switches.
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
StorNext User’s
StorNext 3.5.2.1 Installation Guide 5
Chapter 1: Installing StorNext File System and Storage Manager Getting Ready to Install
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
Ta bl e 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
Ta bl e 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
Windows
a
Linux 2.6
Label for LUNs < 1 TB
Label for LUNs 1–2 TB
Label for LUNs > 2 TB
VTOC, EFI VTOC, EFI EFI, sVTOC
VTOC, EFI VTOC, EFI EFI, sVTOC
Kernel
Linux 2.4
VTOC, EFI VTOC, EFI Not supported
Kernel
Solaris 9
Solaris 10
d
HP-UX
IBM AIX
e
b
c
VTOC, EFI EFI Not supported
VTOC, EFI EFI EFI
VTOC, EFI VTOC, EFI EFI, sVTOC
VTOC, EFI VTOC, EFI EFI, sVTOC
SGI IRIX VTOC VTOC Not supported
Apple Xsan 1.3
VTOC, EFI VTOC, EFI EFI, sVTOC (MacOS X 10.4 Tiger)
Apple Xsan 1.3
VTOC, EFI VTOC, EFI EFI, sVTOC (MacOS X 10.3
Panther)
d
Apple Xsan
d
1.2
VTOC VTOC sVTOC
Chapter 1: Installing StorNext File System and Storage Manager
Getting Ready to Install

Installing the Linux Kernel Source Code

Operating System
a. For Windows XP 32-bit systems only, support for LUNs larger than 2 TB is
limited to the first 2 TB. All other supported Windows platforms
(including Windows XP 64-bit) support LUNs greater 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 the first 2 TB of LUNs larger than 2 TB. e. Supports only LUNs of 2.2 TB or less.
Label for LUNs < 1 TB
Label for LUNs 1–2 TB
Label for LUNs > 2 TB
Note: For best results, Quantum recommends using persistent
binding for disk LUNs. For more information, contact the vendor of your HBA (host bus adapter).
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).
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.)
StorNext 3.5.2.1 Installation Guide 7
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 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
The StorNext support directories are described in Ta bl e 4.
Backup directory, which is stored on the managed file system.
snPreInstall, you are prompted
Table 4 StorNext Support Directories
Support Directory Description
Database /adic/database
Journal /adic/database_jnl
Mapping /adic/mapping_dir
Metadata /adic/database_meta
Backup /backup
Records information about where and how data files are stored.
Records changes made to the database.
Contains index information that enables quick searches on the file system.
Stores metadata dumps (backups of file metadata).
Contains configuration files and support data required for disaster recovery.

Before You Begin Before running the pre-installation script, be prepared to answer the

following questions:
• Is this an upgrade installation?
• What local file systems can be used to store support information?
• Which version of StorNext will be installed?
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.

Running snPreInstall To run the pre-installation script, use the StorNext installation CD.

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 5 running on an x86 64-bit platform, change to the
RedHat50AS_26x86_64 directory.
5 Run the script. At the command prompt, type:
./snPreInstall
The pre-installation script runs (Figure 1).
StorNext 3.5.2.1 Installation Guide 9
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:
• Estimated disk space required for each support directory.
• Recommended file system location for each support directory.
Te c h T i p : 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
Ta bl e 5.
Chapter 1: Installing StorNext File System and Storage Manager

StorNext Installation Script

Table 5 Pre-Installation Script Recommendation Types
Typ e Description
RECOMMEND The suggested directory locations will result in
optimal system performance.
NOTE 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
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
Installation Script.
StorNext
Journal,
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.
If you are upgrading from a StorNext File System only system to include StorNext Storage Manager, please follow the instructions in
From a StorNext File System-Only Configuration. Otherwise, you can
proceed to Launching the StorNext Installation Script.
StorNext 3.5.2.1 Installation Guide 11
Upgrading
Chapter 1: Installing StorNext File System and Storage Manager StorNext Installation Script
Upgrading From a StorNext File System­Only Configuration

Launching the StorNext Installation Script

If you have StorNext File System only and are adding StorNext Storage Manager, some components remain from the File System installation and the new installation could fail. To prevent installation failure, you should first remove the old components.
The following procedure describes how to remove the old components before starting the new StorNext installation. Follow the steps below
only
if you are upgrading from a StorNext File System-only
configuration to StorNext File System and Storage Manger.
1 Log on to the MDC as root. 2 Save /etc/fstab and /usr/cvfs/config
3 Remove the existing rpms.
4 Install StorNext as described in Launching the StorNext Installation
Script.
5 Restore /etc/fstab and /usr/cvfs/config
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 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.
Figure 2 StorNext Installation Script
Chapter 1: Installing StorNext File System and Storage Manager
StorNext Installation Script
For example, for Red Hat Linux 5 running on an x86 64-bit platform, change to the
RedHat50AS_26x86_64 directory.
5 Run the script. At the command prompt, type:
./install.stornext
The installation script runs (Figure 2).
6 Type the number corresponding to a menu option and press
<Enter>. Installation menu options are described in Ta bl e 6.
Table 6 StorNext Installation Main Menu Options

Changing Installation Configuration 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 15).
3 View the status of an installation operation that
is currently in progress.
4 Exit the StorNext installation script.
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.
StorNext 3.5.2.1 Installation Guide 13
Chapter 1: Installing StorNext File System and Storage Manager StorNext Installation Script
On the Main Menu, type 1 and press <Enter>. The Configuration Menu appears (
Figure 3 Configuration Menu
Figure 3).
Changing Application Directory Locations
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 (
<Enter>.
1–14), and then press
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.
Chapter 1: Installing StorNext File System and Storage Manager
StorNext Installation Script
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
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
the x86 64-bit version 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.

Performing an Installation Operation

To install StorNext using the options specified on the Configuration Menu, perform an installation operation.
1 On the Main Menu, type 2 and press <Enter>.
The StorNext installation script runs (Figure 2). The script displays the current progress of the installation.
StorNext 3.5.2.1 Installation Guide 15
Chapter 1: Installing StorNext File System and Storage Manager StorNext Installation Script
Note: Depending on your system configuration, the post-
installation procedure could take a long time (up to several hours) to complete. Until the status changes to Complete, a message informs you that the procedure is still running. Please be patient while this step runs.
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
Configuring StorNext
Chapter 4,
Chapter 2
Installing 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
• Make sure all storage devices are correctly configured and are visible to the MDC (see
File System Requirements).
Getting Ready to Install on page 20).
When you are ready, install StorNext File System on the MDC using the appropriate method for your operating system (see
File System on Linux or Unix on page 22 or Installing StorNext File System on Windows on page 26).
Note: To install both StorNext File System and StorNext Storage
Manager, see
Storage Manager To install the StorNext client software, see Chapter 3, Installing the StorNext Client
StorNext 3.5.2.1 Installation Guide 17
Chapter 1, Installing StorNext File System and
Installing StorNext
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

Table 7 File System Supported Platforms
The operating systems, releases and kernels, and hardware platforms supported by StorNext SNFS are presented in
Ta bl e 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.
Operating System Release or Kernel Platform
Windows Server
®
2003
Windows Server
®
2008
Red Hat® Enterprise
®
4
Linux
R2 SP2 x86 32-bit and
64-bit
SP1, SP2 and R2 x86 64-bit
2.6.9-67.EL (Update 6)
2.6.9-78.EL (Update 7)
x86 32-bit and 64-bit
2.6.9-89 EL (Update 8)
Red Hat® Enterprise
®
Linux
5
2.6.18-53.EL (Update 1)
2.6.18-92.EL (Update 2)
x86 64-bit
2.6.18-128.1.1.EL (Update
3)
2.6.18-164.EL (Update 4)
SUSETM Linux Enterprise Server 10
2.6.16.46-0.12 (SP1)
2.6.16.60-0.27 (SP2)
x86 64-bit and Itanium 64-bit
2.6.16.60-0.54.5 (SP3)
SUSE Linux Enterprise
2.6.27.19-5 Itanium 64-bit
Server 11
Sun SolarisTM 10
Generic 120011-14 Sparc 64-bit
Chapter 2: Installing StorNext File System
File System Requirements

Hardware Requirements

The minimum amount of RAM and available hard disk space required to run StorNext SNFS are presented in
Ta bl e 8.
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 Ta bl e 8 are for running StorNext File
System only. Running additional software (including the StorNext client software) requires additional RAM.
Table 8 File System Hardware Requirements
File Systems RAM Disk Space
1–4* 2 GB 2 GB
5–8** 4 GB 4 GB
*Two CPUs recommended for best performance. **Two CPUs required for best performance.

LAN Requirements The following LAN requirements must be met before installing StorNext

on the MDC:
• 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).
StorNext 3.5.2.1 Installation Guide 19
Chapter 2: Installing StorNext File System Getting Ready to Install
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 20).
• If using LUNs larger than 1 TB, decide on a label type and install any necessary operating system patches (see
than 1 TB on page 21).
• (Linux only) Install the kernel source code (see Installing the Linux
Kernel Source Code on page 22).
Planning for LUNs Larger

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.)
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
Guide
.)
Caution: StorNext does not support the connection of multiple
devices through fibre channel hubs. Multiple devices must be connected using fibre channel switches.
StorNext User’s
Chapter 2: Installing StorNext File System
Getting Ready to Install

Planning for LUNs Larger than 1 TB

Table 9 Required Disk LUN Labels
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).
Required disk LUN label settings based on operating system and LUN size are presented in
Ta bl e 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
Ta bl e 9.
Note: After labeling a disk LUN, you must reboot systems running
Solaris before they can access the disk LUN.
Operating System
Windows
a
Linux 2.6
Label for LUNs < 1 TB
Label for LUNs 1–2 TB
Label for LUNs > 2 TB
VTOC, EFI VTOC, EFI EFI, sVTOC
VTOC, EFI VTOC, EFI EFI, sVTOC
Kernel
Linux 2.4
VTOC, EFI VTOC, EFI Not supported
Kernel
Solaris 9
Solaris 10
d
HP-UX
IBM AIX
e
b
c
VTOC, EFI EFI Not supported
VTOC, EFI EFI EFI
VTOC, EFI VTOC, EFI EFI, sVTOC
VTOC, EFI VTOC, EFI EFI, sVTOC
SGI IRIX VTOC VTOC Not supported
Apple Xsan 1.3
VTOC, EFI VTOC, EFI EFI, sVTOC (MacOS X 10.4 Tiger)
StorNext 3.5.2.1 Installation Guide 21
Chapter 2: Installing StorNext File System Installing StorNext File System on Linux or Unix
Operating System
Apple Xsan 1.3
Label for LUNs
< 1 TB
Label for LUNs 1–2 TB
Label for LUNs > 2 TB
VTOC, EFI VTOC, EFI EFI, sVTOC (MacOS X 10.3
Panther)
Apple Xsan
1.2
a. For Windows XP 32-bit systems only, support for LUNs larger than 2 TB is
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 the first 2 TB of LUNs larger than 2 TB. e. Supports only LUNs of 2.2 TB or less.
d
VTOC VTOC sVTOC
d
limited to the first 2 TB. All other supported Windows platforms (including Windows XP 64-bit) support LUNs greater than 2 TB.
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.
The kernel source code can be installed using the installation disks for your operating system.

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.
Chapter 2: Installing StorNext File System
Installing StorNext File System on Linux or Unix
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.
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 5 running on an x86 64-bit platform, change to the
RedHat50AS_26x86_64 directory.
5 Run the script. At the command prompt, type:
./install.snfs
The installation script runs (Figure 4).
StorNext 3.5.2.1 Installation Guide 23
Chapter 2: Installing StorNext File System Installing StorNext File System on Linux or Unix
Figure 4 SNFS Installation Script
6 Type the number corresponding to a menu option and press
<Enter>. Installation menu options are described in Ta bl e 10.
Table 10 SNFS Installation Main Menu Options

Changing Installation Configuration Options

Menu Option Description
1 Change installation options for the location of
application directories (see
Changing
Installation Configuration Options on page 24).
2 Install StorNext using the installation options
specified on the Configuration Menu (see
Performing an Installation Operation on
page 25).
3 View the status of an installation operation that
is currently in progress.
4 Exit the SNFS installation script.
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 5).
Figure 5 Configuration Menu
Chapter 2: Installing StorNext File System
Installing StorNext File System on Linux or Unix
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 (
<Enter>.
1–6), and then press

Performing an Installation Operation

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.
To install StorNext using the options specified on the Configuration Menu, perform an installation operation.
1 On the Main Menu, type 2 and press <Enter>.
The installation script runs (Figure 4). The script displays the current progress of the installation.
StorNext 3.5.2.1 Installation Guide 25
Chapter 2: Installing StorNext File System Installing StorNext File System on Windows
Note: Depending on your system configuration, the post-
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
You can now access StorNext File System and run the configuration wizard. For more information, see
installation procedure could take a long time (up to several hours) to complete. Until the status changes to Complete, a message informs you that the procedure is still running. Please be patient while this step runs.
accessed. Make a note of this information.
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 27).
When you are ready, use the setup wizard to install StorNext (see
Running the Setup Wizard on page 28).
(Optional) After installation, restore the previous client configuration (see
Restoring a Previous Client Configuration on page 33).
Note: You must log on as an Administrator to install StorNext.

Disabling Automatic IP Address Configuration

Before installing StorNext, you should disable automatic IP address configuration in Windows. Disabling automatic IP address configuration
Chapter 2: Installing StorNext File System
Installing StorNext File System on Windows
ensures that the FSM passes the correct IP address to file system nameservers. Failure to disable automatic IP address configuration could result in StorNext clients or servers being unable to talk to the active FSM.
There are two methods for disabling automatic IP address configuration:
• Manually configuring the TCP/IP information, which disables DHCP. You should use this method if any static IP addresses have been configured.
• Editing the Windows registry to disable automatic IP address configuration but not disable DHCP. To use this method, follow the procedure outlined in Microsoft article 220874 available here:
http:/
/support.microsoft.com/kb/220874.

Removing a Previous Version of StorNext

If a previous version of StorNext older than version 3.0 exists on the system, you must remove it before installing the new version. If you are upgrading from a version of StorNext newer than version 3.0, the old client configuration is retained so there is no need to restore the old configuration.
1 Insert the StorNext installation CD.
2 Browse to the root directory of the installation CD and double-click
the file
SnfsSetup64.exe.
The StorNext Installation window appears (Figure 6).
StorNext 3.5.2.1 Installation Guide 27
Chapter 2: Installing StorNext File System Installing StorNext File System on Windows
Figure 6 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 33).

Running the Setup Wizard

To launch the setup wizard, use the correct StorNext installation CD for your operating system.
Note: Due to variables and different system configurations, the
installation process for Windows could be slightly different than described. For example, you may or may not be asked to reboot your system, depending on your configuration. Generally speaking, the best policy is to follow the onscreen instructions after you launch the Setup Wizard.
Figure 7 StorNext Installation Window: Install StorNext
Chapter 2: Installing StorNext File System
Installing StorNext File System on Windows
1 Insert the StorNext installation CD.
2 Browse to the root directory of the installation CD and double-click
the file
SnfsSetup64.exe.
The StorNext Installation window appears (Figure 7).
3 Click Install StorNext to begin installation.
The StorNext setup wizard appears (Figure 8).
Figure 8 SNFS Setup: Welcome
StorNext 3.5.2.1 Installation Guide 29
Chapter 2: Installing StorNext File System Installing StorNext File System on Windows
4 Click Next to continue.
The License Agreement window appears (Figure 9).
Figure 9 SNFS Setup: End-User License Agreement
Figure 10 SNFS Setup: Customer Information
5 Click the option to accept the license agreement, and then click Next
to continue. The Customer Information window appears (Figure 10).
Figure 11 SNFS Setup: Choose Setup Type
Chapter 2: Installing StorNext File System
Installing StorNext File System on Windows
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 11).
7 Click an installation option:
Typical: (Recommended) Installs StorNext File System, client
software, and help files in the default location (
Files\StorNext
).
C:\Program
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 12).
StorNext 3.5.2.1 Installation Guide 31
Chapter 2: Installing StorNext File System Installing StorNext File System on Windows
Figure 12 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 13).
Figure 13 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.
Chapter 2: Installing StorNext File System
Installing StorNext File System on Windows
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

Figure 14 StorNext Installation Window: Configure StorNext
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.
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 14).
3 Click Configure StorNext.
The StorNext Configuration window appears (Figure 15).
StorNext 3.5.2.1 Installation Guide 33
Chapter 2: Installing StorNext File System Installing StorNext File System on Windows
Figure 15 StorNext Configuration Window
4 Click Import/Export Clie nt Se ttin gs .
The Import/Export Client Configuration window appears (Figure 16).
Figure 16 Import/Export Client Configuration Window
Chapter 2: Installing StorNext File System
Installing StorNext File System on Windows
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
StorNext 3.5.2.1 Installation Guide 35
window.
Chapter 2: Installing StorNext File System Installing StorNext File System on Windows
Chapter 3
Installing 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
Requirements).
To install the StorNext client software, first download the client software from the metadata controller (MDC) (see
Client Software on page 42).
Downloading the StorNext
Client System
After downloading the client software, install and configure it using the appropriate method for your operating system (see
StorNext Client on Linux or Unix on page 45 or Installing the StorNext Client on Windows on page 52).
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.5.2.1 Installation Guide 37
Installing the
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

Table 11 StorNext Client Supported Platforms
The operating systems, releases and kernels, and hardware platforms supported by the StorNext client software are presented in 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.
Operating System Release or Kernel Platform
Windows XP SP2 and SP3 x86 32-bit
Windows 2003 Server R2 and SP2 x86 32-bit
Windows Vista SP1 and SP2 x86 32-bit
Windows 2008 Server SP1, SP2 and R2 x86 32-bit
Windows 7 n/a x86 32-bit
Red Hat Enterprise Linux 4
2.6.9-67.EL (Update 6)
2.6.9-78.EL (Update 7)
2.6.9-89 EL (Update 8)
Ta bl e 11.
x86 64-bit
x86 64-bit
x86 64-bit
x86 64-bit
x86 64-bit
x86 32-bit x86 64-bit
Red Hat Enterprise Linux 5
SUSE Linux Enterprise Server 10
2.6.18-53.EL (Update 1)
2.6.18-92.EL (Update 2)
2.6.18-128.EL (Update 3)
2.6.16-46-0.12 (SP1)
2.6.16-60-0.27 (SP2)
2.6.16.60-0.54.5 (SP3)
x86 64-bit
x86 32 bit x86 64-bit Itanium 64-bit
Chapter 3: Installing the StorNext Client
Client System Requirements
Operating System Release or Kernel Platform
SUSE Linux Enterprise Server 11
2.6.27.19-5 x86 64-bit Itanium 64-bit
Sun Solaris 10 Generic 127128-11 Opteron x86
64-bit Intel x86 64­bit
Generic 120011-14 Sparc 64-bit
HP-UX
IBM AIX
®
®
11i v2 Itanium-64 bit
5.3 64-bit Power Architecture
SGI® IRIX
®
Apple MacOS® X
6.5.30 64-bit MIPS
10.5.5 w/Xsan 2.1.1,
x86 32-bit
StorNext MDC
10.6 w/Xsan 2.2, StorNext
MDC
10.6 w/Xsan 2.2.1,
StorNext MDC
x86 32 bit x86 64-bit
x86 32 bit x86 64-bit

Hardware Requirements

To install and run the StorNext client software, the client system must meet the following minimum hardware requirements.
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
StorNext 3.5.2.1 Installation Guide 39
Chapter 3: Installing the StorNext Client Client System Requirements
Note: Distributed LAN servers may require additional RAM depending
on the number of file systems, distributed LAN clients, and NICs used. See
Distributed LAN Server Memory Tuning in the
StorNext User’s Guide for Distributed LAN Server memory tuning guidelines.

StorNext File System Client Buffer Cache

Table 12 Default Memory Consumed by cachebufsize
As of StorNext 3.0, multiple mounted file systems typically share a single buffer cache. A StorNext client buffer cache is created for each different
cachebufsize. By default, all file systems have the same cachebufsize of
64K, so they all share the same buffer cache.
Note: These settings do not apply to Apple Xsan clients, which do not
use the StorNext buffer cache.
The amount of memory consumed by default for each cachebufsize depends on the platform type and the amount of memory in the system.
cachebufsize.
Ta bl e 12 shows the default amount of memory consumed by
Platform Type <=2GB Memory >2GB Memory
32-bit Windows 32MB 64MB
32-bit Linux 64MB 128MB
All other platforms 64MB 256MB
To see information about the buffer cache after mounting file systems, use the memory used by the buffer cache at mount time, use the
cvdb(1) command with the -b option. To change the amount of
buffercachecap
parameter.
On Windows, the non-paged pool is used for buffer cache memory until it consumes up to 64 megabytes (32-bit systems) or 64 gigabytes (64-bit systems). Any additional buffer cache memory comes from the paged pool.
Chapter 3: Installing the StorNext Client

Client Installation Changes From Previous Releases

Client Installation Changes From Previous Releases
Beginning with StorNext release 3.5.2.1, the delivery mechanism for client software has changed. Client software for all operating systems is now contained on one disk labeled “Client Software and Product Documentation.” (Formerly, client software was distributed on the software disks for all operating systems.)
You must now insert the client software disk, copy the client software from the disk, and then install or upgrade the client packages as described in this guide.
In addition, client software is no longer distributed in compressed format (such as tar.gz files). Instead, the client software disk contains executable files which, when launched, extract the client software for the selected platform to the location /tmp/stornext where you can install the package. Windows client packages have not changed, and are still in .zip format.
Following is a summary of the changed part of installation procedure for UNIX and Linux systems:
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 Run the client software binary. At the command prompt, type:
./<archive name>
where <archive name> is the name of the software archive file you downloaded from the MDC. (For example, the file for RH5 is
sn_dsm_linuxRedHat50AS_x86_64_client.bin)
4 When you are presented with the StorNext End User License
Agreement (EULA), press <ENTER> to read the EULA. After reading the EULA enter y (lower case only) to accept the EULA, or enter any other key to decline.
After you accept the EULA, the client software is extracted to /tmp/stornext.
5 Change directories to /tmp/stornext.
6 Follow the remaining installation steps in Installing the StorNext
Client on Linux or Unix on page 45.
StorNext 3.5.2.1 Installation Guide 41
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,
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 password is
OK. (The default value for both username and
admin.)
http://servername:81
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 17).
Figure 17 Select Platform Window
Chapter 3: Installing the StorNext Client
Downloading the StorNext Client Software
4 In the list, click the operating system running on the client system,
and then click
Next.
The Download Client Software window appears (Figure 18).
StorNext 3.5.2.1 Installation Guide 43
Chapter 3: Installing the StorNext Client Downloading the StorNext Client Software
Figure 18 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 45
Installing the StorNext Client on Windows on page 52.
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 45
Installing the StorNext Client on Sun Solaris on page 47
Installing the StorNext Client on HP-UX on page 49
Installing the StorNext Client on IBM AIX on page 51

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.
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 Run the client software binary. At the command prompt, type:
./<archive name>
where <archive name> is the name of the software archive file you downloaded from the MDC. (For example, the file for RH5 is
sn_dsm_linuxRedHat50AS_x86_64_client.bin)
4 When you are presented with the StorNext End User License
Agreement (EULA), press <ENTER> to read the EULA. After reading the EULA enter y (lower case only) to accept the EULA, or enter any other key to decline.
After you accept the EULA, the client software is extracted to /tmp/stornext.
StorNext 3.5.2.1 Installation Guide 45
Chapter 3: Installing the StorNext Client Installing the StorNext Client on Linux or Unix
5 Change directories to /tmp/stornext.
6 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
Note: The file that ends with .rpm.md5sum is a checksum file, not
7 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
8 Configure the boot order for system services. Do one of the
following:
• For Red Hat Linux, at the command prompt, type:
snfs-client and ends with the .rpm file name extension.
the client software package.
Step 6.
chkconfig --level 3456 cvfs on
• For SUSE Linux Enterprise, at the command prompt, type:
chkconfig -s raw 235 chkconfig -s cvfs 345
9 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 the
fsnameservers file should contain a single line with a
snserver, then
single word: snserver
10 Create a mount point for the file system. At the command prompt,
type:
mkdir -p <mount point>
Chapter 3: Installing the StorNext Client
Installing the StorNext Client on Linux or Unix
chmod 777 <mount point>
where <mount point> is the directory path where you want the file system to be mounted. For example:
/stornext/snfs1
11 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 10.
12 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.
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 Run the client software binary. At the command prompt, type:
./<archive name>
where <archive name> is the name of the software archive file you downloaded from the MDC. (For example, the file for RH5 is
sn_dsm_linuxRedHat50AS_x86_64_client.bin)
4 When you are presented with the StorNext End User License
Agreement (EULA), press <ENTER> to read the EULA. After reading the EULA enter y (lower case only) to accept the EULA, or enter any other key to decline.
StorNext 3.5.2.1 Installation Guide 47
Chapter 3: Installing the StorNext Client Installing the StorNext Client on Linux or Unix
After you accept the EULA, the client software is extracted to /tmp/stornext.
5 Change directories to /tmp/stornext.
6 Install the client software package. At the command prompt, type:
pkgadd -d .
7 Typ e 1 to select the ADICsnfs package. 8 Typ e y to confirm installation of the ADICsnfs package. When
installation is complete, type
9 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 create it.
Note: The fsnameservers file only needs to contain the IP address
q to quit the installation program.
fsnameservers file does not exist, use a text editor to
of the MDC. For example, if the IP address for the MDC is
192.168.143.1, then the fsnameservers file should contain a
single line with 192.168.143.1
10 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
11 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 10.
12 Reboot the client system.
After reboot, the StorNext file system is mounted at the mount point you specified.
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 -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.

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.
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 Run the client software binary. At the command prompt, type:
./<archive name>
where <archive name> is the name of the software archive file you downloaded from the MDC. (For example, the file for RH5 is
sn_dsm_linuxRedHat50AS_x86_64_client.bin)
4 When you are presented with the StorNext End User License
Agreement (EULA), press <ENTER> to read the EULA. After reading the EULA enter y (lower case only) to accept the EULA, or enter any other key to decline.
After you accept the EULA, the client software is extracted to /tmp/stornext.
5 Change directories to /tmp/stornext.
6 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.
7 Install the client software package. At the command prompt, type:
swinstall -s <package path and name> -x mount_all_filesystems=false \*
StorNext 3.5.2.1 Installation Guide 49
Chapter 3: Installing the StorNext Client Installing the StorNext Client on Linux or Unix
where < client software package you identified in
package path and name
> is the full path and name of the
Step 6.
8 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 the
fsnameservers file should contain a single line with a
snserver, then
single word: snserver
9 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
10 Configure the file system to automatically mount after reboot. To do
this, edit the
<mount point> <mount point> cvfs rw,fsname=<file system> 0 0
/etc/fstab file so that it contains the following line:
where <mount point> is the directory path created in Step 9 and <file
system> is the name of the StorNext file system.
11 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.
Chapter 3: Installing the StorNext Client
Installing the StorNext Client on Linux or Unix

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.
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 Run the client software binary. At the command prompt, type:
./<archive name>
where <archive name> is the name of the software archive file you downloaded from the MDC. (For example, the file for RH5 is
sn_dsm_linuxRedHat50AS_x86_64_client.bin)
4 When you are presented with the StorNext End User License
Agreement (EULA), press <ENTER> to read the EULA. After reading the EULA enter y (lower case only) to accept the EULA, or enter any other key to decline.
After you accept the EULA, the client software is extracted to /tmp/stornext.
5 Change directories to /tmp/stornext.
6 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.
7 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 6.
8 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.5.2.1 Installation Guide 51
Chapter 3: Installing the StorNext Client Installing the StorNext Client on Windows
9 Create a mount point for the file system. At the command prompt,
10 Configure the file system to automatically mount. At the command
Note: The fsnameservers file only needs to contain the name of
the MDC. For example, if the MDC is named the
fsnameservers file should contain a single line with a
snserver, then
single word: snserver
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
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 9.
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 <mount point>
where <mount point> is the directory path where you want the file system to be mounted.

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.
Chapter 3: Installing the StorNext Client
Installing the StorNext Client on Windows
Before installing StorNext, remove any previously installed versions (see
Removing a Previous Version of StorNext on page 53).
When you are ready, use the setup wizard to install StorNext (see
Running the Setup Wizard on page 54).
(Optional) After installation, restore the previous client configuration (see
Restoring a Previous Client Configuration on page 58).
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

Figure 19 StorNext Installation Window: Remove StorNext
If a previous version of StorNext exists on the system, you must remove it before installing the new version.
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
SnfsSetup64.exe (64-bit systems).
SnfsSetup32.exe (32-bit systems) or
The StorNext Installation window appears (Figure 19).
StorNext 3.5.2.1 Installation Guide 53
Chapter 3: Installing the StorNext Client Installing the StorNext Client on Windows
3 Click Remove StorNext.
4 Note the name and location of the saved configuration file, and
5 If prompted, click Yes to continue, and then click OK to finish the
6 When the removal is complete, click Yes to reboot the system.
Note: After installing the new version of StorNext, you can restore the
A dialog box appears informing you that the current client configuration has been saved.
then click
OK.
removal.
saved client configuration (see
Restoring a Previous Client
Configuration on page 58).

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.
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
SnfsSetup64.exe (64-bit systems).
SnfsSetup32.exe (32-bit systems) or
The StorNext Installation window appears (Figure 20).
Figure 20 StorNext Installation Window: Install StorNext
Figure 21 SNFS Setup: Welcome
Chapter 3: Installing the StorNext Client
Installing the StorNext Client on Windows
3 Click Install StorNext to begin installation.
The StorNext setup wizard appears (Figure 21).
4 Click Next to continue.
The License Agreement window appears (Figure 22).
StorNext 3.5.2.1 Installation Guide 55
Chapter 3: Installing the StorNext Client Installing the StorNext Client on Windows
Figure 22 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 23).
Figure 23 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 24).
Figure 24 SNFS Setup: Choose Setup Type
Chapter 3: Installing the StorNext Client
Installing the StorNext Client on Windows
7 Click an installation option:
Typical: (Recommended) Installs the StorNext client software
and help files in the default location (
C:\Program Files\StorNext).
Figure 25 SNFS Setup: Ready to Install
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 25).
StorNext 3.5.2.1 Installation Guide 57
Chapter 3: Installing the StorNext Client Installing the StorNext Client on Windows
8 Click Install to continue.
Figure 26 SNFS Setup: Finish
Wait while the setup wizard installs StorNext. When installation is complete, the
Finish window appears (Figure 26).
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.
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
SnfsSetup64.exe (64-bit systems).
SnfsSetup32.exe (32-bit systems) or
Figure 27 StorNext Installation Window: Configure StorNext
Chapter 3: Installing the StorNext Client
Installing the StorNext Client on Windows
The StorNext Installation window appears (Figure 27).
3 Click Configure StorNext.
The StorNext Configuration window appears (Figure 28).
Figure 28 StorNext Configuration Window
4 Click Import/Export Clie nt Se ttin gs .
The Import/Export Client Configuration window appears (Figure 29).
StorNext 3.5.2.1 Installation Guide 59
Chapter 3: Installing the StorNext Client Installing the StorNext Client on Windows
Figure 29 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.
Chapter 4

Configuring 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
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 64).
StorNext GUI).
To configure a StorNext client as a distributed LAN client or server, edit the distributed LAN configuration file (see
LAN Client Server on page 68).
For systems running Windows, use the Windows-based configuration utilities to set up server and client features (see
Utilities on page 73).
StorNext 3.5.2.1 Installation Guide 61
Configuring a Distributed
Windows Configuration
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
Utilities on page 73).
Windows Configuration

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.
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
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
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 for an MDC running File System only is shown in Figure 31.
OK. (The default value for both user name and password is
81.) For example: http://servername:81
Figure 30. The StorNext home page
Figure 30 StorNext Home Page: File System and Storage Manager
Figure 31 StorNext Home Page: File System Only
Chapter 4: Configuring StorNext
StorNext GUI
StorNext 3.5.2.1 Installation Guide 63
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 running File System only is shown in Figure 33.
Figure 32 StorNext Configuration Wizard: Storage Manager
Figure 32. The Configuration Wizard for an MDC
Figure 33 StorNext Configuration Wizard: File System Only
Chapter 4: Configuring StorNext
Configuration Wizard

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:
• 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

Using the Configuration Wizard

menu, click
The Configuration Wizard consists of eight steps. (If Storage Manager is not installed on the MDC, only the first two steps appear.) The wizard
Configuration Wizard.
lets you navigate between steps and tracks your progress as you complete each step.
• 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.
StorNext 3.5.2.1 Installation Guide 65
Chapter 4: Configuring StorNext Configuration Wizard
• To exit the wizard, click Done.
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
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
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.)
Chapter 4: Configuring StorNext
Configuration Wizard
To display the Add New File System Wizard at any time, on the Config menu, click systems, see Chapter 6, “Managing the File System,” in the
User’s Guide
Add File System. For more information about adding file
StorNext
.
Step 3: Add Library
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
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
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
.
Step 6: Add Storage Disks
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.
StorNext 3.5.2.1 Installation Guide 67
Chapter 4: Configuring StorNext Configuring a Distributed LAN Client Server
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
Guide
Step 7: Add Storage Policy
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 storage policies, see Chapter 11, “Data Migration Management,” in the
StorNext User’s Guide
Step 8: E-Mail Notification
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.)
StorNext User’s
.
Add Storage Policy. For more information about adding
.
To display the E-mail Notification Wizard at any time, on the Config menu, click e-mail notifications disks, see Chapter 4 “Common StorNext Tasks,” in the
StorNext User’s Guide
E-Mail Notification. For more information about setting up
.

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.)
Chapter 4: Configuring StorNext
Configuring a Distributed LAN Client Server
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 74 and Distributed
LAN on page 76.

Configuring a Distributed LAN Client on Linux

To configure a StorNext client as a distributed LAN client, edit mount options in the
/etc/fstab file.
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
StorNext 3.5.2.1 Installation Guide 69
Chapter 4: Configuring StorNext Configuring a Distributed LAN Client Server

Configuring a Distributed LAN Server on Linux

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.
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 34).
Figure 34 sndpscfg Configuration Utility
Chapter 4: Configuring StorNext
Configuring a Distributed LAN Client Server
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.
Ta bl e 13
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.
Table 13 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)
StorNext 3.5.2.1 Installation Guide 71
Chapter 4: Configuring StorNext Configuring a Distributed LAN Client Server
Field / Button Description
transfer_buffer_size_kb The transfer buffer size (in KB) used by the
transfer_buffer_count The number of transfer buffers used by the
server_buffer_count The number of I/O buffers allocated for
daemon_threads The maximum number of daemon threads
distributed LAN server. A larger buffer may increase performance for larger files. (Default: 256)
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)
each network interface on the distributed LAN server. This parameter is used only by Linux servers. (Default: 8)
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
Creating an Override Configuration
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>
Chapter 4: Configuring StorNext

Windows Configuration Utilities

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
/user/cvfs/config/ directory.
dpserver.<file system> is created in the
Using Distributed LAN Client and Server Commands
Use the cvadmin commands described in Tab le 14 to see information about distributed LAN servers and clients. (For more information about using
cvadmin commands, see the
CLI Reference Guide
.)
Table 14 Distributed LAN Client and Server Commands
Command Description
proxy Lists all distributed LAN servers for the
proxy long Lists all distributed LAN servers for the
proxy who
<distributed
LAN client>
proxy who
<distributed
LAN server>
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.
currently selected file system.
currently selected file system, as well as tunable parameters and attached disks.
Lists distributed LAN servers connected to the specified distributed LAN client, as well as current I/O statistics.
Lists distributed LAN clients connected to the specified distributed LAN server, as well as current I/O statistics.
To run a configuration utility, on the Windows St art menu, click All
Programs > StorNext File System
StorNext 3.5.2.1 Installation Guide 73
, and then click the utility.
Chapter 4: Configuring StorNext Windows Configuration Utilities
The StorNext client software includes the following configuration utilities:

Client Configuration on page 74

Disk Device Labeler on page 86
License Identifier on page 88
Simple File System Configuration on page 89
Start File System Services on page 91
Stop and Remove File System Services on page 91
Stop File System Services on page 91
Version Information on page 92
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 92
File System Startup List on page 92
Re-initialize a File System on page 94
Repair a File System on page 94
Server Administration on page 94
Server Configuration on page 101
Client Configuration The Client Configuration utility lets you view and modify properties for
the StorNext client software. Use the utility to specify mount points and mount options, set various cache settings, and configure a distributed LAN server or a distributed LAN client.
To run the Client Configuration utility, on the Windows Start menu, click
All Programs > StorNext File System > Client Configuration.
The Client Configuration utility includes four tabs:
Mount Point on page 75
Distributed LAN on page 76
Advanced Mount Options on page 79
Advanced Cache Options on page 83
Figure 35 Client Configuration: Mount Point
Chapter 4: Configuring StorNext
Windows Configuration Utilities
Click a tab to view or modify StorNext client properties. After making changes on one or more tabs, click appears prompting you to restart the system. Click
OK to save the changes. A message
Yes. Most changes
do not take affect until the system is restarted.
Mount Point
StorNext file systems can be mapped to a drive letter or to a folder. When mapping to a folder, the folder must be empty or non-existent,
and must exist within an NTFS file system (e.g., C:\Mount\MySnfs). Use the Mount Point tab (Figure 35) to specify drive mappings. Tab le 15
describes the fields on the Mount Point 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.5.2.1 Installation Guide 75
Chapter 4: Configuring StorNext Windows Configuration Utilities
Table 15 Client Configuration: Mount Point
Field / Button Description
Map to Drive Letter Select Map to Drive Letter to map the drive to
a specific drive letter.
Drive (Letter) Select the desired drive letter.
Map to Directory Instead of selecting Map to Drive Letter,
select Map to Directory. Enter a directory path, or click Browse to navigate to the directory path.
Note: If this is a Distributed LAN client or server, be sure to enter the
parameters on the Distributed LAN tab.
Distributed LAN
The Distributed LAN tab is used to enable and configure StorNext Distributed LAN (DLAN) Clients and Servers for a file system. The Enable Client and Enable Server radio buttons determine whether the system is a Client or Server. Note that separate licensing is required for DLAN.
StorNext Distributed LAN Clients provide the same functionality as normal StorNext Clients but do not need to be connected directly to the SAN. They instead send I/O via the TCP/IP network to a Distributed LAN Server; a normal SAN client with DLAN Server Selected in its configuration. Metadata is sent over the TCP/IP network directly to the File System Metadata Controller (Server/MDC).
Distributed LAN Clients request the location of normal DLAN Servers via the Name Server.
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.)
Figure 36 Client Configuration: Distributed LAN
Chapter 4: Configuring StorNext
Windows Configuration Utilities
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.
Use the Distributed LAN tab (Figure 36) to configure a distributed LAN server or a distributed LAN client. Ta bl e 16 describes the fields on the
Distributed LAN tab.
Table 16 Client Configuration: Distributed LAN
Field / Button Description
Disable Select this option to disable the StorNext
client as a distributed LAN client or distributed LANserver.
StorNext 3.5.2.1 Installation Guide 77
Chapter 4: Configuring StorNext Windows Configuration Utilities
Field / Button Description
Enable Client 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.
Number of Transfer Buffers
Specify the number of socket transfer buffers used for Distributed LAN Client I/O.
Read Timeout (sec) Specify how long the Distributed LAN Client
will wait for a read operation to complete before retrying it on a different Distributed LAN Server.
Write Timeout (sec) Specify how long the Distributed LAN Client
will wait for a write operation to complete before retrying it on a different Distributed LAN Server.
Transfer Buffer Size (kb)
Specify the size in kilobytes of the socket transfer buffers used for Distributed LAN Client I/O.
TCP Window Size (kb)
Specify the size in kilobytes of the TCP window used for Distributed LAN Client I/O connections.
Max Threads Specify the number of kernel threads that
will be used to service Distributed LAN Client I/O requests.
Server Interfaces To complete Distributed LAN Server
configuration, select one or more network interfaces to be used for Distributed LAN Client traffic.
Figure 37 Client Configuration: Advanced Mount Options
Chapter 4: Configuring StorNext
Windows Configuration Utilities
Advanced Mount Options
The Mount Options tab (Figure 37) displays the mount options for the drive currently selected on the Drive Mappings tab. Ta bl e 16 describes the fields on the Distributed LAN 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.5.2.1 Installation Guide 79
Chapter 4: Configuring StorNext Windows Configuration Utilities
Table 17 Client Configuration: Advanced Mount Options
Field / Button Description
Mount Retransmit Limit
Specify the number of times the driver will re-transmit a message to the FSM. After a successful connection, this value is no longer used.
The default is 1.
Hard Mount When this box is checked, the driver attempts
to mount the file system forever. The default is off (Soft Mount). Quantum
recommends that Hard Mount NOT be used on Windows systems.
Allow Diskless Mount When this box is checked, the file system can
be mounted and accessed without all the disks being accessible in the file system stripe groups. In this mode, file metadata can be viewed and changed, but no data can be accessed.
The default is to not allow a file system to be mounted unless all disks are accessible.
Read Only When this box is checked, the file system is
mounted in read-only mode. The default is off or not checked.
Restrict Pre­allocation API
Number of Async I/O Threads
When set to yes, non-administrator users are unable to use the preallocation ioctl.
Specify the number of threads created to be used as asynchronous I/O threads for user applications. The default is 8. The allowed range is 4 to 32.
Number of System Threads
Message TImeout x 1/10th Sec.
Specify the number of threads created for use by the file system. The default value is 16.
Specify (in tenths of a second) the amount of time before a message to the FSM is timed out. The default is 50 (five seconds).
Chapter 4: Configuring StorNext
Windows Configuration Utilities
Field / Button Description
Message Retry Count Specify the number of attempts to be made
for sending a message to the File System Service. The default is 12.
Retry I/Os Forever or Allow I/O
Timeouts
I/O Retry Time Seconds
I/O Penalty TIme Seconds
Choose either Retry I/Os Forever or Allow I/O Timeouts, depending on whether you want to allow timeouts or keep trying I/O. The default value is to Retry I/Os Forever.
When you choose Allow I/O Timouts, this option controls the I/O retry behavior. This parameter establishes the amount of time that may elapse during an I/O retry sequence.
An I/O retry sequence consists of the following:
• Retry an I/O request across all available paths that are currently present.
• Compare the current time to the Instantiation time of the I/O request, if at least <n> seconds have elapsed, return the I/O request in error, otherwise reset the paths used, and retry again.
This option controls the Multi-Path I/O penalty value, where <n> is expressed in seconds with a minimum value of 1 and a maximum value of 15.
This parameter establishes the amount of
time a Path_In_Error will be bypassed in
favor of an Operational Path during a Multi­Path selection sequence. If all paths are currently in the Path_In_Error state, the first available path will be selected, independent of the Path_In_Error state.
The default value is 5 seconds.
StorNext 3.5.2.1 Installation Guide 81
Chapter 4: Configuring StorNext Windows Configuration Utilities
Field / Button Description
Fast Failover Detection
When this box is checked, the client uses a more aggressive approach to detecting if the FSM has failed. With this option on, the client monitors the FSM heartbeat. If no heartbeat is detected within three (3) seconds, a failover request is initiated.
This option is desirable for near realtime activities that cannot sustain more than 10 seconds of access loss to the server. Quantum does not recommend enabling this option for normal file system operations.
Hard Reconnect When this box is checked, the file system
attempts to reconnect to the FSM forever. If this option is not enabled, the file system attempts to reconnect to the FSM for the number of times specified at the Mount Retransmit Limit field before failing the request.
The default value is off.
Token Hold Seconds The QOS Token Hold Time parameter is
applicable only when using the StorNext Quality of Service (QOS) feature for real-time IO.
This parameter determines the number of seconds a client stripe group holds on to a non-realtime I/O token during periods of inactivity. If no I/O is performed on a stripe group within the specified number of seconds, the token is released back to the FSM.
The default value is 60 seconds. The parameter should be specified in five-second increments; if the parameter is not a multiple of five, it will be rounded up automatically.
Loading...