Adic Stornext 2.7 System Administrator Guide: Advanced Digital Information Corporation

Administrator Guide
2.7 System ADIC StorNext

ADVANCED DIGITAL INFORMATION CORPORATION
www.adic.com
Copyright 2003 - 2006 ADIC The information contained in this document is subject to change without notice. This document contains proprietary information which is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without prior written consent of ADIC. 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. All trademarks within this document are the property of their respective owners. Copyright 2003 - 2006 ADIC EuropeTM All rights reserved. No part of this document may be copied or reproduced in any form or by any means, without prior written permission of ADIC Europe, ZAC des Basses Auges, 1 rue Alfred de Vigny, 78112 Fourqueux, France. ADIC Europe assumes no responsibility for any errors that may appear in this document, and retains the right to make changes to these specifications and descriptions at any time, without notice. This publication may describe designs for which patents are pending, or have been granted. By publishing this information, ADIC Europe conveys no license under any patent or any other right. ADIC Europe 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 Europe reserves the right to revise or change this publication without obligation on the part of ADIC Europe to notify any person or organization of such revision of change. Every effort has been made to acknowledge trademarks and their owners. Trademarked names are used solely for identification or exemplary purposes: any omissions are unintentional. ADIC is a registered trademark and ADIC Europe is a trademark of Advanced Digital Information Corporation. ADIC USA 11431 Willows Rd, NE Tel.: 1-425-881-8004 Fax: 1-425-881-2296 ATAC: 1-800-827-3822 http://www.adic.com ADIC Europe ZAC des Basses Auges 1, rue Alfred de Vigny 78112 Fourqueux, France Tel.: 33-1-30-87-53-53 Fax: 33-1-30-87-53-01 ADIC Germany Beteiligungs GmbH, KG Eschenstrae 3 89558 Bhmenkirch, Germany Tel.: 49-7332-83-333 Fax: 49-0-7332-83-135
Published: February 2006
Document Number: 6-00362-05 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") Company: _________________________________________________ Located at: ________________________________________________
_________________________________________________ _________________________________________________
(Referred to as Licensee")
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) means that computer equipment, identified to ADIC in Exhibit A by serial number, upon which the Software is installed. Documentation means ADIC provided materials related to the Software, including, but not limited to operator and user manuals, training materials, guides, listings, specifications, or other written documentation. "Release" means a modification to the Software that does not change ADIC's base version number, but may add functionality. New Releases are provided to the Licensee at no charge when Licensee maintains a current Software Maintenance Agreement with ADIC. Software means only the current version of those software products specified in Exhibit A hereto, in object code form only, and the Documentation provided by ADIC in connection therewith or any portions thereof, and any subsequent Releases. "Upgrade" means a modification to the Software that adds significant features and/or functionality and causes a change in ADIC's base version number. Upgrades may have a new initial License fee or upgrade charge associated with it.
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. Use. 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. Copying. 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.
b.
c.
StorNext System Administrator Guide
iii
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. US Government Rights. If the Licensee is the United States government, Licensee understands and 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.
e.
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. Title to Software. The Software and all copies thereof (except for any embedded third party software) are 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. Restrictions. Licensee will not itself or permit others to: i. ii. 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; 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; modify, merge with other programs or translate any portion of the Software into any other assembly or foreign language; and reverse-assemble, reverse-compile or attempt to derive a source code equivalent of the Software.
b.
c.
iii. iv. d.
Protections. Licensee agrees to secure and protect the Software, the Documentation and copies thereof in 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. Responsibility. Licensee has sole responsibility for use of the program and any information entered, used, 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.
e.
iv
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 Licensees requirements or that the operation of the Software will be uninterrupted or error free. Compatibility. It is the intent of ADIC to provide Software which is compatible with the current releases of 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. Warranty Servicing. The Licensee must notify ADIC in writing, within ninety (90) days after installation of the Software of Licensees claim of any defect. If the Software is found defective by ADIC, ADICs 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. Warranty Exclusions. This warranty is made void if the Licensee or any other third party makes any 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. Warranty Disclaimer. EXCEPT FOR THE EXPRESS LIMITED WARRANTY STATED ABOVE, ADIC MAKES NO WARRANTIES, EXPRESS OR IMPLIED, FOR THE SOFTWARE, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Third Party Warranties. No reseller or distributor of the Software who may have participated in offering, demonstrating, promoting or delivering the Software subject to this License makes any warranty whatsoever. All limitations 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.
b.
c.
d.
e.
f.
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.
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. 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. 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.
b.
c.
Term and Termination

a. b. Term. The term of this License is perpetual, unless terminated by ADIC as provided herein. 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 ADICs election, returned to ADIC the original and all copies of the Software and Documentation in any form maintained by Licensee. Termination for Cause. A violation of any provision of Paragraph 3. above will be deemed a material breach and the basis for immediate termination of this License. Termination upon Insolvency. This License may be terminated by ADIC if the Licensee (i) terminates or 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. Remedies upon Termination. If this License is terminated by ADIC, ADIC will have the right to take 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.
c. d.
e.
vi
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 ADICs prior written consent. Any effort contradictory with this is null and void. Modification. This License or any Exhibit hereto can only be modified by a written agreement executed by Licensee and ADIC. Governing Law. The laws of the state of Washington will govern this license. All litigation between the 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. Enforcement Costs. The party prevailing in any litigation or legal proceeding, including arbitration, arising out of any dispute under this Agreement will be entitled to recover reasonable attorneys fees and costs from the other party. Limitations on Actions. Any action, regardless of form, arising out of the transactions under this License, 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.
b. c.
d.
e.
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.
vii
viii
Contents
1 Introduction 17
17 17 18 18 19 Purpose of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How This Guide is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Explanation of Symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 StorNext GUI Overview
21
21 21 23 24 26 30 40 41 41 43 43 45
Using the StorNext GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . StorNext Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drop-down Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Component Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . StorNext System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . StorNext Server Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the SNFS GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNFS Home Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 Basic Tasks
39
39 44 47 51 57 58
Entering the StorNext License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing StorNext Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Controlling User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running StorNext Software Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling StorNext Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting and Stopping StorNext
ix
Software Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting SNSM / SNFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Help Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61 61 62 63 64 65
4 File System Management
67
Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Labeling Disk Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Globals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Name Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Trashcan Files and Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Making a File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Mounting or Unmounting a File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Creating a File System Using the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Creating a File System Server Using CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Adding a File System Client Using CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Modifying a File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Expanding a File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Deleting a File System Using the GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Stripe Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Adding a Stripe Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Modifying a Stripe Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Deleting a Stripe Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Configuring a Stripe Group Using CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Adding Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Deleting Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Defragmenting a Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Affinities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Adding an Affinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Modifying an Affinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Deleting an Affinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 File System Configuration Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Adding an Affinity Using CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Performing a Metadata Dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Contents
5 Library and Storage Disk Management 111

Managing Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 Adding a Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 Modifying a Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124 Deleting a Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125 Managing Drives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128 Configuring a Tape Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128 Changing a Drive State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135 Cleaning a Tape Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 Drive Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 Managing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 Adding Media to a Configured Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142 Removing or Moving Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147 Mounting and Dismounting Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158 Transcribing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160 Reclassifying a Media Class Grouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161 Managing Storage Disks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164 Configuring a Storage Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164 Changing a Storage Disk State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170 Cleaning a Storage Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
6 Data Migration Management
173
Policy Classes and Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 Managing Policy Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 Adding a Policy Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 Modifying a Policy Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179 Deleting a Policy Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180 Adding Media to a Policy Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182 Performing Disk-to-Disk Relocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183 Creating a Disk-to-Disk Policy Class Using CLI . . . . . . . . . . . . . . . . . . . . . . . . . . .188 Performing Disk-to-Disk Relocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
7 Monitoring and Reporting
191
Generating StorNext Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191 StorNext File System Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191 StorNext Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197
xi
8 Service Management
215
215 216 217 219 220 220 221 222 222
Using Health Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the Health Check History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the Health Check Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using State Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capturing the Current System State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading a Previous System Capture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Previous System Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9 Customer Assistance
227
StorNext Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 ADIC Technical Assistance Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
A File System Commands
229
229 229 230 231 232 232 232 232 233 233 234 234 235 235 235 236 236 236 236 236 236 237 237 237
cvadmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cvaffinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cvcp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cvfsck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cvfsid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cvlabel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cvmkdir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xii
Contents
Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237 cvmkfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238 cvmkfs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239 cvupdatefs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239 cvversions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240
B Storage Manager Commands
241
fsaddclass. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242 fsaddrelation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243 fsaudit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244 fschfiat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 fschmedstate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246 fschstate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247 fsclassinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247 fsclean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248 fsdrvclean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248
StorNext System Administrator Guide xiii
Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fsfileinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fsmedcopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fsmedinfo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fsmedlist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fsmodclass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fspolicy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fsqueue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fsrecover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fsretrieve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fsrmcopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fsrmdiskcopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fsrminfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fsstate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fsstore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fsversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiv
248 248 249 249 249 249 249 250 250 250 250 251 251 251 252 252 252 253 253 254 254 254 255 255 255 255 257 257 257 257 257 257 258 258 258 258 258 258 258 258 258 259 259 259 259 259 260
Contents
fsusedspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260 snrestore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261 vsarchiveqry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263 vsdriveqry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264 vsdrivevary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265 vsmedclassqry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266 vsmedqry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267 vspoolcfg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268 vsreclassify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269 Options / Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269
xv
C StorNext Configuration and Administration Tasks 271

Sharing a Library Between Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually Modifying System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fs_sysparm Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . filesize.config Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . log_params Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a Fibre Channel Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . StorNext Log Rolling Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Log Rolling Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log Rolling Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Avoiding Poor System Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 272 272 273 273 273 274 274 274 274
D StorNext Files
277
The example.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Commonly Used SNFS Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
E Quality of Service Guide
285
285 285 286 286 286 286 286 289 289 290 291 292 293 294 294 295 295 296 296
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Active vs. Passive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unit of I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Converting MB/sec to I/O/sec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Real-time I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SetRtio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Callbacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Callback Failures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tokens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Failure Semantics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FSM Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Token Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sharing Disk Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xvi
Contents
F HA Failover Glossary
297 299
xvii
xviii
Contents
1
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, HPUX, AIX, IRIX, 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 on site and off site. This guide describes how to administer the entire StorNext solution.
Purpose of This Guide

This guide is intended to assist system administrators who manage the StorNext products and perform day-to-day tasks on these systems. This guide also describes how to generate reports and provides the most commonly-used UNIX commands to manage StorNext.
Intended Audience
This guide is written for system administrators who are familiar with file systems and are administering an integrated solution to access, manage, and protect data. ADIC assumes that system administrators have a strong familiarity with UNIX, the Windows operating system, and the applications running in their site environment.
17
How This Guide is Organized

This guide contains the following chapters: Chapter 1: Introduction Chapter 2: StorNext GUI Overview Chapter 3: Basic Tasks Chapter 4: File System Management Chapter 5: Library and Storage Disk Management Chapter 6: Data Migration Management Chapter 7: Monitoring and Reporting Chapter 8: Service Management Chapter 9: Customer Assistance Appendix A: File System Commands Appendix B: Storage Manager Commands Appendix C: StorNext Configuration and Administration Tasks Appendix D: StorNext Files Appendix E: Quality of Service Guide Appendix F: HA Failover
Explanation of Symbols
The following symbols indicate important information in this guide. Symbol Description WARNING: Definition Advises you to take or avoid a specified action. Consequence 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. No hazardous or damaging consequences.
CAUTION:
Advises you to take or avoid a specified action.
NOTE:
Indicates important information that helps you make better use of the software.
18
How This Guide is Organized
Document Conventions
This guide uses the following document conventions to help you recognize different types of information.
Conventions For all UNIX-based commands, the # prompt is implied, although it is not shown. For all UNIX-based commands, words in italic are variables and should be replaced with user-defined values.
Examples TSM_control stop is the same as # TSM_control stop cvaffinity <filename> where <filename> is a variable and should be replaced with a user-defined value.
19
20
Document Conventions
2
StorNext GUI Overview
This chapter provides information for the following: Using the StorNext GUI Using the SNFS GUI on page 43 This chapter also describes how to access and navigate each GUI.
Using the StorNext GUI

Note
StorNext supports internationalization for the name space of the file system. This support is fully UTF-8 compliant. It is up to the individual client to set the proper UTF-8 locale.
The StorNext GUI is browser-based and can be remotely accessed from any machine with access to the StorNext server. This section only describes how to access and navigate through the StorNext GUI. If you purchased SNFS, refer to Using the SNFS GUI on page 43.
Accessing the GUI

Use this procedure to access the StorNext GUI. 1 Open a Web browser.
Note
Supported browsers are: Internet Explorer 5.5 and later Netscape 7.x Mozilla 1.0 and later FireFox 1.0 and later
Type the full address of the machine and its port number http://<machine name>:<port number> in the Address Field and press Enter. Use the name of the machine and port number that you copied when you installed the StorNext software.
21
Note
Typically, the port number is 81. If port 81 is in use, use the next unused port number. (I.e., 82, 83, etc.)
The following screen appears.
3 4
In the User ID Field, type admin and press TAB. In the Password Field, type admin and click OK.
Note
For information on changing your password or setting up additional users, refer to the StorNext System Administrator Guide.
The initial StorNext GUI appears. You are prompted to start non-running components.
Click OK to start the StorNext components.
22
Using the StorNext GUI
The StorNext GUI launches. The main components of the StorNext GUI are shown below on the StorNext Home Page.
Component Navigation
Link to ADIC Drop-down Home Page Menu Options
Refresh Buttons
Monitor Refresh Rate Options
Application System Link Monitors
StorNext System Status
StorNext Server Status
StorNext Home Page

On the home page you will find the following: Link to the ADIC Home Page - Click here to find out more about ADIC System Monitors on page 24 Drop-down Menu Options on page 26 Component Navigation on page 30 Application Link on page 40 Application Link on page 40 StorNext Server Status on page 41 StorNext System Administrator Guide 23
System Monitors
The StorNext Home Page displays two system monitors that are used to monitor the state of the StorNext system. You can view current statistics of managed file systems and configured libraries and/or drives, including file system, library, and drive information. There are two system monitors: File System Monitor Library Monitor on page 25 Storage Disk Monitor on page 25
File System Monitor

The File System Monitor enables you to view statistics on each configured file system. When you open a browser to access StorNext, the File System Monitor appears at the top of the browser window.
The File System Monitor provides the following information: Refresh: Click this button to manually refresh the File System Monitor. Refresh Rate: Set the File System Monitor to automatically refresh with this drop down menu. Options range from No Refresh to every 10 Minutes. File System: The name of the file system (you may see more than one file system being monitored, depending upon how your StorNext system is configured). This pane is scrollable to accommodate numerous file systems. Total Space (GB): Total space (in GB) for the file system Used Space (GB): Currently used space (in GB) for the file system Free Space (GB):Amount of free space (in GB) for the file system Total Files: Number of files on the file system #Store Candidates: Number of files selected for storage to secondary media #Trunc Candidates: Number of files that haves been stored and meets the criteria to become a truncation candidate # Connections: The number of clients connected to the file system Status: The status shows the system status (usage) in percent in addition to low and high watermark settings. The low watermark specifies the level of used disk space that is acceptable to end overflow processing. The high watermark specifies the level of used disk space that initiates overflow processing. In the above example, the system usage is less than 10% with 75% set as the low watermark and 85% set as the high watermark. Overflow processing occurs when your the system processes beyond the set watermark limitations. On an unmanaged file system, the number of Stored and Truncation candidates defaults to N/A.
Note
24
StorNext Home Page
Library Monitor
The Library Monitor enables you to view library and drive information on each library. When you open a browser to access StorNext, the Library Monitor appears below the File System Monitor.
The Library Monitor provides the following information: Refresh: Click this button to manually refresh the Library Monitor Refresh Rate - Set the Library Monitor refresh rate with this drop down menu. Options range from No Refresh to every 10 Minutes. Library: Displays the name of the library Library Type: Indicates the library type: SCSI, Vault, or Network Library State: Indicates the library state: online or offline Number of Drives: Specifies the number of drives that are configured for the library Capacity: Total number of media slots in the library Fill Level: Number of media in the archive Drive Name: Name (or label) of configured drive (or drives) for the library State: Indicates that the drive is online or offline Status: Indicates if the drive is free or in use Read/Write: Indicates if the drive is in a Read or Write state Mounted Media: Media ID of the media currently mounted in the drive
Storage Disk Monitor

The Storage Disk monitor allows you to view configured storage disk information. When you open a browser to access StorNext, the Storage Disk Monitor appears below the Library Monitor.
The Storage Disk Monitor provides the following information: Name: Name of the storage disk Space: Total amount of space on the storage disk in GB Used Space: Space used on the storage disk in GB State: The storage disk is Online or Offline Copy #: The copy number of files on that specific storage disk # Files: Total number of files on the storage disk
25
Drop-down Menu Options

The drop-down menu options are located in the grey bar towards the top of the home page, are menus used to access StorNext configuration, administration, and reporting options. The Drop-down Menu Options are: Config on page 26 Admin on page 27 Reports on page 28 Service on page 29 Help on page 30
Config
The options for the Config Drop-down menu launch the Configuration Wizard or individual configuration wizard tasks.
The Config menu contains these options: Config Wizard: Launches the configuration wizard Enter License: Enter StorNext license information Add File System: Add a file system to your environment Add Library: Add a library or vault Add Tape Drive: Add tape drive Add Media: Add media Add Storage Disk: Add a storage disk Add Storage Policy: Add a storage policy and a directory relation point to a file system
26
StorNext Home Page
E-Mail Notification: Configure e-mail notifications for System Status Tickets, Backup information, and Policy Class alerts Add Affinity: Add an affinity to a file system
Note
Detailed descriptions of the Admin menu options are located in Chapter 4, File System Management, Chapter 5, Library and Storage Disk Management, Chapter 6, Data Migration Management.
Admin
The options for the Admin drop-down menu enable you to control day-to-day operations of StorNext.
The Admin menu contains these options: Access StorNext Logs: Access logs of StorNext operations User Access Control: Control user access to StorNext tasks Download Client Software: Download SNFS client software Library Operator Interface: Enter or eject media from the Library Operator Interface Remove/Move Media: Remove media from a library or move media from one library to another Run Backup: Run a backup of StorNext software Schedule Events: Schedule file system events including Clean Info, Clean Versions, Full Backup, Partial Backup, and Rebuild Policy Start/Stop StorNext: Start or stop the StorNext components
27
Note
Detailed descriptions of the Config menu options are located in Chapter 4, File System Management, Chapter 5, Library and Storage Disk Management, Chapter 6, Data Migration Management.
Reports
Use the options on the Reports drop-down menu to view StorNext reports.
The Report menu contains these options: SNFS: View the three types of SNFS reports (Affinities, File Systems or Stripe Groups) Backups: View a report of StorNext backups Drives: View tape drive information Files: View file information Libraries: View libraries information Library Space: View information about used library space Media: View media information Media Classes: View media classes information Policy Classes: View policy class information Relations: View directory/policy class relationship information Requests: View request information Scheduler: View scheduler information 28 StorNext Home Page
Storage Disk: View storage disk information Detailed descriptions of the Report menu options are located in Chapter 8, Monitoring and Reporting.
Note
Service
Use the options on the Service drop-down menu to monitor and capture system status information.
The Service menu contains these options: Health Check: Perform one or more health checks on StorNext and view recent health check results State Capture: Obtain and preserve detailed information about the current StorNext system state System Status: View tickets indicating faults as reports by the StorNext system Detailed descriptions of the Service menu options are located in Chapter 3, Basic Tasks.
Note
29
Help
Use the options on the Help drop-down menu to access StorNext documentation, find ADIC contact information, or detailed information about this version of StorNext.
The Help menu contains these items: Documentation: Access the StorNext documentation Support: Access ADIC and Technical Support information About: Access detailed information about your version of StorNext and the system it is running on Detailed descriptions of the Help menu options are located in Chapter 3, Basic Tasks.
Note
Component Navigation
The Navigation Pane contains links to the SNFS and SNSM Home Pages along with a Home button to return to the StorNext Home Page. SNFS Home Page - In SNFS mode, you perform file system-specific tasks. The SNFS Home Page contains several drop-down menus: Config, Admin, and Reports. SNSM Home Page on page 35 - In SNSM mode, you perform administrative storage manager tasks. The SNSM Home Page contains several drop-down menus: File, Media, Admin, and Reports.
30
StorNext Home Page
SNFS Home Page

The SNFS Home Page contains a File System Monitor and these drop-down menu options: Config on page 32 Admin on page 33 Reports on page 34 Help on page 34 Use the drop-down menus on this home page as you would from the StorNext Home Page when performing file system-specific administration tasks.
Note
The graphic shows the SNFS Home Page as it appears when it is part of the full StorNext application. The GUI looks different than the home page for the SNFS standalone application, as shown in SNFS Home Page on page 45.
31
Config
Use the options on the SNFS Config drop-down menu to add and modify file system configuration files. You must unmount and stop the file system before using most of the options listed in this section. See Chapter 3, Basic Tasks for more information.
Note
The Config drop-down menu contains these options: File Systems: Add or delete a file system Globals: Modify global settings Affinities: Add, modify, or delete an affinity from file systems Disks: Add or delete a disk to a file system Stripe Groups: Add, modify, or delete a stripe group from a file system Deleting a disk or stripe group requires a remake of the file system and destroys all data on the file system when the task is run.
CAUTION
Note
Detailed descriptions of the Config menu options are located in Chapter 4, File System Management.
32
StorNext Home Page
Admin
Use the options on the SNFS Admin drop-down menu to manage day-to-day operations of the active file systems.
The Admin menu contains these options: Make File System: Make a file system Start/Stop File System: Start or stop a file system Mount/Unmount: Mount or unmount a file system Label Disk Devices: Label disk drives Set Affinities: Create a directory in the file system to the affinity Trashcan Files: Recover deleted files (if the trashcan is enabled) Trashcan Directories: Recover deleted directories (if the trashcan is enabled) Metadata Dump: Generate a Metadata dump of a file system Making a file system or making/labeling disk devices destroys all data on the disk on which the task is run.
CAUTION
Note
Detailed descriptions of the Admin menu options are located in Chapter 2, StorNext GUI Overview, and Chapter 4, File System Management.
33
Reports
Use the options on the SNFS Reports drop-down menu to view all SNFS reports.
For descriptions of the Reports menu options, refer to Reports on page 28.
Help
Use the options on the Help drop-down menu to access StorNext documentation, find ADIC contact information, or detailed information about this version of StorNext.
For descriptions of the Help menu options, refer to Help on page 30.
34
StorNext Home Page
SNSM Home Page

The SNSM Home Page contains a Library Monitor and these drop-down menu options: File on page 36 Media on page 37 Admin on page 38 Reports on page 39 Help on page 39 Use the drop-down menus on this home page as you would from the StorNext Home Page when performing Storage Manager-specific administration tasks.
35
File
Use the options on the SNSM File drop-down menu to manage file data and directories.
The File menu contains these options: Store: Store files to a storage medium Version: Show the version(s) of files stored on storage medium Recover File: Recover deleted files Recover Directory: Recursively recover deleted directories Retrieve File: Retrieve truncated files from a storage medium Retrieve Directory: Recursively retrieve truncated directories from a storage medium Free Disk Blocks: Truncate files Move: Move files from one media to another Attributes: Change file attributes
36
StorNext Home Page
Media
Use the options on the SNSM Media drop-down menu to manage media and libraries.
The Media menu contains these options: Library: Perform media movement tasks within a library (Manual Move, Mount, and Dismount) Add: Add media to a policy class Remove: Remove media from StorNext Move Blank: Associate blank media with a policy class Transcribe: Transcribe (copy) media Attributes: Change the medias state or attributes Reclassify: Reclassify a media to a new media class Clean: Clean a media by policy class, file system, or media identifier
37
Admin
Use the options on the SNSM Admin drop-down menu to perform administration tasks.
The Admin menu contains these options: Library: Perform library tasks such as Config Library, Audit Library, Library State, and Cancel Eject Drive: Perform drive tasks such as Config Drive, Change Drive State, and Clean Drive Storage Disk: Perform storage disks tasks such as Config Storage Disk, Change Storage Disk State, and Clean Storage Disk Disk Space: Perform an immediate file system storage or truncation policy Policy Class: Add, modify, or delete a policy class Backup: Configure backup procedure parameters Relation: Add or remove directory relation points to a policy class Water Mark Parameter: Set water mark parameters (for more information about watermarks, seepage 24) Config Drive Pool: Add, modify, or delete drive pools Cancel Request: Cancel requested operations
38
StorNext Home Page
Reports
Use the options on the SNSM Reports drop-down menu to view different reports.
For descriptions of the Reports menu options, refer to Reports on page 28.
Help
Use the options on the SNSM Help drop-down menu to access StorNext documentation, find ADIC contact information, or detailed information about this version of StorNext.
For descriptions of the Help menu options, refer to Help on page 30.
39
Application Link
The StorNext application link is located at the bottom left of the StorNext Home Page. Click this link to view information about StorNext.
40
StorNext Home Page
StorNext System Status

The StorNext System Status button is located at the bottom center of the StorNext Home Page only when there are open service tickets. This page is always available through the Service drop-down menu by clicking Service > System Status. Click the System Status button to view a list of tickets indicating faults reported by the system. The Service - System Status screen appears.
Note
A detailed description of the Service drop-down menu options are located in Chapter 9, Service Management.

The StorNext Server Status button is located at the bottom right of the StorNext Home Page. This button displays one of three statuses for the file systems residing on the server: Active: All configured file systems are active Warning: One or more of the configured file systems have not been mounted or started Stopped: The storage manager or the file system manager is stopped 1 Click the StorNext Server Status button to view details of the server status.
41
The Start/Stop StorNext screen appears.
2 3
Select the Start or Stop option. Select the component you want to start or stop. Your choices are: All Components StorNext File System StorNext Storage Manager The status (Started, Stopped, or Warning) of the individual components are shown next to each. A Warning status indicates one of your configured file systems is either not mounted or has not been started.
Note
4 5
Select Enable or Disable to start StorNext at the next reboot. Click Next.
42
StorNext Home Page
The Complete Start/Stop StorNext Task screen appears
6 7
Click Next. A status screen appears. Click Close when the status screen shows Success. The StorNext Server Status now displays Stopped or Active depending on your action.
Using the SNFS GUI

The SNFS GUI is browser-based and can be accessed remotely from any machine with access to the local network and the SNFS server. This section only describes how to access and navigate through the SNFS GUI. If you purchased StorNext, refer to Using the StorNext GUI on page 21.
Accessing the GUI

Use the following procedure to access the SNFS GUI. 1 Open a Web browser.
Note
Supported browsers are: Internet Explorer 5.5 and later Netscape 7.x Mozilla 1.0 and later FireFox 1.0 and later
Type the full address of the machine and its port number http://<machine name>:<port number> in the Address Field and press Enter. Use the name of the machine and port number that you copied when you installed the StorNext software. 43
Note
Typically, the port number is 81. If port 81 is in use, use the next unused port number. (I.e., 82, 83, etc.)
The following screen appears.
3 4
In the User ID Field, type admin and press TAB. In the Password Field, type admin and click OK.
Note
For information on changing your password or setting up additional users, refer to the StorNext System Administrator Guide.
The initial StorNext GUI appears. You are prompted to start non-running components.
Click OK to start the SNFS GUI. The SNFS GUI launches. The main components of the SNFS GUI are shown below on the SNFS Home Page.
44
Using the SNFS GUI
Link to ADIC Home Page
Shortcut Menu Options
Help
SNFS Home Page

On the SNFS Home Page you will find the following: Link to the ADIC Home Page Drop-down Menu Options Shortcut Menu Options on page 48 Help on page 49 StorNext Server Status on page 49

The menu options are located in the grey bar towards the top of the home page and, used to access SNFS configuration, administration, and reporting options.The Drop-down Menu Options are: Config Admin on page 47 Reports on page 48
45
Config
The options on the Config drop-down menu enable you to add and modify file systems.
The Config menu contains these options: File Systems: Add or delete a file system Globals: Modify global settings Affinities: Add, modify, or delete an affinity from file systems Disks: Add or delete a disk to a file system Stripe Groups: Add, modify, or delete a stripe group from a file system Name Servers: Specifies machines serving as File System Name Server coordinator(s) to the fsmpm daemon Detailed descriptions of the Config menu options are located in Chapter 4, File System Management.
Note
46
Using the SNFS GUI
Admin
The options on the Admin drop-down menu enable you to control day-to-day operations of active file systems.
The Admin menu contains these options: Make File System: Make a file system Start/Stop File System: Start or stop a file system Mount/Unmount: Mount or unmount a file system Label Disk Devices: Label disk drives Making a file system or making/labeling disk devices destroys all data on the disk on which the task is run.
CAUTION
Set Affinities: Create a relation point in the file system to the affinity Detailed descriptions of the Admin menu options are located in Chapter 4, File System Management.
Note
47
Reports
Use the options on the Reports drop-down menu to view file system reports.
The Reports menu contains these options: Affinities: View the Affinities report File Systems: View the File Systems report Stripe Groups: View the Stripe Groups report Detailed descriptions of the Report menu options are located in Chapter 8, Monitoring and Reporting.
Note
Shortcut Menu Options

The Shortcut Menu is comprised of links to Configuration and Administrative tasks. The Shortcut Menu includes the following: Config Add Affinity: Add an affinity and directory to a file system Add File System: Add a file system Enter License: Enter your StorNext license information User Access Control: Add, modify, or delete the level of user access
48
Using the SNFS GUI
Admin Access StorNext Logs: View logs for SNFS, the Server System, and the StorNext Web Server Download Client Software: Download the SNFS client software for a specific operating system Start/Stop StorNext: Start or Stop StorNext Software
Help
The navigation pane is a vertical, blue bar located on the left side of the home page. It contains a Help section with links to the StorNext documentation, support, and version information. Documentation: Provides links to user documents associated with the SNFS Support: Provides contact information for the ADIC Technical Assistance Center (ATAC) Version: Provides version information for SNFS components

The StorNext Server Status button is located at the bottom right of the SNFS Home Page. This button displays one of three statuses for the file systems residing on the server: Active: All configured file systems are active Warning: One or more of the configured file systems have not been mounted or started Stopped: The storage manager or the file system manager is stopped For more information see StorNext System Status on page 41.
49
50
Using the SNFS GUI
3
Basic Tasks
This chapter provides instructions to perform basic StorNext and StorNext File System (SNFS) tasks such as starting, stopping, and logging on the application. This chapter covers these topics: Entering the StorNext License Accessing StorNext Logs on page 44 Controlling User Access on page 47 Downloading Client Software on page 51 Running StorNext Software Backups on page 57 Scheduling StorNext Events on page 58 Starting and Stopping StorNext Software Components on page 61 Using the Help Menu on page 62
Entering the StorNext License

Use the Enter License wizard to enter a permanent license string. You can also proceed using the 30-day temporary license that comes with StorNext. You must have a permanent or temporary license to configure or use StorNext.
Note
If you use the temporary license, be sure to obtain a permanent license from ADIC before the 30-day temporary license expires.
To obtain a permanent license, you must contact ATAC at licenses@adic.com and give them the following information: The serial number from your product CD or box. The number of file system clients you want to support. The StorNext server identification number. You can find this number on the Configuration Wizards Enter License String screen.
Alternatively, you can obtain a license by going to www.adic.com/swlicense and providing the required information.
StorNext System Adminstrator Guide
39
After ATAC receives the above information, an ATAC representative will send you a license string. Enter this license screen on the Enter License String screen to use StorNext with your permanent license. If you use the temporary license, allow sufficient time for ATAC to receive your information and send your license string before the 30-day limit expires. 1 From the StorNext Home Page click Config > Enter license. The Enter License - Introduction screen appears.
Click Next to continue.
40
The ADIC license agreement appears. You must accept the license agreement in order to continue with the licensing process.
Read the license agreement and then click Accept. The Enter License String screen appears. This screen summarizes the information you must send to license@adic.com in order to receive the license string you enter on this screen.
Do one of the following:
41
Select Generate 30 day temporary license to proceed with the Configuration Wizard using a temporary 30-day license. Continue with step 4. Enter a permanent license. Go to step 7.
After selecting Generate 30 day temporary license, click Next to continue.

The Complete Enter License screen appears.
On the Complete Enter License screen, click Next to complete the task or Back to make changes. When you click Next, a message reminds you to contact ATAC within 30 days to receive your permanent license string.
7 8
Click OK to close the message box. To enter a permanent license, type or copy and paste into the License String field the license string you received from ATAC. If you receive your license string electronically, paste the license string into the /usr/adic/ DSM/config/license.dat file. Updating this file enables StorNext to automatically detect the license string when the Configuration Wizard runs. If you receive your license string in a hard-copy document, type the license string, exactly as it is shown, in the License String Field.
42
Here is an example of a StorNext license file with the license string entered (below License Authorization String). This is an example only. Do not enter the license screen shown.
# System: emerald # Identifier: 3FA781993 # Number Clients: 12 # Expiration Date: None # License: AAAAA/B2AAS/AJDQV/2DCKS/M7RA9/82XUR/CH3TL/9EES7/5ZEGV/ 6ALVD/TA # # License Authorization String:
server 1 3FA781993 12 AAAAAB2AASAJDQV2DCKSM7RA982XURCH3TL9EES75ZEGV6ALVDTA emerald ADIC
Click Next to continue. The Complete Enter License screen appears.
10 Review your selections. Click Next to complete the task or Back to make changes.
43
Accessing StorNext Logs

Use this procedure to access the StorNext log files. 1 From the StorNext Home Page click Admin > Access StorNext Logs. The Select Log screen appears.
You can select one of the following logs: SNFS Logs: Logs about each configured file system StorNext Database Logs:Track changes to the internal database SNSM - File Manager Logs: Tracks storage errors, etc. of the Storage Manager SNSM - Library Manager Logs: Tracks the events and status of the library Server System Logs: System message logs StorNext Web Server Logs:Various logs related to the web server 2 Select the log you wish to view and click Next.
44
The Select File screen appears.
Select the log file you wish to view and select one of the following: Delete: Delete the log file Mail: E-mail the log file to ADIC support. You are prompted to do so after clicking the Mail button. Show: Show the log file in a separate window
45
If you clicked Show, the log file appears.
Click Cancel to close the window.
46
Controlling User Access

Use these procedures to change the Admin password in addition to Add, Modify, or Delete StorNext user access. 1 From the StorNext Home Page click Admin > User Access Control. The User Access Control screen appears.
Do one of the following: Changing the Admin Password Changing the Admin Password Modify an Existing User on page 49 Delete an Existing User on page 51
Changing the Admin Password

1 From the User Access Control screen, select Admin in the User List and click Modify. The Modify User admin screen appears.
47
2 3 4
Enter your new password. Verify your password (enter it again) and click OK. Click OK when the Status Screen displays Success.
Add a New User

1 From the User Access Control screen, click Add. The Add New User Screen appears.
2 3 4
Type the user name in the Enter User Name field. Type the user password in the Enter Password field. Retype the password in the Re-enter Password field.
48
Select the type of access the user will have: Admin Defaults - Enables access to the entire StorNext system including SNFS Advanced Functions, SNSM Advanced Functions, StorNext Home Functions, and StorNext Reports Operator Defaults - Enables access to most of the StorNext Home Functions and StorNext Reports General User Defaults - Enables access to most of the StorNext Reports Each of the above selections auto-populates the screen to correspond with your selection, but you can customize access by clicking on specific items for the user.
6 7
Click OK. Click OK when the Status screen displays Success. The User Access Control screen appears listing the new addition.
Click Cancel to close the window.
Modify an Existing User

Use this procedure to modify an existing users StorNext access. 1 From the User Access Control screen, select a name from the User List and click Modify.
49
The Modify User screen with the users name displayed appears.
2 3
Make the necessary modifications and click OK. Click Close when the Status screen displays Success.
50
Delete an Existing User

Use this procedure to Delete an existing user. 1 From the User Access Control screen, select a name from the User List and click Delete. You are prompted to make sure if you want to delete the user. 2 3 Click OK. Click Close when the Status screen displays Success.
Downloading Client Software

If the client machine can access a Web browser, use this procedure to download the client software. 1 On a StorNext client, launch a browser and enter the URL with the StorNext server name and port number. For example, http://StorNextServer:81. The Enter Network Password window appears.
51
Enter the User ID and password. The default value for both fields is admin, unless changed by your system administrator. Click OK. The StorNext home page appears.
52
From the Admin menu, select Download Client Software. The Select Platform screen appears.
Select the platform that corresponds to the operating system on the StorNext client and then click Next. The Download Client Software screen appears. (Linux is shown as an example.)
53
The following client packages are available to download:
Operating System
IBM AIX 52 IBM AIX 53 HP-UX 11.23 IA64 HP-UX 11.23 PA-RISC IRIX 6.5.xx Linux RedHat 9.0 (Intel 32 bit) Linux RedHat AS 3.0 (Intel 32 bit) Linux RedHat AS 3.0 (Intel 64 bit) Linux RedHat AS 3.0 (Intel IA64) Linux RedHat AS 4.0 (Intel 32 bit) Linux RedHat AS 4.0 (Intel 64 bit) Linux RedHat AS 4.0 (Intel IA64) Linux SuSE ES 9.0 (Intel 32 bit) Linux SuSE ES 9.0 (Intel 64 bit) Linux SuSE ES 9.0 (Intel IA64) Solaris Sparc 510 Solaris Sparc 59 Windows 2000/XP/2003 5
Download File Name

sn_dsm_aix52_client.tar sn_dsm_aix53_client.tar sn_dsm_hpux_B.11.23ia64_client.tar sn_dsm_hpux_B.11.23pa-risc_client.tar sn_dsm_irix65m_client.tar sn_dsm_linuxRH_9i386_client.tar sn_dsm_linuxRH_AS_3i386_client.tar sn_dsm_linuxRH_AS_3x86_64_client.tar sn_dsm_linuxRH_AS_3ia64_client.tar sn_dsm_linuxRH_AS_4i386_client.tar sn_dsm_linuxRH_AS_4x86_64_client.tar sn_dsm_linuxRH_AS_4ia64_client.tar sn_dsm_linuxSuSE_90i386_client.tar sn_dsm_linuxSuSE_90x86_64_client.tar sn_dsm_linuxSuSE_90ia64_client.tar sn_dsm_solaris510sparc64_client.tar sn_dsm_solaris59sparc64_client.tar sn_dsm_win2k_client.exe
Select the software package that corresponds to your system by clicking the link.
54
6 7
Save the file to a location on your local hard drive. Be sure to make a note of this location, because you will need to navigate to it when youre ready to install the client software. After the file download is complete, on the Download Client Software screen click Next to continue. The Install Client Software screen appears. (Linux is shown as an example.)
55
Follow the directions on the Install Client Software screen to install the software for your operating system. When finished, return to the Install Client Software screen and click Next to continue. For all operating systems except Windows, the Configure Client Software screen appears. (Linux is shown as an example.)
Click Finish.
56
Running StorNext Software Backups

The following procedures describe how to run a manual backup. These backups are scheduled by default to run once a week. If you would like to reschedule your backups (for more information on scheduling backups, see Scheduling StorNext Events on page 58). When running backups, you have the option to run either a full or partial backup.
Note
These backups DO NOT backup user data.
Full Backup:By default, a full backup is run once a week. This backup includes: The StorNext database Configuration files File system metadata dump file (after journal files are applied)
Partial Backup: By default, a partial backup is run on all other days of the week (that the full backup is not run). This backup includes: 1 StorNext database journals Configuration files File system journal files
Use this procedure to run a StorNext backup. From the StorNext home page click Admin > Run Backup. The Backup StorNext screen appears.
Select the type of backup you want run, Full or Partial, and click Next.
57
The Complete Backup Task screen appears.
Click Next to start the backup. Click Finish when the Status screen displays success.
Scheduling StorNext Events

Use this procedure to schedule StorNext events. Events that can be scheduled are: Clean Info - Scheduled background operation for removing knowledge of media from StorNext Clean Versions - Clean old inactive versions of files Full Backup - By default, a full backup is run once a week to back up the entire database, configuration files, and the file system metadata dump file. Partial Backup - By default, a partial backup is run on all other days of the week (that the full backup is not run). This backup includes database journals, configuration files, and file system journal files. Rebuild Policy - Rebuild the internal candidate lists (for storing, truncation, and relocation) by scanning the file system for files that need to be stored Each of these events have a default schedules set, these procedures allow you to reconfigure the schedules to suit your system needs. 1 From the StorNext Home Page click Admin > Schedule Events.
58
The Feature Schedules screen appears.
Select a feature to schedule and click Configure. The Feature Schedules screen displays the selected Feature and its current schedule.
Select a schedule and click one of the following: Back: Go back to the previous screen Add: Add a new schedule Modify: Change an existing schedule Delete: Delete an existing schedule Reset: Reset the schedule to the default settings Close: Close the window
59
The Feature Schedule screen displays schedule options.
Use the following options to configure the schedule: Name - If you are adding a new schedule, enter the name of the new schedule. Otherwise the name of the schedule you are modifying appears. Days of Week - Select the days of the week or Day of Month - Select the days of the month for the process to run Run Time - Process start time Start Window - The scheduler attempts to begin the process within the Start WIndow time.If it cannot begin at that time, it will try again during the next cycle
5 6
Configure the schedule and click Apply. Click Close when the Status screen displays Success.
60
Starting and Stopping StorNext Software Components

You can start or stop the StorNext components, SNFS and SNSM, using the Admin Drop-down menu, or by clicking the Server Status button. Use this procedure to start/stop StorNext components using the Admin drop-down menu.
Starting SNSM / SNFS

1 From the StorNext Home Page click Admin > Start/Stop StorNext. The Start/Stop StorNext screen appears.
2 3
Select the Start or Stop option. Select the component you want to start or stop. Your choices are: All Components StorNext File System StorNext Storage Manager The status (Started, Stopped, or Warning) of the individual components are shown next to each. A Warning status indicates one of your configured file systems is either not mounted or has not been started.
Note
4 5
Select Enable or Disable to start StorNext at the next reboot. Click Next.
61
The Complete Start/Stop StorNext Task screen appears
Click Next. A status screen appears.
Click Finish when the status screen shows Success. The StorNext Server Status now displays Stopped, Warning or Active depending on your action.
Using the Help Menu

The Help Drop-down menu contains options to find useful information about your StorNext system. These options are: Documentation on page 63 - Links to the current StorNext set of documentation Support on page 64 - Access ADIC and Technical Support information About on page 65 - Access detailed information about your version of StorNext
62
Using the Help Menu
To view these options, click Help on the StorNext Home page.
Documentation
Use this procedure to view StorNext documentation. 1 Click Help > Documentation.
63
The StorNext Documentation Table of Contents appears.
The StorNext documentation includes: StorNext File System Installation Guide: An installation guide for StorNext File System only for UNIX users that use the Command Line Interface (CLI) rather than the GUI The StorNext Installation Guide: A GUI-based installation guide for both the larger StorNext and StorNext File System products StorNext System Administratorss Guide: This guide goes into detail about system configuration and troubleshooting. StorNext File System Quick Reference Booklet: This booklet contains the most common file system CLI commands and uses StorNext Storage Manager Quick Reference Booklet: This booklet contains the most common storage manager CLI commands and uses StorNext File System Tuning Guide: This guide is directed at helping users optimize file system performance with specific tuning and configuration information Online Product Literature: This link connects to the ADIC web site where all product manuals and instructions are located.
Support
Use this procedure to access the StorNext Support information. 1 Click Help > Support.
64
Using the Help Menu
The StorNext Support screen appears
The StorNext Support screen includes the following information: Advanced Digital Information Corporation - The address and phone numbers to ADIC corporate headquarters Technical Assistance - Phones numbers and an e-mail address for technical support around the world
About
Use this procedure to access the StorNext About information. 1 Click Help > About.
65
The StorNext About screen appears
The About screen contains the following information about StorNext: File System - The version and build number of the file system you are running Storage Manager - The File and Library Manager build numbers GUI - The GUI build number Database - The database version number Perl - the Perl version number Web Server - The Web Server version number and type of web server used Operating System - The operating system version number
66
Using the Help Menu
4
File System Management
This chapter describes how to manage file systems, including configuration and administration tasks. Some tasks have a single procedure that is used to complete them. Others can be done in a variety of ways, either through the Advanced Pages, through the StorNext Shortcuts, or by using the Command Line Interface (CLI). Where applicable, each method of completing the task is presented. This chapter covers these topics: Operations on page 67 File Systems on page 83 Stripe Groups on page 90 Disks on page 98 Affinities on page 101
Operations
This section outlines tasks that can be performed on an individual basis while administering your file system. They do not have to be used in any particular order, or with any other tasks to be successfully completed, except where noted. This section includes: Labeling Disk Devices on page 68 Labeling Disk Devices Using CLI on page 70 Globals on page 72 Name Servers on page 76 Trashcan Files and Directories on page 76 Making a File System on page 78 Making a File System Using CLI on page 81 Starting and Stopping the File System Using the GUI on page 80 Starting and Stopping SNFS Using CLI on page 81 Mounting or Unmounting a File System Using the GUI on page 82 Unmounting or Mounting a File System Using CLI on page 83
67
Labeling Disk Devices

Each drive used by SNFS must be labeled. A new drive needs to be labeled only one time. A drive can be labeled from any StorNext server or client that has a Fibre Channel (FC) connection to the drive. Use the following procedures to label disk devices. Labeling Disk Devices Using the GUI Labeling Disk Devices Using CLI on page 70 Labeling a disk device will result in a complete loss of data on that disk device.
CAUTION
Labeling Disk Devices Using the GUI

Use this procedure to label a disk device using the Advanced Pages. 1 From the SNFS Home Page, click Admin > Label Disk Devices. The Label Disk Device screen appears.
Note
Greyed out devices in the Disk Devices list are in use by a configured file system.
From this screen, you can perform these tasks: Select Label Type - Enables you to select VTOC or EFI label types for your disks Label - Enables you to label any unused devices or relabel any device
68
Operations
Unlabel - Enables you to unlabel any device in use by the file system
CAUTION
If you unlabel a device all data on that device will be lost. Additionally, the unlabeled device will no longer be used by the file system until it is relabeled.
Probe - Allows you to pulse a disks activity light 2 From the Unused Disk Devices list, select a device to label and click Label. You are prompted to select a VTOC label for disks less than 1TB in size.
Click OK. You are warned that the device may have a file system on it and labeling it will destroy any data.
Make sure the disk you are labeling is empty and click OK.
Enter a name or accept the default and click OK. You are prompted that all data will be lost if you label this device.
Click OK to label the device. The Label Disk Devices Status screen appears.
Click Close when the status displays Success.
69
The Label Disk Device screen appears with the label you created.
Labeling Disk Devices Using CLI

Each drive used by SNFS must be labeled. A new drive only needs to be labeled one time. A drive can be labeled from any StorNext server or client that has a Fibre Channel (FC) connection to the drive. Use this procedure to label a disk device using CLI. The process of disk labeling re-partitions the drives. If you select an incorrect drive, you may lose data.
CAUTION
On a SNFS client, at the system prompt, display a list of connected drives. Type: /usr/cvfs/bin/cvlabel -l The command output is similar to this:
Device Name
Device
Volume Type/ Label
Sectors
Sector Size
/dev/sdb [SEAGATE ST19171FS 0018] unknown Sectors: 17691712. Sector Size: 512. /dev/sdc [SEAGATE ST19171FS 0018] unknown Sectors: 17691712. Sector Size: 512. /dev/sdd [SEAGATE ST19171FS 0018] unknown Sectors: 17691712. Sector Size: 512.
70
Operations
Note
2 3 4
Output example shown will differ from the output you will see, but will be similar in structure and information.
In the output information, identify any drives that are unused or do not have a recognized Volume Type and write down their associated device names. In the /usr/cvfs/config/cvlabels file, delete any lines that refer to disks that will not be labeled or that have already been labeled. Create /usr/cvfs/config/cvlabels. Type: /usr/cvfs/bin/cvlabel -c > /usr/cvfs/config/cvlabels The created file displays an entry for disks located by the /usr/cvfs/bin/cvlabel command. CvfsDisk_UNKNOWN /dev/sdb # host 4 lun 1 sectors 639570752 ... CvfsDisk_UNKNOWN /dev/sdc # host 4 lun 2 sectors 639570752 ... CvfsDisk_UNKNOWN /dev/sdd # host 4 lun 3 sectors 639570752 ...
Note
CAUTION
Identify any drives that already contain a recognized Volume Type. Do not write a label to these drives or you may lose data.
Edit /usr/cvfs/config/cvlabels file to provide a unique name for each drive to be used by SNFS. In this example, the _UNKNOWN variable in the drive name associated with disk device /dev/sdb has been renamed to a numeral (in sequence) 0,1,and 2. The disk devices have also been alphabetically ordered. CvfsDisk0 /dev/sdb # host 4 lun 1 sectors 639570752 ... CvfsDisk1 /dev/sdc # host 4 lun 2 sectors 639570752 ... CvfsDisk2 /dev/sdd # host 4 lun 3 sectors 639570752 ...
Note
6 7
Save the /usr/cvfs/config/cvlabels file. Use the cvlabel command to label the disks. Type: /usr/cvfs/bin/cvlabel /usr/cvfs/config/cvlabels For each disk, you are prompted if you are sure if you want to label each disk. Type Y for yes.
71
Globals
The global section of the file system configuration file contains general parameters that control feature enable/disable, system performance, and components related to the file systems resource consumption. For most of these parameters, it is only necessary to restart the File System Manager (FSM) to cause the modified parameter to take effect. However, the following parameters require that the file system be fully re-initialized (this will result in data loss) before they take effect. If a parameter change requires file system re-initialization, the system will notify the administrator in the system log. The initial configuration of the following parameters should be carefully planned in order to reduce the number of file system remakes: For the StorNext GUI: File System Block Size Windows Security
For CLI: FSBlockSize WindowsSecurity
The global section also contains several parameters that can dramatically improve or degrade system performance. For more information, refer to Viewing a Fibre Channel Device on page 273. Exercise caution when modifying performance parameters. A key performance parameter is: For the StorNext GUI: Inode Cache Size
For CLI: InodeCacheSize Before making any changes to the file systems configuration, carefully review the cvfs_config(4) man pages or the CVFS Configuration File help file. Use the following procedures to modify global settings. Modifying Global Settings Using the GUI on page 73 Modifying Global Settings Using CLI on page 75
72
Operations
Modifying Global Settings Using the GUI

This task describes how to modify global configuration settings. These settings affect all stripe groups in the file system. 1 Access the SNFS Home Page and click Config > Globals. The Modify Global Settings screen appears.
2 3
In the File Systems drop-down menu, select a file system. After selecting the file system, type valid values in the fields, check boxes, and scroll list on the Modify Global Settings page. File System Block Size: This value defines the granularity of the file system's allocation size. The default setting is 16,384. The block size must be specified in powers of 2. Inode Cache Size: This value defines the number of inodes that can be cached in the SNFS server. The default and minimum setting for the cache size is 16. Maximum Log Size: This value defines the maximum number of bytes (size) to which a SNFS Server log file can grow. When the log file reaches the specified size, it is rolled and a new log is started. In this situation, the two log files could use twice the maximum log size space specified in this field. The range is from 1 to 256 megabytes. Maximum Number of Logs: Number of rolled logs that are kept Journal Size: Size of the file system journal in bytes
73
Thread Pool Size: This value defines the number of client pool threads to be activated and used by the SNFS server. This setting affects system performance. There should be at least two threads per client. Increasing the number of threads will improve file system response time in operations that affect allocation and meta-data functions. The range is from 8 to 1024 threads. Migrating File System: Enable this option (check the box) if the data on the file system should be migrated to tertiary storage. Migration cannot be disabled once it is enabled.
Note
Trashcan: Enable this option (check the box) to enable Trashcan functionality on the file system. Trashcan cannot be disabled once it is enabled.
Note
Global Super User: Enable this option (check the box) to allow a user with super-user privileges to assert these privileges on the file system. If the Global Super User option is enabled, then super users have global access rights on the file system. This selection is the same as the maproot=0 directive in the Network File System (NFS). If the Global Super User option is not enabled, then super users can only modify files that they can access, like any other users.
Note
Windows Security: Enable this option (check the box) to allow all Windows clients to use Microsoft Windows native security. If this option is enabled, then a Windows administrator may set Windows security on all files and directories for any user or group defined on the local Windows client or Windows domain. Use Physical Memory Only: When this option selected, the file system will use only physical memory, not swapped or paged Quotas: Enable enforcement of user and group quotas (disabled is the default setting) Inode Expansion Blocks: Use these fields to configure the minimum (floor), maximum (ceiling), and increment of the block allocation size for a dynamically expanding file. Minimum: This value specifies the minimum number of blocks allocated when a file requires additional space. Maximum: This value specifies the maximum number of blocks allocated on subsequent expansion. The range is from 1 to 32768 blocks. Increment: When the allocation space is exhausted, this value specifies the increment added to the last allocation size, up to the maximum number of file system blocks.
74
Operations
Debug Log Settings: Settings to turn on debug functions for the file system server. The log information may be useful if a problem occurs. An ADIC Technical Assistance Center (ATAC) representative may ask for certain debug options to be activated to analyze a file system or hardware problem. Disable Debugging: Disables detailed file system eebug tracing File system performance can be significantly reduced by turning on debug traces.
Note
LDAP Configuration UNIX File Creation Mode on Windows - Mode bits for UNIX files UNIX Directory Creation Mode on Windows - Mode bits for UNIX directories UNIX ID Fabrication on Windows - Allows you to enable or disable the use of fabricated IDs an a per-file system basis. If it is configured to Yes, then Windows User IDs will be mapped using Fabricated IDs. The default value for enabling Fabrication is based on the type of StorNext server you are using. On Windows, the default is No. 4 5 UNIX Nobody UID on Windows - UNIX user ID if no other mapping can be found UNIX Nobody GID on Windows - UNIX group ID if no other mapping can be found
Click Apply. The Modify Global Setting Status screen appears. Once the status screen indicates that the global settings have been modified, click Close.
Modifying Global Settings Using CLI

Use this procedure to modify system global settings using CLI. 1 Unmount the file system. Type: unmount <file_system_name> Where the file system name is the name of the file system where the settings are being modified 2 Stop the file system. Type: /usr/cvfs/bin/cvadmin snadmin> stop <file_system_name> snadmin> quit where snadmin is the prompt shown after invoking the cvadmin command. 3 Edit the configuration file. Type: edit /usr/cvfs/config/<file_system_name>.cfg 4 5 Make the appropriate edits to the configuration file. Restart the file system. Type: /usr/cvfs/bin/cvadmin snadmin> start <file_system_name> snadmin> activate <file_system_name> snadmin> select snadmin> quit StorNext System Administrator Guide 75
Mount the file system. Type: mount -t cvfs <file_system_name> <mount_point> For example: mount -t cvfs snfs1 /stornext/snfs1
Name Servers
The SNFS fsnameservers file specifies machines serving as File System Name Server coordinator(s) to the fsmpm daemon. The File System Name Server coordinator is a critical component of the StorNext File System Services (FSS). A principal function of the coordinator is to manage failover voting in a high-availability configuration. Therefore, it is critical to select highly reliable systems as coordinators. Redundancy is provided by listing multiple machine entries in the fsnameservers file, one entry per line. The first machine listed is the primary coordinator and any subsequent machines listed serve as backup coordinators. To create redundancy, it is recommended that you list two machines. Typically, the selected systems are also configured for FSM services, but this is not a requirement. If the fsnameservers file does not exist, then the file system operates as a local file system, requiring both a client and a server. The file system will not communicate with any other StorNext File System product on the network, thus eliminating the sharing of the FSS over the SAN. It is extremely important that all copies of /usr/cvfs/config/ fsnameserver file in a SAN be identical. A stale configuration on a system that is not in use can cause election problems if fsmpm processes are running with mismatched fsnameservers. It is also critical to verify that complete network connectivity exists between all systems running SNFS (client or server). This is important because all StorNext systems participate in the failover process.
CAUTION
After you type the IP addresses of two reliable machines on your network in the fsnameservers file, copy the fsnameservers file to every machine running SNFS. After changing the fsnameservers file, always restart (stop and start) all file system services running on the SNFS. Redundant NICs are supported in the fsnameservers file; simply list both NIC addresses in the file.
Trashcan Files and Directories

The Trashcan allows you to recover undeleted files or directories from a StorNext file system using any supported operating system. The Trashcan can only be enabled on managed file systems. If the Trashcan feature is disabled on a managed file system, data on the file system is still automatically archived to tape. Use the following procedures to enable or disable the Trashcan. Enabling the Trashcan Using the Configuration Wizard on page 77 Enabling the Trashcan Using the Globals Page on page 77 Enabling or Disabling the Trashcan Using CLI
76
Operations
Note
Trashcan functionality is not supported in the root directory of the file system. If your Trashcan is set up in the root, files and directories will continue to be removed from the file system, but they will not be recoverable.
Note
To improve file system performance, the Trashcan can be disabled.
Enabling the Trashcan Using the Configuration Wizard

Enabling the Trashcan using the Shortcuts method is only done though the Configuration Wizard during the installation of StorNext.
Enabling the Trashcan Using the Globals Page

For information on using the Globals page to enable the Trashcan, refer to Modifying Global Settings Using the GUI on page 73.
Enabling or Disabling the Trashcan Using CLI

Use this procedure to enable the Trashcan. 1 Stop the Trashcan Manager (TCM). Type: /usr/adic/TCM/bin/TCM_control stop 2 Edit the /usr/adic/TCM/config/trashcan.config file to enable or disable the trashcan for defined file systems. Refer to the trashcan.config README for file system entries and examples. Start the TCM. Type: /usr/adic/TCM/bin/TCM_control start
CAUTION
Disabling the Trashcan from a file system configuration after the file system has been in use for a while could result in abnormal behavior.
77
Making a File System

This task destroys all existing data for the selected file system and creates a new configuration. Use the following procedures to make or re-make a file system. Making a File System Using the GUI Making a File System Using CLI on page 81 Making or re-making a file system will result in a complete loss of user data.
CAUTION
CAUTION
After creating a relation point on a managed file system, you must delete and recreate the file system, not just remake.
Conditions to Make or Re-Make a File System

The following are reasons to make or re-make a file system. Creating a new file system Removing a stripe group from the file system Removing a disk from a stripe group Changing a stripe group's stripe breadth Changing the sector count of a disk
Making a File System Using the GUI

Use this procedure to make a file system. 1 Access the SNFS Home Page and click Admin > Make File Systems.\
78
Operations
The Make File System screen appears.
79
In the File Systems list, select a new or existing file system and click Apply. A confirmation screen warns that all relation points on the system will be removed during this process and prompts if you still want to make the selected file system.
Click OK. A second confirmation screen warns that all data will be lost on the selected file system.
Click OK. A status screen appears.
Once the status screen indicates success, click Close.
Starting and Stopping the File System Using the GUI

This task enables you to start or stop a file system. You need to stop a file system if you want to take it out of service to make configuration changes or perform other administrative tasks. You need to start a file system to place it back into service. 1 Access the SNFS Home Page and click Admin > Start/Stop File System. The Start or Stop File System screen appears.
Note
Greyed out file systems in the Start or Stop File System screen require a metadata dump in order to be started.
Start or stop a file system. Select a file system from the Inactive File Systems list and click Start. The Start Stop File System Status screen appears. Select a file system from the Active File Systems list and click Stop. The Start Stop File System Status screen appears.
Once the status screen displays the successful completion of the task, click Close.
80
Operations
Making a File System Using CLI

Use this procedure to make a file system using CLI. 1 2 Log on to the machine as root. Make sure you are at the root directory. Type: cd / 3 Unmount the system. Type: umount <mount_point> where the <mount_point> is where you have mounted the SNFS. For example: umount /stornext/snfs1 4 Stop the system. Type: /usr/cvfs/bin/cvadmin snadmin> stop <file_system_name> where the <file_system_name> is the name of the file system to be stopped. 5 Make the file system. Type: /usr/cvfs/bin/cvmkfs <file_system_name> 6 Start the system. Type: /usr/cvfs/bin/cvadmin snadmin> start <file_system_name> 7 Mount the system. Type: mount -t cvfs snfs1 /stornext/snfs1
Starting and Stopping SNFS Using CLI

Use this procedure to start SNFS using CLI. Type: /usr/cvfs/bin/cvadmin snadmin> select snadmin> start <file_system_name> snadmin> activate <file_system_name> where snadmin is the prompt shown after invoking the cvadmin command. Use this procedure to stop SNFS using CLI. Type: /usr/cvfs/bin/cvadmin snadmin> select snadmin> stop <file_system_name>
81
Mounting or Unmounting a File System

Use the following procedures to mount or unmount a file system. Mounting or Unmounting a File System Using the GUI Unmounting or Mounting a File System Using CLI on page 83
Mounting or Unmounting a File System Using the GUI

This task enables you to mount or unmount a file system. You need to unmount a file system if you want to take it out of service to make configuration changes or perform other administrative tasks. You need to mount a file system to place it back into service. If you are running StorNext, you must stop the SNSM component before you unmount the file system. Refer to Use this procedure to stop SNFS using CLI. Type: on page 81. The StorNext GUI does NFS export / unexport on mount / dismount. 1 Access the SNFS Home Page and click Admin > Mount/Unmount. The Mount or Unmount File System screen appears.
Note
Mount or unmount a file system. Select a file system from the Unmounted File Systems list and click Mount. The Mount File System Status screen appears. Select a file system from the Mounted File Systems list and click Unmount. The Unmount File System Status screen appears.
3 82
Once the status screen displays the successful completion of the task, click Close. Operations
Unmounting or Mounting a File System Using CLI

Use this procedure to unmount a file system using CLI. 1 Change directories to the root. Type: cd / 2 Unmount the system. Type: umount <mount_point> where the <mount_point> is where you are mounting the SNFS. For example: umount /stornext/snfs1 Use this procedure to mount a file system using CLI. 1 Change directories to the root. Type: cd / 2 Mount the system, type: mount -t cvfs <file_system_name> <mount_point> where the <mount_point> is where you are mounting the SNFS. For example: mount -t cvfs snfs1 /stornext/snfs1
File Systems
The following tasks outline the processes for creating, modifying, and using both the GUI method or through CLI. This section includes: Creating a File System Using the GUI Creating a File System Server Using CLI on page 85 Adding a File System Client Using CLI on page 86 Modifying a File System on page 87 Expanding a File System on page 88 Deleting a File System Using the GUI on page 89
83
Creating a File System Using the GUI

Note
Creating a file system in the following method is an advanced task and is simplified using the Configuration Wizard.
Use this procedure to create a file system. 1 Access the SNFS Home Page and click Config > File System. The Configure File System screen appears.
Click Add to continue. The Add File System screen appears.
Type a name and mount point for the new file system and click OK. A status screen appears.
4 5 6 7
When the status screen indicates that the file system has been added, click Close. Configure global settings for the file system. For instructions, refer to Modifying Global Settings Using the GUI on page 73. Add disks to the file system. For instructions, refer to Adding Disks on page 98. Configure stripe groups for the file system. For instructions, refer to Adding a Stripe Group on page 90.
Note
Make sure that each stripe group is associated with no more than one affinity when using disk-to-disk migration.
Make the file system. For instructions, refer to Making a File System Using the GUI on page 78.
84
File Systems
Start the file system. For instructions, refer to Starting SNSM / SNFS on page 61
10 Mount the file system. For instructions, refer to Mounting or Unmounting a File System Using the GUI on page 82. 11 Add affinities to the file system. For instructions, refer to Modifying an Affinity on page 103.
Note
You can only define up to two affinities per file system when using disk-to-disk relocation.
Creating a File System Server Using CLI

CAUTION
Do not attempt to perform the procedures in this section unless you have completed ADICs StorNext training and are confident you understand all procedures. (You may perform these procedures if Professional Services is assisting you.)
Note
Before initially executing any SNFS command line programs, you are required to source either the .profile or the .cshrc file. This updates the user environment with the SNFS environment variables. If you are running sh, ksh, or bash, type: . /usr/adic/.profile For all other shells, type: source /usr/adic/.cshrc
Use this procedure to install the file system server using CLI. 1 2 Install StorNext. For instructions, refer to the chapter in the StorNext File System Installation Guide that applies to your operating system. Write the list of system and FC disks to a file in a format recognized by the cvlabel command. Type: /usr/cvfs/bin/cvlabel -c > /usr/cvfs/config/cvlabels The created file displays an entry for disk located by the /usr/cvfs/bin/cvlabel command. CvfsDisk_UNKNOWN /dev/sdb # host 4 lun 1 sectors 639570752 ... CvfsDisk_UNKNOWN /dev/sdc # host 4 lun 2 sectors 639570752 ... CvfsDisk_UNKNOWN /dev/sdd # host 4 lun 3 sectors 639570752 ...
Note
3
Edit the cvlabels file which has a list of all system and FC disks visible on the machine. Edit the file to remove all the system disks and any FC disks you do not want labeled or are already labeled. Label the FC drives. Type: /usr/cvfs/bin/cvlabel /user/cvfs/config/cvlabels
85
Copy the example file system configuration file to the config directory. Type: cp /usr/cvfs/examples/example.cfg /usr/cvfs/config/ <file_system_name>.cfg
6 7
Edit the StorNext configuration file created in Step 5 to include the desired settings, disks, and stripe groups. Copy the fsnameservers file to the config directory. Type: cp /usr/cvfs/examples/fsnameservers.example /usr/cvfs/config/ fsnameservers
8 9
Edit the fsnameservers file to include the IP address of the host. Copy the example fsmlist file to the config directory. Type: cp /usr/cvfs/examples/fsmlist.example /usr/cvfs/config/fsmlist
10 Edit the fsmlist file created in step 9 to include the name of those file systems to start at boot time. 11 Obtain your license.dat from ATAC. For contact information, refer to Customer Assistance on page 227. 12 Place the license.dat file in the /usr/cvfs/config directory. 13 Make the file system. Type: /usr/cvfs/bin/cvmkfs <file_system_name>
CAUTION
When you run the cvmkfs command, you will lose any data on the file system at that time.
14 Reboot the machine. 15 Verify that the labeled drives are available to the file system. Type: /usr/cvfs/bin/cvlabel -l 16 Restart the file system. Type: /usr/cvfs/bin/cvadmin snadmin> start <file_system_name> snadmin> activate <file_system_name> snadmin> select <file_system_name> snadmin> show snadmin> who snadmin> quit 17 Mount the system. Type: mount -t cvfs <file_system_name> <mount_point> For example: mount -t cvfs snfs1 /stornext/snfs1
Adding a File System Client Using CLI

Use this procedure to add a file system client using CLI. 86 File Systems
1 2
Install StorNext. For instructions, refer to the chapter in the StorNext File System Installation Guide that applies to your operating system. Copy the example fsnameservers file to the config directory. Type: cp /usr/cvfs/examples/fsnameservers.example /usr/cvfs/config/ fsnameservers
3 4 5 6
Edit the fsnameservers file created in step 2 to add the IP address or host name of the SNFS server. Edit the /etc/fstab file to mount on boot (for Solaris, edit the /etc/vfstab file). Reboot the machine. Validate the system has mounted. Type: df -k If your machine did not mount on boot, refer to Resolving Installation Problems in the StorNext File System Installation Guide.
Modifying a File System

This section describes how to manage all aspects of modifying a file system.
Note
Before initially executing any SNFS command line programs, you are required to source either the .profile or the .cshrc file. This updates the user environment with the SNFS environment variables. If you are running sh, ksh, or bash, type: . /usr/adic/.profile For all other shells, type: source /usr/adic/.cshrc
Use this procedure to modify the configuration of an existing file system. Changes to an existing file system may include adding or modifying a stripe group, adding disks, adding affinities, and performance tuning.
Note
This procedure assumes that the file system exists with at least two stripe groups.
1 2 3
Unmount the file system. For instructions, refer to Mounting or Unmounting a File System Using the GUI on page 82. Stop the file system. For instructions, refer to Use this procedure to stop SNFS using CLI. Type: on page 81. Make the appropriate changes to the file system. Refer to: Globals on page 72. Expanding a File System on page 88. Modifying an Affinity on page 103. Adding Disks on page 98.
87
Adding a Stripe Group on page 90. Modifying a Stripe Group on page 93. 4 5 Start the file system. For instructions, refer to Starting SNSM / SNFS on page 61. Mount the file system. For instructions, refer to Mounting or Unmounting a File System Using the GUI on page 82.
Expanding a File System

Expanding an existing file system enables you to allocate additional storage to that file system. Additional storage is added by creating a new stripe group in the file system configuration file and assigning new disks to the stripe group.
Note
You cannot expand a metadata stripe group.
Use the following procedures to expand a file system. 1 2 3 4 5 Unmount the file system. See Mounting or Unmounting a File System Using the GUI on page 82. Stop the file system. See Starting and Stopping the File System Using the GUI on page 80. Label as many disks as you are going to add (to expand your file system. See Labeling Disk Devices Using the GUI on page 68. Select the file system to add the disk devices to. See Adding Disks on page 98. Do one of the following: Add a stripe group to the disks you just labeled and added in steps 3 and 4. See Adding a Stripe Group on page 90. or Add a disk to one of the exisiting stripe groups by using the Modify Stripe Group page. See Modifying a Stripe Group on page 93. ADIC recommends that you add a stripe group.
Note
6
When the Status screen displays Success, click OK.
Note
The GUI runs a check on the expanded file system that may take up to three hours, depending on the configuration and size of the file system.
88
File Systems
Deleting a File System Using the GUI

Use this procedure to delete a managed file system. 1 From the SNFS Home Page click Config > File System. The Configure File System screen appears.
Select a file system and click Delete. You are warned that this operation cannot be undone and asked if you are sure that you want to continue.
Click OK.
89
You are warned that deleting the files system deletes all files and directories on the file system.
4 5
Click OK. Click Close when the Status Screen displays Success.
Stripe Groups
A stripe group is a logical volume in a file system that consists of one or more disks used to store metadata information, journaling information and/or user data. A file system can contain multiple stripe groups. A stripe group contains definitions about read and write permissions, real time I/O constraints, a stripe breadth definition, multi-pathing methodology, and/or an affinity association. Configuring a stripe group consists of the following tasks: Adding a Stripe Group Modifying a Stripe Group on page 93 Deleting a Stripe Group on page 96
Adding a Stripe Group

Use this procedure to add a stripe group. 1 Access the SNFS Home Page and click Config > Stripe Groups.
90
Stripe Groups
The Configure Stripe Groups screen appears.
In the File Systems drop-down menu, select a file system and click Add. The Add Stripe Group screen appears.
Name: The name of the new stripe group. Breadth: The breadth size is the number of file system blocks that the system reads/writes before moving to the next disk in the stripe group. This value should be optimized for the major application that uses the disks. The default setting is 64. StorNext System Administrator Guide 91
Available Disks: Disks available to the stripe group. To populate this list, you must first add disks to the file system. Navigate to the SNFS Home page, select Config > Disks, select the file system, click Add, and add one or more disks.
Note
Disks in Stripe Group: Disks associated with the new stripe group. Available Affinities: Affinities associated with existing stripe groups that, if selected, would also apply to this stripe group. Affinities in Stripe Group: Affinities associated with the new stripe group. Metadata, Journal, and Exclusive: Enable one or more of these options (check the boxes) to create a location for metadata and journaling on the stripe group. To enable metadata and journaling to be placed on the new stripe group, but not user data, select the Metadata, Journal, and Exclusive check boxes. Do not associate an affinity with a metadata, journal, or an exclusive stripe group. To enable only metadata to be placed on the new stripe group, select both the Metadata and Exclusive check boxes. To enable only journaling to be placed on the new stripe group, select both the Journal and Exclusive check boxes. Journaling can only be enabled on one stripe group. If the Metadata and/or Journal boxes are not checked on any of the stripe groups in this file system, default settings cause metadata and journaling to be placed on the first defined stripe group.
Note
Realtime IO/sec (optional): The number of disk I/O operations per second that are available to real-time applications. This is an optional setting and can be left blank. Realtime MB/sec (optional): The number of megabytes per second that are available to realtime applications. This is an optional setting and can be left blank. Non-realtime IO/sec (optional): The number of disk I/O operations per second that are available to non-realtime applications. If both Non-realtime IO/sec and Non-realtime MB/sec Fields are selected, then the system uses the lower of the two values. This is an optional setting and can be left blank. Non-realtime MB/sec (optional): The lower threshold (in MB per second) that is reserved for non-realtime applications. If both Non-realtime MB/sec and Non-realtime IO/sec Fields are selected, then the system uses the lower of the two values. This is an optional setting and can be left blank. 3 4 Type valid values for the new stripe group and click OK. Once the status screen indicates that the new stripe group has been added, click Close.
92
Stripe Groups
Modifying a Stripe Group

Use this procedure to modify a stripe group configuration. 1 Access the SNFS Home Page and click Config > Stripe Groups. The Configured Stripe Groups screen appears.
Select the stripe group to modify. a. In the File Systems drop-down menu, select the file system. b. In the Stripe Groups list, select the stripe group to modify.
Click Modify.
93
The Modify Stripe Group screen appears.
Stripe Group - The selected stripe group. Available Disks - Disks available to the stripe group. To populate this list, you must first add disks to the file system. Navigate to the SNFS Home page, select Config > Disks, select the file system, click Add, and add one or more disks.
Note
Disks in Stripe Group - Disks associated with the stripe group. Available Affinities - Affinities associated with existing stripe groups that, if selected, would also apply to this stripe group. Affinities in Stripe Group - Affinities associated with the stripe group. Status - The status of the stripe group, either online or offline. Select Up to put the stripe group online. Select Down to take the stripe group offline. Data stored in the stripe group is unavailable when the status is Down.
Metadata, Journal, and Exclusive - Enable one or more of these options (check the boxes) to create a location for metadata and journaling on the stripe group. To enable metadata and journaling to be placed on the new stripe group, but not user data, select the Metadata, Journal, and Exclusive check boxes. Do not associate an affinity with a metadata, journal, or an exclusive stripe group. To enable only metadata to be placed on the new stripe group, select both the Metadata and Exclusive check boxes.
94
Stripe Groups
To enable only journaling to be placed on the new stripe group, select both the Journal and Exclusive check boxes. Journaling can only be enabled on one stripe group. If the Metadata and/or Journal boxes are not checked on any of the stripe groups in this file system, default settings cause metadata and journaling to be placed on the first defined stripe group. If the file system was made, the metadata cannot be removed.
Note
Realtime IO/sec (optional) - The number of disk I/O operations per second that are available to real-time applications. This is an optional setting and can be left blank. Realtime MB/sec (optional) - The number of megabytes per second that are available to realtime applications. This is an optional setting and can be left blank. Non-realtime IO/sec (optional) - The number of disk I/O operations per second that are available to non-realtime applications. This is an optional setting and can be left blank. Non-realtime MB/sec (optional) - The lower threshold (in megabytes per second) that is reserved for non-realtime applications. This is an optional setting and can be left blank. 4 5 Type valid values for the modified stripe group and click OK. Once the screen indicates that the stripe group has been modified, click Close.
95
Deleting a Stripe Group

Use this procedure to delete a stripe group. Deleting a stripe group causes a complete loss of data and requires re-make of the file system. Refer to Making a File System on page 78.
CAUTION
Access the SNFS Home Page and click Config > Stripe Groups. The Configure Stripe Group screen appears.
Select the stripe group to delete. a. In the File Systems drop-down menu, select the file system. b. In the Stripe Groups list, select the stripe group to delete.
Click Delete. A confirmation screen prompts if you want to delete the stripe group.
Click OK. The Delete Stripe Group Status screen appears.
Once the status screen indicates that the stripe group has been deleted, click Close.
96
Stripe Groups
Configuring a Stripe Group Using CLI

The following is an example of a stripe group configuration in a file system configuration file, for example, refer to The example.cfg File on page 277. You can modify any of these variables using a text editor. (The following values may not be representative of typical definitions.) Modifying these variables may result in a complete loss of user data and a re-make of the file system: Metadata StripeBreadth Removing a Node [StripeGroup StripeGroup1] Status UP Exclusive Yes MetaData Yes Journal Yes Read Enabled Write Enabled StripeBreadth 16 MultiPathMethod Rotate Node fortune1 0 [StripeGroup StripeGroup2] Status UP Affinity media1 Read Enabled Write Enabled StripeBreadth 16 Rtios 100 Rtmb 100 RtiosReserve 100 RtmbReserve 100 MultiPathMethod Rotate Node fortune2 0
CAUTION
97
Disks
A disk may be used as an individual element or as one of many disks in a Redundant Array of Inexpensive Disks (RAID). A disk may contain metadata information, journaling, and/or data. A disk can constitute a single stripe group itself or can be one node of a multi-disk stripe group. A disk can be a local hard disk located inside a server (if only a metadata disk), or most commonly, used in a RAID visible to all machines in the Storage Area Network (SAN) over FC. Use the following procedures to manage disks (add disks, delete disks, label disks, and defragmenting disks). Each disk is assigned to a disk type that specifies the number of sectors on the disk. Adding Disks Deleting Disks on page 100 Labeling Disk Devices on page 68 Defragmenting a Disk on page 101
Adding Disks
Use this procedure to add disk to a selected file system. 1 Access the SNFS Home Page and click Config > Disks. The Manage Disks screen appears.
98
Disks
In the File Systems drop-down menu, select a file system and click Add. The Add Disk screen appears.
3 4
In the Available Disks scroll list, select one or more disks and click OK. The Add Disk Status screen appears. Once the status screen indicates that the disk has been added, click Close. The Manage Disks screen appears with the added disk in the disks list.
99
Deleting Disks
Use this procedure to delete disk from a selected file system. If you delete a disk that was used in a stripe group, this results in a complete loss of user data and requires a re-make of the file system. Refer to Making a File System on page 78.
CAUTION
From the SNFS Home Page click Config > Disks. The Manage Disks screen appears.
Delete a disk from a selected file system. a. On the File Systems drop-down menu, select the file system. b. In the Disks list, select the disk to delete from.
Click Delete. A confirmation screen prompts if you want to delete the disk.
Click OK. The Delete Disk status screen appears.
Once the status screen indicates that the disk has been deleted, click Close.
100
Disks
Defragmenting a Disk
This procedure describes how to defragment a disk using the snfsdefrag utility to relocate SNFS file data into a single, pre-allocated extent. Reducing the number of extents in a file improves system performance by minimizing disk head movement when I/O occurs. You can defragment a single file or multiple files, perform a recursive defragment on files in a directory, or defragment the entire file system. 1 Log on a metadata controller as root.
Note
The metadata controller is the computer where the StorNext server (not the client) is installed.
Defragment a file(s) on disk, a directory, or the entire file system. To defragment a single file or a list of files, type: /usr/cvfs/bin/snfsdefrag <filename> [filename ....] To perform a recursive defragment on files in a directory, type: /usr/cvfs/bin/snfsdefrag -r <directory_name> If the directory_name value is equal to the mount point, then the entire StorNext file system is defragmented.
Note
For more information about using the snfsdefrag command, refer to the snfsdefrag(1) man pages.
Affinities
An affinity is a label assigned to one or more stripe groups. An affinity enables a user to direct data to its associated stripe groups. A file system can have one or more affinities associated with it. These associations are defined in stripe groups. An association is made with the affinity key to a directory or file. If a directory association is created with Affinity aff1, then all data written to that directory is written to StripeGroup StripeGroup2, and therefore only to Disk disk2. If an association is made with Affinity aff2, and a separate directory in the file system, then all data is directed to StripeGroup StripeGroup3 which contains three disks; disk3, disk4, and disk5. All data is written to these disks when directed to the associated directory with Affinity aff2. This section includes: Adding an Affinity on page 102 Modifying an Affinity on page 103 Deleting an Affinity on page 105 File System Configuration Restrictions on page 106
101
Adding an Affinity
Use this procedure to add an affinity to an existing file system. 1 Access the SNFS Home Page and click Config > Affinities. The Add, Modify, or Delete Affinities screen appears.
Click the Add button to continue. You are warned to stop the Storage Manager and the File System if you have not already done so.
Click OK. The Add Affinity screen appears.
Select a Stripe Group with which to associate the affinity, type a name for the affinity in the Affinity Name Field, and click OK to continue.
102
Affinities
Note
5
An exclusive, metadata, or journal stripe group, or a stripe group on a managed file system with a configured affinity cannot be selected.
When the Status Screendispays success, click Close. You are returned to the Add, Modify, or Delete Affinities screen where the newly added affinity appears in the Affinities list.
Modifying an Affinity
Use this procedure to modify an affinity on a configured file system. 1 2 3 If the file system is mounted, unmount the file system. For instructions, refer to Mounting or Unmounting a File System Using the GUI on page 82. If the file system is started, stop the file system. For instructions, refer to Starting and Stopping the File System Using the GUI on page 80. Modify the affinity.
103
a. Access the SNFS Home Page and click Config > Affinities. The Add, Modify, or Delete Affinities screen appears.
b. In the File Systems drop-down menu, select a file system. c. In the Affinity list, select an affinity. d. Click Modify. The Modify Affinity screen appears.
e. Select the stripe group(s) to associate the affinity with. The Modify Affinity status screen appears. f. Once the status screen indicates that the affinity has been modified, click Close. The Add, Modify, or Affinity Status screen appears.
104
Affinities
4 5
Start the file system. For instructions, refer to Making a File System Using CLI on page 81. Mount the file system. For instructions, refer to Mounting or Unmounting a File System Using the GUI on page 82.
Deleting an Affinity
Use this procedure to delete an affinity on a configured file system.
CAUTION
Deleting affinities from a file system configuration after the file system has been in use for a while could result in abnormal behavior. Contact ATAC before deleting affinities from a file system configuration.
1 2 3
If the file system is mounted, unmount the file system. For instructions, refer to Mounting or Unmounting a File System Using the GUI on page 82. If the file system is started, stop the file system. For instructions, refer to Starting and Stopping the File System Using the GUI on page 80. Delete the affinity. a. Access the SNFS Home Page and click Config > Affinities. The Add, Modify, or Delete Affinities screen appears.
105
b. In the File Systems drop-down menu, select a file system. c. In the Affinity list, select an affinity. d. Click Delete. The Delete Affinity prompt appears. e. Click Yes. The Delete Affinity Status screen appears. f. 4 5 Once the status screen indicates that the affinity has been deleted, click Close.
Start the file system. For instructions, refer to Making a File System Using CLI on page 81. Mount the file system. For instructions, refer to Mounting or Unmounting a File System Using the GUI on page 82.
File System Configuration Restrictions

When using affinities, the StorNext administrator must adhere to the file system configuration restrictions listed below to enable proper execution of data management policies. These restrictions only apply to managed file systems. They do not apply to non-managed (SNFS-only) installations. Taking into account all managed file systems, no more than two unique affinity names can be used. However, these two affinity names can be re-used across file systems. All data stripe groups must have exactly one affinity association, but several stripe groups may be associated to the same affinity. This restriction does not apply to exclusive metadata/journal stripe groups. At least one policy class must be created to use the configured affinities. At least one data stripe group in each managed file system should be designated as non-exclusive. If this designation is not made, then writing to the area of the file system that is not associated with any of the affinities will result in an out of space error.
CAUTION
CAUTION
Deleting affinities from a file system configuration after the file system has been in use for a while could result in abnormal behavior. Contact ATAC before deleting affinities from a file system configuration.
Adding an Affinity Using CLI

This task lets you set stripe group affinities for assigning file locations to a specific file system stripe group. All subsequent allocations to a file that have been assigned a valid stripe group affinity will occur on the specified stripe group. Affinities may also be assigned to files and directories using the cvaffinity command. For more information about the cvaffinity command, refer to cvaffinity on page 232. 1 Unmount the file system. Type: umount <mount_point>
106
Affinities
where the <mount_point> is where you have mounted the SNFS. For example: umount /stornext/snfs1 2 Stop the file system using cvadmin. Type: /usr/cvfs/bin/cvadmin snadmin> stop <file_system_name> where the <file_system_name> is file system to which the affinity will be added. snadmin> quit 3 4 Using a text editor, open the file system (<file_system_name>.cfg)configuration file, where <file_system_name> is the name of the file system. Locate the stripe group section and select the stripe group to which you want to add the affinity. The following is a part of a stripe group configuration with an affinity definition: [StripeGroup StripeGroup2] Status UP Affinity aff1 Read Enabled Write Enabled StripeBreadth 16 Node disk2 0 StripeGroup StripeGroup3] Status UP Affinity aff2 Read Enabled Write Enabled StripeBreadth 16 Node disk3 0 Node disk4 1 Node disk5 2 If a directory association is created with Affinity aff1, then all data written to that directory is written to StripeGroup StripeGroup2, and therefore only to Disk disk2. If an association is made with Affinity aff2, and a separate directory in the file system, then all data is directed to StripeGroup StripeGroup3 which contains three disks; disk3, disk4, and disk5. All data is written to these disks when directed to the associated directory with Affinity aff2.
107
Add the affinity to the selected stripe group with a line entry in this format: Affinity <affinity_name> where <affinity_name> is the name of the affinity The following is an example of a stripe group configuration after an affinity was added. The affinity line is the flag for the Data1 stripe group. [StripeGroup Data1] Status UP Read Enabled Write Enabled Affinity data1_aff StripeBreadth 512 Node CvfsDisk2 0 Node CvfsDisk3 1
6 7
Save and close the configuration file. Start the file system using cvadmin. Type: /usr/cvfs/bin/cvadmin snadmin> start <file_system_name> snadmin> activate <file_system_name> snadmin> select <file_system_name> snadmin> show
Mount the file system. Type: mount -t cvfs <file_system_name> <mount_point> For example: mount -t cvfs snfs1 /stornext/snfs1
Create an affinity/directory association. Type: /usr/cvfs/bin/cvmkdir -k <affinity_name> <directory_name> For example: /usr/cvfs/bin/cvmkdir -k data1_aff /stornext/snfs1/video_data This associates the all data written to /stornext/snfs1/video_data with stripe group Data1 and, therefore, disks CvfsDisk2 and CvfsDisk3.
Performing a Metadata Dump

This procedure replaces any existing metadata dump data for the selected file system and should only be run if the metadata file has been lost or corrupted. 1 From the SNFS Home Page, click Admin > Metadata Dump.
108
The Metadata Dump of File System screen appears.
2 3
Select the file system to perform the metadata dump from and click Apply. When the Status Screen displays Success, click Close.
109
110
5
Library and Storage Disk Management
StorNext configures, allocates, and manages all components associated with libraries. Resources that can be used for libraries include a wide variety of storage drives and media. Once configured, StorNext performs automated and manual operations to ensure the libraries resources are operating at efficient levels and in stable states. StorNext also offers flexibility when maintaining or replacing library components by minimizing system downtime. This chapter includes the following topics: Managing Libraries Managing Drives on page 128 Managing Media on page 141 Managing Storage Disks on page 164
Managing Libraries
Managing libraries consists of the following tasks: adding a library, modifying a library, or deleting a library. Each of these tasks is described in this section.
Adding a Library
Use the procedure in this section to add libraries to StorNext. The StorNext Storage Manager (SNSM) component of StorNext supports three types of libraries: SCSI, Network (ACSLS or DAS), and Vault. SCSI: Select SCSI if you have a SCSI or a fibre channel-attached library. Network: Select Network if you have a network-attached library. There are two options from for a network-attached library, ACSLS or DAS. For more information on ACSLS and DAS, refer to the StorNext Release Notes. Vault: Select Vault if your library stores media that has been moved from a robotic library. A Vault library is a library used only to store media and cannot be reconfigured after it has been designated as a vault.
111
Depending on the library type, refer to the appropriate procedure to add the library to StorNext. Adding a SCSI Library on page 113 Adding an ACSLS Network Library on page 115 Adding a DAS Network Library on page 117 Adding a Vault Library on page 122 1 From the StorNext Home Page, click Config > Add Library. The Library Introduction screen appears and displays all configured libraries.
Do one of the following: Click Next and follow the procedure in Adding a SCSI Library on page 113 to add a SCSI library. Click Next and follow the procedure in Adding an ACSLS Network Library on page 115 to add an ACSLS network library. Click Next and follow the procedure in Adding a DAS Network Library on page 117 to add a DAS network library. Click Next and follow the procedure in Adding a Vault Library on page 122 to add a vault library.
112
Managing Libraries
Adding a SCSI Library

After you click Next on the Library Introduction screen, the Library Type screen appears. If you have no SCSI libraries configured, (when you click Next) you are informed that no SCSI devices were detected.
Select the SCSI option and click Next. The Library Name screen appears.
113
Accept the default or type a name in the Library Name Field and click Next. The Media Types screen appears.
Select a media type from the list and click Next. The SCSI Device screen appears.
114
Managing Libraries
Select a SCSI device from the list and click Next. The Complete Add Library Task screen appears.
5 6
Review your selections. Click Next to complete the task or Back to make changes. Once a status screen displays the successful addition of the library, click Close.
Adding an ACSLS Network Library

After you click Next on the Library Introduction screen, the Library Type screen appears. 1 Select the Network option, choose ACSLS from the drop-down menu, and then click Next.
115
Enter the fields on the Library Name screen.
Enter Name: The name of the library. This can be any name you choose. Enter Host Name: The actual host name or IP address of the ACSLS server. 3 Type valid values for each field and click Next. The Media Types screen appears.
116
Managing Libraries
Select a media type from the list and click Next. The Complete Add Library Task screen appears.
5 6
Adding a DAS Network Library

The Library Introduction screen shows the libraries that have been configured.
117
Click Next to add a DAS network library. The Library Type screen appears.
Click the Network option, select DAS from the drop-down list, and click Next. The DAS Configuration screen appears.
Do one of the following: Select the Failover option, or both the Failover and Dual Aisle options, click Next, and go to Adding a DAS Network Library with Failover on page 119. Select the Dual Aisle option (if applicable) or click Next, and go to Adding a DAS Network Library with or without Dual Aisle Configuration on page 121.
118
Managing Libraries
Note
For more information about failover or dual aisle configurations, contact ATAC. Refer toCustomer Assistance on page 227.
Adding a DAS Network Library with Failover

3a. On the Library Name screen, enter valid values and click Next.
Enter Name: The name of the library. This can be any name you choose Enter DAS Server Name: The name of the DAS server Enter DAS Client Name: The name of the DAS client configured on the DAS server Standby Server Host Name: Standby server host name configured on the network Standby Server Client Name: Standby server client name configured on the network
119
The Media Types screen appears.
3b. Use the drop-down lists to map the mail boxes (EIF ports) to specific media and click Next. The Complete Add Library Task screen appears.
120
Managing Libraries
3c. Review your selections. Click Next to complete the task or Back to make changes. 3d. Once a status screen displays the successful addition of the library, click Close.
Adding a DAS Network Library with or without Dual Aisle Configuration

3e. On the Library Name screen, enter valid values and click Next.
Enter Name: The name of the library. This can be any name you choose. Enter Host Name: The actual host name or IP address of the DAS server. Enter Client Name: The name of the client for the current configuration. It is queried by StorNext and automatically populated.
The Media Types Screen appears.
121
3f. Use the drop-down lists to map the mail boxes (EIF ports) to specific media and click Next. The Complete Add Library Task screen appears.
3g. Review your selections. Click Next to complete the task or Back to make changes. 3j. Once a status screen displays the successful addition of the library, click Close.
Adding a Vault Library

The Library Introduction screen shows the libraries that have been configured.
Click Next to add a vault library.
122
Managing Libraries
The Library Type screen appears.
Click the Vault option and click Next. The Library Name screen appears.
123
Accept the defaults or type a name for the library and click Next. The Complete Add Library Task screen appears.
4 5
Modifying a Library
This task enables you to modify a library. 1 From the SNSM Home Page and click Admin > Library > Config Library. The Configure Library screen appears.
2 124
In the Select Library list, select a library to modify and click Modify. Managing Libraries
The Modify SCSI Library screen appears and displays the selected library and its associated SCSI device.
3 4 5
In the Media Types list, select a media type. Click Apply. The Modify Library Status screen appears. Once the status screen indicates that the library has been modified, click Close.
Deleting a Library
This task enables you to delete a library.
Note
Before deleting a library: All media must be removed from the library. For more information see Removing or Moving Media on page 147.
All drives associated with the library must be deleted. For more information see Deleting a Tape Drive on page 134.
Access the SNSM Home Page and click Admin > Library > Config Library.
125
The Configure Library screen appears.
In the Select Library list, select the library to delete and click Delete. A confirmation screen prompts if you want to delete the library.
3 4
Click OK. The Delete Library Status screen appears. Once the status screen indicates that the library has been deleted, click Close.
Auditing a Library
Use this procedure to audit a library. An audit is a physical check of each library component to verify its integrity and make sure the database and library are synchronized. ADIC recommends that you audit the library after each restore. 1 Access the SNSM Home Page and click Admin > Library > Audit Library.
126
Managing Libraries
The Audit Library screen appears.
Select the library to audit in the Select Library list and click Apply.
Note
ADIC recommends that you select the Remap Audit check box to synchronize the StorNext and SNSM databases with the library databases. If you are using an AML library, the audit may take hours or days to complete. Audits should be run when there are no other processes running on the library.
The library audit launches and the Library Audit status screen appears. 3 Once the status screen indicates that the library audit is successful, click Close.
127
Managing Drives
Tape drives provide I/O for a StorNext media library. For a detailed list of supported media, refer to the StorNext Release Notes. Managing tape drives consists of the following tasks: Configuring a Tape Drive Changing a Drive State on page 135 Cleaning a Tape Drive on page 136 Drive Pools on page 137
Configuring a Tape Drive

Configuring a drive consists of the following tasks: Adding a Tape Drive Modifying a Tape Drive on page 132 Deleting a Tape Drive on page 134 Use the procedures in this section to assist with tape drive configuration.
Adding a Tape Drive

Use this procedure to add tape drives to your libraries. You can add any number of connected tape drives to the StorNext system. 1 From the SNSM Home Page, click Admin > Drive > Config Drive. The Configure Drives screen appears.
Click Add.
128
Managing Drives
The Tape Drive Introduction screen appears. The Tape Drive Introduction screen lists the number of configured tape drives and hardware devices that are currently available for configuration.
Click Next to add a tape drive. The Associated Library screen appears.
Configured Libraries list: Select the configured library to associate with added tape drives. Fibre-Channel Attached Drives check box: Check this box if you have fibre channelattached tape drives. If you check this box, the Match Devices with Slots screen appears. Go to Step 6 on page 131. StorNext System Administrator Guide 129
Note
For SCSI direct-attached tapes that are not fibre channel, it is not necessary to match the device with the correct slot because slot-to-drive matching is automatically performed. If StorNext cannot perform slot matching, the screen shown in Step 6 on page 131 appears.
After selecting a configured library on the Associated Library screen, click Next. The Hardware Devices screen appears.
Hardware Devices list: The hardware devices to be added as drives. Drive names are automatically generated in this format: <library_dr1>, <library_dr2> Enable Compression check box: Enable this option (check the box) to allow data compression on added tape drives. 5 After adding hardware devices, click Next. Go to Step 7 on page 132
130
Managing Drives
When you select the Fibre-Channel Attached Drives check box on the Associated Library screen, the Matched Devices with Slots screen appears. The information on this screen varies from configuration to configuration.
3a. If you need help mapping the tape drive to a slot, click Show Mapping Help to display a list of device mappings
Note
StorNext may not be able to determine the device to slot mapping. Limitations include ACSLS and DAS libraries.
3b. In the Device list, select a device to be configured. 3c. In the Slot list, select a slot with which to match the device. 3d. If you need help mapping the tape drive to a slot, click Show Mapping Help to display a list of device mappings.
131
3e. Click Insert to add the device/slot combination to the Type>>Device>>Slot list. 3f. For each device and slot, repeat Step 3b. and Step 3c..
Note
If you want to enable compression on some devices in the Type/Device/Slot list, but not others, you must complete this procedure twice: once to enable compression on selected devices, and a second time to specify devices without compression.
Click Next to continue. The Complete Add Drive Task screen appears.
8 9
Review your selections. Click Next to complete the task or Back to make changes. Once a status screen displays the successful addition of the tape drive, click Next. The Tape Drive Introduction screen appears.
10 Do one of the following: Add more tape drives. Click Next to repeat the Adding a Tape Drive procedure (Step 1 on page 128). When the Status Screen displays Success, click Done.
Modifying a Tape Drive

Use this procedure to modify configured tape drives. 1 From the SNSM Home Page, click Admin > Drive > Config.
132
Managing Drives
The Configure Drives screen appears.
Select a drive from the Configured Drive List and click Modify. The Modify Drive screen appears.
You can modify the following information: Drive Name: The name of the modified drive. Dismount Delay: Change the dismount delay time (in seconds). Select New Drive Path: The drop-down menu displays available drives that the path can be modified to. Compression Enabled: Enable or disable compression. 3 4 Make drive modifications and click Apply. When the Status Screen displays Success, click Close.
133
Deleting a Tape Drive

Use this procedure to delete a configured tape drive. 1 From the SNSM Home Page, click Admin > Drive > Config. The Configure Drives screen appears.
Select a drive from the Configured Drive List and click Delete. You are prompted and asked if you are sure that you want to delete the drive.
3 4
Click OK. When the Status Screen displays Success, click Close.
134
Managing Drives
Changing a Drive State

The drive state function allows you to change the logical (database) state to online or offline. Use this procedure to change the drive state. 1 From the SNSM Home Page, click Admin > Drive > Drive State. The Change Drive State screen appears.
The Change Drive State screen displays all configured drives and the current state for each. 2 3 4 Select the drive to change. Select the state to change to and click Apply. When the Status Screen displays Success, click Close.
135
The Change Drive State screen appears with the changed state for the selected drive.
Cleaning a Tape Drive

Use this procedure to manually clean a tape drive.
Note
To perform this procedure, you must have a cleaning tape specifically labeled for cleaning. For example, CLN_XXX.
From the SNSM Home Page click Admin > Drive > Clean Drive.
136
Managing Drives
The Clean Drive screen appears.
Select a drive to clean in the Select Drive list and click Apply. The Clean Drive status screen appears.
Once the status screen indicates that the drive has been cleaned, click Close.
Drive Pools
Drive pools are groups of tape drives allocated for various administrator-defined storage tasks. Drive pools enable you to delimit storage processes based on data type, performance, security, location, or all of these variables. Drive pools can reside in a single tape library or span multiple tape libraries. The following procedures describe how to add, modify, and delete drive pools.
Adding a Drive Pool

Use this procedure to add a drive pool.
Note
1
This procedure requires the restart of the Storage Manager component.
From the SNSM Home page click Admin > Config Drive Pool.
137
The Configure Drive Pools screen appears.
Click Add to add a drive pool. The Add Drive Pool screen appears.
In the Select Drive IDs list, select a drive and click Apply. You are warned that continuing with the task will restart the Storage Manager.
138
Managing Drives
4 5
Click OK. When the status screen displays Success, click Close.
Modifying a Drive Pool

Use this procedure to modify a drive pool. 1 Access the SNSM Home page and click Admin > Config Drive Pool. The Configure Drive Pools screen appears.
In the Select Drive Pool list, select an existing drive pool and click Modify. The Modify Drive Pool screen appears.
In the Associated Drives list, select a drive and click Remove Left.
139
The drive appears in the Available Drives list.
Click Apply. You are warned that continuing with the task will restart the Storage Manager.
5 6
Click OK. When the status screen displays Success, click Close.
140
Managing Drives
Deleting a Drive Pool

Use this procedure to delete a drive pool. 1 Access the SNSM Home page and click Admin > Config Drive Pool. The Configure Drive Pool screen appears.
In the Select Drive Pool list, select a drive pool and click Delete. One drive pool must be configured at all times. Do not delete the default drive pool.
CAUTION
A prompt appears asking if you are sure you want to delete the drive pool.
3 4
Click OK to continue. When the status screen displays Success, click Close.
Managing Media
In StorNext, data is usually stored on tapes in a media library. For a detailed list of supported media, refer to the StorNext Release Notes. Managing tape media consists of the following tasks: Adding Media to a Configured Library Removing or Moving Media on page 147
141
Mounting and Dismounting Media on page 158 Transcribing Media on page 160 Reclassifying a Media Class Grouping on page 161 If you are sharing a library between applications, refer to Sharing a Library Between Applications on page 271.
CAUTION
Adding Media to a Configured Library

Use this task to add media to a configured library. Make sure there is no media in your tape drives before continuing with this procedure.
CAUTION
From the StorNext Home Page click Config > Add Media. The Add Media - Introduction screen shows a list of libraries along with the number of media that each library can hold.
CAUTION
1
Make sure that only media you want StorNext to use is in the library. StorNext will use all available tapes and overwrite them.
Click Next to add media to a configured library.
142
Managing Media
The Associated Library screen appears.
On the Associated Library screen, select a configured library to which you want to add media, and then click Next. The second Associated Library screen appears.
If you selected a media vault, go to Step 7 on page 145. 3 On the second Associated Library screen, do one of the following: Specify Bulk Load and click Next.
143
Specify Mailbox and click Next. Go to Step 4 on page 144.
The Complete Add Media Task screen appears. Go to Step 5 on page 144.
After you select Mailbox, the Select Mailbox screen appears. Select a mailbox and click Next.
5 6
Review your selections. Click Next to complete the task or click Back to make changes. Once a status screen displays the successful addition of the media, click Next. The Add Media Introduction screen appears. Go to Step 12 on page 147.
144
Managing Media
When you select a media vault on the Associated Library screen, the Select Media Type screen appears.
On the Select Media Type screen, select the type of media you want to add to the vault. The Add Media IDs screen appears.
On the Add Media IDs screen, do one of the following: Select one or more previously entered media IDs from the list, and click Next. Go to Step 12 on page 147. Enter the name for the new media in the Media Name field. Go to Step 11 on page 146.
145
Add multiple media labels by clicking the New Media button.
After you click New Media, the Create New Media ID screen appears.
10 On the Create New Media ID screen, perform the following steps: a. Enter the new media label name. b. Enter the number of media IDs you want to generate for the label. c. Enter a starting value for the new media ID. d. If you want to create additional media IDs, click Apply and repeat steps a through c. e. When you are finished creating media IDs, click OK. The Add Media IDs screen is shown again. 11 On the Add Media IDs screen, select one or more media IDs from the list, and then click Next to continue. The Complete Add Media Task screen appears.
146
Managing Media
12 On the Complete Add Media Task screen, click Next to finish adding the media, or Back to make changes. 13 Once the status screen indicates that the media has been added, click Finish.
Removing or Moving Media

These procedures enable you to remove or move media from a library to a different library or to a vault while maintaining the existing data. You can remove blank media, backup tapes, or cleaning media from the StorNext system. You can move data, blank media, backup tapes, or cleaning media to another library. Removing Media on page 147 Moving Media on page 152
Removing Media
Use this procedure to remove media. 1 From the StorNext Home Page click Admin > Remove/Move Media. The Remove or Move Media screen appears.
Remove Media - Select this option to remove media from a library. Move Media - Select this option to move media to a different library. Select Library - The library from which you want to remove media. Select Media Type - The specific media that you want to remove from the selected library. 2 Click Remove Media, select the library from which to remove the media and click Next.
147
The Select Media screen appears.
Select the media to remove. For individual media, enter a media name in the Enter Media Field and click OK. The Complete Remove/Move Media Task screen appears. Go to Step 5. For multiple media, click Browse. The StorNext Media Browser screen appears. Go to Step 4.
Select the Media Class to remove. The StorNext Media Browser displays all the media associated with the class you have selected in the Select Media Field. Field descriptions are listed below: Current Media Class - The selected media class appears. Select Media Class - The media class from which to remove or move media. For each media class, all media within the class are shown in the Select Media list.
148
Managing Media
Media Filter - Use this field to narrow your search of your selected media type. For example, to display all media with 01 in its name, enter *01* where the asterisks are wild cards representing any characters before or after the specified search criteria. Select Media - Select the specific media (one or more) to remove or move from the library. 5 From the Media Browser window, select the media to remove and click OK.
Note
In the Select Media window, you can select any number of media from one to all.
In the Media List window, the Select Media screen appears and displays the selected media.
In the Media List window, select the media to remove or move and click Next.
Note
In the Media List window, you can select any number of media from one to all.
149
The Complete Remove/Move Media Task screen appears.
7 8
Review your selections and click Next to apply them or Back to make changes. The Remove/Move Media status screen appears. Once the status screen indicates that the media has been removed or moved, click Finish. The Library Operator Interface (LOI) is launched.
The library on which the media resides is displayed. Click Eject Media. The Library Operator Interface screen updates and indicates the selected library. Available media operations for each library are shown.
150
Managing Media
Note
Not all media operations will be available for each library.
Note
If you are using a vault library, you have to manually move the media.
Select All: Select all media to be removed Deselect All: Deselect all media Details: Shows information on selected media
Ejected: Eject (remove) media from the library Fail: Mark selected media as Failed Close: Close the current window 10 For the selected Media IDs, click Ejected.
151
The LOI Eject screen appears without the Media IDs listed.
11 Click Close.
Moving Media
Use this procedure to move media from one library to another. 1 From the StorNext Home Page click Admin > Remove/Move Media. The Remove or Move Media screen appears.
Remove Media: Remove media from a library Move Media: Move media to a different library Select Library: The library from which you want to move media Select Media: The specific media that you want to move from the selected library 2 3 Select Move Media. Select the library from which to remove the media and media type.
152
Managing Media
Click Next. The Select Media screen appears
Select the media to move. For individual media, enter a media name in the Enter Media Field and click OK. The Complete Remove/Move Media Task screen appears. Go to Step 7 on page 154. For multiple media, click Browse. The StorNext Media Browser screen appears. Go to Step 6.
153
Select media from the list. In the following example, the Blank media class was chosen. The Media Browser appears. The Select Media list is populated with all available media in the class selected in Step 6 on page 154.
Select the media to be moved (one or more selections can be made), and click OK. The Select Media screen appears and populated with your selection.
154
Managing Media
Click Next to continue. The Select Destination Library appears.
Select the destination library from the list and click Next. The Complete Remove/Move Media Task screen appears.
155
10 Click Next to continue. A status screen appears. 11 When the status screen indicates that the task has been successful, click Finish. The LOI appears with the source library flagged.
12 Eject the media from the source library and click the highlighted Eject Media. The LOI Eject screen appears.
13 Select the media to be moved and click Ejected. The LOI Eject screen appears without your selection.
156
Managing Media
14 Click Close to continue. The LOI screen appears with the destination library flagged.
15 Move the media to the destination library and click the highlighted Enter Media. The LOI Enter screen appears.
16 Click Entered to continue. The LOI Enter screen appears without your selection.
17 Click Close.
157
The LOI screen appears without flags or highlights.
18 Click Close to finish.
Mounting and Dismounting Media

Use the procedures in this section to mount and dismount media in a tape drive as needed.
Mounting Media
1 Access the SNSM Home Page and click Media > Library > Mount. The Mount Media screen appears.
2 3 4
Select an archive from the Archive drop-down menu. The screen updates to show available media. Select the media you want to mount from the Media ID list. Select a drive from the Drive ID drop-down menu.
158
Managing Media
Review your selections.
5 6
Click Apply. When the Status screen displays Success click Close.
Dismounting Media
Use this procedure to dismount media. 1 Access the SNSM Home Page and click Media > Library > Dismount. The Dismount Media screen appears.
159
Select a Media or Drive ID from the drop-down menu. Depending on which ID you selected, the information in the other field automatically populates.
3 4
Review your selections and click Apply. When the Status screen displays Success click Close.
Transcribing Media
This task lets you transcribe the contents of one media type to another media type, or reclaim (defragment) media. During the transcription and/or reclamation process, SNSM uses two drives to transcribe one media to another media, file by file. For SNSM to successfully transcribe one media to another media, two drives must be online. If only one drive is online, then the transcription and/or reclamation process fails.
CAUTION
If transcription and/or reclamation starts and all the drives are in use, SNSM prioritizes and queues the job. When two drives become available, the queued job starts and all active files are transcribed. When the transcription is complete, SNSM updates the database to reflect the new location of the files. If the transcription and/or reclamation process encounters a file that spans multiple media, then only the portion of the file that exists on the old media is transcribed. When the transcription and/or reclamation process is complete, only deleted files remain on the source media. To remove the source copy of the deleted files, access SNSM and select Clean from the Media menu. When the cleaning process is complete and the source copy of the deleted files are removed, the media is available for reuse as blank media.
160
Managing Media
Access the SNSM Home Page and click Media > Transcribe. The Transcribe Media Advanced Page appears.
2 3
Select one or more media on the Select Media to Transcribe list and click Apply. Once the status screen indicates that the media has been transcribed, click Close.
Reclassifying a Media Class Grouping

A media class grouping is a media management tool that segregates media into classes. Membership in a media class grouping is exclusive, so that media can only belong to one of class grouping. Media class groupings are restricted to one type of media. For example, LTO media cannot enter a media class grouping that contains AIT media. When media is initially imported into the SNSM, it enters a media class grouping. Import mapping to media class is automatic and driven by media type. 1 Access the SNSM Home Page and click Media > Reclassify.
161
The Reclassify Media screen appears.
In the Source Media Class menu, select the source media class and click Browse to select media IDs to reclassify. The Media Class Browser screen appears.
Select one or more media from the Select Media list and click OK.
162
Managing Media
You are returned to the Reclassify Media screen.
The IDs for the selected media are shown in the Entered Media IDs list. 4 Select a destination for media IDs in the Destination Media Class drop-down menu and click Apply. The new media class must be associated with the type of media you are reclassifying. For example, if you select 3590 BACKUP as your source media class, then select 3590 DATA as your destination media class.
CAUTION
Your source and destination media types must be the same. For example: Source: F0_3590_DATA Destination: F0_3590_CLEAN
Once the Status Screen displays Success, click Close.
163
Managing Storage Disks

Storage disks are external NFS devices or UNIX based file systems that can be used for long term data storage. Storage Manager moves data to storage disks for long term retention in addition to, or instead of tape. This enables users leverage the specialized third party functionality of appliances or store small files that may take longer to retrieve from tape. While many users will still use tape for long term storage and vaulting, storage disk can also be used to create tape-free archives. Storage disk management includes the following tasks: Configuring a Storage Disk Changing a Storage Disk State on page 170 Cleaning a Storage Disk on page 170 Before you create a storage disk, the disks you wish to use must reside in an existing and mounted file system.
Note
Configuring a Storage Disk

Use the following procedures to add, modify and delete a storage disk.
Adding a Storage Disk

1 From the SNSM Home Page, click Admin > Storage Disk > Config. The Configure Storage Disk screen appears.
Click Add.
164
The Add Storage Disk - Introduction screen appears.
3 4
Click Next. The Add Storage Disk screen appears.
5 6 7
Enter the name for the storage disk or accept the default name in the Storage Disk Name field. Select a mount point from the Select a file system mount point drop-down menu. Click Browse to select a directory for your files.
165
The Directory Browser screen appears.
8 9
Select the directory for your files and click OK. The Add Storage Disk screen reappears with your selections.
10 Select the Copy # (1-4) for use by all policy classes for this storage disk.
Note
Only copies of the number you choose can be written to this disk. For example, if you select copy number 1, only files with that copy number can be written to the storage disk.
11 Click Next.
166
The Complete Storage Disk screen appears.
12 Review your selections and click Next. 13 When the Status Screen displays success, click Finish.
Modifying a Storage Disk

Use this procedure to modify a storage disk.
Note
1
You can only modify a blank storage disk. A blank is a storage disk that has not been written to and where no files system files reside.
From the SNSM Home Page, click Admin > Storage Disk > Config.
167
The Configure Storage Disk screen appears.
Select a storage disk from the Current Storage Disks list and click Modify. The Modify Storage Disk screen appears.
This screen displays the following: Name: The name of the storage disk being modified Mount Point: The current mount point of the storage disk. You can only change the mount point on a blank or unused files system. To change the mount point, select and existing mount point from the drop-down menu and click Browse. The directory will change in the Mount Point field. 168 Managing Storage Disks
Directory: The directory selected for file storage when the storage disk was created (you cannot modify this setting) # of streams: Number of I/O streams that can concurrently write to the disk Copy: Copy number selected when the storage disk was created 3 4 Modify these settings and click Apply. When the Status Screen displays success, click Close.
Deleting a Storage Disk

Note
Deleting a storage disk does not unmount it. You must manually unmount the disk or you can use it to create a new storage disk.
Use this procedure to delete a storage disk. 1 From the SNSM Home Page, click Admin > Storage Disk > Config. The Configure Storage Disk screen appears.
Select a storage disk and click Delete. You are warned that all data on the disk will be deleted with the disk and prompted to continue.
169
3 4
Click OK. When the Status Screen displays success, click Close.
Changing a Storage Disk State

Changing a storage disk state allows you to change the storage disk state from online to offline and back to online. Use this procedure to change the state of a storage disk. 1 From the SNSM Home Page, click Admin > Storage Disk > State. The Change Storage Disk State screen appears.
2 3 4 5
Select the storage disk to change states for. Select the state to change to. Click Apply. When the Status Screen displays success, click Close.
Cleaning a Storage Disk

Cleaning a storage disk looks for orphaned file copies (an archive copy on the file system disk) and removes them preventing the unused files from taking up large amounts of disk space. Use this procedure to clean a storage disk. 1 From the SNSM Home Page, click Admin > Storage Disk > Clean.
170
The Clean Storage Disk screen appears.
2 3
Select the storage disk to clean and click Apply. When the Status Screen displays success, click Close.
171
172
6
Data Migration Management
This chapter describes how to use StorNext to manage data. This chapter covers these topics: Policy Classes and Relationships on page 174 Adding a Policy Class on page 174 Modifying a Policy Class on page 179 Deleting a Policy Class on page 180 Performing Disk-to-Disk Relocation on page 183
Note
Before initially executing any StorNext command line programs, you must source either the .profile or the .cshrc file to update the user environment with StorNext environment variables. If you are running sh, ksh, or bash, type: . /usr/adic/.profile For all other shells, type: source /usr/adic/.cshrc
173
Policy Classes and Relationships

A policy class defines how files will be managed in a directory and subdirectories. Available policy class settings are: Number of copies to create Media type to use when storing data Amount of time after being modified to store data If disk-to-disk relocation is enabled, the amount of time (in days) before relocating a file Amount of time after being modified to truncate a file. Policy classes can be related to one or more directories (a relation point) and all files in that directory and sub-directories are governed by the policy class. A relation is the linking of a policy class and a directory. Examples of policy class use: A directory is created to store backups every night. This directory is seldom accessed after the files are copied over. A policy class can be set up to create two tape copies of the files, store the files to AIT media, store the files to the media after residing on disk for 10 minutes, and truncate the files immediately after storing them to free up disk space. This policy can be associated with a directory such as: /sandsm/dsm1/backup. A directory has been created to store all documents that are accessed frequently, and if truncated, needs to be able to retrieve quickly. The policy class in this case can be set up to create a single tape copy, store the files to LTO media, store them after 15 minutes of being on disk, and truncate after 60 days of non-use. This policy can be associated with a directory such as: /sandsm/dsm1/docs.
Managing Policy Classes

Managing policy classes consists of the following tasks: adding a policy class, modifying a policy class, or deleting a policy class. Policy class parameters determine storage and truncation rules for files associated with the policy class. This section includes these procedures: Adding a Policy Class Without a Relation Point Adding Relation Point to a Policy Class on page 177
Adding a Policy Class

Use the following procedures to create policy classes that logically segregate and control data, either with or without a relation point.
Adding a Policy Class Without a Relation Point

Use this procedure to add a policy class without a relation point. 1 From the SNSM Home Page click Admin > Policy Classes.
174
Policy Classes and Relationships
The Manage Policy Classes screen appears.
Click Add to continue. The Add Policy Class screen appears.
Policy Class Name: The name of the new policy class. Properties: Click Properties if you want to change the default parameters of the new policy class.
175
Parameters can be modified in the Modify Parameters screen.
File Copy options (1-4): The number of the copies to store for assigned media. This value includes the primary copy file. The default value is one (1) and the maximum number of file copies is four (4). The copy number assigned to the media determines which copy of that number goes to the media. File Cleanup (Truncation) radio button: The file retention policy for class Select Immediate to immediately archive the data to media and remove (truncate) the data from the disk as soon as it is saved to media. The next time the file is accessed, the system reads the file back from the media. Select Apply Policy to apply the policy once all copies are saved to media.
Max Inactive Versions: The maximum number of inactive versions of a file that StorNext will keep track of for recovery purposes. File Age Before Migration: Following file creation, indicates the minimum time (in minutes) that a file must reside unmodified on a disk before it is considered a candidate for storage on media. File Age Before Truncation: The minimum time (in days) that a file must reside on a disk unaccessed before it is considered a candidate for truncation from disk. Truncation removes the disk blocks of a stored file, but not the file. Drive Pool to Use: Associates a drive pool to use with a policy class. If a drive pool is specified, the drive pool name must be defined before any data operation can occur. Two affinities must be created before you can enable the disk-to-disk functionality on this screen.
Note
176
Enable Disk-To-Disk:Enables the disk-to-disk relocation functionality. Managing Policy Classes
3 4
Affinity From: The primary affinity where a file resides. Affinity To: The secondary affinity the file will relocate to. File Age Before Relocation:The minimum time in days that a file must reside unaccessed on the primary affinity before relocation to a secondary affinity.
In the Add Policy Class screen, type valid values and click Apply. Once the Status Screen displays Success, click Close.
Adding Relation Point to a Policy Class

After you have added a policy class, you can use this procedure to add a relation point to it. 1 From the SNSM Home Page and click Admin > Relations. The Manage Policy Class Relationships screen appears.
Select the policy class you wish to create a relation point for and click Add. The Add Relationship screen appears.
177
Click Browse to view directories to which the relationship can be made. The Directory Browser screen is shown.
In the list, select a directory to which to add the relationship directory. The Directory Browser screen is shown with the directory you selected in the Current Directory Field.
Click OK. The Add Relationship screen appears and displays the new directory.
178
6 7
Click Apply. When the Status Screen displays Success, click Close.
Modifying a Policy Class

Use this procedure to modify a policy class. 1 From the SNSM Home Page click Admin > Policy Classes. The Manage Policy Classes screen appears.
In the Select Policy Class list, select a policy class to modify and click Modify.
179
The Modify Parameters screen is shown.
3 4
In the Modify Parameters screen, type valid values and click OK. Once the status screen indicates that the policy class has been modified, click Close.
Deleting a Policy Class

Use this procedure to delete a policy class.
Note
Before you can delete a policy class, you must delete everything associated with that policy class: media, directories, and Trashcan entries, and you must clean the media and return it to a system-blank state.
Remove all files in directories associated with the policy class (on disk). a. Log on as root. b. Change directories to the location where the relation resides. c. Remove all files and directories.
Remove the relations for the policy class.
180
a. From the SNSM Home Page click Admin > Relations. The Manage Policy Class Relationships appears.
b. In the list, select a policy class and click Remove. The Remove Relationships for... screen is shown.
c. In the Select Directory list, select a directory and click Apply. A status screen is shown. d. Once the screen indicates that the relationship has been removed, click Close. 3 4 In the Trashcan, recursively remove all files in the relation directories. From the SNSM Home Page click Admin > Policy Classes.
181
The Manage Policy Classes screen appears.
5 6
In the Select Policy Class list, select a policy class and click Delete. Once the status screen indicates that the policy class was deleted, click Close.
Adding Media to a Policy Class

Use this procedure to add media to a policy class. Before performing this procedure, make sure that media has already been added to a library. 1 From the SNSM Home Page click Media > Add. The Add Media screen appears.
182
Media Type: Type of media available to add Quantity Available: Quantity of media available Policy Class list: Select a policy class to which to add the media Number of Media text box: Type the number of media that are being added Format Type: Select the type of media formatting to perform 2 3 Delay: Select this option if you want the media to be formatted when data is first written to it Immediate: Select this option if you want all media to be formatted when Apply is clicked
Add appropriate values and click Apply. Once the status screen indicates that the media has been added click Close.
Performing Disk-to-Disk Relocation

Disk-to-Disk relocation allows for the movement of data from one set of disks (disk stripe group) to another without affecting the file name space. This procedure can only be performed if you have the full StorNext suite. Before performing this task, you must create a new managed file system with affinities, or reconfigure an existing one to add affinities, create a policy class or modify an existing one, create a relation point, and determine relocation criteria. Once you have accomplished these preliminary tasks, you can then perform disk-to-disk relocation. Prerequisite: Create a managed file system with no more than 2 affinities. For instructions on how to create the file system see File System Management on page 67 for instructions.
183
Creating a Disk-to-Disk Policy Class Using the GUI

1 From the StorNext Home Page click Config > Add Storage Policy. The Storage Policy - Introduction screen appears.
Click Next. The Policy and Directory screen appears.
3 4
Select Enable Disk-to-Disk. Click Browse.
184
The Directory Browser screen appears.
Select a directory and click OK. The screen appears with the directory to be migrated.
Review your selections and click Next.
185
The Relocation Policy Selection screen appears
From the drop-down menus, select the affinity to move your data from, and the affinity to move the data to and click Next. The Store, Truncate, and Relocate Time screen appears.
Minimum Store Time (Minutes): The minimum amount of time a file must remain unaccessed before it is considered a candidate for storage. Minimum Truncation Time (Days): The minimum number of days a file must remain unaccessed before it is considered a candidate for truncation. Minimum Relocation Time (Days): The minimum number of days a file must remain unaccessed on the primary affinity before it is considered a candidate for relocation to a secondary affinity.
186
Set your times and click Next. The Number of File Copies and Media Type screen appears.
Select the number of copies to store each file, including the primary file.
10 Select the media type for this policy and click Next. 11 The Complete Storage Policy Task screen appears
12 Review the information and click Next to continue or Back to edit your choices. 13 When the Status screen displays Success, click Close.
187
Creating a Disk-to-Disk Policy Class Using CLI

Use this procedure to create a disk-to-disk-specific policy class.
Note
Before initially executing any StorNext command line programs, you are required to source either the .profile or the .cshrc file. This will update the user environment with the StorNext environment variables. If you are running sh, ksh, or bash, type: . /usr/adic/.profile For all other shells, type: source /usr/adic/.cshrc
Note
You must have 2 affinities configured to perform this task.
Use the fsaddclass command to create a new policy class. Type: /usr/adic/TSM/exec/fsaddclass <policy_class_name> -a <default_affinity> <destination_affinity> -i <relocation_time_in_days> For example: /usr/adic/TSM/exec/fsaddclass dtdclass1 -a Aff1 Aff2 -i 1 The list of affinities are the same affinities that were defined through the GUI. See Affinities on page 101 for more information. If the -i option is not used (MinRelocTime), then the default relocation time of seven (7) days is used. If only one affinity is listed with the -a option, then no relocation occurs because a destination affinity is not defined. The first affinity listed after the -a option is the default affinity.
Modifying a Disk-to-Disk Policy Class

Use the fsmodclass command to modify an existing policy class. Type: /usr/adic/TSM/exec/fsmodclass <policy_class_name> -a <default_affinity> <destination_affinity> -i <relocation_time_in_days> For example: /usr/adic/TSM/exec/fsmodclass dtdclass1 -a Aff1 Aff2 -i 1
188

Use the following procedures to perform automatic or manual disk-to-disk relocation.
Automatic Disk-to-Disk Relocation

A migration policy starts, automatically, every night at midnight (12 a.m.). When the policy runs, files that belong to the policy classes with defined relocation criteria are migrated to the destination affinity if they meet the migration criteria. For a file to be eligible for migration/relocation, it must meet all of these criteria: Have a source and destination affinity Be a non-zero sized file Not be truncated Not be specifically excluded from relocation via the fschfiat command Not have been accessed or modified within the MinRelocTime, as defined by its policy class
Manual Disk-to-Disk Relocation

Manual disk-to-disk migration is performed by using the fsrelocate command. This command can be used to relocate a file from the current affinity to another affinity, provided it meets these criteria: Be a non-zero sized file Not be truncated Not be specifically excluded from relocation via the fschfiat command For example: /usr/adic/TSM/exec/fsrelocate /stornext/snfs1/data1/file1 -a Aff2 In the previous example, the file /stornext/snfs1/data1/file1 will be relocated to affinity Aff2. Meta characters may also be used when defining the file name parameter. For example: /usr/adic/TSM/exec/fsrelocate -a Aff2 /stornext/snfs1/relocate/*
189
190
7
Monitoring and Reporting
This chapter describes how to monitor StorNext and generate StorNext reports. This chapter contains these topics: StorNext File System Reports StorNext Reports on page 197
Generating StorNext Reports

StorNext enables you to generate a number of reports that provide information about affinities, system configurations, and statistics. Reports are generated for SNFS and StorNext: StorNext File System Reports StorNext Reports on page 197
StorNext File System Reports

SNFS reports cover the following topics: Affinities on page 192 File Systems on page 194 Stripe Groups on page 196
191
Affinities
The Affinities report shows the existing affinities for a selected directory in the file system. Use this procedure to run the Affinities report. 1 Click Reports > SNFS > Affinities. The Affinities Report screen appears.
Do one of the following: In the Select Individual Directory text box, type the full path of the directory on which the report is to be run and click Apply. The Directory Affinity Information screen appears.
192
Click Browse to select a directory The Directory Browser screen appears.
Use the Directory Browser to locate the directory on which the report is to be run and click OK.
Highlight the directory on which the report is to be run and click Apply.
193
The Directory Affinity Information screen appears.
Click Close when you are finished.
File Systems
The File System report provides file system statistics including active clients, space, size, disks, and stripe groups. Use this procedure to run the File System report. 1 Click Reports > SNFS > Systems. The File System Report screen appears.
In the active file systems list, select one or more active file systems on which to run the report and click Apply.
194
The File System Statistics Report screen appears and provides statistical data for the selected file systems.
The File System report provides the following information: Creation Date: The date and time that the file system was created # Active Clients: The number of client machines that are associated with the file system File System Block Size: The block size of the file system Message Buffer Size: The size of the file system message buffer # Disk Devices: The number of disk devices on the file system # Stripe Groups: The number of stripe groups on the file system Total Space: The total size of the file system Available Space: The space that is still available in the file system Managed: Indicates whether the file system is managed (Yes) or unmanaged (No) Trashcan: Indicates whether the Trashcan is enabled or disabled on the file system 3 When finished, click Close.
195
Stripe Groups
The Stripe Groups report provides stripe group statistics including space, affinities, and disks. Use this procedure to run the Stripe Groups report. 1 Click Reports > SNFS > Stripe Groups. The Stripe Groups Report screen appears.
2 3
In the Active File Systems menu, select a file system. In the Stripe Groups list, select one or more stripe groups on which to run the report and click Apply. The Stripe Group Statistics Report screen appears.
The Stripe Group report provides the following information: Total Space: The total space available in the stripe group Available Space: The available space that has not been used in the stripe group Breadth (blocks): The number of contiguous blocks in the stripe group Affinity: Indicates whether an affinity is associated with the stripe group Status: Indicates whether the stripe group is up or down, and whether the data is Metadata, Journal, or Exclusive 196 Generating StorNext Reports
Read: Indicates whether the stripe group is read-enabled Write: Indicates whether the stripe group is write-enabled Read Method: Indicates whether the read method is assigned to the stripe group Disks in Group: The list of disks assigned to the stripe group 4 When finished, click Close.
StorNext Reports
StorNext reports provide information about the following aspects of your system: Backups on page 197 Drives on page 198 Files on page 200 Libraries on page 202 Library Space on page 203 Media on page 204 Media Classes on page 207 Policy Classes on page 208 Relations on page 209 Requests on page 211 Scheduler on page 212 Storage Disks on page 213
Backups
The Backup report provides backup information about primary and secondary backups of the StorNext system. Use this procedure to run the Backup report. 1 Click Reports > Backups.
197
The Backup Information Report appears and provides backup data (dates and times) for the specified backups.
The Backup Information Report provides the following information: Date: The date and time the last backup was run Type: Type of backup that was run, either Full or Partial Status: Status of backup, PASS, NOT, or STORED. NOT means that all copies of the backups were not stored to media. Media: The media ID on which the backup was stored 2 When finished, click Close.
Drives
The Drive States report provides information about the drives configured in StorNext, including drive IDs and types, archives, usage, errors, and mount data. Use this procedure to run the Drive States report. 1 Click Reports > Drives.
198
The Drive States Report screen appears.
In the drives list, select one or more drives on which to run the report and click Apply. The Drive State Information Report appears and provides state information for the selected drives.
The Drive States report provides the following information: Drive ID:The drive ID (1, 2, 3, etc.) Drive Type: The type of drive being used Device Pathname:The pathname of the drive Tape Compression:Indicates whether tape compression is on or off Associated Library:The name of the library that is associated with the drive State:indicates whether the drive is online or offline Status: FREE: No medium mounted IN USE: Medium in use FAILED: Drive failed 199
DELAYED: Drive is in a dismount delayed state CLEANING: Cleaning medium mounted USER MOUNT: Medium mounted using Media > Mount or fsmount commands OTHER: Medium was not mounted directly by the Tertiary Manager but by other means such as through the Media Manager
Dismount Delay: The time delay (in seconds) before media is dismounted Assignment: Indicates whether the drive is free or mounted Mount Count: The number of times that the tape has been mounted Error Count: The number of errors (mostly write errors) that a tape has incurred Mount State: Indicates whether the drive is mounted or unmounted Mounted Media ID: The ID of the mounted drive 3 When finished, click Close.
Files
The Files Report provides file information, including the current location of a file, owner, size, and number of copies for the file. Use this procedure to run the Files report. 1 Click Reports > Files. The Files Report screen appears.
In the Enter Individual File Field, type the name of the file on which the report is run or click Browse to select files from a managed directory.
200
The StorNext File Browser screen appears.
If you typed a file name in the Enter Individual File Field or selected a file name from the Select Files list, click Apply and go to Step 5. 3 In the Select Directory list, select a directory. The selected directory appears in the Current Directory Field. A list of directories appears in the Select Directory list, and a list of files in the Current Directory Field appears in the Select Files list. 4 In the Select Files list, select one or more files and click OK. The Files report screen appears with the selected files in the Select Files list. 5 To run the report, click Apply. The File Information Report screen appears and provides information for the selected files.
The Files report provides the following information: Last Modification Timestamp: The timestamp (date) when the file was last modified Owner (Access): The access permissions that the Owner has to the file Group (Access): The access permissions that the Group has to the file; Read, Write, Execute (rwx), or all three permissions Public Access: Indicates public access permissions
201
Policy Class: An associated policy class which manages the file lifecycle Truncation Attribute: The time period (in days) when the file is truncated Size (bytes): The size (in bytes) of the file File Location: The media on which the file is stored Copies: The number of copies of the file Affinity: The affinity the file is associated with 6 When finished, click Close.
Libraries
The Libraries Report provides information about libraries, including the type and state, associated media associated, and imported media classes. Use this procedure to run the Libraries report. 1 Click Reports > Libraries. The Libraries Report screen appears.
In the Library list, select one or more libraries on which to run the report and click Apply. The Library Information Report screen appears and provides information about the selected libraries.
202
The Library Report provides the following information: Library Type: The library type, such as SCSI, Network, or Vault Current State: Indicates whether the library is online or offline Library Mode: Displays two modes: Attended: The LOI will be associated with required actions Unattended: Fails any actions that require user interaction
Media Type: The media type that the library uses Slot Count: The number of media slots that are available for the library type Current Fill Count: The current number of media slots that are associated with the library Import Media Class: The media type to import 3 When finished, click Close.
Library Space
The Library Space Used report is a utility that measures total storage capacity being used in all configured libraries. Use this procedure to run the Library Space Used report. 1 Click Reports > Library Space. The Library Space Used Report screen appears and provides information on the current amount of storage being used by all configured libraries is displayed (in GB).
When finished, click Close.
203
Media
The Media report provides media configuration and statistics. Use this procedure to run the Media report. 1 Click Reports > Media. The Media Report screen appears.
In the Enter Media ID Field, type the ID of the media on which the report is run or click Browse to select media from specific libraries. The Media Browser screen appears.
If you typed a media ID in the Enter Media ID Field or selected media from the Entered Media IDs list, click Apply and go to Step 5 on page 205. 3 In the View by: list, select a library or media class.
204
The selected library or media class appears in the Current Selection field and the media associated with the selected library are shown in the Select Media list. 4 In the Select Media list, select one or more media and click OK.
Note
If you want to limit the media list to a specific selection, type the attributes of the media name (that is, *8 will list all media ending with an 8) in the Media Filter Field to only browse these items.
The Media Report screen appears with the selected media shown in the Entered Media IDs list. 5 Click Apply to continue. The Media Information Report screen appears.
The Media Report provides the following information: Copy #: Number next to the media ID (000091 (1) above). If the copy number does not exist, this media has not been allocated to a policy class. Show Details link: Click this link to view media dead space and files on that media (see the Detailed Media Information Report Screen on page 206) Media Type: The type of media Media Class: The media class designated for that tape Policy Class: Indicates whether a policy class is associated with the media Last Access Time: The date and time when the media was last used Media Status: Indicates media status as Available, Unavailable, or In Use Write Protect: Indicates whether the media is write-protected Formatted: Indicates whether the media is formatted Import Date: The date the media was added to the library Export: This is an attribute that is currently not utilized in StorNext and should remain at UNMARKED # Files: The number of files associated with the media Space Used: The amount of space written % Used: The percentage (%) of used space StorNext System Administrator Guide 205
Space Remaining (bytes): The available space on the media (in bytes) Dead Space: The percentage (%) of fragmented space on the media Mount Count: The number of times the tape has been mounted Move Count: The number of times the tape has been moved Suspect Count: Indicates if the media has any errors and marks it suspect Current Action: This is an attribute that is currently not utilized in StorNext and should remain at NONE Location: The location of the tape Current Archive: The current library in which the media is located Pending Archive: Indicates whether the media is associated with another library Clicking on the Show Details link may take a long time depending on the number of files on that media. Detailed Media Information Report Screen
Note
Figure 1
This Detailed Media Information Report provides the following information: Dead Space: Unused space on the media File Pathname: Path location of the file File Size: Size of the file Version: Version of the file 206 Generating StorNext Reports
Status: Status of the file; Active or Inactive Modify/Delete Date: Last date the file was modified or deleted 6 When finished, click Close.
Media Classes
The Media Class report provides information about media classes, including the number and type of media in each class. Use this procedure to run the Media Class report. 1 Click Reports > Media Classes. The Media Class Report screen appears.
Select one or more media classes on which the report is run and click Apply. The Media Class Information Report screen appears and provides the following information about the selected media classes.
The Media Class Report provides the following information: Media Type: The type of media Maximum Members: The maximum number of files/backups on a tape Current Fill Level: The current fill percentage (%) for the tape
207
Auto-Migrate Fill%: Indicates how full the media class can get before being declared full 3 When finished, click Close.
Policy Classes
The Policy Classes report provides information about policy classes in the StorNext system, including media, mintimes, hard limits, and cleanup. Use this procedure to run the Policy Classes report. 1 Click Reports > Policy Classes. The Policy Classes Report screen appears.
In the Select Policy Class list, select one or more policy classes on which the report is run and click Apply.
Note
To view media associated with these policy classes, select the Show Media box.
208
The Policy Class Information Report screen appears.
The Policy Classes report provides the following information: Drive Pool: The association of tape drives Default # Copies: The number of copies to store per file Max # Copies: The maximum number of copies per file Media Type: The type of media in association with the policy class # Media Associated: The number of media that are associated with the class Max Inactive Versions: The maximum number of inactive versions to keep for a file File Truncate Policy: The number of days before truncation can occur Media Clean Pool: The class name with which the media is associated after it is logically blank Minimum Store Time (minutes): The time before the file becomes available for storage to tape Minimum Trunc Time (days): The time before the files on tape become available for truncation Disk-to-Disk: Whether the disk-to-disk functionality is enabled for the selected policy class Affinity From: If disk-to-disk is enabled, the primary affinity where a file resides Affinity To: If disk-to-disk is enabled, the secondary affinity the file will relocate to File Age Before Relocation: The age of a file when it becomes eligible for relocation File Copy (1-4): The number of copies to store for each file. This value includes the primary copy file. The default value is one (1) and the maximum number of file copies is four (4). The copy number assigned to the storage disk determines which copy the storage disk is in. 3 When finished, click Close.
Relations
The Relations or Directory/Policy Class Relationship report provides information about the directoryto-policy class relationships in the file system. Use this procedure to run the Directory/Policy Class Relationship report. 1 Click Reports > Relations.
209
The Directory/Policy Class Relationships Report screen appears.
In the Select Managed Directories list, select the directory on which the report is run and click Apply. The Relation Information Report screen appears and displays the pathname of the selected directory and the corresponding policy class name for the directory.
210
Requests
The Requests report provides information about requests, including the type of request, priority, and current status. Use this procedure to run the Requests report. 1 Click Reports > Requests. The Requests Report screen appears.
In the Request ID list, select one or more request IDs on which to run the report and click Apply. The Request Report screen appears.
211
Scheduler
The Scheduler report provides information about StorNext schedules. Use this procedure to run the Scheduler report. 1 Click Reports > Scheduler. The Scheduler Report screen appears.
Select one or more of the schedules to report and click Apply. The Scheduler Information Report appears.
The Scheduler report provides the following information: Name: The name of the schedule Run Days: The days the feature is run Start Time: The time the feature is run Window: If StorNext was down at the time of the scheduled event and is restarted during the window time period, the event will be launched; otherwise it will be skipped until the next scheduled time Last Run: The last time the schedule was run 3 212 When finished, click Close. Generating StorNext Reports
Storage Disks
The Storage Disks report provides information about the configured storage disks on your system. You can modify the report to include the files on the selected configured storage disks, but depending on the number of files, this action can take a long time to run. Use this procedure to run the Storage Disks report. 1 Click Reports > Storage Disks The Storage Disk Report screen appears.
Select the disks on which to run the report and click Apply.
Note
Depending on the number of files on the Storage Disk, selecting the Yes option to Show Files on Storage Disk can cause the report to be very large and take a long time to run.
The Storage Disk Information Report screen appears.
The Storage Disk Information Report provides the following information. Name: Name of the storage disk for which the report was run Mount Point: The mount point of the storage disk StorNext System Administrator Guide 213
Copy #: Copy ID for media on the storage disk. # of Streams: The number of streams simultaneously accessing the disk Status: Shows if the disk is ONLINE or OFFLINE Last Access Time: The date and time the disk was last accessed 3 When finished, click Close.
214
8
Service Management
This chapter describes how to use the StorNext Service Management tools to run a health check on your system, create a log that captures the current state of your system, or check current system status. This chapter contains these topics: Using Health Check Using State Capture Using the System Status
Using Health Check

The following health checks are available: Archive: Verify that all configured archives are online Config: Verify affinities are configured correctly in SNSM for managed file systems Verify the SNSM managed file systems are identified correctly Verify the SNSM managed file systems are configured correctly
Disk Space: Verify that enough disk space exists for the SNSM database tables, logging, and other functions Drive: Verify that all configured drives are online Media: Verify that there are enough media available for all policies to store all file copies
215
Verify the SNSM media are configured correctly Verify the SNSM is keeping up with file system events Verify the SNSM is keeping up with store candidate processing
Policies:
Running a Health Check

Use these procedures to run a health check. 1 From the StorNext Home Page click Service > Health Check. The Health Check Tests screen appears.
Note
2 3
All of the health options are linked to specific information about that particular health check.
Select one or more health checks to run and click Run. When the Status screen displays Success, click Close.
216
Using Health Check
Viewing the Health Check History

After running a health check, you can view a five-run history of each health check that has been run. 1 2 Select a health check from the Health Check Tests screen. Click History. The Health Check History screen appears.
Do one of the following: Select a specific report to view and click Details and proceed to Step 4 on page 218 or Click the Pass or Fail link in the Results column and proceed to Viewing the Health Check Results on page 219.
217
The Health Check Results screen appears.
Click Back to view more archives or close the window when finished.
218
Using Health Check
Viewing the Health Check Results

When viewing the Health Check Tests or the History screen, you can check the details of the Last Status of a particular health check. In the example below, the last status check is being run from the Health Check Tests screen. 1 From the StorNext Home Page click Service > Health Check. The Health Check Tests screen appears.
Click the Last Status Indicator (Pass or Fail).
219
The Health Check Results screen appears.
This screen details the results of the last check run. 3 When you are finished viewing the results, click Close.
Using State Capture

The StorNext State Capture tool enables you to create a log that captures the current state of your system. This log assists ADIC support personnel in analyzing and debugging some problems in the storage system. When you use the State Capture tool, StorNext creates a log file named using the format snapshotmachinehostname-YYYYMMDDHHMMSS.tar.gz. This file contains a summary report that are produced by executing the pse_snapshot command on all component config/filelist files. If desired, you can download or delete a previously captured file. When you are finished using the State Capture tool, you can return to the StorNext home page or select another tool or option.
Capturing the Current System State

The StorNext State Capture option enables you to capture, download, or delete system information. Use this procedure to access the StorNext State Capture tool. 1 Access the StorNext home page and click Service > Capture State.
220
Using State Capture
The StorNext Capture System State screen is shown.
Click Capture. The Capture State Status window is shown.
When the status window indicates the capture was successful, click Close.
Downloading a Previous System Capture

After you have created one or more system captures, you can select and download one of those .tar files to view. 1 Access the StorNext home page and click Service > State Capture. A list of capture files stored in the directory /usr/adic/www/logs/capture_state is shown. The directory where the files are stored resides on the StorNext server. 2 3 Locate the capture file you want to download, and then click the radio button beside the filename. Click Download. You are notified that the download will start automatically, if it does not, to use the given link.
221
Specify whether you want to open or save the capture file. (The file is in compressed tar.gz format, so in most cases you will want to save the file and then open it with a file decompression utility such as WinZip.)
Deleting a Previous System Capture

When you are finished viewing and analyzing a capture file, you can delete the file. 1 Access the StorNext home page and click Service > Capture State. A list of capture files stored in the directory /usr/adic/www/logs/capture_state is shown. 2 3 Locate the capture file you want to delete, and then click the radio button beside the filename. Click Delete. A confirmation screen prompts you to confirm that you want to delete the file. 4 Click OK. The Delete Capture File screen shows deletion progress.
The Delete Capture File screens status changes to Success after the file has been deleted. Click Close.
Using the System Status

The System Status tool creates a list of tickets, referred to as RAS tickets, that relate to system faults or errors. Ticket details provide a summary of the system fault, an area for Analysis note, and contains a Recommended Actions link to assist in correcting the fault. Use this procedure to use the System Status tool. 1 Access the StorNext home page and click Service > System Status.
222
The Service - System Status screen appears
The Service - System Status page contains this information: Total Number of Tickets: Number of RAS tickets the system has generated Ticket Display Window: All tickets are displayed here; each ticket has the following assigned to them: Ticket: The number of the ticket in the order in which it was created State: The status of the ticket is either OPEN or CLOSED Priority: Describes the priority set on the ticket per its impact on the system. Priorities are HIGH, MEDIUM, and LOW Last Update: Shows the date of the last system status update Summary: A short summary of the fault that triggered the ticket
Show Tickets: Controls the type of tickets viewed in the display window. Options are to show the OPEN, CLOSED, or ALL tickets. Previous and Next: Allow you to toggle between ticket pages (if there are more than one) Details: Click this button to view the details of a selected ticket Close All: Click this button to close all tickets in the display window Refresh: Click this button to refresh the display window
223
Highlight the ticket you wish to view.
Click the Details button to view the details of the ticket. The RAS Ticket Details screen appears.
The RAS Ticket Details screen contains this information: Ticket Number: The number of the ticket within the ticket list Opened: The date and time the ticket was created Status: The status of the ticket; OPEN or CLOSED Priority: Describes the priority set on the ticket per its impact on the system. Priorities are HIGH, MEDIUM, and LOW Summaries and Descriptions: Displays detailed information about the ticket including a Recommended Actions link to assist in correcting the fault
224
Analysis: You can enter information about the action taken upon analysis in this field Apply Analysis: Click this button to save your entered information in the Analysis field Close Ticket: Click this button when you have corrected the fault Cancel: Click this button to close the RAS Ticket Details screen 4 Click the View Recommended Actions link. The Recommended Actions screen appears.
This screen provides steps and information as to correct the fault that the created the RAS ticket. 5 6 7 Follow the instructions on the Recommended Actions screen. Click the Close Window link at the bottom of the Recommended Actions screen. Click the Close or Cancel button on the RAS Ticket Details screen.
225
226
9
Customer Assistance
More information about this product is available on the Customer Service Center website at www.adic.com/csc. The Customer Service Center contains a collection of information, including answers to frequently asked questions (FAQs). You can also access software, firmware, and drivers through this site.
StorNext Website
For the latest information and accessories for the StorNext, visit the product website at www.adic.com/stornext. The most recent versions of all documents are also located here.
ADIC Technical Assistance Center

For further assistance, or if training is desired, contact ADIC:
In the USA: For other contact numbers: To open a Service Request online: 800-827-3822 www.adic.com/contact www.adic.com/techsup
227
228
A
File System Commands
The StorNext File System (SNFS) commands that appear on the following manual (man) pages are the most commonly used with SNFS. For each command, the following information is provided: Description of what the command does and how it is used. Command syntax that show how to compose the command. List of the commands options and arguments. Several manual pages also list command examples.
cvadmin
cvadmin is an interactive utility that is used to view and modify attributes of SNFS stripe groups. A stripe group is a collection of disks that comprise a logical component. One or more stripe groups comprise a file system.
Syntax
cvadmin [ -H FSMHostName ] [ -F FileSystemName ] [ -f filename ] [ -e command1 -e command2 ] In cvadmin interactive mode (snadmin), several commands use name as an argument. For example, the select, start, and stop commands use file_system_name as an argument and the up and down commands use the stripe group (groupname) as an argument. If the value of file_system_name or groupname is identical to the snadmin command name or command keyword, then use double quotation marks on the command argument. For example, to start a file system named quotas where quotas is the snadmin command name, the syntax is: snadmin (localfs) > start quotas Additionally, snadmin command keywords must use double quotation marks as they are used as quota user or group names. For example, user is a snadmin command keyword, so it would need double quotation marks: snadmin (localfs) > quotas set group user 11G 10G 1440 When creating a group quota, you cannot name the group user.
StorNext Management Suite System Administrator Guide
229
Options / Arguments
-F FileSystemName -H FSMHostName [ -f filename ] [ -e command ] activate file_system_name debug [ value ] disable groupname [ read | write ] disks [ refresh ] Sets FileSystemName as the selected file system in cvadmin. Connects to the SNFS on the FSMHostName machine. Reads commands from the specified file. Runs the cvadmin command and exits. Activates a file system (file_system_name). Views or sets the SNFSs debugging flags. Disables stripe group (groupname) for either reads or writes. Displays SNFS disk volumes visible to this machine. If the refresh option is used, the volumes are re-scanned. Disables access to the stripe group (groupname). Enables the stripe group (groupname) for either reads or writes. Fails over the specified file system (file_system_name) or index number (index_number). Enables or disables cluster-wide file/record lock enforcement. Modifies the multipath method for the specified stripe group. Displays SNFS-labeled disks visible to the local system. Disconnects cvadmin from SNFS and exits. Enables or disables quota accounting and enforcement. Displays current quota parameters for the user or group (name). Sets current quota parameters for the user or group (name). Recalculates the amount of space consumed by all users and groups in the file system.
down groupname enable groupname [ read | write ] fail file_system_name | index_number
filelocks [ yes | no ] multipath groupname [ rotate | static | sticky ] paths quit quotas [ yes | no ] quotas get [ user | group ] name quotas set [ user | group ] name hardlim softlim timelim quotacheck
230
cvadmin
repquota select file_system_name show [ groupname ] [ long ] start file_system_name [ hostname | IP address ] stat stop file_system_name up groupname who
Generates quota reports for all users and groups in the file system. Selects the active file system (file_system_name). Displays all stripe groups or a specific stripe group. Starts the SNFS manager for the specified file system (file_system_name). Displays status of the specified file system. Stops the SNFS manager for the specified file system. Enables the specified stripe group (groupname). Displays a list of mounted clients on the selected file system.
Examples
Enter cvadmin interactive mode (snadmin): cvadmin Show all stripe groups in the file system: cvadmin <file_system_name> show Display which FSM debug flags are set: cvadmin <file_system_name> debug Display the long version of the RegularFiles stripe group: cvadmin <file_system_name> show stripe1 long Down the stripe group named RegularFiles: cvadmin <file_system_name> down stripe1 Change the read-back method of RegularFiles to sticky: cvadmin <file_system_name> method stripe1 rotate
231
cvaffinity
The cvaffinity command is used to set a session affinity type. When a file system is configured, an affinity (name describing a special media type) is created in a stripe group. Once a stripe group affinity is established for a session, all allocations of files associated with the session are made on stripe groups having the specified affinity in the affinity set list. If an affinity does not exist for any of the stripe groups, then the allocation occurs on the non-exclusive data pool. If there is no non-exclusive data pool, then an ENOSPC is returned.
Command Syntax
cvaffinity [ -k key ] filename cvaffinity -l filename cvaffinity -d filename
Options / Arguments
[ -k key ] Indicates where the file system should place the data file. If the key parameter is defined, then the data file is placed on stripe groups specified to support this parameter. Lists the affinity for the specified file. Deletes the affinity from the specified file or directory. File or directory name.
[ -l ] [ -d ] filename
Examples
Set the session to use the stripe group that supports the specified affinity key, with the file systems mount point as a reference handle: cvaffinity -k 6100_n8 /usr/clips Turn off the stripe group affinity for this session, using the file systems mount point as a reference handle: cvaffinity /usr/clips
232
cvaffinity
cvcp
The cvcp command provides a high speed, multi-threaded copy mechanism to copy directories and tar images on and off SNFS. The cvcp commands works in a number of modes: Directory-to-directory copies of regular files Single file-to-file copy Data stream to a target directory Single file or directory copy to an output stream The cvcp utility can be tuned to improve performance and resource utilization by adjusting the -b, -k, and -t options. -b option specifies the number of copy buffers. This option should be set between one to three times the number of copy threads. Increasing the number of copy buffers increases the amount of work that queues waiting for an available copy thread, but it also consumes more resources. -k option specifies the size of the copy buffer. This option can be tuned to fit the I/O characteristics of a copy. If files smaller than 4MB are being copied, performance may be improved by reducing this setting to match the copy buffer size to the source file size. -t option specifies the number of copy threads. This option is useful when copying large directory structures. Single file copies are not affected by the number of copy threads.
Command Syntax
cvcp [ -A ] [ -b buffers ] [ -k buffer_size ] cvcp [ -l ] [ -n ] [ -p source_prefix ] [ -t num_threads ] cvcp [ -x ] [ -y ] [ -z ] cvcp Source Destination
233
Options / Arguments
Source Destination [ -A ] [ -b buffers ] [ -k buffer_size ] [ -l ] [ -n ] [ -p source_prefix ] [ -t num_threads ] [ -v ] [ -x ] [ -y ] [ -z ] Source file or directory. Destination file or directory. Disables file pre-allocation. Sets the number of I/O buffers. Default: two times the number of copy threads started Sets the I/O buffer size. Default: 4MB Copies the target of symbolic links rather than copying the link itself. Prevents recursion through subdirectories. Only copies files that begin with the value of the source_prefix parameter. Specifies the number of copy threads. Default: 8 Displays verbose output about copied files. Retains original permissions from the source file. Retains ownership and group information (if set by the super user). Retains original modification times.
Examples
Copy the ABC directory and its sub-directories to /usr/clips/foo. This example uses the default number of copy threads and buffers, has a total buffer pool size of 24MB (6 buffers of 4MB each), retains all permissions and ownerships, and shows all files being copied. cvcp -vxy abc /usr/clips/foo Within the abc directory, copy all files that start with mumblypeg: cvcp -vxy -p mumblypeg abc /usr/clips/foo
234
cvcp
cvfsck
The cvfsck command is used to check and repair a file system that was corrupted by a system crash, bad disk, or other catastrophic failure.
Command Syntax
cvfsck [ -defgjJKlnrvx ] [ -T directory ] FsName FsPath
Options / Arguments
[ -d ] [ -e ] [ -f ] [ -g ] [ -j ] [ -J ] [ -K ] Enables internal debugging. Reports statistics on all file extents. Reports fragmentation. Prints the journal recovery log. Executes journal recovery and exits. Dumps the raw journal to stdout and exits. Resets the journal and exits. WARNING: Resetting the journal may introduce meta-data inconsistency. Exercise extreme caution when using this option. Writes information to syslog. Does not update meta-data (read only). Reports statistics on all files. Places temporary files in the specified directory. Displays verbose output. Reports statistics for input to a spreadsheet. Name of the file system to check. An optional, alternate file system path (other than /usr/cvfs/data) to locate file systems.
[ -l ] [ -n ] [ -r ] [ -T directory ] [ -v ] [ -x ] FsName FsPath
235
cvfsid
The cvfsid command provides a mechanism to display the SNFS identifier for the executing system. This identifier is submitted to ATAC, which issues license authorization keys.
Command Syntax
cvfsid
Options / Arguments
None
Examples
Display the SNFS identifier for the executing system. cvfsid
cvlabel
The cvlabel command is used to label SNFS disk devices. One client with visibility to all SAN disk devices must create a list of disk labels, associated device names and, optionally, the sectors to use. The mount_cvfs (1M) process uses the volume labels to determine which disk drive is used for SNFS stripe group nodes. ADIC recommends that the cvlabel command first be used with the -l option, which presents all disk devices found on the system. The next step is to create the /usr/cvfs/config/cvlabels file, the default reference file for all generated labels. Dumping a label from a volume causes the disk device to be disassociated from the specified volume, although the disk devices still has a label. A dumped disk device can be associated with another volume. Unlabeling a disk device removes the device label entirely.
Command Syntax
cvlabel -l [ -s ] [ -v ] cvlabel -c cvlabel [ -v ] [ -f ] [ -q tag_q_depth ] [ label_list ] cvlabel -u VolumeName
236
cvfsid
Options / Arguments
-l -u VolumeName [ -s ] [ -v ] [ -q tag q depth ] [ -f ] -c [ label_list ] Lists available disk devices on the system. Unlabels the specified volume (VolumeName). Prints the disk device serial number. Reports verbose output about labeling. Used to set the Command Tag Queue Depth (tag q depth) on IRIX systems. Forces labeling, even if a label exists. Lists, on stdout, all located devices that are compatible with a /usr/cvfs/config/cvlabels file. File that specifies StorNext disk labels.
Examples
List all disk devices in a system. /usr/cvfs/bin/cvlabel -l Label the disk drives. /usr/cvfs/bin/cvlabel Re-label the disk drives using the force (-f) and verbose (-v) options. /usr/cvfs/bin/cvlabel -fv
cvmkdir
The cvmkdir command is used to create a SNFS directory and attach the affinity parameter (-k key) to it. If no option is used and there is an existing directory, the cvmkdir command output displays the assigned affinity. Once an affinity is assigned to a directory, it cannot be altered. If no option is used and the directory does not exist, the directory will not be created.
Command Syntax
cvmkdir [ -k key ] dirname
Options / Arguments
[ -k key ] Indicates the affinity to associate with the directory. All new subdirectories and files beneath this directory inherit its affinity as they are created. If the affinity is changed or removed, only files or directories created after the change are affected. Path where the directory is created. 237
dirname
cvmkfile
The cvmkfile command is used to create a pre-allocated file on SNFS. This is a useful method when preparing a file for use in a real-time or streaming environment because the entire file is represented in only one file system extent. Additionally, a file can be placed on a specific stripe group by specifying the key parameter (used as an affinity locator).
Command Syntax
cvmkfile [ -k key ] [ -p ] [ -s ] [ -w ] [ -z ] size [ k | m | g ] filename
Options / Arguments
[ -k key ] Indicates where the file system should place the data file. If the key parameter is defined, then the data file is place on stripe groups specified to support the key parameter. Forces the allocation and subsequent expansions to fit as multiples of the InodeExpandMin parameter. Forces the allocation to begin on a stripe-aligned block. Sets the file size to the value of the size parameter. Causes the file to physically zero out. Specifies the file size in bytes. If appended with k, m, or g, the value represents kilobytes, megabytes or gigabytes. Name of the file to create.
[ -p ] [ -s ] [ -w ] [ -z ] size [ k | m | g ] filename
Examples
Make a 1GB file with 0 (zero) length. Allocate a stripe group that favors the media type 6100_n8. cvmkfile -k 6100_n8 1g foobar
cvmkfs
The cvmkfs command is used to reinitialize the SNFS and, optionally, to specify the file system name. If a file system name is not provided, a list of configured file systems is presented. Active file systems may not be re-initialized. Use the cvmkfs command with extreme caution. Executing this command will destroy any existing file system data for the named SNFS.
CAUTION
238
cvmkfile
Command Syntax
cvmkfs [ [ -GF ] [ -n # k, m, g ] file_system_name ]
Options / Arguments
[ -G ] [ -F ] Bypasses Press return to continue... type prompts. Executes the cvmkfs command in non-interactive mode; the user does not receive confirmation prompts. WARNING: Executing the cvmkfs command without prompts results in an irreversible re-initialization of SNFS. Use extreme caution when invoking this option. Pre-allocates inodes on SNFS. Name of the SNFS to reinitialize.
[ -n # k, m, g ] file_system_name
Examples
Re-initialize a StorNext file system. /usr/cvfs/bin/cvmkfs [ file_system_name ]
cvupdatefs
The cvupdatefs command is used to update a file system's configuration. This allows you to add stripe groups or expand current stripe groups to expand the storage space available to a file system. The cvupdatefs command must be run on the machine on which the File System Service is running.
Note
All meta-data modifications must be made on an inactive (stopped) file system.
Command Syntax
cvupdatefs [ -f ] [ FsName ] [ FsPath ]
Options / Arguments
[ -f ] [ FsName ] [ FsPath ] Forces updates. Name of the file system (FsName) to update. An optional, alternate file system path (other than /usr/cvfs/data) to locate file systems.
239
cvversions
The cvversions command is used to display different versions (revision, build level and creation date) for the File System Manager and client sub-systems of the SNFS. If you contact ATAC, provide this information.
Command Syntax
cvversions
Options / Arguments
None
Examples
Display version information for a StorNext file system. cvversions
240
cvversions
B
Storage Manager Commands
The StorNext Storage Manager (SNSM) commands that appear on the following manual (man) pages are the most commonly used with StorNext. For each command, the following information is provided: Description of what the command does and how it is used. Command syntax that show how to compose the command. List of the commands options and arguments. Several man pages also list command examples.
fsaddclass
The fsaddclass command is used to create and define a new policy class.
Command Syntax
fsaddclass class [ -s softlimit ] [ -h hardlimit ] [ -n notifyID ] [ -t mediatype ] [ -l securitycode ] [ -o acctnum ] [ -x maxcopies ] [ -d defaultcopies ] [ -k maxversions ] [ -m minstoretime ] [ -c mintrunctime ] [ - a affinity ] [ -i minreloctime ] [ -v drivepool ] [ -f i | p ] [ -r c | s ]
CAUTION
The file system must be mounted and active before running this command or it will fail.
241
Options / Arguments
class [ -s softlimit ] [ -h hardlimit ] [ -n notifyID ] [ -t mediatype ] [ -l securitycode ] [ -o acctnum ] [ -x maxcopies ] [ -d defaultcopies ] [ -k maxversions ] The policy class. Warning limit for the number of media allocated in the policy class. Maximum number of media allowed in the policy class. E-mail address of the user to notify when the policy classs softlimit and hardlimit are reached. Defines the media type to use. Security code for the policy class (up to four characters in length). Account number for the policy class (up to five characters in length). Maximum number of copies allowed for any file associated with the policy class. Total number of copies allowed for each file associated with the policy class. This value cannot exceed the maxcopies setting. Maximum number of inactive versions to keep for a file. The minimum is 1 and the maximum is 25. Default: 10 Minimum time (in minutes) that a file must reside unmodified on disk before being considered a candidate for storage on media. Minimum time (in days) that a file must reside unaccessed on disk before being considered a candidate for truncation. Lists disk affinities that the files in this policy class will traverse in their life cycle. Minimum time (in days) that a file must reside unaccessed on disk before being considered a candidate for relocation. Media Manager drive pool used to store or retrieve data. File retention policy for the policy class. Files can be: i - Truncated immediately p - Truncated at policy application time [ -r c | s ] Media classification cleanup action. When all files are deleted from a medium, the medium can revert back to: c - Policy class blank pool s - System blank pool
[ -m minstoretime ] [ -c mintrunctime ] [ -a affinity ] [ -i minreloctime ] [ -v drivepool ] [ -f i | p ]
242
fsaddclass
fsaddrelation
The fsaddrelation command is used to associate a directory with a policy class.
Command Syntax
fsaddrelation directory -c class
Options / Arguments
directory -c class Path name of the directory to associate with the policy class. Name of the policy class to associate with the directory. The name of the policy class can be up to 16 characters in length and these special characters, the comma (,), period (.) and underscore (_) can be used.
CAUTION
fsaddrelation fails if the directory has an affinity associated with it. Use the cvaffinity command to remove its affinity before running this command.
CAUTION
ADIC recommends running this command before adding any files or subdirectories to the directory. If the directory has subordinate directories when you run the fsaddrelation command, the subordinate directories retain their current affinity association. In this case, any new files created in those directories can result in allocations to unexpected stripe groups. The command fails if the directory has an affinity associated with it. Use the cvaffinity command to remove its affinity.
Note
After the fsaddrelation command completes running successfully, if the class has any affinities, the directory has its affinity set to the first affinity in the class affinity list.
243
CAUTION
If the operating system is RedHat Linux, do not run the fsaddrelation command from the CVFS parent directory(ies) of the relation <directoryName>. For RedHat Linux: 1. Create a subdirectory under the file system mount point where data will be created. For example: mkdir /stornext/snfs1/data1 2. Change the permissions of the directory to read, write, execute for world, group, and user. For example: chmod 777 /stornext/snfs1/data1 3. Create the association between the policy class and the directory. a. Change directory. Type: cd /stornext b. Run the fsaddrelation command. Be sure to provide the full pathname of the relation <directoryName>. For example: fsaddrelation -c policyclass1 /stornext/snfs1/dir20041021
fsaudit
The fsaudit command is used to audit the file system.
Command Syntax
fsaudit filesystem [ -f | -i ] fsaudit filesystem -r [ -f ]
Options / Arguments
filesystem [ -r ] [ -f | -i ] Mount point for the file system to be audited. Runs the fsaudit command in recovery mode. Corrects the file system discrepancies in non-interactive mode (-f) or specifies interactive mode in which the user is prompted for permission to correct each file system discrepancy encountered during the audit. NOTE: If fsaudit -f terminates abnormally, then permissions on the mount point must be reset manually.
244
fsaudit
fschfiat
The fschfiat command is used to modify the class attributes of a file.
Command Syntax
fschfiat [ -s e | p ] [ -r e | p ] [ -t e | p | i ] [ -c copies ] [ -a class ] filename
Options / Arguments
filename [ -c copies ] [ -t e | p | i ] File having changed attributes. Number of file copies to store (including the primary copy). This value cannot exceed the maxcopies setting. Indicates how truncation policies (-t) operate on the file: e - Excludes the file from truncation when a store or cleanup policy application occurs. p - Truncates the file by cleanup policy. i - Truncates the file immediately. [ -s e | p ] Indicates how storage policies (-s) operate on the file: e - Excludes the file from truncation when a store policy occurs. p - Stores the file by storage policy. [ -r e | p ] Indicates how relocation policies (-r) operate on the file: e - Excludes the file from truncation when a relocation policy occurs. p - Stores the file by relocation policy. [ -a class ] Specifies an alternate policy class associated with the file.
fschmedstate
The fschmedstate command is used modify the state of media or a policy class to which the media belongs.
Command Syntax
fschmedstate mediaID [ -c class | b ] fschmedstate mediaID [ -s state ]
245
Options / Arguments
mediaID [ -c class | b ] [ -s state ] The media identifier. For blank media, changes the name of the associated policy class (-c class) or changes the policy class to system blank pool (-b). The media state. Valid values are: unsusp protect unprotect avail unavail unmark
fschstate
The fschstate command is used to view or modify the state of all storage subsystems and drive components.
Command Syntax
fschstate componentalias -s state
246
fschstate
Options / Arguments
componentalias Component alias name used to identify storage subsystems and drive components. During system configuration, the System Administrator specifies the values of the componentalias parameter. Desired state of drive components or subsystems. Valid values: MAINT ON OFF Displays drive status. Valid values: FREE IN USE FAILED DELAYED CLEANING
[ -s state ]
fsclassinfo
The fsclassinfo command is used to report policy class and, within each group, its processing parameters and directory paths.
Command Syntax
fsclassinfo [ class ] [ -l ]
Options / Arguments
[ class ] [ -l ] One or more policy classes to be listed. Long report - processing parameters, directory paths, and the disk affinity list for the policy class.
247
fsclean
The fsclean command is used to remove inactive file version data.
Command Syntax
fsclean -m mediaID [ -t [ endtime ] ] fsclean -s filesystem [ -t [ endtime ] ] fsclean -c class [ -t [ endtime ] ] fsclean -t [ endtime ]
Options / Arguments
-m mediaID -s filesystem -c class [ -t endtime ] The media identifier. The file system to clean. Policy class associated with the data to clean. Endtime option. The value of this parameter should be less than or equal to the current time. Format is: YYYY:MM:DD:hh:mm:ss Default: current time
fsdrvclean
The fsdrvclean command cleans the specified drive.
Command Syntax
fsdrvclean drivealias
Options / Arguments
drivealias The drive alias. Valid values: 1 to 255 characters
248
fsclean
fsfileinfo
The fsfileinfo command is used to report the current location of files, whether on disk, media, or not in the system.
Command Syntax
fsfileinfo filename
Options / Arguments
filename Full path and filename of the file.
fsmedcopy
The fsmedcopy command enables duplication of files on media. Media duplication for replacement is intended for: Media maintenance - if errors occur frequently when attempting to read or write to the media Media defragmentation - if the medium is filled with unusable space due to deleted files.
Command Syntax
fsmedcopy mediaID -r [ -d destinationmediaID ] [ -u runtime ] fsmedcopy mediaID -r [ -b ] [ -t mediatype ] [ -u runtime ] fsmedcopy [ mediaID ] [ -f fill ] [ -w fragmentation ]
249
Options / Arguments
mediaID [ -r ] [ -d destinationmediaID ] [ -b ] [ -f fill ] The media identifier. Initiates copy-replace for a medium. Copies a data file to the destination media identifier. Specifies blank media for media destination. Specifies the fill level threshold (between 0 and 100%). The value of the fill parameter is the percentage of the medium that has been written, including active and inactive file versions. Defines the media type to be used. Maximum allowable time (in hours) for the fsmedcopy command to finish. On the medias filled space, the percentage (0 to 100%) of wasted (fragmented) space. The percentage is based on the amount of filled media space, not the total capacity of the medium. If not specified, the fragmentation parameter is set to zero (0) percent.
[ -t mediatype ] [ -u runtime ] [ -w fragmentation ]
fsmedinfo
The fsmedinfo command is used to generate a report on specified media.
Command Syntax
fsmedinfo mediaID [ -l ]
Options / Arguments
mediaID [ -l ] The media identifier. Generates a long-form report, which includes a list of files on the media.
250
fsmedinfo
fsmedlist
The fsmedlist command is used to generate a media report based on the medias current status.
Command Syntax
fsmedlist [ -c class ][ -g ] [ -l [ km ] ] fsmedlist [ -c class ][ -g ] [ -l [ bfjpqanus ] ] fsmedlist [ -c class ][ -g ] [ -l [ dhtzo ] ]
Options / Arguments
[ -c class ] [ -g ] [ -l ] [ -k ] [ -m ] [ -b ] [ -f ] [ -j ] [ -p ] [ -q ] [ -a ] [ -n ] [ -u ] [ -s ] [ -d ] [ -h ] [ -t ] [ -z ] [ -o ] Policy class for which the report is to be generated. Reports on blank media in the general scratch pool. Lists media in long report format. Lists all media marked for check out. Lists all media marked for removal. Lists unformatted blank media. Lists formatted blank media. Lists all media marked to contain duplicate files. Lists all write-protected media. Lists media with mark error. Lists all available media. Lists all media unavailable to the StorNext software. Lists all media marked as unavailable but still located in the StorNext system. Lists all suspect media. Lists all media located in a drive. Lists all media located in its home slot/bin. Lists all media transitioning between locations. Lists all media exiting a storage area. Lists all media checked out of storage areas.
251
fsmodclass
The fsmodclass command is used to modify the parameters of a policy class.
Command Syntax
fsmodclass class [ -s softlimit ] [ -h hardlimit ] [ -n notifyID ] [ -t mediatype ] [ -l securitycode ] [ -o acctnum ] [ -x maxcopies ] [ -d defaultcopies ] [ -m minstoretime ] [ -c mintrunctime ] [ - a affinity ] [ -i minreloctime ] [ -v drivepool ] [ -f i | p ] [ -r c | s ]
Options / Arguments
class [ -d defaultcopies ] [ -f i | p ] The policy class. Total number of copies allowed for each file associated with the policy class. File retention policy (-f) for the policy class. Files can be: i - Truncated immediately p - Truncated at policy application time [ -h hardlimit ] [ -l securitycode ] [ -m minstoretime ] [ -c mintrunctime ] [ -i minreloctime ] [ -n notifyID ] [ -o acctnum ] [ -r c | s ] Maximum number of media allocated in the policy class. Security code for the policy class (up to 4 characters in length). Minimum time (in minutes) that a file must reside unmodified on disk before being considered a candidate for storage on media. Minimum time (in days) that a file must reside unaccessed on disk before being considered a candidate for truncation. Minimum time (in days) that a file must reside unaccessed on disk before being considered a candidate for relocation. E-mail address of the user to notify when the policy classs softlimit and hardlimit are reached. Account number for the policy class (up to 5 characters in length). Media classification cleanup action. When all files are deleted from a medium, the medium can revert (-r) back to: c - Policy class blank pool s - System blank pool [ -s softlimit ] [ -t mediatype ] Warning limit for the number of media allocated in the policy class. Defines the media type to use.
252
fsmodclass
[ -a affinity ] [ -v drivepool ] [ -x maxcopies ]
Lists disk affinities that the files in the policy class will traverse in their life cycle. Media Manager drive pool used to store or retrieve data. Maximum number of copies allowed for any file associated with the policy class.
fspolicy
The fspolicy command is used to manage files on a file system controlled by the StorNext software.
Command Syntax
fspolicy -s -y filesystem [ -e ] [ -v drivepool ] [ -m minstoretime ] fspolicy -r -y filesystem [ -e ] [ -o goal ] [ -m minreloctime ] [ -z minsize ] -a affinity fspolicy -t -y filesystem [ -e ] [ -o goal ] [ -m mintrunctime ] [ -z minsize ] -a affinity fspolicy -s -c class [ -v drivepool ] [ -m minstoretime ] fspolicy -r -c class [ -m minreloctime ] [ -z minsize ] fspolicy -t -c class [ -o goal ] [ -m mintrunctime ] [ -z minsize ] fspolicy -b -y filesystem
253
Options / Arguments
[ -c class ] [ -e ] [ -s ] [ -m minreloctime ] [ -m minstoretime ] [ -m mintrunctime ] [ -o goal ] [ -t ] [ -v drivepool ] [ -b ] [ -y filesystem ] [ -r ] [ -z minsize ] Policy class associated with data to be stored or truncated. Invokes a high priority for immediate action on file storage in a file system. Invokes the storage policy. Minimum time (in minutes) that a file must reside on disk before being considered a candidate for relocation. Minimum time (in minutes) that a file must reside on disk before being considered a candidate for storage. Minimum time (in days) that a file must reside unaccessed on disk before being considered a candidate for truncation. Percentage of used disk space at which a relocation or truncation policy ceases to be applied. Invokes the cleanup (truncation) policy. Specifies the drivepool from which to allocate drives when storing files. Scans file system for candidate files to store or truncate and rebuilds the candidate lists. File system to which the policy will be applied. Invokes the relocation policy. Minimum file size (in bytes) to relocate or truncate.
fsqueue
The fsqueue command is used to view subsystem resource requests.
Command Syntax
fsqueue [ -r requestID ] fsqueue -m [ -r requestID ] fsqueue -f [ -r requestID | filename ]
254
fspolicy
Options / Arguments
[ -f ] [ -m ] filename [ -r requestID ] Reports files in the queue or specific files for a request identifier or filename. Reports media movement for a request identifier or all media in the queue. Path and file name of the file. Identifier of the request to be reported.
fsrecover
The fsrecover command is used to recover files back to disk that were removed from disk. The command only recovers the primary file copy, but once recovered, all copies are available.
Command Syntax
fsrecover filename [ -p ] [ -t starttime [ endtime ] ] fsrecover dirname -d [ -p ] [ -r ] [ -a ] fsrecover [RM_time::]filepathname -u [ -v ] fsrecover dirpathname -u [ -d ] [ -r ] [ -a ]
Options / Arguments
filename Name of the file to report on. The name can be a file name, a partial path name, or a complete path name. The % character is a wild card character. NOTE: Files that are recoverable no longer reside on disk, but are still located in the StorNext data base. The Trashcan does not have to be enabled to recover files. Name of the directory containing one or more files to recover. The name can be a directory name, partial path, or full path. The % character is a wild card. Full path of the file to recover. Optionally, you can have a timestamp of the form YYYY:MM:DD:hh:mm:ss::/stornext/snfs2/ rel1/sub1/file.a. If there are two files with the same paths that were removed at different times, use the timestamp to distinguish between them. When you specify the timestamp, put it with the pathname, as in the report. Full path of the directory containing the file(s) to recover. Indicates that recovery processing is requested. Indicates that directory recovery processing is requested.
dirname
[RM_time:]filepathname
dirpathname -u -d
255
[ -p ]
Specifies that the user report displays all entries for which the user has permissions (file entries to which the user has read access and directory entries to which the user has write access). If this option is not specified, the report to the user displays only user-owned entries. Indicates recursive processing is requested. Indicates a time range to restrict the length of the user report. The format of the starttime and endtime parameters is: YYYY:MM:DD:hh:mm:ss Specifies active files rather than recoverable files when either reporting or recovering a directory. Specifies the verbose mode during a recover sequence. The system reports on the recovered files.
[ -r ] [ -t starttime [endtime ] ]
[ -a ] [ -v ]
256
fsrecover
fsretrieve
The fsretrieve command is used to retrieve or recover a file from media and place it on disk. By default, the primary copy of a file is retrieved.
Command Syntax
fsretrieve [ -a ] filename fsretrieve filename -n newfilename [ -b startbyte endbyte ] [ -a ] fsretrieve filename -n newfilename -c [ -a ] fsretrieve -R directory [ -a ]
Options / Arguments
filename [ -c ] [ -n newfilename ] -R directory [ -b startbyte endbyte ] Full path and filename of the file to retrieve. Retrieves a secondary copy of the file (if a second copy exists). New path and name into which to retrieve the file. Directory from which to start recursive retrieval. Specifies a byte range to retrieve. The value of startbyte must be less than the endbyte value. Both values must be within the files byte range. Updates the access time of the requested files.
[ -a ]
fsrmcopy
The fsrmcopy command is used to remove a copy/copies of a file from disk or media.
Command Syntax
fsrmcopy [ -c copynum | -a ] filename fsrmcopy - m mediaID
Options / Arguments
filename [ -c copynum | a ] -m mediaID Removes a specific file (filename) or file to remove from disk or media. Deletes either a specific number of file copies (copynum) or all file copies (a) from the media. Deletes all files on media which reside on disk.
257
fsrmdiskcopy
The fsrmdiskcopy command removes a file copy from disk after the file is stored to media.
Command Syntax
fsrmdiskcopy filename
Options / Arguments
filename Full path and name of the file copy to remove from disk.
fsrminfo
The fsrminfo command is used to remove file information from the StorNext database.
Command Syntax
fsrminfo mediaID [ -f ]
Options / Arguments
mediaID [ -f ] The media identifier. Forces the removal of database information.
fsstate
The fsstate command is used to generate a report showing the state of drive components, storage subsystems, or the StorNext software.
Command Syntax
fsstate [ componentalias | -f ]
Options / Arguments
[ componentalias ] [ -f ] Alias for drives and storage subsystems. Generates a report showing the status of the StorNext software. Valid states are: Active, Not Active, Not Available
258
fsrmdiskcopy
fsstore
The fsstore command is used to expedite the storage of data to media, instead of allowing data migration by the StorNext software.
Command Syntax
fsstore filename [ -t mediatype ] [ -c copies ] [ -f i | p ] [ -v drivepool ] [ -z minsize ]
Options / Arguments
filename [ -c copies ] [ -f i | p ] Name of file on disk to store to media. Number of file copies to store, including the primary copy. File retention policy (-f) for the file. Files can be: i - Truncated immediately p - Truncated at policy application time [ -t mediatype ] [ -v drivepool ] [ -z minsize ] Defines the media type to use for storage. Specifies the Media Manager drive pool group used to store the file. Specifies the minimum file size (in bytes) to store.
fsversion
The fsversion command is used to determine a files current version. This command is useful because a file version saved by the Trashcan can fall back to older file versions.
Command Syntax
fsversion -h fsversion [ -a ] [ -v ] name fsversion -c ver [ -f ] name
259
Options / Arguments
name -h [ -a ] [ -v ] -c ver [ -f ] File for which the version number will be checked. Displays usage. Lists all available versions of the file (current and inactive). Verbose listing of the files current version (version number and modification time). Modifies the files current version to the specified inactive version. Forces the change operation.
fsusedspace
The fsusedspace command is used to report the total amount of stored primary copy data in the storage subsystem. This value is displayed in gigabytes (GB).
Command Syntax
fsusedspace
Options / Arguments
None
snrestore
The snrestore command is used to restore elements of a StorNext Storage Manager file system.
Command Syntax
snrestore [ -p temp_path ] [ -h ][ -e ] [ -r restore_path ] [ -m | -mj [ file_system_name ] ] [ -d | -dj ] [ -c | -cl component ]
260
fsusedspace
Options / Arguments
[ -p temp_path ] Specifies a temporary storage directory for restored files. By default, this directory is /usr/ adic/TSM/tmp. Requests help for the entered command. Extracts files to the temporary storage directory. Specifies the directory files to restore. No files are restored from media. Specifies the file system metadata restore values. You can specify: m - Restore all software configuration information or for the selected optional file system. mj- Restore file system journal information for all file systems or for the selected optional file system. [ -d | -dj ] Specifies the database restore values. You can specify: d - Restore database and journal files. dj - Restore only the journal files and apply them to the existing database on the system. [ -c | -cl component ] Specifies the software files you restore. You can specify: c - Restore all software configuration information. cl component - Restore the specified software component. Use the -h option to find a list of available components.
[ -h ] [ -e ] [ -r restore_directory_path ] [ -m | -mj [ file_system_name ] ]
Examples
Restore all components from backup located on tape media: snrestore Restore database from backup located on tape media and use the /tmp temporary directory: snrestore -d -p /tmp Restore database journals from backup located on tape media. snrestore -dj Restore from a backup file located in the /backup directory. StorNext Management Suite System Administrator Guide 261
snrestore -r /backup Restore TSM and DSM configuration components from storage disk /sdisk. snrestore -cl TSM -cl DSM Restore file system data for snfs1 file system. snrestore -m snfs1
vsarchiveqry
The vsarchiveqry command is used to query for information about an archive.
Command Syntax
vsarchiveqry archivename | -a [ -cdmtv ] [ -Ih ] [ -H hostname ] [ -P priority ] [ -R retries ] [ -T timeout ] [ -V number ]
Options / Arguments
archivename | -a [ -c ] [ -d ] [ -m ] [ -t ] [ -v ] [ -l ] [ -h ] [ -H hostname ] [ -P priority ] Specifies the archive (archivename) to be queried or that all archives (-a) will be queried. Indicates that detailed information on all media classes associated with the specified archive(s) will be reported. Indicates that all drives associated with the specified archive(s) will be reported. Indicates that all media associated with the specified archive(s) will be reported. Indicates that detailed information on all media types associated with the specified archive(s) will be reported. Indicates that all drives, media classes, media, and media types associated with the specified archive(s) will be reported. Indicates that command line options are read from stdln. Requests help for the entered command. Hostname of the Media Manager server. Execution priority of the entered command. Default: 15 Valid values: 1 to 32 Number of retries that the software attempts if a timeout is received. Default: 3
[ -R retries ]
262
vsarchiveqry
[ -T timeout ]
Time interval (in seconds) that the software waits for status before returning a timeout. Default: 120 RPC program number for the software. Default: 300016
[ -V number ]
Examples
Requests that the Media Manager software return the media classes and the media types associated with the shelf1 archive: vsarchiveqry shelf1 -ct Requests that the Media Manager software return the drives, media, media classes, and media types associated with the stage1 archive: vsarchiveqry stage1 -v
vsdriveqry
The vsdriveqry command queries for information about the specified drive.
Command Syntax
vsdriveqry driveID [ -Ih ] [ -H hostname ] [ -P priority ] [ -R retries ] [ -T timeout ] [ -V number ] vsdriveqry -a [ -Ih ] [ -H hostname ] [ -P priority ] [ -R retries ] [ -T timeout ] [ -V number ]
263
Options / Arguments
driveID | -a [ -l ] [ -h ] [ -H hostname ] [ -P priority ] Indicates a specific drive (driveID) or all drives (-a) to be queried. Indicates that the command line options are to be read from stdln. Requests help for the entered command. Hostname of the Media Manager server. Execution priority of the entered command. Default: 15 Valid values: 1 to 32 Number of retries that the software attempts if a timeout is received. Default: 3 Time interval (in seconds) that the software waits for status before returning a timeout. Default: 120 RPC program number for the software. Default: 300016
[ -R retries ] [ -T timeout ]
[ -V number ]
Examples
Requests that the Media Manager software return information on every drive known to the Media Manager system: vsdriveqry -a
264
vsdriveqry
vsdrivevary
The vsdrivevary command is used to change (vary) the operational availability state of a drive.
Command Syntax
vsdrivevary driveID -s state [ -v ] [ -lh ] [ -H hostname ] [ -P priority ] [ -R retries ] [ -T timeout ] [ -V number ] vsdrivevary -p drivepool -s state [ -v ] [ -lh ] [ -H hostname ] [ -P priority ] [ -R retries ] [ -T timeout ] [ -V number ]
Options / Arguments
driveID -p drivepool -s state [ -v ] [ -l ] [ -h ] [ -H hostname ] [ -P priority ] Specifies the drive(s) whose state is to be varied. Specifies the drivepool for which associated drives states will be varied. Specifies the target state of the specified drive. Verbose listing (status information) of varied drives. Indicates that command line options are read from stdln. Requests help for the entered command. Hostname of the Media Manager server. Execution priority of the entered command. Default: 15 Valid values: 1 to 32 Number of retries that the software attempts if a timeout is received. Default: 3 Time interval (in seconds) that the software waits for status before returning a timeout. Default: 120 RPC program number for the software. Default: 300016
[ -V number ]
Examples
Requests that the Media Manager software vary all drives in the drvpoolusr drive pool to the offline state and to return status on every drive in drvpoolusr: vsdrivevary -p drvpoolusr -s offline -V
265
vsmedclassqry
The vsmedclassqry command queries for the attributes of a specified Media Class group or all Media Class groups. The members of the Media Class group and any additionally requested information on each medium is returned.
Command Syntax
vsmedclassqry mediaclass [ -m | -v ] [ -Ih ] [ -H hostname ] [ -P priority ] [ -R retries ] [ -t timeout ] [ -V number ] vsmedclassqry -a [ -m | -v ] [ -Ih ] [ -H hostname ] [ -P priority ] [ -R retries ] [ -t timeout ] [ -V number ]
Options / Arguments
mediaclass | -a [ -m ] [ -v ] [ -l ] [ -H hostname ] [ -P priority ] Specifies a media class (mediaclass) or all media classes (-a) on which to request information. Requests a list of media identifiers for all media associated with each reported media calss. Requests detailed information for all media associated with each reported media class. Indicates that command line options are to be read from stdln. Hostname of the Media Manager server. Execution priority of the entered command. Default: 15 Valid value: 1 to 32 Number of retries that the software attempts if a timeout is received. Default: 3 Time interval (in seconds) that the software waits for status before returning a timeout. Default: 120 RPC program number for the software. Default: 300016
[ -V number ]
Examples
Requests that the Media Manager software return information on every Media Class group known to the Media Manager system. No media-specific information is requested. vsmedclassqry -a Requests that the Media Manager software return detailed information for every medium in the medclassh1user Media Class group: vsmedclassqry medclassh1user -m 266 vsmedclassqry
vsmedqry
The vsmedqry command queries for the attributes of one or more specified media
Command Syntax
vsmedqry mediaID [ -Ih ] [ -H hostname ] [ -P priority ] [ -R retries ] [ -T timeout ] [ -V number ] vsmedqry -a [ -Ih ] [ -H hostname ] [ -P priority ] [ -R retries ] [ -T timeout ] [ -V number ]
Options / Arguments
mediaID | -a [ -l ] [ -h ] [ -H hostname ] [ -P priority ] Specifies a media type (mediaID) or all media (-a) to be queried. Indicates that command line options are to be read from stdln. Requests help for the entered command. Hostname of the Media Manager server. Execution priority of the entered command. Default value: 15 Valid values: 1 to 32 Number of retries that the software attempts if a timeout is received. Default value: 3 Time interval (in seconds) that the software waits for status before returning a timeout. Default value: 120 RPC program number for the software. Default value: 300016
[ -V number ]
Examples
Requests that the Media Manager software return information on every medium known to the Media Manager system: vsmedqry -a
267
vspoolcfg
The vspoolcfg command is used to configure a drive pool.
Command Syntax
vspoolcfg -p drivepool -c driveID | -d | -i driveID | -r driveID [ -Ih ] [ -H hostname ] [ -P priority ] [ -R retries ] [ -T timeout ] [ -V number ]
Options / Arguments
- p drivepool - c driveID -d - i driveID - r driveID [ -l ] [ -h ] [ -H hostname ] [ -P priority ] [ -R retries ] [ -T timeout ] [ -V number ] Configures the specified drive pool. Creates a drive pool with a list of drive identifiers. Deletes the drive pool. Inserts drives into an existing drive pool. Removes drives from an existing drive pool. Indicates that command line options are to be read from stdln. Requests help for the entered command. Hostname of the Media Manager server. Execution priority of the entered command. Number of retries attempted if the software receives a timeout. Time interval (in seconds) that the software waits for status before returning a timeout. RPC program number for the software.
268
vspoolcfg
vsreclassify
The vsreclassify command changes the Media Class group associated with the specified media.
Command Syntax
vsreclassify mediaID -c currentmediaclass -n newmediaclass [ -v ] [ -Ih ] [ -H hostname ] [ -P priority ] [ -R retries ] [ -T timeout ] [ -V number ]
Options / Arguments
mediaID -c currentmediaclass -n newmediaclass [ -v ] [ -l ] [ -h ] [ -H hostname ] [ -P priority ] Specifies one or more media to reclassify. Specifies the media class with which the specified media is to be associated. Specifies the new media class with which the specified media is to be associated. Specifies verbose output. Indicates that command line options are to be read from stdln. Requests help for the entered command. Hostname of the Media Manager server. Execution priority of the entered command. Default: 15 Valid values: 1 to 32 Number of retries that the software attempts if a timeout is received. Default: 3 Time interval (in seconds) that the software waits for status before returning a timeout. Default: 120 RPC program number for the software. Default: 300016
[ -V number ]
Examples
Requests that the Media Manager software reclassify media MED002, MED023 and MED044 from media class medclassm1 to medclassstgsm11 and return status on the medium only if processing for that medium was unsuccessful. vsreclassify MED002 MED023 MED044 -c medclassm1 -n medclassstgsm1
269
270
vsreclassify
C
StorNext Configuration and Administration Tasks
Use the following information to perform specific file system configuration tasks that do not apply to a typical StorNext set up.
Sharing a Library Between Applications

If two or more software applications (on one or multiple machines), are configured to use the same library, then you must use the following procedure to enable the library to be shared and to prevent media being overwritten when these applications are used. This task must be performed when the Configuration Wizard (CW) is run during initial StorNext setup and configuration. For more information on using the CW, refer to the StorNext Installation Guide.
Note
For library sharing to be effective, the steps in the following procedure must be performed in the order in which they are presented.
You must have root privileges to perform this task. 1 When you match hardware devices to their correct slots on the Matched Devices With Slots screen (you will see this screen during the execution of Step 4 of the Configuration WIzard, Add Tape Drive), only configure the tape drives that your software application will use. You do not need to configure all tape drives listed as part of the library. Once the tape drives are added and configured in Step 4 of the CW (Add Tape Drive), but before continuing to Step 5 of the CW (Add Media), go to a metadata controller and perform these steps: a. Change directory to the config directory. Type: cd /usr/adic/MSM/internal/config b. List all files in the config directory. Type: ls -l c. Using a text editor, edit the media_file_<library_name> file. For example: vi media_file_<library_name>
271
The media_file contains a filter for barcode labels that are read by StorNext. This action is performed by using regular expressions. (A regular expression provides a mechanism to select strings from a set of character strings. In the above example, the character strings refer to the barcode labels.) In the example above, <library_name> is the library that was configured in Step 3, Add Library, of the CW. d. Set up the pattern matching of the media file. Multiple entries may exist in the media file. Read the examples in the file to learn how to set up pattern matching. These are examples of pattern matching: scsi_archive 1111.. (brings in all media with the 1111 prefix) scsi_archive AB9... (brings in all six-character media labels with the AB9 prefix) scsi_archive CLN1.. (brings in all media that have the CLN1 prefix) 3 Continue to the Add Media section of the Configuration Wizard.
Manually Modifying System Configuration

StorNext employs global parameters that define the file system. These parameters are located in files in the /usr/adic/TSM/config directory. Although the default values in these files are sufficient for most installations, you can edit the files to customize the StorNext software for your specific installation. This section provides a procedure that can be used to modify three different StorNext configuration files: fs_sysparm, filesize.config, and log_params.
fs_sysparm Configuration File

The fs_sysparm configuration file is used to tune items related to system administration, drives and media, media manager interface, and other miscellaneous items. For more information about the parameters in the fs_sysparm configuration file, refer to the fs_sysparm.README file.
CAUTION
Incorrect modification of the fs_sysparm configuration file can cause a serious, adverse effect on StorNext functionality. Before modifying this file, ADIC recommends that you contact ATAC.
CAUTION
If you have files larger than 100GB and are using LTO2 media, the MED_SEG_OVER_LTO parameter may be modified to a value less than or equal to 190G to reduce file fragmentation. This has the adverse effect of reducing the potential for parallel I/O for multiple file segments. Setting the MED_SEG_OVER_LTO parameter to a value larger than 190GB may result in allocation failures that prevent file movement to tape.
272
Manually Modifying System Configuration
filesize.config Configuration File

The filesize.config configuration file is used to control the file steering feature and has these characteristics: Allows the placement of files on different media types, based on the size of the files Specifies which drive pool a policy class should use when storing data Contains specific syntax and usage information Enables the system administrator to make changes without recycling the Tertiary Manager software
log_params Configuration File

The log_params configuration file is used to control various levels of trace logging. The file specifies each log level and how to enable and/or disable it. Use the following procedure to modify the fs_sysparm, filesize.config, and log_params configuration files. Use the following procedure to modify a configuration file 1 2 Use a text editor to open the configuration file located in the /usr/adic/TSM/config directory. Locate the parameter you want to modify and replace the setting with a new, valid value. All entries must be in the format: name=value; with no blank spaces around the equal (=) sign and each value terminated with a semicolon (;). 3 Recycle the Tertiary Manager software. a. Stop the software by typing TSM_control stop b. Restart the software by typing TSM_control start
Viewing a Fibre Channel Device

Use this procedure to add a Fibre Channel (FC) device. Before adding a FC device, first configure the Host Bus Adapter (HBA) card so you can view the device. Use the fs_scsi -p command to make sure you can view your devices over FC. FC devices include tape libraries, individual drives, or RAID disk. The fs_scsi -p command is only available if the storage manager is installed on the FSM server.
Note
1
Type the /usr/adic/TSM/util/fs_scsi -p command to make sure that the necessary devices can be viewed over FC. To view tape libraries, access the StorNext GUI to view your tape libraries. To view individual drives or RAID LUNs, access either the StorNext or SNFS GUI.
To add a disk, refer to Adding Disks on page 98. To add tape drives to configured libraries, refer to Configuring a Tape Drive on page 128. StorNext System Administrator Guide 273
StorNext Log Rolling Administration

Use the following procedures to configure StorNext log rolling options.
Changing Log Rolling Times

Use this procedure to change the frequency of rolling the StorNext logs. This process requires that you edit the tldm crontab to set log times. Use this procedure to edit tdlm crontab. 1 2 Log on as root. Edit the tdlm crontab and update the sn_log_update script. Below is an example crontab: 0 * * * * /usr/adic.bin/cmdwrap /usr/adic/util/sn_log_update /usr/adic where 0 * * * * designates the times when logs run. In the above example, the logs run every hour.
Log Rolling Options

Note
In this release of StorNext the sn_log_update information is overwritten and no longer contains the $DEF_SIZE or the $DEF_LOGS variables. These entries are now contained in the sn_log_update.cfg file
You can change these options to optimize log rolling. -s: This option sets the directory where logs are saved (copied) to as they are rolled. This directory is typically a managed directory. For example: sn_log_update [-s <dir>] where <dir> is the directory where you want the logs to reside. $DEF_SIZE = 2000000: This is the default size at which logs are rolled. Edit this entry in the /usr/adic/util/sn_log_update.cfg file if you want the log sizes to be larger or smaller. $DEF_LOGS = 7: This is the default number of logs that are saved before they are deleted. Edit this entry in the /usr/adic/util/sn_log_update.cfg file if you want to save less than 7 logs or are saving the logs to a managed directory.
Avoiding Poor System Performance

Most systems run administrator scripts to rebuild namespace databases and/or to remove certain files. Unfortunately, running these scripts can degrade StorNext performance. It is recommended that you review administrator scripts to determine if they may adversely affect your StorNext installation and its performance.
274
StorNext Log Rolling Administration
For example, many UNIX systems have a find command in the root crontab that traverses the entire directory hierarchy while searching for old temporary and core files. Typically, the find commands are configured only to run on the local file system. However by default, these commands do not skip StorNext file systems because they are considered to be local, even though the file system manager may be running remotely. StorNext performance can be dramatically degraded when these commands visit a StorNext file system if the system contains a large number of files. If StorNext performance is degraded to an unacceptable level due to the operation of administrator scripts, you can modify them to skip StorNext file systems. A sample command (original and modified is shown below: On IRIX, by default, the root crontab contains the following find command: find / -local -type f '(' -name core -o -name dead.letter ')' -atime +7 -mtime + 7 -exec rm -f '{}' ';' To prevent the find command from searching in StorNext file systems, modify it as shown: '(' -type d -fstype cvfs -prune ')' -o The modified find command looks like this: find / -local '(' -type d -fstype cvfs ')' -o -type f '(' -name core o -name dead.letter ')' -atime +7 mtime +7 -exec rm -f '{}' ';'
275
276
Avoiding Poor System Performance
D
StorNext Files
StorNext creates a series of files that are used and modified to configure a file system. This section includes an expanded example.cfg file and a listing of the most commonly used StorNext files with descriptions and locations for each.
The example.cfg File

The following is listing of the configuration file created by StorNext. This file is modified during the configuration of a file system. The location for this file is: /usr/cvfs/examples/example.cfg # ************************************************************************* # A global section for defining file system-wide parameters. # # For Explanations of Values in this file see the following: # # UNIX Users: man cvfs_config # Windows Users: Start > Programs > StorNext File System > Help > # Configuration File Internal Format # ************************************************************************* GlobalSuperUser Systems ## WindowsSecurity Quotas FileLocks DataMigration InodeExpandMin InodeExpandInc InodeExpandMax FsBlockSize JournalSize AllocationStrategy Yes No No No No 32K 128K 8M 4K 4M Round 277 ## SNMS Managed File Systems Only ## ## Must be set to Yes for SNMS Managed File
MaxConnections ForceStripeAlignment Debug MaxLogSize MaxLogs # # Globals Defaulted # # ThreadPoolSize # InodeCacheSize # BufferCacheSize # StripeAlignSize # MaxMBPerClientReserve # OpHangLimitSecs
32 Yes 0x0 4M 4
64
# default 16, 2 MB memory per thread
32K # 800-1000 bytes each, default 8K 64M # default 32MB 2M # auto alignment, default MAX(StripeBreadth) 50 # in MBs, default 100MB reserved per client 300 # default 180 secs
# DataMigrationThreadPoolSize 128 # Managed only, default 8 # ************************************************************************* # A disktype section for defining disk hardware parameters. ************************************************************************* [DiskType MetaDrive] ##1+1 Raid 1 Mirrored Pair## Sectors XXXXXXXX SectorSize 512 [DiskType JournalDrive] ##1+1 Raid 1 Mirrored Pair## Sectors XXXXXXXX SectorSize 512 [DiskType VideoDrive] ##8+1 Raid 5 Lun for Video## Sectors XXXXXXXX SectorSize 512 [DiskType AudioDrive] ##4+1 Raid 3 Lun for Audio## Sectors XXXXXXXX SectorSize 512 [DiskType DataDrive] ##4+1 Raid 5 Lun for Regular Data## Sectors XXXXXXXX SectorSize 512 278 The example.cfg File ## Sectors Per Disk From Command "cvlabel -l" ##
# ************************************************************************* # A disk section for defining disks in the hardware configuration. ************************************************************************* [Disk CvfsDisk0] Status UP Type MetaDrive [Disk CvfsDisk1] Status UP Type JournalDrive [Disk CvfsDisk2] Status UP Type VideoDrive [Disk CvfsDisk3] Status UP Type VideoDrive [Disk CvfsDisk4] Status UP Type VideoDrive [Disk CvfsDisk5] Status UP Type VideoDrive [Disk CvfsDisk6] Status UP Type VideoDrive [Disk CvfsDisk7] Status UP Type VideoDrive [Disk CvfsDisk8] Status UP Type VideoDrive
279
[Disk CvfsDisk9] Status UP Type VideoDrive [Disk CvfsDisk10] Status UP Type AudioDrive [Disk CvfsDisk11] Status UP Type AudioDrive [Disk CvfsDisk12] Status UP Type AudioDrive [Disk CvfsDisk13] Status UP Type AudioDrive [Disk CvfsDisk14] Status UP Type DataDrive [Disk CvfsDisk15] Status UP Type DataDrive [Disk CvfsDisk16] Status UP Type DataDrive [Disk CvfsDisk17] Status UP Type DataDrive
280
# ************************************************************************* # A stripe section for defining stripe groups. # ************************************************************************* [StripeGroup MetaFiles] Status UP MetaData Yes Journal No Exclusive Yes Read Enabled Write Enabled StripeBreadth 256K MultiPathMethod Rotate Node CvfsDisk0 0 [StripeGroup JournFiles] Status UP Journal Yes MetaData No Exclusive Yes Read Enabled Write Enabled StripeBreadth 256K MultiPathMethod Rotate Node CvfsDisk1 0 [StripeGroup VideoFiles] Status UP Exclusive Yes##Exclusive StripeGroup for Video Files Only## Affinity VideoFiles Read Enabled Write Enabled StripeBreadth 4M MultiPathMethod Rotate Node CvfsDisk2 0 Node CvfsDisk3 1 Node CvfsDisk4 2 Node CvfsDisk5 3 Node CvfsDisk6 4 StorNext System Administrator Guide 281
Node CvfsDisk7 5 Node CvfsDisk8 6 Node CvfsDisk9 7 [StripeGroup AudioFiles] Status UP Exclusive Yes##Exclusive StripeGroup for Audio File Only## Affinity AudioFiles Read Enabled Write Enabled StripeBreadth 1M MultiPathMethod Rotate Node CvfsDisk10 0 Node CvfsDisk11 1 Node CvfsDisk12 2 Node CvfsDisk13 3 StripeGroup RegularFiles] Status UP Exclusive No##Non-Exclusive StripeGroup for all Files## Read Enabled Write Enabled StripeBreadth 256K MultiPathMethod Rotate Node CvfsDisk14 0 Node CvfsDisk15 1 Node CvfsDisk16 2 Node CvfsDisk17 3
282
Commonly Used SNFS Files

The following is a list of commonly used SNFS files and provides the name and location of the files installed during a SNFS installation. Each entry also includes a brief description of the files utility in SNFS functionality. /usr/cvfs/bin/ cvadmin Allows you to view and modify the active SNFS system(s). cvaffinity Associates a stripe group with a media type. cvcp A high-speed file copy utility. cvdb A client debugging tool. cvdbset A wrapper for cvdb. cvfsck A utility to check and repair a SNFS file system. cvfsd SNFS server daemon launched at mount time. cvfsdb A metadata debugging tool. cvfsid Provides the SNFS site identifier cvlabel Lists and labels SNFS drives. cvmkdir Associates an affinity with a directory. cvmkfile Pre-allocates space and attributes for a file. cvmkfs Initializes a SNFS file system cvupdatefs Modifies the configuration of an existing SNFS file system. cvversions Lists SNFS version information. fsm A SNFS server daemon. fsmpm A SNFS portmapper daemon. mount_cvfs A mount helper for SNFS. snfsdefrag Defragments files and file systems. /usr/cvfs/config/ fsmlist A list of SNFS file systems that have been serviced. fsnameservers Identifies the SNFS name service coordinators. license.dat The SNFS license file. /usr/cvfs/data/<FS Name>/log/ Cvlog debug and runtime messages /usr/cvfs/debug/ cvfsd.out Displays debug and status messages from cvfsd. fsmpm.out Displays debug and status messages from fsmpm. mountall.out Displays debug and status messages from mount_cvfs. nssdbg.out Displays debug and status messages from fsmpm.
283
/usr/cvfs/CLIENTS/ The following are client installation files for various operating systems. sn_dsm_aix52_client.tar sn_dsm_irix65f_client.tar sn_dsm_irix65m_client.tar sn_dsm_linuxRH_80i386smp_client.tar sn_dsm_linuxRH_80i386up_client.tar sn_dsm_linuxRH_AS_3i386smp_client.tar sn_dsm_linuxRH_AS_3ia64smp_client.tar sn_dsm_linuxSuSE_81i386smp_client.tar sn_dsm_linuxSuSE_81i386up_client.tar sn_dsm_solaris58sparc64_client.tar sn_dsm_solaris59sparc64_client.tar sn_dsm_win2k_client.exe sn_dsm_winnt_client.exe /usr/cvfs/docs/ external_api.pdf Documentation for the SNFS API. /usr/cvfs/examples/ The following are examples of files that are present in certain file system configurations. For example, the cvfail.example will be in the configuration file of a system running failover. cvfail.example cvlabels.example cvpaths.example example.cfg fsmlist.example fsnameservers.example fsports.example fsroutes.example /usr/cvfs/lib/ cvextapi.a A SNFS API library. libcvfsdmapi.a A SNFS DMAPI library. /usr/cvfs/src/ cvapi.c A sample API application.
284
Commonly Used SNFS Files
E
Quality of Service Guide
Introduction
This document describes how to configure and use the StorNext File System (SNFS) Quality of Service (QOS) feature. QOS allows real-time applications to reserve some amount of bandwidth on the storage system. This is known as real-time I/O (RTIO). SNFS gates (that is, throttles) non-realtime applications so their I/O accesses do not interfere with the real-time application. QOS is a passive implementation in that it does not actively monitor a process activity and then schedule the process so that it receives the bandwidth it has requested. It is up to real-time applications to gate their own I/O requests to the desired rate. SNFS QOS provides a "get out of the way" gating for non-real-time I/O requests so they do not hinder the real-time requests. QOS is fully functional in SNFS version 2.1.2 and later. Earlier versions of SNFS do not support QOS. If a pre-QOS client connects, the file system manager (FSM) logs a message to syslog. If the preQOS client connects while real-time I/O is in progress, the message is logged at the critical event level. The remainder of this document explains the client and server configuration settings for QOS; describes the use of tokens and callbacks for gating non-real-time I/O; describes setting real-time I/ O on a file; and discusses the performance monitoring tools that are available for diagnosis.
Overview
QOS is stripe-group centric; all configuration and operations act on a specific stripe group. This allows stripe groups with differing access characteristics to use different real-time settings. When a client requests a certain amount of real-time I/O, the FSM informs all connected clients of the amount remaining and available for non-real-time I/O accesses. This information is encapsulated in a token. Think of the token as a capability that enables the client to perform I/O without contacting the FSM. When the amount of real-time I/O on a stripe group changes, the FSM informs all connected clients about the change via a callback. In both the client and the server, QOS is implemented as a state machine. Each state has a set of events and allowable actions. In this document, the term state thusly refers to the internal state machine.
285
Active vs. Passive

QOS is a passive, not active implementation of real-time I/O. In an active implementation (such as the SGI IRIX guaranteed rate I/O known as GRIO), the scheduler is tightly coupled with the I/O subsystem. The qualities of the disk subsystem are well known so the scheduler can guarantee that a process will be scheduled such that it will receive the required amount of bandwidth. Since SNFS is a cross-platform file system that does not have hooks in the operating system scheduler, it cannot provide such a guarantee. In a passive implementation, a real-time process gates its I/O according to some outside metric (such as a frame rate for specific video formats). The file system then gates all other non-real-time I/O so they do not interfere. These differences cannot be over-stressed. It is a misconception to think that QOS, despite its name, guarantees a specific amount of real-time I/O to a process.
Supported Platforms
QOS has been tested on Windows 2000, XP, Linux, IRIX, and Solaris. In the Windows world, an application gets a handle to a file to perform I/O, usually via the Win32 CreateFile() API. In the UNIX world, an application receives a file descriptor (fd) via the open(2) system call. In this document, handle is synonymous with fd.
Configuration
The primary configuration for QOS is in the FSM configuration file. No client configuration is required, although there is a QOS tuning parameter that can be specified when the file system is mounted.
Unit of I/O
Real-time I/O is based on well-formed I/O. This means that for the purposes of determining bandwidth rates, well-formed I/O is characterized as being a stripe width in size. This makes the best utilization of the disks in the stripe group and maximizes the transfer rate. Internally, non-real-time I/O is tracked by number of I/O operations per second. An I/O operation is a minimum of a file system block size, and a maximum of the file system block size multiplied by the stripe breadth (FsBlocksize * StripeBreadth). FsBlockSize <= I/O <= (FsBlocksize * StripeBreadth)
Converting MB/sec to I/O/sec

Typically, it is easier to qualify an I/O subsystem in terms of MB/sec that can be sustained. However, internally the file system tracks everything on an I/O/sec basis. Note that the file system tracks only non-real-time I/O (that is, it gates only non-real-time I/O). An I/O is a minimum of the file system block size, and is typically the point at which the file system hands the request off to the disk driver (IoCallDriver in Windows, or a strategy call in UNIX). The file system counts the number of I/Os that have taken place during a given second. If the number exceeds that which is allotted, the request is pended until I/O becomes available (typically in the next second). I/O is honored in FIFO fashion; no priority is assigned.
286
Configuration
To convert between I/Os and MB/sec, SNFS uses a somewhat unique formula that quantifies I/O as well-formed. The rationale behind this is due to the way in which many video applications make realtime I/O requests. To optimize the disk subsystem, real-time I/Os are well-formed so they saturate the disks. In SNFS terminology, this would be an I/O that covers all of the disks in a stripe. This can be expressed as follows:
ios_sec = mb_sec / (stripe_breadth * stripe_depth *fs_blocksize)

For example, with a file system blocksize of 4k, a stripe_breadth of 384, and a stripe_depth of four, the equivalent number of I/Os/sec for each well-formed I/O would be 216 Mb/ sec / (384 * 4 * 4k). This is equivalent to 221184 k/sec / 6144k= 36 I/O/sec.
Server Configuration
All storage subsystems are different, so users must qualify the I/O subsystem and determine the maximum amount of I/O bandwidth available. SNFS relies on the correct setting in the configuration file; if the storage system changes (for example, because of a new disk array,) the user must requalify the I/O subsystem to determine the amount of bandwidth available. This amount will be specified in the FSM configuration file. The user can also specify the minimum amount of bandwidth to be provided to non-real-time applications. There are five keywords controlling QOS that can be specified in the stripe group section of the FSM configuration file. Not all keywords need be present. Typically, the user specifies the RTIO bandwidth in terms of either number of I/O operations per second (rtios) or megabytes per second (rtmb). Keywords are not case sensitive. For a minimum configuration, only the real-time limit (either rtios or rtmb) need be specified. All other configuration variables default to reasonable values. Table 1 QOS Configuration Keywords
Name Rtios Rtmb RtiosReserve
Description The maximum number of real-time I/Os allowed in a stripe group during any one-second period. Maximum amount of real-time MB/sec allowed on the stripe group during any one-second period.
Default 0 (no real-time) 0 (no real-time)
Amount of reserve in I/Os/sec from the maximum Equivalent to allowed for non-real-time I/Os. Must be greater than 1MB/sec the equivalent to 1MB/sec or the amount that can be transferred to a single stripe line. Amount to reserve in MB/sec from the maximum 1MB/sec allowed for non-real-time I/O. Must be greater than 1. Time in seconds to wait for clients to respond to a token callback. 2 seconds
RtmbReserve RtTokenTimeout
287
RTIO Upper Bound

The limit will be specified in terms of I/Os per second (parameter Rtios) or in terms of MB/sec (parameter Rtmb). Case is not sensitive. Note that I/Os per second are I/Os of any size to the disk subsystem. Either or both may be specified. If both are specified, the lower limit is used to throttle I/O. If neither is specified, no real-time I/O is available on the stripe group. These parameters are applied to a stripe group definition.
[StripeGroup MyStripeGroup] Rtios 2048 Rtmb 10

The above example specifies that the storage system can support a maximum of 2048 I/Os per second at any instant, aggregate among all the clients, or 10 MB/sec, whichever is lower. Most real-time I/O requests will be a stripe line at a time to maximize performance. Non-real-time I/Os will be a minimum of a file system block size. It is important to realize that the rtios and rtmb settings refer to the total amount of sustained bandwidth available on the disk subsystem. Any I/O, either real-time or non-real-time, will ultimately be deducted from this overall limit. The calculations of available real-time and non-real-time are discussed later. Specifying rtmb in the FSM configuration file is only recommended if all I/Os are well formed (that is, a full stripe width). Otherwise, the conversion between MB/sec and I/Os/sec using the well-formed I/O calculation could lead to unexpected results.
Note
Reserve
To prevent deadlock, the QOS implementation never allows zero I/O/sec for non-real-time I/O. Otherwise, a system could block with many critical file system resources held waiting for I/O to become available. This is especially true via flush-on-close I/O via the buffer cache. It becomes extremely difficult to diagnose system hangs because no I/O is available. For this reason, QOS always reserves some amount of I/O for non-real-time I/O. The minimum amount of non-real-time I/O reserved for non-real-time applications is one MB/sec. This can be changed via the stripe group section parameters (again, case is not sensitive). If both are specified, the lower of the two amounts is chosen. This amount is shared by all non-real-time applications on each client.
[StripeGroup MyStripeGroup] RtiosReserve 256 RtmbReserve 2
Token Timeouts
The RtTokenTimeout parameter controls the amount of time the FSM waits for clients to respond to callbacks. In most normal SANs, the default two-second setting is sufficient. This value may need to be changed for a SAN that has a mixture of client machine types (Linux, NT, IRIX, etc.) that all have different TCP/IP characteristics. Also, large numbers of clients (greater than 32) may also require increasing the parameter.
288
Configuration
For example, if the FSM should ever fail, the clients will attempt to reconnect. When the FSM comes back online, the amount of time the clients take to re-establish their TCP/IP connection to the FSM can differ wildly. To avoid unnecessary timeouts, the RtTokenTimeout parameter can be increased, meaning the FSM waits longer for callback responses. If a client times out on a token retraction, the original requestor receives an error from the FSM that includes the IP address of the offending client. This error is logged to syslog, and alternatively to the desktop on Windows clients. This can help in diagnosing reconnect failures, and in determining if the token time value should be increased.
Client Configuration
When a client obtains a non-real-time I/O token from the FSM, the token allows the client a specific amount of non-real-time I/O. If the client is inactive for a period of time, the token is relinquished and the non-real-time I/O released back to the FSM for distribution to other clients. The timeout period is controlled by the nrtiotokenhold mount option on UNIX platforms, and the QOS Token Hold Time parameter in the mount options tab of the SNFS control panel on Windows platforms. The default is sixty (60) seconds. This means that after sixty seconds without non-real-time I/O on a stripe group, the non-real-time token for that stripe group is released. The parameter should be specified in five (5) second increments. If it is not, it will be silently rounded up to the next five-second boundary. If the syslog level is set to debug, the file system dumps out its mount parameters so the value can be seen.
Real-time I/O
A process requests real-time (ungated) I/O by using the SNFS External API SetRtio call (F_SETRIO ioctl). A library function is included in the External API sample source code that provides all the required cross-platform handling. As an example, assume that a video playback application requires a constant rate of 186 MB/sec to correctly display images without dropping any frames. The application gates itself; that is, it requests I/O at a rate to satisfy the requirements of correctly displaying an image. QOS provides a mechanism so other I/O requests do not perturb the real-time display. In the following example, assume the I/O subsystem has been qualified at 216 MB/sec. The file system block size is 4k. The disk subsystem is actually a large RAID array that internally maps many drives to a single LUN. There are four LUNs in the stripe group; each LUN is optimized for a 1.5 MB transfer. This corresponds to the following in the fsm configuration file:
[StripeGroup MyStripeGroup] StripeBreadth 384 Node CvfsDisk0 0 Node CvfsDisk1 1 Node CvfsDisk2 2 Node CvfsDisk3 3 Rtmb 216
Also, assume there is only one stripe group for user data in the file system. As recommended by ADIC, there may be other stripe groups for metadata and journal that are not shown.
289
SetRtio
Initially, all stripe groups in the file system are in non-real-time mode. Clients make their requests directly to the I/O subsystem without any gating. In our example, the process requires 186 MB/sec and the system designers know there will never be a need to support more than one stream at 186 MB/sec. The SetRtio request has a number of flags and parameters to control its operation. These are all documented in the external_api.pdf file that describes the external API in detail. For this example, set the handle for the indicated stripe group using the RT_SET parameter.
Oversubscription
In most cases, system designers ensure that the amount of rtio is not oversubscribed. This means that processes will not ask for more rtio than is specified in the configuration file. However, it is possible to request more rtio than is configured. The API uses the RT_MUST flag to indicate that the call must succeed with the specified amount. If the flag is clear, the call allocates as much as it can. In both cases, the amount allocated is returned to the caller.
Handles
The SetRtio call accepts two different types of handles. The first is a handle to the root directory. In this mode the stripe group is put into real-time mode, but no specific file handle is tagged as being ungated. Real-time I/O continues on the stripe group until it is explicitly cleared with a SetRtio call on the root directory that specifies the RT_CLEAR flag; the file system is unmounted; or the system is rebooted. It is up to the application to make a subsequent call to EnableRtio (F_ENABLERTIO) on a specific handle. If the handle in the SetRtio call refers to a regular file, it is the equivalent of a SetRtio call on the root directory followed by an EnableRtio call. The file handle will be ungated until it is closed, cleared (RT_CLEAR in a SetRtio call), or disabled (DisableRtio). When the handle is closed, the amount of real-time I/O is released back to the system. This causes the FSM to readjust the amount of bandwidth available to all clients by issuing a series of callbacks. The client automatically issues a call to the FSM with the RT_CLEAR flag specifying the amount of real-time I/O set on the file. If multiple handles are open on the fileeach with a different amount of real-time I/Oonly the last file close triggers the releasing action; all aggregate rtio are released. This automatic clearing of real-time I/O is carried out in the context of the process that is closing the file. If the FSM cannot be reached for some reason, the request is enqueued on a daemon and the process closing the file is allowed to continue. In the background, the daemon attempts to inform the FSM that the real-time I/O has been released. Different processes can share the same file in real-time and non-real-time mode. This is because the level of gating is at the handle level, not the file level. This allows a real-time process to perform ingest of material (video data) at the same time as non-real-time processes are performing other operations on the file.
290
Real-time I/O
Figure 1
Figure 1: Sharing Access to Files
In the above figure, Process A has ungated access to file foo. Processes B and C also are accessing file foo, but the client gates their I/O accesses. If multiple handles are open to the same file and all are in real-time mode, only the last close of the handle releases the real-time I/O back to the system. This is because on most platforms the file system is informed only on the last close of a file.
Ungated files
It is also possible to denote using the RT_NOGATE flag that a handle should not be gated without specifying any amount of real-time I/O. This is useful for infrequently accessed files (such as index files) that should not be counted against the non-real-time I/O. System designers typically allow for some amount of overage in their I/O subsystem to account for non-gated files.
Calculating Available RTIO

When the FSM receives a request for rtio, it takes the amount reserved into consideration. The reserve amount functions as a soft limit beyond which the FSM will not traipse. The calculation for rtio is as follows:
avail_rtio = rtio_limit - rtio_current avail_rtio -= rtio_reserve

All internal calculations are done in terms of I/O/sec.
Callbacks
The cornerstones of the communications between the FSM and the client are callbacks and tokens. A callback is an unsolicited message from the FSM to the client requesting that the client adjust its real-time I/O parameters. The callback contains a token that specifies the amount of non-real-time I/ O available on a stripe group. Initially, all stripe groups in a file system are in non-real-time (ungated) mode. When the FSM receives the initial request for real-time I/O, it first issues callbacks to all clients informing them that the stripe group is now in real-time mode. The token accompanying the message specifies no I/O is available for non-real-time I/O. Clients must now obtain a non-real-time token before they can do any non-realtime I/O.
291
After sending out all callbacks, the FSM sets a timer based on the RtTokenTimeout value, which by default is set to five seconds. If all clients respond to the callbacks within the timeout value the rtio request succeeds, and a response is set to the requesting client. Figure 2 Figure 2: Callback Flow for Initial RTIO Request
In the above diagram, a process on client A requests some amount of RTIO in Step 1. Since this is the first request, the FSM issues callbacks to all connected clients (Steps 2-5) informing them that the stripe group is now in real-time mode. The clients respond to the FSM in Steps 6-9. After all the clients have responded, the FSM responds to the original requesting client in Step 10. If the timer expires and one or more clients have not responded, the FSM must retract the callbacks. It issues a response to the requesting client with the IP number of the first client that did not respond to the callback. This allows the requesting client to log the error with the IP number so system administrators have a chance of diagnosing the failure. It then sends out callbacks to all the clients to which it first sent the callbacks, retracting them to the original state. In our example, it would set the stripe group back to non-real-time mode. After sending out the callbacks, the FSM waits for a response using the RtTokenTimeout value as before. If a client again does not respond within the timeout value, the callbacks are retracted and sent out again. This repeats until all clients respond. During this time of token retractions, real-time requests cannot be honored and will only be enqueued.
Callback Failures
The FSM must handle a case where a client does not respond to a callback within the specified timeout period (RtTokenTimeout). If a client does not respond to a callback, the FSM must assume the worst: that it is a rogue that could wreak havoc on real-time I/O. It must retract the tokens it just issued and return to the previous state. As mentioned earlier, the original requestor will receive an error (EREMOTE) and the IP address of the first client that did not respond to the callback. The FSM enters the token retraction state, and will not honor any real-time or token requests until it has received positive acknowledgement from all clients to which it originally sent the callbacks.
292
Callbacks
Figure 3
Callback Retraction Example
In Figure 3, Client A requests some amount of rtio as in Figure 2. However, assume that Client C did not respond to the initial callback in time (step 7). The FSM will return a failure to Client A for the initial rtio request, then send out callbacks to all clients indicating the stripe group is no longer realtime (steps 11-14). In the example, Client C responds to the second callback, so the FSM will not send out any more callbacks. The stripe group is back in non-real-time mode. Note that this can have interesting repercussions with file systems that are soft mounted by default (such as Windows). When the caller times out because other clients are not responding and then gives up and returns an error to the application, if at some point the FSM is able to process the rtio request it may result in the stripe group being put into real-time mode after the original caller has received an error code. Both the FSM and clients log their actions extensively to syslog, so if this situation arises it can be detected. In Figure 3, if the stripe group were already in real-time mode the FSM would only send out callbacks to those clients that already have tokens. Once all clients responded to the token callbacks, the stripe group would be back in its original state.
Tokens
A token grants a client some amount of non-real-time I/O for a stripe group. Tokens are encapsulated in callback messages from the FSM. Initially, no tokens are required to perform I/O. Once a stripe group is put into real-time mode, the FSM sends callbacks to all clients informing them that they will need a token to perform any non-real-time I/O. The first I/O after receiving the callback will then request a non-real-time I/O token from the FSM. The FSM calculates the amount of non-real-time bandwidth using the following formula:
avail_nrtio = rtio_limit - rtio_current; avail_nrtio /= current_num_nonrtio_clients + 1

In the above calculation, the amount of existing real-time I/O (rtio_current) has already been adjusted with the reserve parameter. As each client requests a non-real-time I/O token, the number of clients increases (current_num_nonrtio_clients in the above formula) and the amount of available non-real-time I/O decreases.
293
Each time there is a change in the amount of non-real-time I/O available, the FSM sends callbacks to the clients with tokens. It is important to note that unlike the initial set of callbacks where the FSM sent callbacks to all connected clients, it is now only necessary to send callbacks to those clients that have an existing token. Once a client has a token, it can perform as much I/O per second as is allowed by that token. It does not need to contact the FSM on every I/O request. The FSM will inform the client whenever the token changes value. Figure 4 Non-Real-time Token Adjustments
In Figure 4, assume the stripe group is already in real-time mode as a result of an rtio request from client A. Clients B and D are doing non-real-time I/O to the stripe group and have a token that specifies the amount of non-real-time I/O available. Client C then requests a non-real-time I/O token in Step 1. The FSM calls back to Clients B and D and specifies the new token amount in Steps 2-3. The clients respond in Steps 4-5, acknowledging the new token amount. The FSM then responds to Client C with the new token in Step 6.
Failure Semantics
There are two major failures that affect QOS: FSM crashes and client crashes. These can also be loss of communication (network outages). For client and server failures, the system attempts to readjust itself to the pre-failure state without any manual intervention.
FSM Failures
If the FSM crashes or is stopped, there is no immediate affect on real-time (ungated) I/O. As long as the I/O does not need to contact the FSM for some reason (attribute update, extent request, etc.), the I/O will continue. From the standpoint of QOS, the FSM being unavailable has no affect.
294
Failure Semantics
Non-real-time I/O will be pended until the FSM is re-connected. The rationale for this is that since the stripe group is in real-time mode, there is no way to know if the parameters have changed while the FSM is disconnected. The conservative design approach was taken to hold off all non-real-time I/O until the FSM is reconnected. Once the client reconnects to the FSM, the client must re-request any real-time I/O it had previously requested. The FSM does not keep track of QOS parameters across crashes; that is, the information is not logged and is not persistent. Therefore, it is up to the clients to inform the FSM of the amount of required rtio and to put the FSM back into the same state as it was before the failure. In most cases, this results in the amount of real-time and non-real-time I/O being exactly the same as it was before the crash. The only time this would be different is if the stripe group is oversubscribed. In this case, since more rtio had been requested than was actually available, and the FSM had adjusted the request amounts, it is not deterministically possible to re-create the picture exactly as it was before. Therefore, if a deterministic picture is required across reboots, it is advisable to not oversubscribe the amount of real-time I/O. The process of each client re-requesting rtio is exactly the same as it was initially; once each client has reestablished its rtio parameters, the non-real-time I/O is allowed to proceed to request a nonreal-time token. It may take several seconds for the SAN to settle back to its previous state. It may be necessary to adjust the RtTokenTimeout parameter on the FSM to account for clients that are slow in reconnecting to the FSM.
Client Failures
When a client disconnects either abruptly (via a crash or a network partition,) or in a controlled manner (via an unmount), the FSM releases the client's resources back to the SAN. If the client had real-time I/O on the stripe group, that amount of real-time I/O is released back to the system. This causes a series of callbacks to the clients (all clients if the stripe group is transitioning from real-time to nonreal-time,) informing them of the new amount of non-real-time I/O available. If the client had a non-real-time I/O token, the token is released and the amount of non-real-time I/O available is recalculated. Callbacks are sent to all clients that have tokens informing them of the new amount of non-real-time I/O available.
Client Token Releases

While it is not a failure case, the handling of a client token release is exactly the same as in the case where the client disconnected. All clients retain non-real-time tokens for a fixed amount of time. The default is 60 seconds. This can be controlled via the nrtiotokentimeout mount option. After the specified period of inactivity (i.e., no non-real-time I/O on the stripe group), the client will release the token back to the FSM. The FSM will re-calculate the amount of non-real-time bandwidth available, and send out callbacks to other clients. Therefore, if a situation exists where a periodic I/O operation occurs every 70 seconds, it would be beneficial to set the nrtiotokentime mount option to something greater than or equal to 70 seconds to cut down on system and SAN overhead.
295
Monitoring
The current real-time statistics are available via the cvadmin utility. The show long command has been enhanced to provide information as to the current limit, the minimum amount reserved for nonreal-time I/O, the number of active clients, the amount currently committed, and the amount a nonreal-time application could hope to get when requesting I/O. Whenever the stripe group status changes (such as from non-real-time to real-time mode), an event is logged to syslog (system event log on Windows platforms). On the NT platform, real-time performance is also available via the perfmon utility. There are counters for both the client (SNFS Client) and FSM (SNFS File System Server [FSS]). In the client, a number of rtio_xxx counters are available to track the number of real-time I/Os/sec, number of nonreal-time I/O requests, non-real-time I/O starvation, and other counters. A full explanation of each counter is provided with the perfmon utility by clicking Explain. In the FSM, information about the number of outstanding non-real-time clients, available rtio, and other QOS information is available. Performance counters are not enabled by default in the client. To enable them, you must execute cvdb -P ; this toggles the state of collection. To turn off the perfmon counters, do another cvdb P. To re-enable, again do cvdb -P, and so on. To clear all client counters to zero, disable, then reenable the counters with cvdb -P.
Sharing Disk Resources

As a final example, consider the case of a full-featured disk subsystem (Redundant Array of Very Expensive Disks, or RAVED) using a very high speed interconnect. Many clients can share these disk arrays, but it is sometimes desirable to limit a client's access to the array. QOS provides a mechanism for political bandwidth management so that no one client can consume all the bandwidth of the channel interconnects. In such a scenario, the stripe group would always be in real-time mode. Each client would have a token specifying the number of I/Os/sec permissible. In the current version of QOS, it is unfortunately not possible to assign different non-real-time limits to different clients. The foundation of such an approach is a simple program that puts the stripe group into real-time mode as soon as the FSM is up and servicing requests. An example of such a program is included in the source code for the External API. Once the stripe group is in real-time mode, the bandwidth as specified in the FSM configuration file is shared by all clients. In cases such as this, the real-time limit (rtios or rtmb) is calculated to be the total bandwidth desired to each client times the number of possible clients. As each client attempted to access the disk subsystem, it would obtain a token. The FSM would send out callbacks adjusting down the amount of bandwidth available. No one client would be allowed to exceed the threshold specified in the non-real-time token. This assures fairness among all the clients.
296
Monitoring
F
HA Failover
StorNext is designed to be a resilient data management solution. StorNext supports operation in degraded mode and provides functionality to guarantee data protection in the event of a storage device failure or total site outage. For certain environments though, additional protection is required to deliver a higher level of availability. To meet these demands, StorNext includes MetaData Controller (MDC) failover. MDC failover allows a secondary MDC to take over StorNext operations in the event a primary MDC fails. Failover is supported for all StorNext management operations including client IO requests (File System) and data mover operations (Storage Manager). MDCs in a failover pair typically run in an active / passive configuration, but both MDCs can be configured to run active File System processes. In the event one MDC fails, the other continues to perform its current operations, as well as those of the failed MDC. Active / Active Storage Manager processes are not currently supported in MDC failover.
Note
Like all failover solutions, StorNext must provide functionality to prevent a damaged or inaccessible MDC from incorrectly processing IO requests that should be handled by the active MDC (often referred to as a "split brain" scenario). To handle this, StorNext utilizes a special failover methodology call STONITH - shoot the other node in the head. STONITH shuts down a degraded MDC and then reboots it so that, on recovery, it becomes the standby MDC in the event future MDC failover is required. While other methods of failover are available, such as quorums, STONITH is the only widely acknowledged method of reliable failover control - especially for software that runs on multiple operating systems. Without STONITH, there is the possibility that a damaged MDC could continue acting as the primary MDC and attempt to handle client IO requests or move data between storage tiers. For shared file systems STONITH is especially critical because a MDC controls access for multiple hosts reading and writing to a single volume - and potentially the same file. Currently MDC failover is only supported when configured by ADIC Solutions Engineering staff.
297
298
Glossary
ADIC Technical Assistance Center (ATAC) The ADIC customer help desk. Affinity An association between a relation point in the file system and a stripe group. It allows the user to direct data to specific primary disks by writing to the affinities associated relation point. Clean Media The operation of logically removing old file versions from a piece of media. This is a database operation that removes knowledge of managed files that have been updated or removed. A piece of media that contains nothing but removed files will not be considered blank until it is cleaned. Configuration Wizard A tool for setting up a basic environment for the management of data, both on disk and on removable media (tape or disk). It appears the first time the administrator connects to the browser after installing StorNext. Data Storage Manager (DSM) One of several components that make up StorNext. The DSM corresponds to the StorNext File System. Drive Pool A grouping of drives for use in storing and retrieving data. Fibre Channel (FC) A high speed data transfer architecture. File Transfer Protocol (FTP) The protocol used on the Internet for sending files.
299
GUI Graphical User Interface. Managed Directory A directory that has a policy class relationship. Managed File System A file system that enables automatic data movement managed by StorNext Storage Manager between the primary disk and secondary storage (either disk or tape). MediaClass A grouping of media used for storing or retrieving data. Media Storage Manager (MSM) The Media Storage Manager is responsible for controlling media and archives. Metadata Server The system hosting the SNFS and SNSM server installation and processes. PolicyClass A set of rules and criteria set up by SNSM that control the movement of data between primary disk to secondary storage (either disk or tape). Quota This variable enables or disables the enforcement of the file system quotas. Recover The process of bringing back to disk a managed file that was previously removed from the disk. This can only be done if the file had been successfully stored to media. Also, the file cannot not exist in the Trash can. (See Undelete) File recovery can be done regardless of whether the Trash can is enabled, up until the time the containing media is cleaned. Relation Point/Relations A mapping of a policy class to a directory in a managed file system. Relocation The process of moving a file from one affinity on a file system to another affinity on that file system. Restore The process of replacing a file system's contents after some sort of disaster. Also known as disaster recovery.
300
Retrieve The process of retrieving data for a file from secondary storage (either disk or tape). RHAS Red Hat Advanced Server RHEL Red Hat Enterprise Linux SCSI Small Computer System Interface. The interface that is used to talk to most hardware devices such as tape and libraries. StorNext A scalable, high performance, data management solution that ensures the long-term safety and recoverability of data in SAN environments, while optimizing the use of storage resources. It consists of two components, the StorNext Storage Manager (SNSM) and the StorNext File System (SNFS). Storage Area Network (SAN) A SAN is a dedicated, high-performance network whose primary purpose is the transfer of data along FC or high-speed Ethernet connections between servers, interconnect devices, and storage peripherals. StorNext File System (SNFS) One of the two components that make up StorNext. SNFS is primarily used to provide Fibre Channel connections (but supports other types of connections) in a serverless environment which enables clients to access data and share files. StorNext Storage Manager (SNSM) One of several components that make up StorNext. SNSM combines the functionality of two products, TSM and MSM to provide high-performance file migration and management services, and to manage automated and manual media libraries, including library volumes. Store The process of copying data for a file to secondary storage (either disk or tape). Stripe Group A set of similar storage devices that can be maintained as a group. Tertiary Storage Manager (TSM) The Tertiary Storage Manger is responsible for policy management and controlling data movement between primary disk and secondary storage (either disk or tape).
301
Trash can A repository for files deleted from the file system but not yet permanently removed.Files in the trash can can be recovered or undeleted if necessary. Truncation The process of freeing date blocks stored to secondary storage (either disk or tape). The file name remains visible in the file system. Undelete The process of returning a file from the Trash can to its original location on disk. This can be done only if the Trash can is enabled. Unmanaged File System A file system that does not have archive capability controlled by SNSM.
302
Index
Symbols
/usr/cvfs/bin/ . . . . . . . . . . . . . . . . . . . . . . . . 283 /usr/cvfs/CLIENTS/ . . . . . . . . . . . . . . . . . . . 284 /usr/cvfs/config/ . . . . . . . . . . . . . . . . . . . . . 283 /usr/cvfs/data//log/ . . . . . . . . . . . . . . . . . . . 283 /usr/cvfs/debug/ . . . . . . . . . . . . . . . . . . . . . 283 /usr/cvfs/docs/ . . . . . . . . . . . . . . . . . . . . . . 284 /usr/cvfs/examples/ . . . . . . . . . . . . . . . . . . . 284 /usr/cvfs/lib/ . . . . . . . . . . . . . . . . . . . . . . . . 284 /usr/cvfs/src/ . . . . . . . . . . . . . . . . . . . . . . . . 284 affinities report . . . . . . . . . . . . . . . . . . . . . . 192 ATAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 auditing, library . . . . . . . . . . . . . . . . . . . . . 126
B
backup report . . . . . . . . . . . . . . . . . . . . . . 197 basic tasks . . . . . . . . . . . . . . . . . . . . . . . . . . 39
C
changing log rolling . . . . . . . . . . . . . . . . . . 274 cleaning tape drive . . . . . . . . . . . . . . . . . . 136 configuration file filesize.config . . . . . . . . . . . . . . . . . . . . 273 fs sysparm . . . . . . . . . . . . . . . . . . . . . . 272 log params . . . . . . . . . . . . . . . . . . . . . . 273 conventions in document . . . . . . . . . . . . . . . 19 creating policy class . . . . . . . . . . . . . . . . . 184, 188 customer assistance . . . . . . . . . . . . . . . . . 227 cvadmin command . . . . . . . . . . . . . . . . . . 229 cvaffinity command . . . . . . . . . . . . . . . . . . 232 cvcp command . . . . . . . . . . . . . . . . . . . . . 233 cvfsck command . . . . . . . . . . . . . . . . . . . . 235 cvfsid command . . . . . . . . . . . . . . . . . . . . 236 cvlabel command . . . . . . . . . . . . . . . . . . . 236 cvmkdir command . . . . . . . . . . . . . . . . . . . 237 cvmkfile command . . . . . . . . . . . . . . . . . . . 238 cvmkfs command . . . . . . . . . . . . . . . . . . . 238 cvupdatefs command . . . . . . . . . . . . . . . . 239 cvversions command . . . . . . . . . . . . . . . . . 240
A
accessing SNMS GUI . . . . . . . . . . . . . . . . . . . . . . . 21 StorNext FS GUI . . . . . . . . . . . . . . . . . . . 43 adding disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 drive pool . . . . . . . . . . . . . . . . . . . . . . . 137 FC drive . . . . . . . . . . . . . . . . . . . . . . . . 273 library . . . . . . . . . . . . . . . . . . . . . . . . . . 111 stripe group . . . . . . . . . . . . . . . . . . . . . . . 90 adding media . . . . . . . . . . . . . . . . . . . . . . . 142 policy class . . . . . . . . . . . . . . . . . . . . . . 182 advanced pages admin StorNext SM . . . . . . . . . . . . . . . . . 38 file StorNext SM . . . . . . . . . . . . . . . . . 36 media StorNext SM . . . . . . . . . . . . . . . . . 37 reports StorNext SM . . . . . . . . . . . . . . . . . 39
303
D
data migration management . . . . . . . . . . . . 173 defragmenting, disk . . . . . . . . . . . . . . . . . . 101 deleting disks . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 drive pool . . . . . . . . . . . . . . . . . . . . . . . 141 library . . . . . . . . . . . . . . . . . . . . . . . . . . 125 policy class . . . . . . . . . . . . . . . . . . . . . . 180 stripe group . . . . . . . . . . . . . . . . . . . . . . . 96 directories, trashcan . . . . . . . . . . . . . . . . . . . 76 directory/policy class relationship report . . 209 disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 adding . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 defragmenting . . . . . . . . . . . . . . . . . . . . 101 deleting . . . . . . . . . . . . . . . . . . . . . . . . . 100 disk-to-disk relocation . . . . . . . . . . . . . . . . . 183 disk-to-disk relocation, performing . . . . . . . 189 document conventions . . . . . . . . . . . . . . . . . 19 drive pool adding . . . . . . . . . . . . . . . . . . . . . . . . . . 137 deleting . . . . . . . . . . . . . . . . . . . . . . . . . 141 modifying . . . . . . . . . . . . . . . . . . . . . . . 139 drive states report . . . . . . . . . . . . . . . . . . . . 198 drive, managing . . . . . . . . . . . . . . . . . . . . . 128 drive, tape cleaning . . . . . . . . . . . . . . . . . . . . . . . . 136
E
entering StorNext license . . . . . . . . . . . . . . . 39
F
FC drive, adding . . . . . . . . . . . . . . . . . . . . . 273 file system making, manually . . . . . . . . . . . . . . . . . . 78 managing . . . . . . . . . . . . . . . . . . . . . . . . 67 mounting . . . . . . . . . . . . . . . . . . . . . .82, 83 unmounting . . . . . . . . . . . . . . . . . . . .82, 83 file system commands cvadmin . . . . . . . . . . . . . . . . . . . . . . . . 229 cvaffinity . . . . . . . . . . . . . . . . . . . . . . . . 232 cvcp . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 cvfsck . . . . . . . . . . . . . . . . . . . . . . . . . . 235 cvfsid . . . . . . . . . . . . . . . . . . . . . . . . . . 236 cvlabel . . . . . . . . . . . . . . . . . . . . . . . . . 236 cvmkdir . . . . . . . . . . . . . . . . . . . . . . . . . 237 cvmkfile . . . . . . . . . . . . . . . . . . . . . . . . . 238 cvmkfs . . . . . . . . . . . . . . . . . . . . . . . . . 238 cvupdatefs . . . . . . . . . . . . . . . . . . . . . . 239 304
cvversions . . . . . . . . . . . . . . . . . . . . . . 240 file system report . . . . . . . . . . . . . . . . . . . . 194 files report . . . . . . . . . . . . . . . . . . . . . . . . . 200 files, installed /usr/cvfs/bin/ . . . . . . . . . . . . . . . . . . . . 283 /usr/cvfs/CLIENTS/ . . . . . . . . . . . . . . . 284 /usr/cvfs/config/ . . . . . . . . . . . . . . . . . . 283 /usr/cvfs/data//log/ . . . . . . . . . . . . . . . . 283 /usr/cvfs/debug/ . . . . . . . . . . . . . . . . . . 283 /usr/cvfs/docs/ . . . . . . . . . . . . . . . . . . . 284 /usr/cvfs/examples/ . . . . . . . . . . . . . . . 284 /usr/cvfs/lib/ . . . . . . . . . . . . . . . . . . . . . 284 /usr/cvfs/src/ . . . . . . . . . . . . . . . . . . . . 284 files, trashcan . . . . . . . . . . . . . . . . . . . . . . . 76 filesize.config configuration file . . . . . . . . . 273 fs sysparm configuration file . . . . . . . . . . . 272 fsaddclass command . . . . . . . . . . . . . . . . . 241 fsaddrelation command . . . . . . . . . . . . . . . 243 fsaudit command . . . . . . . . . . . . . . . . . . . . 243 fschfiat command . . . . . . . . . . . . . . . . . . . 245 fschmedstate command . . . . . . . . . . . . . . 245 fschstate command . . . . . . . . . . . . . . . . . . 246 fsclassinfo command . . . . . . . . . . . . . . . . . 247 fsclean command . . . . . . . . . . . . . . . . . . . 248 fsdrvclean command . . . . . . . . . . . . . . . . . 248 fsfileinfo command . . . . . . . . . . . . . . . . . . 249 fsmedcopy command . . . . . . . . . . . . . . . . 249 fsmedinfo command . . . . . . . . . . . . . . . . . 250 fsmedlist command . . . . . . . . . . . . . . . . . . 251 fsmodclass command . . . . . . . . . . . . . . . . 252 fsqueue command . . . . . . . . . . . . . . . . . . . 254 fsrecover command . . . . . . . . . . . . . . . . . . 255 fsretrieve command . . . . . . . . . . . . . . . . . . 257 fsrmcopy command . . . . . . . . . . . . . . . . . . 257 fsrmdiskcopy command . . . . . . . . . . . . . . . 258 fsrminfo command . . . . . . . . . . . . . . . . . . . 258 fsstate command . . . . . . . . . . . . . . . . . . . . 258 fsstore command . . . . . . . . . . . . . . . . . . . . 259 fsusedspace command . . . . . . . . . . . . . . . 260 fsversion command . . . . . . . . . . . . . . . . . . 259
G
global settings, modifying . . . . . . . . . . . . . . 73 globals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 guide organization . . . . . . . . . . . . . . . . . . . . 18
Index
H
help, website . . . . . . . . . . . . . . . . . . . . . . . 227 home page SNMS GUI . . . . . . . . . . . . . . . . . . . . . . . 23 StorNext FS . . . . . . . . . . . . . . . . . . . . . . 45 StorNext SM on the SNMS GUI . . . . . . 35 how this guide is organized . . . . . . . . . . . . . 18
I
installed files /usr/cvfs/bin/ . . . . . . . . . . . . . . . . . . . . 283 /usr/cvfs/CLIENTS/ . . . . . . . . . . . . . . . 284 /usr/cvfs/config/ . . . . . . . . . . . . . . . . . . 283 /usr/cvfs/data//log/ . . . . . . . . . . . . . . . . 283 /usr/cvfs/debug/ . . . . . . . . . . . . . . . . . . 283 /usr/cvfs/docs/ . . . . . . . . . . . . . . . . . . . 284 /usr/cvfs/examples/ . . . . . . . . . . . . . . . 284 /usr/cvfs/lib/ . . . . . . . . . . . . . . . . . . . . . 284 /usr/cvfs/src/ . . . . . . . . . . . . . . . . . . . . 284 intended audience . . . . . . . . . . . . . . . . . . . . 17 introduction . . . . . . . . . . . . . . . . . . . . . . . . . 17
L
libraries report . . . . . . . . . . . . . . . . . . . . . . 202 library adding . . . . . . . . . . . . . . . . . . . . . . . . . 111 auditing . . . . . . . . . . . . . . . . . . . . . . . . 126 deleting . . . . . . . . . . . . . . . . . . . . . . . . 125 managing . . . . . . . . . . . . . . . . . . . . . . . 111 modifying . . . . . . . . . . . . . . . . . . . . . . . 124 sharing between applications . . . . . . . 271 library monitor . . . . . . . . . . . . . . . . . . . . . . . 25 library space used report . . . . . . . . . . . . . . 203 license, entering . . . . . . . . . . . . . . . . . . . . . 39 log params configuration file . . . . . . . . . . . 273 logging on . . . . . . . . . . . . . . . . . . . . . . . . . . 66 logs changing log rolling . . . . . . . . . . . . . . . 274 log rolling options . . . . . . . . . . . . . . . . 274
media . . . . . . . . . . . . . . . . . . . . . . . . . . 141 policy class . . . . . . . . . . . . . . . . . . . . . . 174 media adding . . . . . . . . . . . . . . . . . . . . . . . . . . 142 managing . . . . . . . . . . . . . . . . . . . . . . . 141 mounting . . . . . . . . . . . . . . . . . . . . . . . . 158 moving . . . . . . . . . . . . . . . . . . . . . . . . . 147 removing . . . . . . . . . . . . . . . . . . . . . . . . 147 transcribing . . . . . . . . . . . . . . . . . . . . . . 160 media class grouping, reclassifying . . . . . . 161 media class report . . . . . . . . . . . . . . . . . . . 207 media report . . . . . . . . . . . . . . . . . . . . . . . . 204 menu options admin SNMS GUI . . . . . . . . . . . . . . . . . . . 27 StorNext FS GUI . . . . . . . . . . . . . . 47 config StorNext FS GUI . . . . . . . . . . . . . . 46 reports SNMS GUI . . . . . . . . . . . . . . . . . . . 28 StorNext FS GUI . . . . . . . . . . . . . . 48 StorNext FS . . . . . . . . . . . . . . . . . . . . . . 45 modifying drive pool . . . . . . . . . . . . . . . . . . . . . . . 139 global settings . . . . . . . . . . . . . . . . . . . . 73 library . . . . . . . . . . . . . . . . . . . . . . . . . . 124 policy class . . . . . . . . . . . . . . . . . .179, 188 stripe group . . . . . . . . . . . . . . . . . . . . . . 93 monitor, library . . . . . . . . . . . . . . . . . . . . . . . 25 mounting file system . . . . . . . . . . . . . . . . . . . .82, 83 mounting media . . . . . . . . . . . . . . . . . . . . . 158 moving media . . . . . . . . . . . . . . . . . . . . . . . 147
N
name servers . . . . . . . . . . . . . . . . . . . . . . . . 76 navigating SNMS GUI . . . . . . . . . . . . . . . . . . . . . . . 23 StorNext FS GUI . . . . . . . . . . . . . . . . . . 45
O
overview, StorNext GUI . . . . . . . . . . . . . . . . 21
M
making file system . . . . . . . . . . . . . . . . . . . . 78 managing data migration . . . . . . . . . . . . . . . . . . . 173 drive . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 file system . . . . . . . . . . . . . . . . . . . . . . . 67 library . . . . . . . . . . . . . . . . . . . . . . . . . . 111 StorNext System Administrator Guide
305
P
performing, disk-to-disk relocation . . . . . . . 189 policy class adding media . . . . . . . . . . . . . . . . . . . . 182 creating . . . . . . . . . . . . . . . . . . . . .184, 188 deleting . . . . . . . . . . . . . . . . . . . . . . . . . 180 managing . . . . . . . . . . . . . . . . . . . . . . . 174 modifying . . . . . . . . . . . . . . . . . . .179, 188 relationship . . . . . . . . . . . . . . . . . . . . . . 174 policy classes report . . . . . . . . . . . . . . . . . . 208 pools, drive . . . . . . . . . . . . . . . . . . . . . . . . . 137 poor system performance, avoiding . . . . . . 274 purpose of this guide . . . . . . . . . . . . . . . . . . 17
R
reclassifying media class grouping . . . . . . . 161 relationship, policy class . . . . . . . . . . . . . . . 174 relocation, disk-to-disk, performing . . . . . . 183 removing media . . . . . . . . . . . . . . . . . . . . . 147 report affinities . . . . . . . . . . . . . . . . . . . . . . . . 192 backup . . . . . . . . . . . . . . . . . . . . . . . . . 197 directory/policy class relationship . . . . . 209 drive states . . . . . . . . . . . . . . . . . . . . . . 198 file system . . . . . . . . . . . . . . . . . . . . . . . 194 libraries . . . . . . . . . . . . . . . . . . . . . . . . . 202 library space used . . . . . . . . . . . . . . . . 203 media . . . . . . . . . . . . . . . . . . . . . . . . . . 204 media class . . . . . . . . . . . . . . . . . . . . . . 207 policy classes . . . . . . . . . . . . . . . . . . . . 208 requests . . . . . . . . . . . . . . . . . . . . . . . . 211 stripe groups . . . . . . . . . . . . . . . . . . . . . 212 reports, files . . . . . . . . . . . . . . . . . . . . . . . . 200 requests report . . . . . . . . . . . . . . . . . . . . . . 211
S
server name/status SNMS GUI . . . . . . . . . . . . . . . . . . . . . . . 26 sharing library between applications . . . . . 271 SNMS basic tasks . . . . . . . . . . . . . . . . . . . . . . . 39 introduction . . . . . . . . . . . . . . . . . . . . . . . 17 logging on . . . . . . . . . . . . . . . . . . . . . . . . 66 starting . . . . . . . . . . . . . . . . . . . . . . .61, 81 stopping . . . . . . . . . . . . . . . . . . . . . . . . . 81 SNMS GUI accessing . . . . . . . . . . . . . . . . . . . . . . . . 21 home page . . . . . . . . . . . . . . . . . . . . . . . 23 306
menu options admin . . . . . . . . . . . . . . . . . . . . . . 27 reports . . . . . . . . . . . . . . . . . . . . . . 28 navigating . . . . . . . . . . . . . . . . . . . . . . . 23 server name/status . . . . . . . . . . . . . . . . 26 using . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 starting . . . . . . . . . . . . . . . . . . . . . . . . . . 61, 81 stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 storage manager commands fsaddclass . . . . . . . . . . . . . . . . . . . . . . 241 fsaddrelation . . . . . . . . . . . . . . . . . . . . 243 fsaudit . . . . . . . . . . . . . . . . . . . . . . . . . 243 fschfiat . . . . . . . . . . . . . . . . . . . . . . . . . 245 fschmedstate . . . . . . . . . . . . . . . . . . . . 245 fschstate . . . . . . . . . . . . . . . . . . . . . . . 246 fsclassinfo . . . . . . . . . . . . . . . . . . . . . . 247 fsclean . . . . . . . . . . . . . . . . . . . . . . . . . 248 fsdrvclean . . . . . . . . . . . . . . . . . . . . . . 248 fsfileinfo . . . . . . . . . . . . . . . . . . . . . . . . 249 fsmedcopy . . . . . . . . . . . . . . . . . . . . . . 249 fsmedinfo . . . . . . . . . . . . . . . . . . . . . . . 250 fsmedlist . . . . . . . . . . . . . . . . . . . . . . . 251 fsmodclass . . . . . . . . . . . . . . . . . . . . . . 252 fsqueue . . . . . . . . . . . . . . . . . . . . . . . . 254 fsrecover . . . . . . . . . . . . . . . . . . . . . . . 255 fsretrieve . . . . . . . . . . . . . . . . . . . . . . . 257 fsrmcopy . . . . . . . . . . . . . . . . . . . . . . . 257 fsrmdiskcopy . . . . . . . . . . . . . . . . . . . . 258 fsrminfo . . . . . . . . . . . . . . . . . . . . . . . . 258 fsstate . . . . . . . . . . . . . . . . . . . . . . . . . 258 fsstore . . . . . . . . . . . . . . . . . . . . . . . . . 259 fsusedspace . . . . . . . . . . . . . . . . . . . . 260 fsversion . . . . . . . . . . . . . . . . . . . . . . . 259 vsarchiveqry . . . . . . . . . . . . . . . . . . . . 262 vsdriveqry . . . . . . . . . . . . . . . . . . . . . . 263 vsdrivevary . . . . . . . . . . . . . . . . . . . . . 265 vsmedclassqry . . . . . . . . . . . . . . . . . . . 266 vsmedqry . . . . . . . . . . . . . . . . . . . . . . . 267 vspoolcfg . . . . . . . . . . . . . . . . . . . . . . . 268 vsreclassify . . . . . . . . . . . . . . . . . . . . . 269 StorNext system monitor . . . . . . . . . . . . . . . . . . . 24 website . . . . . . . . . . . . . . . . . . . . . . . . 227 StorNext FS basic tasks . . . . . . . . . . . . . . . . . . . . . . . 39 home page . . . . . . . . . . . . . . . . . . . . . . . 45 logging on . . . . . . . . . . . . . . . . . . . . . . . 66 menu options . . . . . . . . . . . . . . . . . . . . . 45 starting . . . . . . . . . . . . . . . . . . . . . . . 61, 81 stopping . . . . . . . . . . . . . . . . . . . . . . . . . 81 StorNext FS GUI Index
accessing . . . . . . . . . . . . . . . . . . . . . . . 43 menu options admin . . . . . . . . . . . . . . . . . . . . . . 47 config . . . . . . . . . . . . . . . . . . . . . . 46 reports . . . . . . . . . . . . . . . . . . . . . 48 navigating . . . . . . . . . . . . . . . . . . . . . . . 45 using . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 StorNext GUI, overview . . . . . . . . . . . . . . . . 21 StorNext license, entering . . . . . . . . . . . . . . 39 StorNext SM advanced pages admin . . . . . . . . . . . . . . . . . . . . . . 38 file . . . . . . . . . . . . . . . . . . . . . . . . . 36 media . . . . . . . . . . . . . . . . . . . . . . 37 reports . . . . . . . . . . . . . . . . . . . . . 39 StorNext SM on the SNMS GUI home page . . . . . . . . . . . . . . . . . . . . . . 35 stripe group . . . . . . . . . . . . . . . . . . . . . . . . . 90 adding . . . . . . . . . . . . . . . . . . . . . . . . . . 90 deleting . . . . . . . . . . . . . . . . . . . . . . . . . 96 modifying . . . . . . . . . . . . . . . . . . . . . . . . 93 stripe groups report . . . . . . . . . . . . . . . . . . 212 symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 symbols in document, explanations . . . . . . 18 system monitor, StorNext . . . . . . . . . . . . . . 24 system performance, avoiding poor performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
V
vsarchiveqry command . . . . . . . . . . . . . . . 261 vsdriveqry command . . . . . . . . . . . . . . . . . 263 vsdrivevary command . . . . . . . . . . . . . . . . 265 vsmedclassqry command . . . . . . . . . . . . . . 266 vsmedqry command . . . . . . . . . . . . . . . . . . 267 vspoolcfg command . . . . . . . . . . . . . . . . . . 268 vsreclassify command . . . . . . . . . . . . . . . . 269
T
tape drive cleaning . . . . . . . . . . . . . . . . . . . . . . . . 136 transcribing media . . . . . . . . . . . . . . . . . . . 160 trashcan, directories . . . . . . . . . . . . . . . . . . 76 trashcan, files . . . . . . . . . . . . . . . . . . . . . . . 76
U
unmounting file system . . . . . . . . . . . . . 82, 83 using SNMS GUI . . . . . . . . . . . . . . . . . . . . . . . 21 StorNext FS GUI . . . . . . . . . . . . . . . . . . 21
307

Adic Stornext 2.7 System Administrator Guide: Advanced Digital Information Corporation

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Adic Stornext 2.7 System Administrator Guide: Advanced Digital Information Corporation

Uploaded by

Copyright:

Available Formats

Administrator Guide

2.7 System ADIC StorNext

Published: February 2006

Document Number: 6-00362-05 Rev A

Advanced Digital Information Corporation Software Licenses Agreement

StorNext System Administrator Guide

Price and Payment

Software Ownership and Protection

Advanced Digital Information Corporation Software Licenses Agreement

Use and Training

Warranty and Warranty Servicing

StorNext System Administrator Guide

Term and Termination

Advanced Digital Information Corporation Software Licenses Agreement

Notices and Correspondence

DISCLAIMER AND LIMITATION OF LIABILITY

StorNext System Administrator Guide

Advanced Digital Information Corporation Software Licenses Agreement

2 StorNext GUI Overview

4 File System Management

5 Library and Storage Disk Management 111

6 Data Migration Management

7 Monitoring and Reporting

StorNext System Administrator Guide

StorNext Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 ADIC Technical Assistance Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

A File System Commands

B Storage Manager Commands

StorNext System Administrator Guide

C StorNext Configuration and Administration Tasks 271

The example.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Commonly Used SNFS Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

E Quality of Service Guide

StorNext System Administrator Guide

Purpose of This Guide

StorNext System Administrator Guide

How This Guide is Organized

Advises you to take or avoid a specified action.

How This Guide is Organized

StorNext System Administrator Guide

Using the StorNext GUI

Accessing the GUI

StorNext System Administrator Guide

The following screen appears.

Click OK to start the StorNext components.

Using the StorNext GUI

Link to ADIC Drop-down Home Page Menu Options

Monitor Refresh Rate Options

Application System Link Monitors

StorNext System Status

StorNext Server Status

StorNext Home Page

File System Monitor

StorNext Home Page

Storage Disk Monitor

StorNext System Administrator Guide

Drop-down Menu Options

StorNext Home Page

StorNext System Administrator Guide

StorNext System Administrator Guide

StorNext Home Page

SNFS Home Page

StorNext System Administrator Guide

StorNext Home Page

StorNext System Administrator Guide