ADIC Webcam 2.8 User Manual

StorNext

2.8 File System and Storage

Manager Installation Guide

ADVANCED DIGITAL INFORMATION CORPORATION

www.adic.co

reserved. No part of this document may be reproduced, modified, distributed, or translated to another language without prior written consent of ADIC.

ADIC USA 11431 Willows Road NE Redmond, Washington 98052-4952 Tel.: 1-800-336-1233 Fax: 1-425-881-2296

This document may describe designs for which patents are pending, or have been granted. By publishing this information, ADIC conveys no license under any patent or any other right.

ADIC shall not be liable for errors contained herein or for incidental or consequential damages (including lost profits) in connection with the furnishing, performance or use of this material whether based on warranty, contract, or other legal theory. ADIC makes no representation or warranty with respect to the contents of this document and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Further, ADIC reserves the right to revise or change this document without obligation on the part of ADIC to notify any person or organization of such revision or change.

Every effort has been made to acknowledge trademarks and their owners. All trademarks within this document are the property of their respective owners. Trademarked names are used solely for identification or exemplary purposes, and any omissions are unintentional. ADIC is a registered trademark of Advanced Digital Information Corporation.

Published: July 2006 Document Number: 6-00360-08 Rev A

Advanced Digital Information Corporation Software Licenses Agreement

This Software License is entered into and effective as of this _____, day of_____________ 2006 ("Effective Date"), by and between:

and Advanced Digital

Information Corporation PO Box 97057 Redmond, WA 98073-9757 (Referred to as “ADIC")

This License sets forth the terms and conditions under which ADIC agrees to grant and Licensee agrees to accept a license to use certain of ADIC's proprietary software and related documentation. Any software programs or related materials provided to Licensee by ADIC will be subject to the terms and conditions of this License. Definitions “Designated Computer(s) upon which the Software is installed. “Documentation and user manuals, training materials, guides, listings, specifications, or other written documentation. "Release functionality. New Releases are provided to the Licensee at no charge when Licensee maintains a current Software Maintenance Agreement with ADIC. “Software form only, and the Documentation provided by ADIC in connection therewith or any portions thereof, and any subsequent Releases. "Upgrade change in ADIC's base version number. Upgrades may have a new initial License fee or upgrade charge associated with it.

” means ADIC provided materials related to the Software, including, but not limited to operator

" means a modification to the Software that does not change ADIC's base version number, but may add

” means only the current version of those software products specified in Exhibit A hereto, in object code

" means a modification to the Software that adds significant features and/or functionality and causes a

” means that computer equipment, identified to ADIC in Exhibit A by serial number,

Company: _______________________ Located at: _______________________ _______________________ _______________________ (Referred to as “Licensee")

Software License

a. License. In consideration of Licensee's full payment of the License fees and subject to the terms and

conditions of this License, ADIC hereby grants to Licensee a personal, non-exclusive, non-transferable license to use and copy the Software. A separate license is required for use of each Software program on each Designated Computer.

b. Use

c. Copying

StorNext File System and Storage Manager Installation Guide iii

. Licensee is authorized hereby to use the Software on the Designated Computer(s) only, or on backup equipment if the Designated Computer is inoperative until such time as the Designated Computer is restored to operation and processing on the back-up equipment is completed. This grant is specifically limited to use by the Licensee for normal, customary internal data processing, and specifically excludes Licensee's time-sharing or the rental of the Software or use of the Software in the development or marketing of a competitive or compatible product. No right to use, print, copy or display the Software or Documentation, in whole or in part, is granted hereby except as expressly provided in this License.

. Licensee may make one (1) copy of the Software in a non-printed, machine-readable form for archival and back-up purposes only. In order to protect ADIC's trade secret and copyrights in the Software, Licensee agrees to reproduce and incorporate Licensee's trade secret or copyright notice in any copy or partial copy, and will maintain appropriate records of the location of such copy.

d. Transfer Rights. The Software will be installed initially on Licensee's Designated Computer(s) set forth in

Exhibit A. Licensee may thereafter transfer the Software to another one of its computers of the same machine architecture, provided that the Software is installed on one (1) Designated Computer at a time, b) is covered under a current maintenance support plan with ADIC, and c) provides ADIC with written notice thirty (30) days prior to the transfer. If Licensee transfers the Software to a machine of a different architecture, Licensee may be subject to a transfer fee.

e. US Government Rights

agrees that ADIC Software and documentation are provided as "Commercial Items" as defined at 48 CFR

2.101 and are being licensed to U.S. Government end users consistent with 48 CFR 12.212.

. If the Licensee is the United States government, Licensee understands and

Price and Payment

Licensee will make payment to ADIC for the Software license pursuant to those fees set forth in the agreement of the parties. The Licensee must pay any such fees within thirty (30) days of the date of ADIC's invoice.

Software Ownership and Protection

a. ADIC's Warranty . ADIC warrants that it is the owner of the Software and all portions thereof, except for any

embedded third party software for which ADIC holds a license that is not inconsistent with the license granted under this agreement, and that it has the right to modify the Software and to grant this License for its use.

b. Title to Software

proprietary to ADIC and title thereto remains in ADIC. All applicable rights to patents, copyrights, trademarks, trade secrets or other proprietary rights in the Software and any modifications made at Licensee's request are and will remain in ADIC.

c. Restrictions

i. sell, sublicense, transfer, publish, disclose, display , provide access via a network or otherwise make or

allow available the Software or any copy thereof, in any form whatsoever, to others;

ii. remove, obscure, or alter any copyright, trade secret, trademark, patent or other proprietary rights

notice affixed to or displayed on the Software or Documentation or affixed to or printed on any of its factory packaging;

iii. modify, merge with other programs or translate any portion of the Software into any other assembly or

foreign language; and

iv. reverse-assemble, reverse-compile or attempt to derive a source code equivalent of the Software.

e. Protections

a manner consistent with ADIC's rights therein and to take appropriate action to satisfy its obligations in this Article by instruction or agreement with its employees, agents, subcontractors or others who are permitted access to the Software. All programs or copies developed by or for the Licensee in violation of this License, including translations, compilations, partial copies with modifications and up-dated works, are the property of ADIC.

f. Responsibility

or stored thereon. This responsibility includes protection of data from modification, destruction, or disclosure, and for the accuracy and integrity of the results from improper use. ADIC assumes no responsibility for Licensee's negligence or failure to protect data from modification, destruction, or disclosure.

. The Software and all copies thereof (except for any embedded third party software) are

. Licensee will not itself or permit others to:

. Licensee agrees to secure and protect the Software, the Documentation and copies thereof in

. Licensee has sole responsibility for use of the program and any information entered, used,

iv Advanced Digital Information Corporation Software Licenses Agreement

Installation

Installation. Licensee will, at its own expense, ensure that the installation site conforms to the requirements of the Software and, at its own expense, prepare and maintain the environmental conditions at the installation site in accordance with the requirements of the relevant hardware manufacturer. ADIC will be responsible for reasonable support during the initial installation process.

Use and Training

Licensee will limit the use of the Software to those individuals who have been appropriately trained. ADIC will make training for the Software available to Licensee pursuant to its standard training procedures. Unless otherwise mutually agreed, any additional training will be provided at ADIC's Englewood, Colorado facility at ADIC's then current rates.

Warranty and Warranty Servicing

a. Warranty. ADIC warrants that for a period of ninety (90) days from installation the Software will conform to

all substantial operational features in ADIC's current published specifications and will be free of defects which substantially affect performance of the Software. ADIC does not warrant that the Software will meet the Licensee’s requirements or that the operation of the Software will be uninterrupted or error free.

b. Compatibility

common computer operating systems, however, ADIC does not warrant that the Software is compatible with the current releases of all operating systems, nor that the Software, including any future Releases, will be made compatible with new releases of the operating system within a specified amount of time, or at all. At Licensee's request, ADIC will notify Licensee of the version level of the operating system with which the current version of the Software is intended to be compatible, and the version level of operating systems for which a subsequent release of the Software is intended to be compatible.

c. Warranty Servicing

the Software of Licensee’s claim of any defect. If the Software is found defective by ADIC, ADIC’s sole obligation under this warranty is for ADIC, at its option, either to correct, in a manner consistent with ADIC's regular support practices, any defect in the Software or to accept the return of the Software. Where Software is returned for claims made during the warranty period, Licensee will be provided a full refund for the Software and related products sold under the same Purchase Agreement.

d. Warranty Exclusions

modifications to the Software. Licensee will pay ADIC for corrections necessitated by difficulties or defects traceable to Licensee's errors or system changes in accordance with ADIC's then current standard time and material charges.

e. Warranty Disclaimer

MAKES NO WARRANTIES, EXPRESS OR IMPLIED, FOR THE SOFTWARE, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

f. Third Party Warranties

demonstrating, promoting or delivering the Software subject to this License makes any warranty whatsoever. All limit ations and exclusions of warranty, disclaimers of warranty, limitations of damages and remedies are as set forth hereinabove and the terms of all portions of this License apply to such reseller or distributor to the full extent applicable to ADIC.

. It is the intent of ADIC to provide Software which is compatible with the current releases of

. The Licensee must notify ADIC in writing, within ninety (90) days after installation of

. This warranty is made void if the Licensee or any other third party makes any

. EXCEPT FOR THE EXPRESS LIMITED WARRANTY STATED ABOVE, ADIC

. No reseller or distributor of the Software who may have participated in offering,

Maintenance

Maintenance, enhancements and Updates for the Software are not covered under this License. If desired by the Licensee, such services must be provided for under separate agreement.

StorNext File System and Storage Manager Installation Guide v

Infringement Indemnification

a. ADIC will defend, indemnify, save, and hold Licensee harmless against claims, demands, liability,

damages, and judgments which are finally adjudicated, including attorney's fees and court costs arising or resulting directly from any claim, suit or litigation brought against Licensee based on infringement of any U. S. patent or copyright by the Software (except that indemnification does not apply to any third party software which may be embedded therein), provided, however, that such indemnity is conditioned upon receipt by ADIC of prompt notification in writing of such claim and that Licensee provides continuing information and reasonable assistance for the defense and settlement of any claim. ADIC will retain attorneys, as deemed necessary, and conduct the defense and settlement of such claim. ADIC may, at its own expense and at its option, either (1) procure for Licensee the right to continue using the Software, or (2) replace the same with non-infringing software, or (3) modify the Software so that it becomes noninfringing provided such modified intellectual property will reasonably meet Licensee's needs.

b. Upon failure of (1), (2) or (3) above, despite the reasonable efforts of ADIC, Licensee may terminate this

License only with respect to the Software adversely affected by such action or claim. Upon such termination ADIC will promptly refund to Licensee any License Fees paid and other payments made for the adversely affected Software. ADIC may deduct from the refund a fair market value for usage, which will be a pro rata share of the License charge for the time period used, assuming a three (3) year straight line depreciation with no salvage value.

c. Notwithstanding the foregoing ADIC has no liability if any such claim or suit is based upon or arises out of:

1) alterations of the Software by Licensee or any third party; 2) Licensee's failure to install updated Software provided by ADIC for avoiding such infringement; 3) use of the Software in combination with apparatus or software not furnished by ADIC; 4) use of the Software in a manner for which it was neither designed nor contemplated; 5) third party software embedded in the Software; 6) Software modified by ADIC for Licensee in accordance with Licensee's specifications or requests; or 7) a patent, trademark or copyright in which Licensee or any of its affiliates or subsidiaries has a direct or indirect interest by license or otherwise.

Term and Termination

a. Term. The term of this License is perpetual, unless terminated by ADIC as provided herein. b. Termination. This License commences on the Effective Date and will continue in perpetuity unless

Licensee fails to comply with any of the material conditions of this License. ADIC may, after allowing Licensee a reasonable time to cure its default, terminate this License upon written notice to the Licensee. Within thirty (30) days after termination of this License, Licensee will certify, in writing, to ADIC, that Licensee has discontinued the use of all Software; and either destroyed or, at ADIC’s election, returned to ADIC the original and all copies of the Software and Documentation in any form maintained by Licensee.

c. Termination for Cause

breach and the basis for immediate termination of this License.

d. Termination upon Insolvency

indefinitely suspends its business; (ii) becomes subject to any bankruptcy or insolvency proceeding under governmental statute; or (iii) becomes insolvent or becomes subject to direct control by a trustee, receiver or similar authority.

e. Remedies upon Termination

immediate possession of the Software, Documentation, and all copies wherever located, without demand or notice. Termination of this License is in addition to and not in lieu of any equitable or legal remedies available to ADIC.

vi Advanced Digital Information Corporation Software Licenses Agreement

. A violation of any provision of Paragraph 3. above will be deemed a material

. This License may be terminated by ADIC if the Licensee (i) terminates or

. If this License is terminated by ADIC, ADIC will have the right to take

Notices and Correspondence

All notices and correspondence sent by one party to the other in all matters will be sent to the addresses listed in the initial paragraph hereof, except as otherwise requested in writing.

DISCLAIMER AND LIMITATION OF LIABILITY

THE LICENSEE HAS THE SOLE RESPONSIBILITY FOR THE ADEQUATE PROTECTION AND BACK-UP OF ITS DATA USED IN CONNECTION WITH THE SOFTWARE. IN NO EVENT WILL ADIC BE LIABLE FOR SPECIAL, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, RERUN TIME, INACCURATE INPUT OR WORK DELAYS, OR ANY PERSONAL OR PROPERTY DAMAGE ARISING OUT OF OR IN CONNECTION WITH THIS LICENSE OR THE USE, PERFORMANCE OR NON-PERFORMANCE OF THE SOFTWARE, WHETHER IN ACTION, IN CONTRACT, OR TORT INCLUDING NEGLIGENCE, EVEN IF ADIC KNEW, SHOULD HAVE KNOWN OR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ADIC's LIABILITY FOR DAMAGES HEREUNDER WILL IN NO EVENT EXCEED THE AMOUNT OF FEES PAID BY LICENSEE UNDER THIS LICENSE.

General

a. No Assignment. This License is not assignable. None of the Software or Documentation may be

sublicensed, assigned, or transferred to any other party without ADIC’s prior written consent. Any effort contradictory with this is null and void.

b. Modification

Licensee and ADIC.

c. Governing Law

parties, including all applications for injunctive relief, must be conducted before a court of competent jurisdiction within King County, Washington, USA and both parties consent to personal jurisdiction of such court. If any of the provisions of this License are held to be invalid under any applicable statute or law, they are, to that extent, deemed omitted.

d. Enforcement Costs

out of any dispute under this Agreement will be entitled to recover reasonable attorneys’ fees and costs from the other party.

e. Limitations on Actions

may not be brought by either party more than one (1) year after the cause of action has accrued, except that an action for nonpayment may be brought within four (4) years after the last payment date.

. This License or any Exhibit hereto can only be modified by a written agreement executed by

. The laws of the state of Washington will govern this license. All litigation between the

. The party prevailing in any litigation or legal proceeding, including arbitration, arising

. Any action, regardless of form, arising out of the transactions under this License,

Entirety

Licensee acknowledges that it has read this Software License, understands it, and agrees to be bound by its terms and conditions. Further, Licensee agrees that this is the complete and exclusive statement of the agreement between the parties and supersedes all proposals or prior agreements, oral or written and all other communications between the parties relating to the subject matter of this License. Any variance from the terms and conditions of this License or any supplement in any Licensee purchase order or other written notification or agreement will be of no effect.

StorNext File System and Storage Manager Installation Guide vii

viii Advanced Digital Information Corporation Software Licenses Agreement

Contents

Advanced Digital Information Corporation Software Licenses Agreement . . . . . . . . . . . iii

1 Introduction 1

Who Should Read this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

How This Book is Organized. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Explanation of Symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 Installing StorNext 5

Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Windows Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Red Hat Linux Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

SuSE Linux Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Sun Solaris Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

HP-UX Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

IBM AIX Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

SGI IRIX Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

RAM and Hard Disk Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2TB LUN Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Label Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Using the Optional Pre-Installation Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Running the Pre-Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

StorNext Support Directory Location Recommendations . . . . . . . . . . . . . . . . . . . . 15

Installing StorNext Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3 Configuring StorNext 21

Using the Configuration Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Step 1: Entering a License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Step 2: Adding File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

StorNext File System and Storage Manager Installation Guide ix

Step 3: Adding a Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Adding a SCSI Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Adding an ACSLS Network Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Adding a DAS Network Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Adding a Vault Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Step 4: Adding a Tape Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Step 5: Adding Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Step 6: Adding Secondary Storage Disks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Step 7: Adding a Storage Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Step 8: E-mail Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

4 Installing StorNext Client Software 71

Downloading the Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Installing StorNext Client Software on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Installing StorNext Client Software on Red Hat Linux. . . . . . . . . . . . . . . . . . . . . . . . . . 91

Installing StorNext Client Software on SuSE Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Installing StorNext Client Software on Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Installing StorNext Client Software on HP-UX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Installing StorNext Client Software on IBM AIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Installing StorNext Client Software on SGI IRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5 Customer Assistance 97

StorNext Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

ADIC Technical Assistance Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Glossary 99

x Contents

Introduction

StorNext is data management software that enables customers to complete projects faster and confidently store more data at a lower cost. Used in the world's most demanding environments, StorNext is the standard for high performance shared workflow operations and multi-tier archives. StorNext consists of two components: StorNext File System (SNFS) a high performance data sharing software, and StorNext Storage Manager (SNSM) the intelligent, policy based data mover.

StorNext File System streamlines processes and facilitates faster job completion by enabling multiple business applications to work from a single, consolidated data set. Using SNFS, applications running on different operating systems (Windows, Linux, UNIX, and Mac OS X) can simultaneously access and modify files on a common, high speed SAN storage pool. This centralized storage solution eliminates slow LAN based file transfers between workstations and dramatically reduces delays caused by single client failures. With SNFS, any server can access files and pick up processing requirements of a failed system to continue operations.

StorNext Storage Manager enhances the StorNext solution by reducing the cost of long term data retention, without sacrificing accessibility. SNSM sits on top of SNFS and utilizes intelligent data movers to transparently locate data on multiple tiers of storage. This enables customers to store more files at a lower cost, without having to reconfigure applications to retrieve data from disparate locations. Instead, applications continue to access files normally and SNSM automatically handles data access – regardless of where the file resides. As data movement occurs, SNSM also performs a variety of data protection services to guarantee that data is safeguarded both onsite and offsite.

This guide describes how to install the StorNext product. The StorNext installation process includes steps for adding a file system, so you do not need to separately install the StorNext FS product, whose installation is described in a separate guide.

Who Should Read this Book

This guide is intended for system administrators and service personnel who want to install both the StorNext Storage Manager and StorNext File System. If you are installing only the StorNext File System, refer to the StorNext File System Installation Guide.

StorNext File System and Storage Manager Installation Guide 1

How This Book is Organized

This book contains the following chapters.

• Chapter 1: the guide is organized, and introduces symbols and document conventions used in the guide.

• Chapter 2: Installing StorNext — Provides instructions for installing StorNext on servers.

• Chapter 3: software.

• Chapter 4: Installing StorNext Client Software — Describes how to install and configure StorNext software on a client machine.

• Chapter 5: Customer Assistance — Provides information on different types of customer assistance available for StorNext.

Introduction — Provides information on the audience for this guide, explains how

Configuring StorNext — Describes how to configure StorNext after installing the

Explanation of Symbols

The following symbols indicate important information.

Symbol Description Definition Consequence

WARNING: Advises you to take or avoid

a specified action

CAUTION: Advises you to take or avoid

a specified action

Failure to take or avoid this action could result in physical harm to the user or hardware

Failure to take or avoid this action could result in loss of data

NOTE: Indicates important

information that helps you make better use of the software

No hazardous or damaging consequences

Conventions

The conventions used throughout this book are listed below

Convention Example

For all UNIX-based commands, the # prompt is implied, although it is not shown.

Screen text, file names, program names, and commands are in Courier font.

2 How This Book is Organized

/usr/cvfs/bin/cvlabel -l

is the same as

# /usr/cvfs/bin/cvlabel -l

mkdir -p <mount point>

Site-specific variables are enclosed wi th i n brackets < > .

Pressing Return or Enter after each command is assumed.

chmod 777 <mount point>

A menu name with an arrow refers to a sequence of menus.

Programs > StorNext File System > Help

StorNext File System and Storage Manager Installation Guide 3

4 Conventions

Installing StorNext

You can install the StorNext software on a server. When you have successfully installed the StorNext software, use the Configuration Wizard to configure the software. (After initial configuration, you can use the StorNext GUI to change your configuration parameters.) You are then ready to use the StorNext software.

You can also run the StorNext software on a client machine by downloading the client files from the server and then installing them on your client. You can install client files on machines that use an SGI IRIX, Solaris, Linux, IBM AIX, HP-UX, or Windows (2000, 2003 Server, and XP) operating system.

This chapter includes:

• Installation Requirements

• 2TB LUN Requirements

• Using the Optional Pre-Installation Configuration on page 13

• Running the Pre-Installation Script

on page 5

on page 11.

on page 14

Installation Requirements

Before installing StorNext on any machine, verify that you meet the installation prerequisites described in this section. This section contains installation requirements for the following supported operating systems:

• Windows Prerequisites

• R

ed Hat Linux Prerequisites on page 6

• SuSE Linux

• Sun Solaris Prerequisites

• HP-UX Prerequisites on page 9

• IBM AIX Prerequisites

• SGI IRIX Prerequisites

• RAM and Hard Disk Requirements on page 11

Prerequisites on page 8

on page 6

on page 9

on page 10

StorNext File System and Storage Manager Installation Guide 5

Windows Prerequisites

Before installing StorNext on a Windows server, verify that the following installation prerequisites have been met.

A Windows machine that will be used as a StorNext server must meet these requirements.

• 512 MB of RAM minimum for the first two file systems. Each subsequent file system (up to eight total) either passive or active, must have an additional 256 MB of RAM minimum.

• StorNext requires 350 MB of hard disk space for binaries, documentation, configuration, and

log files. If internal metadata is used, approximately 2.5 GB of additional hard disk space is required per 1M files.

In addition, each StorNext-supported Windows platform must meet these service pack requirements.

• Windows 2000 — Service Pack 4

• Windows 2003 Server — Enterprise Edition SP1

• Windows XP — Service Pack 2

Red Hat Linux Prerequisites

Before installing StorNext on a Red Hat Linux machine, verify that the following installation prerequisites have been met.

• Kernel Requirements - To run StorNext on Red Hat Linux, you must use the following kernels:

• For Red Hat 3: 2.4.21 - 37.EL (Update 6); 2.4.21 - 40.EL (Update 7)

• For Red Hat 4: 2.6.9 - 22 (Update 2); 2.6.9 - 34.EL (Update 3)

To verify the kernel information for Red Hat Enterprise Advanced Server, type: uname -a The following is similar to what is shown:

Linux APU 2.4.21-27.EL # 1SMP <date><platform><compiler>

StorNext is distributed as a loadable kernel module. To build the kernel module, the Red Hat Linux software must be installed with the Linux kernel source and tools, including compilers.

To build and install the StorNext modules, a symbolic link must exist in the /usr/src directory that points to the kernel source for the running kernel.

Use this procedure to view the symbolic links.

1 Change to the /usr/src directory. Type:

cd /usr/src

2 To view the symbolic links type:

ls -l

For the Linux 2.4.21-27.EL kernel, the symbolic link is shown as:

linux-2.4 > linux-2.4.21-27.EL

6 Installation Requirements

3 Make sure the symbolic link is pointing to the correct kernel.

• If the symbolic link shows a kernel in the specified range (2.4.21.EL to 2.4.27.EL,) continue with the next task.

• If the symbolic link is either missing or pointing to the source of a different kernel, the StorNext

modules will either not install or not function.

• Mapping LUNs - Before installing StorNext, it is necessary to correctly map LUNs in the customer SAN.

A LUN is assigned to each device (target) that is visible locally and over the SAN. The process of LUN mapping depends on many factors, including the operating system on which StorNext is running on, the type of SCSI card installed on the machine, and the type of FC HBA installed on the machine.

For each HBA, check the vendor documentation to determine the operating system files th at must be configured to correctly map LUNs to devices over the SAN. Configure the operating system file as indicated below:

• Edit the /etc/sysconfig/rawdevices file and use the rpm and insmod commands to install the specific Fibre Channel HBA driver.

For additional requirements, see 2TB LUN Requirements For assistance configuring the operating system file, contact ATAC. Refer to Customer

Assistance on page 97.

• Multiple LUN support - If your file system storage device uses non-zero SCSI Logical Unit Numbers (LUNs), configure the Red Hat Linux kernel to scan for all SCSI LUNs. By default, Red Hat Linux only scans for LUN 0. Use this procedure to configure the Linux kernel for multiple LUNs:

1 Change directories. Type:

cd /etc

2 In the /etc/modules.conf file, add the following line:

options scsi_mod max_scsi_luns=nLUNs

where nLUNs equals the number of LUNs required by your file system storage device.

For example:

on page 11.

alias parport_lowlevel parport_pc alias scsi_hostadapter aic7xxx alias eth0 eepro100 alias eth1 e1000 alias scsi_hostadapter1 qla2300 options scsi_mod options scsi_mod max_scsi_luns=128

StorNext File System and Storage Manager Installation Guide 7

3 Create a new initial RAM disk file by using the mkinitrd command.

For example:

• For IA64:

cd /boot/efi/efi/redhat

mkinitrd -f initrd-2.4.21-27.EL.img 2.4.21-27.EL

• For x86:

cd /boot

mkinitrd -f initrd-2.4.21-27.EL.img 2.4.21-27.EL

4 Reboot the machine.

SuSE Linux Prerequisites

Before installing StorNext on a SuSE Linux machine, verify that the following installation prerequisites have been met.

• Kernel Requirements - Before installing StorNext on a SuSE Linux machine (either client or server), verify that the required kernels are loaded: 2.6.5 - 7.191 (SP2); 2.6.5-7.244-SMP (SP3 )

1 Run the rpm command. Type:

rpm -qf /boot/vmlinuz

The command output should display one of these kernels:

• For uniprocessor systems:

k_delft-2.6.5-7.191

• For multiprocessor systems:

k_smp-2.6.5-7.191

2 Do one of the following:

• If the correct kernel is shown, continue with th e installation.

• If an incorrect kernel is shown, install the correct kernel and repeat Step 1

• Mapping LUNs - Before installing StorNext, it is necessary to correctly map LUNs in the customer SAN.

A LUN is assigned to each device (target) that is visible locally and over the SAN. The process of LUN mapping depends on many factors, including the operating system on which StorNext is running, the type of SCSI card installed on the machine, and the type of FC HBA installed on the machine.

For each HBA, check the vendor documentation to determine the operating system files that must be configured to correctly map LUNs to devices over the SAN. Configure the operating system file as indicated below:

•Edit the /etc/raw file and use the rpm and insmod commands to install the specific Fibre Channel HBA driver.

For additional requirements, see 2TB LUN Requirements For assistance configuring the operating system file, contact ATAC. Refer to Customer

Assistance on page 97.

8 Installation Requirements

on page 11.

Sun Solaris Prerequisites

Before installing StorNext on a Solaris machine, verify that the following installation prerequisites have been met. StorNext supports Solaris 9 and 10 only.

• Mapping LUNs - Before installing StorNext, it is necessary to correctly map LUNs in the customer SAN.

A LUN is assigned to each device (target) that is visible locally and over the SAN. The process of LUN mapping depends on many factors, including the operating system on which StorNext is running, the type of SCSI card installed on the machine, and the type of FC HBA installed on the machine.

For each HBA, check the vendor documentation to determine the operating system files that must be configured to correctly map LUNs to devices over the SAN. Configure the operating system files as indicated below:

•Edit the sd.conf, st.conf, and the sgen.conf files and use the pkgadd command to install the specific Fibre Channel HBA driver.

For additional requirements, see 2TB LUN Requirements For assistance configuring the operating system files, contact ATAC. Refer to Customer

Assistance on page 97.

on page 11.

HP-UX Prerequisites

Before installing StorNext on an HP-UX machine, verify that the following installation prerequisite has been met. StorNext supports HP-UX 11 iv2.

• Mapping LUNs - Before installing StorNext, it is necessary to correctly map Logical Unit Numbers (LUNs) in the customer SAN.

A LUN is assigned to each device (target) that is visible locally and over the SAN. The process of LUN mapping depends on many factors, including the operating system on which StorNext is running, the type of SCSI card installed on the machine, and the type of FC Host Bus Adaptor (HBA) installed on the machine.

For each HBA, check the vendor documentation to determine the operating system files that must be configured to correctly map LUNs to devices over the SAN.

For additional requirements, see 2TB LUN Requirements For assistance configuring the operating system files, contact the ADIC Technical Assistance

Center (ATAC). Refer to Customer Assistance

• 64-bit Inodes - StorNext supports only 64-bit inodes for installations of the software on the HP-UX operating system on IA64 and PA-RISC architectures.

on page 97.

on page 11.

StorNext File System and Storage Manager Installation Guide 9

IBM AIX Prerequisites

Before installing StorNext on an AIX machine, verify that the following installation prerequisite has been met. StorNext supports AIX 5.2 and 5.3 only.

• Mapping LUNs - Before installing StorNext, it is necessary to correctly map Logical Unit Numbers (LUNs) in the customer SAN.

A LUN is assigned to each device (target) that is visible locally and over the SAN. The process of LUN mapping depends on many factors, including the operating system on which StorNext is running, the type of SCSI card installed on the machine, and the type of FC Host Bus Adaptor (HBA) installed on the machine.

For each HBA, check the vendor documentation to determine the operating system files that must be configured to correctly map LUNs to devices over the SAN.

For additional requirements, see 2TB LUN Requirements For assistance configuring the operating system files, contact the ADIC Technical Assistance

Center (ATAC). Refer to Customer Assistance on page 97.

on page 11.

SGI IRIX Prerequisites

Before installing StorNext on an IRIX machine, verify that the following installation prerequisites have been met.

• 64-bit Inodes - StorNext supports only 64-bit inodes for software installations on the IRIX operating system.

• Mapping LUNs - Before installing StorNext, it is necessary to correctly map LUNs in the customer SAN.

A LUN is assigned to each device (target) that is visible locally and over the SAN. The process of LUN mapping depends on many factors, including the operating system on which StorNext is running, the type of SCSI card installed on the machine, and the type of FC HBA installed on the machine.

For each HBA, check the vendor documentation to determine the operating system files that must be configured to correctly map LUNs to devices over the SAN. Configure the operating system file as indicated below:

•Edit the /var/sysgen/master.d/qlfc file. For additional requirements, see 2TB LUN Requirements For assistance configuring the operating system file, contact ATAC. Refer to Customer

Assistance on page 97.

on page 11.

10 Installation Requirements

RAM and Hard Disk Requirements

The following are requirements for each StorNext mount.

• Client Memory - StorNext requires 512 MB of RAM minimum.

• Client Hard Disk - StorNext requires 200 MB of hard disk space for binaries, documentation,

configuration, and log files.

• Server Memory - For the first two file systems, a minimum of 512 MB of RAM for each file

system. Each subsequent file system (up to eight total) either passive or active, must have an additional 256 MB of RAM minimum.

• Server Hard Disk - Depending on file system activity, StorNext binaries, documentation,

configuration, and log files require up to 30 GB of local hard disk space. An additional 2GB of hard disk space is required per 1 million managed files.

2TB LUN Requirements

StorNext supports LUNs larger than 2TB. The level of support for this feature varies, depending on the operating system you are using:

• Full support for LUNs larger than 2TB

• Full support for LUNs larger than 2TB, with a specific label type required

• Support for only the first 2TB for LUNs larger than 2TB

• No support for LUNs larger than 2TB

Label Types

The type of label you use determines whether your system supports LUNs larger than 2TB. Even if your operating system provides support for LUNs larger than 2TB, you cannot use this feature if you apply the incorrect label type.

There are three label types:

•VTOC

•EFI

• sVTOC (or short VTOC)

Generally speaking, the VTOC label is for LUNs less than 2TB, while the EFI and sVTOC labels are used for LUNs greater than 2TB. However, in many cases, EFI labels can also be used for LUNs less than 2TB.

The following table summarizes the operating system levels for the possible LUN sizes, the level of support, and the type of label you should use for the LUN size you want to use. Where there are multiple label types listed, the preferred label type is listed first.

StorNext File System and Storage Manager Installation Guide 11

Table 1

Support Level

Full support of LUNs larger than 2TB

Full support of LUNs larger than 2TB, with specific label requirements

Support for only the first 2TB of LUNs larger than 2TB

No support for LUNs larger than 2TB

Operating System

IBM AIX Linux 2.6 kernel VTOC or EFI VTOC or EFI EFI or sVTOC Windows Server

2003 SP1 Apple Xsan 1.3

on OS X Tiger Solaris 10

Update 2

Apple Xsan 1.2 VTOC only VTOC only sVTOC only Apple Xsan 1.3

on OS X Panther HP-UX VTOC or EFI VTOC or EFI sVTOC or EFI Windows XP or

Windows 2000 SGI IRIX VTOC only VTOC only Not supported Linux 2.4 kernel VTOC or EFI VTOC or EFI Not supported Solaris 9 with

the “Big LUN” patch

Label Type For LUNs Less Than 1TB

VTOC or EFI VTOC or EFI EFI or sVTOC

VTOC or EFI EFI only EFI only

VTOC or EFI VTOC or EFI sVTOC or EFI

VTOC or EFI EFI only Not supported

Label Type For LUNs Between 1-2TB

Label Type For LUNs Larger Than 2TB

Solaris 10 with no patches

Solaris 9 with no patches

a. AIX is limited to LUNs that are 2.2TB or smaller.

VTOC or EFI EFI only Not supported

VTOC only Not supported Not supported

12 2TB LUN Requirements

Using the Optional Pre-Installation Configuration

StorNext requires the tdlm and www user accounts to exist in the passwd file, and the adic group account to be in the group file. StorNext automatically creates these accounts during the installation process, but if you prefer you can create them manually before running the installation.

• If you want the system utility to create the accounts, skip this section and continue with

Running the Pre-Installation Script

• If you prefer to manually add these accounts, use this procedure. You must perform this

procedure on each machine where the StorNext software is installed. After completing this procedure, continue with Running the Pre-Installation Script on page 14.

1 Add the following user accounts tdlm and www to your metadata server.

The following example shows sample values. You can specify any user ID or group ID you wish.

Username UserID Grou pID Login Shell Home Directory

tdlm 100 100 /bin/sh /usr/adic www 101 100 /bin/sh /usr/adic/www

2 Add the group account adic.

Group Name GroupID Members List

on page 14.

adic 100 root, tdlm, www

StorNext File System and Storage Manager Installation Guide 13

Running the Pre-Installation Script

StorNext includes a script called snPreInstall that you can run before installing the software. The output of this script indicates whether your system meets the minimum disk space requirements required for the installation.

If your local system does not have sufficient disk space for the software installation, the script will warn you so you can add more disk space before proceeding with the installation.

Note

Minimum disk space amounts (in MB) are provided for the following directories:

• Database

• Journal

• Mapping

• Metadata

• Backup

When you run the snPreInstall script, you must provide answers about your system configuration so the script can determine space requirements. You will be asked to do the following:

• Specify whether you are performing a StorNext upgrade or a new installation

• Estimate the maximum number of additional directories (in millions) you anticipate

• Estimate the approximate number of additional files (in millions) you anticipate

• Enter the number of copies for each file

• Enter the number of versions you plan to keep for each file

Note

The snPreInstall script ignores all unmounted file systems. Only mounted local file systems are considered when the script runs and makes its calculations. Before running the snPreInstall script, be sure to mount all local file systems you want the script to consider.

If you are performing an upgrade, the file systems that currently contain existing TSM support directories will be reported. Additionally, you will be asked about other local file systems to include when calculating space requirements.

If you are performing a new installation, you will be asked whether all local file systems should be included when calculating space requirements.

When performing either an upgrade or new installation, you can eliminate from consideration file systems you do not want used for StorNext support directories.

Based on the information you provide about your system, the script will calculate space requirements. If the script says you have sufficient space, you can proceed with the installation. If you do not have sufficient space, you must add more disk space before installing the StorNext software.

14 Running the Pre-Installation Script

Script output might look similar to this:

Database dir space required: 1686 MB Journal dir space required: 33 MB Mapping dir space required: 3540 MB Metadata dir space required: 4291 MB Backup dir space required: 2791 MB (On a managed file system)

StorNext Support Directory Location Recommendations

The snPreInstall script also provides recommendations for StorNext support directory locations. The recommendations are made with the following considerations:

1 In descending order (from greatest to least,) the order of space required is Database, Metadata,

Backup, Mapping, and Journal.

2 The Database and Journal should be on separate file systems for integrity reasons. 3 The Journal and Metadata should be on separate file systems for performance reasons. Both file

systems will have lots of head movement during normal operation.

4 The Database and Metadata should be on separate file systems for performance reasons. Both

file systems will have lots of head movement during normal operation.

5 The Mapping and Metadata should be on separate file systems for performance reasons (during

mapping operations).

6 The Backup directory should be on the largest of the managed file systems.

Note

ADIC recommends moving directories through the installation menu (option 1, Installation Configuration) rather than moving them manually.

StorNext File System and Storage Manager Installation Guide 15

Installing StorNext Software

Use this procedure to install StorNext software. The installation process loads both server and client files on your machine.

1 Designate one machine as the server. 2 Load the StorNext CD appropriate for your operating system. 3 Open the StorNext folder. 4 Launch the executable program install.stornext.

The StorNext Install Main Menu is shown.

Figure 1 StorNext Install Main Menu

Stornext Install 2.8.0 MAIN MENU

1) Installation Configuration

2) Install stornext

3) Show Status

4) Quit

Enter your choice <2>:

StorNext defaults to option 2) Install stornext.

5 Type 1 to display a list of parameters that can be modified.

The following menu is shown. By default, the software is installed into the directory containing the greatest amount of space (in this example, <disk1>).

16 Installing StorNext Software

Figure 2 StorNext Configuration Menu

Stornext 2.8.0 Configuration Menu

__VALUE_________________ __DESCRIPTION___________

1) /home/adic/perl Perl installation directory

2) /home/adic/docs Docs installation directory

3) /home/adic/PCL Pcl installation directory

4) /home/adic/database Dbm installation directory

5) /home/adic/SRVCLOG Srvclog installation directory

6) /home/adic/PSE Pse installation directory

7) /home/adic/MSM Media Manager installation directory

8) /home/adic/TSM Tertiary Manager installation directory

9) /home/adic/TCM Trashcan Manager installation directory

10) /home/adic/www GUI installation directory

11) /home/adic/apache Web installation directory

12) /usr/cvfs Disk Manager installation directory

13) /home/adic/database_meta Metadumps directory

14) /home/adic/mapping_dir TSM mapping directory

15) /home/adic/database_jnl Database journal directory

16) LTO Default media type

17) LTO Backup media type

Enter number to modify or hit <RETURN> to continue install

6 Type the parameter number to modify the default parameters.

If you do not need to modify the parameters, then skip this step and go to Step 8

CAUTION

parameter numbers 16 and 17 to match the media type that is located in your library.

For mixed media or multiple libraries, you must change the parameter numbers to match the media type that you use as your primary backup.

For increased reliability, install the database journal directory (database_jnl) on a disk that is different from the one on which the database installation directory is stored.

To maximize performance, place all four of the following support directories on different file systems: database, database_jnl, metadumps, and mapping_dir. If this is not possible, ADIC recommends separating at least the first three support directories.

7 When you are satisfied with the parameter settings of the installation configuration, press ENTER

to return to return to the StorNext Install Main Menu and continue the install.

StorNext File System and Storage Manager Installation Guide 17

If you do not use LTO media in your library, you must change

Stornext INSTALL 2.8.0 MAIN MENU

1) Installation Configuration

2) Install stornext

3) Show Status

4) Quit

Enter your choice <2>:

8 Type 2 or press ENTER to install the StorNext software.

• If you have set up your database and database journal to install on the same file system, the following warning is shown:

The /home/adic/database and /home/adic/database_jnl are defined to be on the same file system. It is recommended that they reside on different file systems. To change the values, answer 'No' to return to the configuration menu.

Database journal directory => /home/adic/database_jnl

Dbm installation directory => /home/adic/database

Do you wish to keep these settings (quit, no or <yes>)?

•Select quit, no, or yes.

• If you select quit, you will exit the StorNext Installation

• If you select no, you will return to the StorNext Configuration Menu (Figure 2 page 17)

• If you select yes, you will proceed with the StorNext Install

• If you have set up your database and database journal to install on the separate file systems, the StorNext Status Install Menu (Figure 3 component-level status. As the installation progresses, the status menu updates and shows steps as Complete.

18 Installing StorNext Software

on page 19) is shown and lists fourteen steps of

Figure 3 StorNext Install Status

Stornext Install 2.8.0 Status

1) Install Pre-Install 2.8.0(9) Complete

2) Install perl 5.8.3_3.0.0(16) Complete

3) Install docs 2.8.0(7) Complete

4) Install PCL 1.1.0(3) Complete

5) Install database 5.9.25.50_4.1.0(2) Working / unbundle software Complete create database Working start software To do

6) Install SRVCLOG 2.1.0(2) To do

7) Install PSE 1.1.0(3) To do

8) Install MSM 2.8.0(13) To do

9) Install TSM 2.8.0(11) To do

10) Install TCM 2.8.0(9) To do

11) Install www 2.8.0(8) To do

12) Install apache 2.0.54_3.0.0(17) To do

13) Install DSM 2.8.0(9) To do

14) Install Post-Install 2.8.0(9) To do

After exiting the install.stornext utility, the following information is shown

When the installation has completed you will point your browser at the following address and port# to access the stornext home page:

http://snsan.adic.com:81

Please make a note of this information.

Note

Note the machine name and port number from the above screen. You will need this information to access the StorNext GUI. If your operating system requires a restart, you will be notified that you must reboot the machine.

9 When the installation process is complete, press ENTER to return to the Install Main Menu

(Figure 1

on page 16).

10 Type 3 to review the screen that displays the component-level status of the StorNext installation

(Figure 3

on page 19).

11 Type 4 to quit the installation process and exit the menu.

StorNext File System and Storage Manager Installation Guide 19

20 Installing StorNext Software

+ 84 hidden pages

ADIC Webcam 2.8 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Advanced Digital Information Corporation Software Licenses Agreement

Introduction

Who Should Read this Book

How This Book is Organized

Explanation of Symbols

Conventions

Installing StorNext

Installation Requirements

Windows Prerequisites

Red Hat Linux Prerequisites

SuSE Linux Prerequisites

Sun Solaris Prerequisites

HP-UX Prerequisites

IBM AIX Prerequisites

SGI IRIX Prerequisites

RAM and Hard Disk Requirements

2TB LUN Requirements

Label Types

Using the Optional Pre-Installation Configuration

Running the Pre-Installation Script

StorNext Support Directory Location Recommendations

Installing StorNext Software