Professional Documents
Culture Documents
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.
and
Advanced Digital Company: _________________________________________________
Information Corporation Located at: ________________________________________________
PO Box 97057 _________________________________________________
Redmond, WA 98073-9757 _________________________________________________
(Referred to as “ADIC") (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.
b. 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.
c. 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.
ii. remove, obscure, or alter any copyright, trade secret, trademark, patent or other proprietary rights
notice affixed to or displayed on the Software or Documentation or affixed to or printed on any of its
factory packaging;
iii. modify, merge with other programs or translate any portion of the Software into any other assembly or
foreign language; and
iv. reverse-assemble, reverse-compile or attempt to derive a source code equivalent of the Software.
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.
e. 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.
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.
General
a. No Assignment. This License is not assignable. None of the Software or Documentation may be
sublicensed, assigned, or transferred to any other party without ADIC’s prior written consent. Any effort
contradictory with this is null and void.
b. Modification. This License or any Exhibit hereto can only be modified by a written agreement executed by
Licensee and ADIC.
c. 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.
d. 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.
e. 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.
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.
3 Basic Tasks 39
Entering the StorNext License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Accessing StorNext Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Controlling User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Downloading Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Running StorNext Software Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Scheduling StorNext Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Starting and Stopping StorNext
x 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
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
xiv 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
xvi Contents
F HA Failover 297
Glossary 299
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.
• 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.
Conventions Examples
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.
2 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.
The initial StorNext GUI appears. You are prompted to start non-running components.
Application System
StorNext System Status StorNext Server Status
Link Monitors
• 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
• 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
Note watermark limitations.
• On an unmanaged file system, the number of Stored and Truncation
candidates defaults to N/A.
• 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.
Admin
The options for the Admin drop-down menu enable you to control day-to-day operations of StorNext.
Reports
Use the options on the Reports drop-down menu to view StorNext reports.
• 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
Service
Use the options on the Service drop-down menu to monitor and capture system status information.
• 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
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.
• 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.
The graphic shows the SNFS Home Page as it appears when it is part of the
Note 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.
You must unmount and stop the file system before using most of the options
Note listed in this section. See Chapter 3, Basic Tasks for more information.
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.
• 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.
• Library: Perform media movement tasks within a library (Manual Move, Mount, and Dismount)
• 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
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.
• All Components
• StorNext File System
• StorNext Storage Manager
6 Click Next.
A status screen appears.
7 Click Close when the status screen shows Success.
The StorNext Server Status now displays Stopped or Active depending on your action.
2 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.
The initial StorNext GUI appears. You are prompted to start non-running components.
Help
• Config
• Admin on page 47
• Reports on page 48
• Set Affinities: Create a relation point in the file system to the affinity
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.
To obtain a permanent license, you must contact ATAC at licenses@adic.com and give them the
following information:
6 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.
# 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
10 Review your selections. Click Next to complete the task or Back to make changes.
3 Select the log file you wish to view and select one of the following:
• 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 Click OK.
7 Click OK when the Status screen displays Success.
The User Access Control screen appears listing the new addition.
4 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.)
5 Select the software package that corresponds to your system by clicking the link.
9 Click Finish.
• 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:
• StorNext database journals
• Configuration files
• File system journal files
Use this procedure to run a StorNext backup.
1 From the StorNext home page click Admin > Run Backup.
The Backup StorNext screen appears.
2 Select the type of backup you want run, Full or Partial, and click Next.
• 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.
• 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 Configure the schedule and click Apply.
6 Click Close when the Status screen displays Success.
• All Components
• StorNext File System
• StorNext Storage Manager
6 Click Next.
A status screen appears.
7 Click Finish when the status screen shows Success.
The StorNext Server Status now displays Stopped, Warning or Active depending on your
action.
Documentation
Use this procedure to view StorNext documentation.
1 Click Help > Documentation.
• 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 Administrators’s 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.
• 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.
• 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
• 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:
Greyed out devices in the Disk Devices list are in use by a configured file
Note system.
• 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
3 Click OK.
You are warned that the device may have a file system on it and labeling it will destroy any data.
4 Make sure the disk you are labeling is empty and click OK.
1 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:
/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
Output example shown will differ from the output you will see, but will be similar
Note in structure and information.
2 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.
3 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.
4 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 ...
Output example shown will differ from the output you will see, but will be similar
Note in structure and information.
5 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 ...
Output example shown will differ from the output you will see, but will be similar
Note in structure and information.
• For CLI:
• InodeCacheSize
Before making any changes to the file system’s configuration, carefully review the cvfs_config(4)
man pages or the “CVFS Configuration File” help file.
Use the following procedures to modify global settings.
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.
• 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
• Trashcan: Enable this option (check the box) to enable Trashcan functionality on the file
system.
• 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
Note 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.
• 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
• 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 Window’s, the default is “No”.
• 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
4 Click Apply.
The Modify Global Setting Status screen appears.
5 Once the status screen indicates that the global settings have been modified, click Close.
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.
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.
76 Operations
Trashcan functionality is not supported in the root directory of the file system.
Note 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.
Disabling the Trashcan from a file system configuration after the file
CAUTION system has been in use for a while could result in abnormal behavior.
78 Operations
The Make File System screen appears.
Greyed out file systems in the Start or Stop File System screen require a
Note metadata dump in order to be started.
• 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.
3 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 Log on to the machine as root.
2 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
• If you are running StorNext, you must stop the SNSM component before you
Note 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.
• 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 Once the status screen displays the successful completion of the task, click Close.
82 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:
Make sure that each stripe group is associated with no more than one affinity
Note when using disk-to-disk migration.
8 Make the file system. For instructions, refer to Making a File System Using the GUI on page 78.
84 File Systems
9 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.
You can only define up to two affinities per file system when using disk-to-disk
Note relocation.
Before initially executing any SNFS command line programs, you are required
Note 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 Install StorNext. For instructions, refer to the chapter in the StorNext File System Installation
Guide that applies to your operating system.
2 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 ...
Output example shown will differ from the output you will see, but will be similar
Note in structure and information.
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.
4 Label the FC drives. Type:
/usr/cvfs/bin/cvlabel /user/cvfs/config/cvlabels
When you run the cvmkfs command, you will lose any data on the
CAUTION file system at that time.
86 File Systems
1 Install StorNext. For instructions, refer to the chapter in the StorNext File System Installation
Guide that applies to your operating system.
2 Copy the example fsnameservers file to the config directory. Type:
cp /usr/cvfs/examples/fsnameservers.example /usr/cvfs/config/
fsnameservers
3 Edit the fsnameservers file created in step 2 to add the IP address or host name of the SNFS
server.
4 Edit the /etc/fstab file to mount on boot (for Solaris, edit the /etc/vfstab file).
5 Reboot the machine.
6 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.
Before initially executing any SNFS command line programs, you are required
Note 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.
This procedure assumes that the file system exists with at least two stripe
Note groups.
1 Unmount the file system. For instructions, refer to Mounting or Unmounting a File System Using
the GUI on page 82.
2 Stop the file system. For instructions, refer to Use this procedure to stop SNFS using CLI. Type:
on page 81.
3 Make the appropriate changes to the file system. Refer to:
• 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.
The GUI runs a check on the expanded file system that may take up to three
Note 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.
3 Click OK.
4 Click OK.
5 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:
90 Stripe Groups
The Configure Stripe Groups screen appears.
2 In the File Systems drop-down menu, select a file system and click Add.
The Add Stripe Group screen appears.
To populate this list, you must first add disks to the file system. Navigate to the
Note SNFS Home page, select Config > Disks, select the file system, click Add,
and add one or more disks.
• 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.
• 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 real-
time 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 Type valid values for the new stripe group and click OK.
4 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.
To populate this list, you must first add disks to the file system. Navigate to the
Note SNFS Home page, select Config > Disks, select the file system, click Add,
and add one or more disks.
94 Stripe Groups
• To enable only journaling to be placed on the new stripe group, select both the Journal
and Exclusive check boxes.
• 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 real-
time 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 Type valid values for the modified stripe group and click OK.
5 Once the screen indicates that the stripe group has been modified, click Close.
1 Access the SNFS Home Page and click Config > Stripe Groups.
The Configure Stripe Group screen appears.
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.)
[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
• 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
2 In the File Systems drop-down menu, select a file system and click Add.
The Add Disk screen appears.
3 In the Available Disks scroll list, select one or more disks and click OK.
The Add Disk Status screen appears.
4 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.
If you delete a disk that was used in a stripe group, this results in a
CAUTION complete loss of user data and requires a re-make of the file system.
Refer to Making a File System on page 78.
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.
The metadata controller is the computer where the StorNext server (not the
Note client) is installed.
For more information about using the snfsdefrag command, refer to the
Note 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:
4 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
An exclusive, metadata, or journal stripe group, or a stripe group on a managed
Note file system with a configured affinity cannot be selected.
Modifying an Affinity
Use this procedure to modify an affinity on a configured file system.
1 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.
2 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.
3 Modify the affinity.
104 Affinities
4 Start the file system. For instructions, refer to Making a File System Using CLI on page 81.
5 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.
1 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.
2 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.
3 Delete the affinity.
a. Access the SNFS Home Page and click Config > Affinities.
The Add, Modify, or Delete Affinities screen appears.
• 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
CAUTION 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.
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 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.
4 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.
2 Select the file system to perform the metadata dump from and click Apply.
3 When the Status Screen displays Success, click Close.
• 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.
5 Review your selections. Click Next to complete the task or Back to make changes.
6 Once a status screen displays the successful addition of the library, click Close.
• 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.
5 Review your selections. Click Next to complete the task or Back to make changes.
6 Once a status screen displays the successful addition of the library, click Close.
2 Click the Network option, select DAS from the drop-down list, and click Next.
The DAS Configuration screen appears.
• 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.
• 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
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.
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.
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.
4 Review your selections. Click Next to complete the task or Back to make changes.
5 Once a status screen displays the successful addition of the library, click Close.
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 In the Select Library list, select a library to modify and click Modify.
Deleting a Library
This task enables you to delete a library.
1 Access the SNSM Home Page and click Admin > Library > Config Library.
2 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 Click OK.
The Delete Library Status screen appears.
4 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.
2 Select the library to audit in the Select Library list and click Apply.
• ADIC recommends that you select the Remap Audit check box to
Note 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.
2 Click Add.
• 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 channel-
attached tape drives. If you check this box, the Match Devices with Slots screen appears. Go
to Step 6 on page 131.
4 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
3a. If you need help mapping the tape drive to a slot, click Show Mapping Help to display a
list of device mappings
StorNext may not be able to determine the device to slot mapping. Limitations
Note include ACSLS and DAS libraries.
8 Review your selections. Click Next to complete the task or Back to make changes.
9 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).
2 Select a drive from the Configured Drive List and click Modify.
The Modify Drive screen appears.
2 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 Click OK.
4 When the Status Screen displays Success, click Close.
The Change Drive State screen displays all configured drives and the current state for each.
2 Select the drive to change.
3 Select the state to change to and click Apply.
4 When the Status Screen displays Success, click Close.
To perform this procedure, you must have a cleaning tape specifically labeled
Note for cleaning. For example, CLN_XXX.
1 From the SNSM Home Page click Admin > Drive > Clean Drive.
2 Select a drive to clean in the Select Drive list and click Apply.
The Clean Drive status screen appears.
3 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.
1 From the SNSM Home page click Admin > Config Drive Pool.
3 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.
2 In the Select Drive Pool list, select an existing drive pool and click Modify.
The Modify Drive Pool screen appears.
3 In the Associated Drives list, select a drive and click Remove Left.
4 Click Apply.
You are warned that continuing with the task will restart the Storage Manager.
5 Click OK.
6 When the status screen displays Success, click Close.
2 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
CAUTION default drive pool.
A prompt appears asking if you are sure you want to delete the drive pool.
3 Click OK to continue.
4 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:
1 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.
Make sure that only media you want StorNext to use is in the library.
CAUTION StorNext will use all available tapes and overwrite them.
2 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.
4 After you select Mailbox, the Select Mailbox screen appears. Select a mailbox and click Next.
5 Review your selections. Click Next to complete the task or click Back to make changes.
6 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.
8 On the Select Media Type screen, select the type of media you want to add to the vault.
The Add Media IDs screen appears.
• 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.
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.
• 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.
In the Select Media window, you can select any number of media from one to
Note all.
In the Media List window, the Select Media screen appears and displays the selected media.
6 In the Media List window, select the media to remove or move and click Next.
In the Media List window, you can select any number of media from one to all.
Note
7 Review your selections and click Next to apply them or Back to make changes.
The Remove/Move Media status screen appears.
8 Once the status screen indicates that the media has been removed or moved, click Finish.
The Library Operator Interface (LOI) is launched.
9 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.
If you are using a vault library, you have to manually move the media.
Note
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.
• 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.
7 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.
9 Select the destination library from the list and click Next.
The Complete Remove/Move Media Task screen appears.
12 Eject the media from the source library and click the highlighted Eject Media.
The LOI Eject screen appears.
15 Move the media to the destination library and click the highlighted Enter Media.
The LOI Enter screen appears.
17 Click Close.
Mounting Media
1 Access the SNSM Home Page and click Media > Library > Mount.
The Mount Media screen appears.
2 Select an archive from the Archive drop-down menu. The screen updates to show available
media.
3 Select the media you want to mount from the Media ID list.
4 Select a drive from the Drive ID drop-down menu.
5 Click Apply.
6 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.
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.
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.
2 Select one or more media on the Select Media to Transcribe list and click Apply.
3 Once the status screen indicates that the media has been transcribed, click Close.
2 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.
3 Select one or more media from the Select Media list and click OK.
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.
Before you create a storage disk, the disks you wish to use must reside in an
Note existing and mounted file system.
2 Click Add.
3 Click Next.
4 The Add Storage Disk screen appears.
5 Enter the name for the storage disk or accept the default name in the Storage Disk Name field.
6 Select a mount point from the Select a file system mount point drop-down menu.
7 Click Browse to select a directory for your files.
10 Select the Copy # (1-4) for use by all policy classes for this storage disk.
Only copies of the number you choose can be written to this disk. For example,
Note if you select copy number 1, only files with that copy number can be written to
the storage disk.
11 Click Next.
You can only modify a blank storage disk. A blank is a storage disk that has not
Note been written to and where no files system files reside.
1 From the SNSM Home Page, click Admin > Storage Disk > Config.
2 Select a storage disk from the Current Storage Disks list and click Modify.
The Modify Storage Disk screen appears.
Deleting a storage disk does not unmount it. You must manually unmount the
Note disk or you can use it to create a new storage disk.
Before initially executing any StorNext command line programs, you must
Note 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
• 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.
• 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
Note functionality on this screen.
2 Select the policy class you wish to create a relation point for and click Add.
The Add Relationship screen appears.
5 Click OK.
The Add Relationship screen appears and displays the new directory.
2 In the Select Policy Class list, select a policy class to modify and click Modify.
3 In the Modify Parameters screen, type valid values and click OK.
4 Once the status screen indicates that the policy class has been modified, click Close.
Before you can delete a policy class, you must delete everything associated
Note with that policy class: media, directories, and Trashcan entries, and you must
clean the media and return it to a system-blank state.
1 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.
2 Remove the relations for the policy class.
5 In the Select Policy Class list, select a policy class and click Delete.
6 Once the status screen indicates that the policy class was deleted, click Close.
2 Click Next.
The Policy and Directory screen appears.
7 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.
9 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.
Before initially executing any StorNext command line programs, you are
Note 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
• 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.
• 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.
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.
2 In the active file systems list, select one or more active file systems on which to run the report
and click Apply.
• 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.
StorNext Reports
StorNext reports provide information about the following aspects of your system:
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.
• 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.
2 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.
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.
2 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.
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.
• 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
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.
2 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.
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).
2 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.
If you want to limit the media list to a specific selection, type the attributes of
Note 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.
• 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
Clicking on the Show Details link may take a long time depending on the
Note number of files on that media.
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.
2 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.
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.
2 In the Select Policy Class list, select one or more policy classes on which the report is run and
click Apply.
To view media associated with these policy classes, select the Show Media
Note box.
Relations
The Relations or Directory/Policy Class Relationship report provides information about the directory-
to-policy class relationships in the file system. Use this procedure to run the Directory/Policy Class
Relationship report.
1 Click Reports > Relations.
2 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.
2 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.
2 Select the disks on which to run the report and click Apply.
Depending on the number of files on the Storage Disk, selecting the Yes option
Note to Show Files on Storage Disk can cause the report to be very large and take
a long time to run.
• Name: Name of the storage disk for which the report was run
• Mount Point: The mount point of the storage disk
All of the health options are linked to specific information about that particular
Note health check.
• 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.
4 Click Back to view more archives or close the window when finished.
2 Click Capture.
The Capture State Status window is shown.
3 When the status window indicates the capture was successful, click Close.
5 The Delete Capture File screen’s status changes to Success after the file has been deleted. Click
Close.
• 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
• 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
This screen provides steps and information as to correct the fault that the created the RAS ticket.
5 Follow the instructions on the Recommended Actions screen.
6 Click the Close Window link at the bottom of the Recommended Actions screen.
7 Click the Close or Cancel button on the RAS Ticket Details screen.
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.
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”.
230 cvadmin
repquota Generates quota reports for all users
and groups in the file system.
start file_system_name Starts the SNFS manager for the specified file
[ hostname | IP address ] system (file_system_name).
stop file_system_name Stops the SNFS manager for the specified 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
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.
Examples
• Set the session to use the stripe group that supports the specified affinity key, with the file
system’s mount point as a reference handle:
cvaffinity -k 6100_n8 /usr/clips
• Turn off the stripe group affinity for this session, using the file system’s 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:
• -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
[ -l ] Copies the target of symbolic links rather than copying the link itself.
[ -p source_prefix ] Only copies files that begin with the value of the source_prefix parameter.
[ -y ] Retains ownership and group information (if set by the super user).
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 ] Enables internal debugging.
[ -f ] Reports fragmentation.
FsPath An optional, alternate file system path (other than /usr/cvfs/data) to locate
file systems.
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 Lists available disk devices on the system.
[ -q tag q depth ] Used to set the Command Tag Queue Depth (tag q depth) on IRIX
systems.
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 sub-
directories 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.
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.
size [ k | m | g ] Specifies the file size in bytes. If appended with k, m, or g, the value
represents kilobytes, megabytes or gigabytes.
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.
238 cvmkfile
Command Syntax
cvmkfs [ [ -GF ] [ -n # k, m, g ] file_system_name ]
Options / Arguments
[ -G ] Bypasses “Press return to continue...” type prompts.
[ -F ] 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.
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.
Command Syntax
cvupdatefs [ -f ] [ FsName ] [ FsPath ]
Options / Arguments
[ -f ] Forces updates.
[ FsPath ] An optional, alternate file system path (other than /usr/cvfs/data) to locate
file systems.
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:
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 ]
The file system must be mounted and active before running this
CAUTION command or it will fail.
[ -s softlimit ] Warning limit for the number of media allocated in the policy class.
[ -n notifyID ] E-mail address of the user to notify when the policy class’s softlimit and
hardlimit are reached.
[ -l securitycode ] Security code for the policy class (up to four characters in length).
[ -o acctnum ] Account number for the policy class (up to five characters in length).
[ -x maxcopies ] Maximum number of copies allowed for any file associated with the
policy class.
[ -d defaultcopies ] Total number of copies allowed for each file associated with the policy
class. This value cannot exceed the maxcopies setting.
[ -k maxversions ] Maximum number of inactive versions to keep for a file. The minimum is
1 and the maximum is 25.
Default: 10
[ -m minstoretime ] Minimum time (in minutes) that a file must reside unmodified on disk
before being considered a candidate for storage on media.
[ -c mintrunctime ] Minimum time (in days) that a file must reside unaccessed on disk before
being considered a candidate for truncation.
[ -a affinity ] Lists disk affinities that the files in this policy class will traverse in their
life cycle.
[ -i minreloctime ] Minimum time (in days) that a file must reside unaccessed on disk before
being considered a candidate for relocation.
[ -f i | p ] File retention policy for the policy class. Files can be:
• i - Truncated immediately
[ -r c | s ] Media classification cleanup action. When all files are deleted from a
medium, the medium can revert back to:
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 Path name of the directory to associate with the policy class.
-c 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.
The command fails if the directory has an affinity associated with it.
Use the cvaffinity command to remove its affinity.
3. Create the association between the policy class and the directory.
cd /stornext
fsaudit
The fsaudit command is used to audit the file system.
Command Syntax
fsaudit filesystem [ -f | -i ]
fsaudit filesystem -r [ -f ]
Options / Arguments
filesystem Mount point for the file system to be audited.
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 File having changed attributes.
[ -c copies ] Number of file copies to store (including the primary copy). This value cannot
exceed the maxcopies setting.
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 ]
[ -c class | b ] For blank media, changes the name of the associated policy class
(-c class) or changes the policy class to system blank pool (-b).
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.
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 ] One or more policy classes to be listed.
[ -l ] Long report - processing parameters, directory paths, and the disk affinity list
for the policy class.
Command Syntax
fsclean -m mediaID [ -t [ endtime ] ]
fsclean -s filesystem [ -t [ endtime ] ]
fsclean -c class [ -t [ endtime ] ]
fsclean -t [ endtime ]
Options / Arguments
-m mediaID The media identifier.
[ -t endtime ] 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:
Command Syntax
fsmedcopy mediaID -r [ -d destinationmediaID ] [ -u runtime ]
fsmedcopy mediaID -r [ -b ] [ -t mediatype ] [ -u runtime ]
fsmedcopy [ mediaID ] [ -f fill ] [ -w fragmentation ]
[ -f fill ] 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.
[ -u runtime ] Maximum allowable time (in hours) for the fsmedcopy command
to finish.
fsmedinfo
The fsmedinfo command is used to generate a report on specified media.
Command Syntax
fsmedinfo mediaID [ -l ]
Options / Arguments
mediaID The media identifier.
250 fsmedinfo
fsmedlist
The fsmedlist command is used to generate a media report based on the media’s 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 ] Policy class for which the report is to be generated.
[ -u ] Lists all media marked as unavailable but still located in the StorNext system.
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 The policy class.
[ -d defaultcopies ] Total number of copies allowed for each file associated with the policy
class.
[ -f i | p ] File retention policy (-f) for the policy class. Files can be:
• i - Truncated immediately
[ -l securitycode ] Security code for the policy class (up to 4 characters in length).
[ -m minstoretime ] Minimum time (in minutes) that a file must reside unmodified on disk
before being considered a candidate for storage on media.
[ -c mintrunctime ] Minimum time (in days) that a file must reside unaccessed on disk
before being considered a candidate for truncation.
[ -i minreloctime ] Minimum time (in days) that a file must reside unaccessed on disk
before being considered a candidate for relocation.
[ -n notifyID ] E-mail address of the user to notify when the policy class’s softlimit and
hardlimit are reached.
[ -o acctnum ] Account number for the policy class (up to 5 characters in length).
[ -r c | s ] Media classification cleanup action. When all files are deleted from a
medium, the medium can revert (-r) back to:
[ -s softlimit ] Warning limit for the number of media allocated in the policy class.
252 fsmodclass
[ -a affinity ] Lists disk affinities that the files in the policy class will traverse in their
life cycle.
[ -x maxcopies ] 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
[ -m minreloctime ] Minimum time (in minutes) that a file must reside on disk before being
considered a candidate for relocation.
[ -m minstoretime ] Minimum time (in minutes) that a file must reside on disk before being
considered a candidate for storage.
[ -m mintrunctime ] Minimum time (in days) that a file must reside unaccessed on disk before
being considered a candidate for truncation.
[ -v drivepool ] Specifies the drivepool from which to allocate drives when storing files.
[ -b ] Scans file system for candidate files to store or truncate and rebuilds the
candidate lists.
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 ] Reports files in the queue or specific files for a request identifier or filename.
[ -m ] Reports media movement for a request identifier or all media in the queue.
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.
[RM_time:]filepathname 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.
[ -t starttime [endtime ] ] 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
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 Full path and filename of the file to retrieve.
[ -n newfilename ] New path and name into which to retrieve the file.
[ -b startbyte endbyte ] Specifies a byte range to retrieve. The value of startbyte must be
less than the endbyte value. Both values must be within the file’s
byte range.
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 Removes a specific file (filename) or file to remove from disk or media.
[ -c copynum | a ] Deletes either a specific number of file copies (copynum) or all file
copies (a) from the 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 The media identifier.
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 ] Alias for drives and storage subsystems.
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 Name of file on disk to store to media.
[ -f i | p ] File retention policy (-f) for the file. Files can be:
• i - Truncated immediately
• p - Truncated at policy application time
[ -v drivepool ] Specifies the Media Manager drive pool group used to store the file.
fsversion
The fsversion command is used to determine a file’s 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
-h Displays usage.
[ -v ] Verbose listing of the file’s current version (version number and modification
time).
-c ver Modifies the file’s current version to the specified inactive version.
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.
[ -c | -cl component ] Specifies the software files you restore. You can
specify:
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.
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 Specifies the archive (archivename) to be queried or that all archives (-a)
will be queried.
[ -c ] Indicates that detailed information on all media classes associated with the
specified archive(s) will be reported.
[ -d ] Indicates that all drives associated with the specified archive(s) will
be reported.
[ -m ] Indicates that all media associated with the specified archive(s) will
be reported.
[ -t ] Indicates that detailed information on all media types associated with the
specified archive(s) will be reported.
[ -v ] Indicates that all drives, media classes, media, and media types associated
with the specified archive(s) will be reported.
262 vsarchiveqry
[ -T timeout ] Time interval (in seconds) that the software waits for status before returning
a timeout.
Default: 120
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 ]
[ -l ] Indicates that the command line options are to be read from stdln.
[ -T timeout ] Time interval (in seconds) that the software waits for status before returning a
timeout.
Default: 120
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 Specifies the drive(s) whose state is to be varied.
-p drivepool Specifies the drivepool for which associated drives’ states will be varied.
[ -T timeout ] Time interval (in seconds) that the software waits for status before returning a
timeout.
Default: 120
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
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 Specifies a media class (mediaclass) or all media classes (-a) on which to
request information.
[ -m ] Requests a list of media identifiers for all media associated with each reported
media calss.
[ -v ] Requests detailed information for all media associated with each reported
media class.
[ -T timeout ] Time interval (in seconds) that the software waits for status before returning a
timeout.
Default: 120
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 Specifies a media type (mediaID) or all media (-a) to be queried.
[ -T timeout ] Time interval (in seconds) that the software waits for status before
returning a timeout.
Default value: 120
Examples
• Requests that the Media Manager software return information on every medium known to the
Media Manager system:
vsmedqry -a
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 Configures the specified drive pool.
[ -T timeout ] Time interval (in seconds) that the software waits for status before returning
a timeout.
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 Specifies one or more media to reclassify.
-c currentmediaclass Specifies the media class with which the specified media is to be
associated.
-n newmediaclass Specifies the new media class with which the specified media is to be
associated.
[ -T timeout ] Time interval (in seconds) that the software waits for status before
returning a timeout.
Default: 120
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
If you have files larger than 100GB and are using LTO2 media, the
CAUTION 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.
• 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
• 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.
• -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:
• $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.
#
# Globals Defaulted
#
[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
[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
[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
[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
• /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.
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-real-
time applications so their I/O accesses do not interfere with the real-time application.
QOS is a passive implementation in that it does not actively monitor a process’ activity and then
schedule the process so that it receives the bandwidth it has requested. It is up to real-time
applications to gate their own I/O requests to the desired rate. SNFS QOS provides a "get out of the
way" gating for non-real-time I/O requests so they do not hinder the real-time requests.
QOS is fully functional in SNFS version 2.1.2 and later. Earlier versions of SNFS do not support QOS.
If a pre-QOS client connects, the file system manager (FSM) logs a message to syslog. If the pre-
QOS client connects while real-time I/O is in progress, the message is logged at the critical event
level.
The remainder of this document explains the client and server configuration settings for QOS;
describes the use of tokens and callbacks for gating non-real-time I/O; describes setting real-time I/
O on a file; and discusses the performance monitoring tools that are available for diagnosis.
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.
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)
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 real-
time I/O requests. To optimize the disk subsystem, real-time I/Os are well-formed so they saturate
the disks. In SNFS terminology, this would be an I/O that covers all of the disks in a stripe. This can
be expressed as follows:
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 re-
qualify the I/O subsystem to determine the amount of bandwidth available. This amount will be
specified in the FSM configuration file. The user can also specify the minimum amount of bandwidth
to be provided to non-real-time applications.
There are five keywords controlling QOS that can be specified in the stripe group section of the FSM
configuration file. Not all keywords need be present. Typically, the user specifies the RTIO bandwidth
in terms of either number of I/O operations per second (rtios) or megabytes per second (rtmb).
Keywords are not case sensitive.
For a minimum configuration, only the real-time limit (either rtios or rtmb) need be specified. All
other configuration variables default to reasonable values.
It is important to realize that the rtios and rtmb settings refer to the total
Note amount of sustained bandwidth available on the disk subsystem. Any I/O, either
real-time or non-real-time, will ultimately be deducted from this overall limit. The
calculations of available real-time and non-real-time are discussed later.
Specifying rtmb in the FSM configuration file is only recommended if all I/Os
are well formed (that is, a full stripe width). Otherwise, the conversion between
MB/sec and I/Os/sec using the well-formed I/O calculation could lead to
unexpected results.
Reserve
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.
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 file—each with a different amount of
real-time I/O—only the last file close triggers the releasing action; all aggregate rtio are released.
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.
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.
Callbacks
The cornerstones of the communications between the FSM and the client are callbacks and tokens.
A callback is an unsolicited message from the FSM to the client requesting that the client adjust its
real-time I/O parameters. The callback contains a token that specifies the amount of non-real-time I/
O available on a stripe group.
Initially, all stripe groups in a file system are in non-real-time (ungated) mode. When the FSM receives
the initial request for real-time I/O, it first issues callbacks to all clients informing them that the stripe
group is now in real-time mode. The token accompanying the message specifies no I/O is available
for non-real-time I/O. Clients must now obtain a non-real-time token before they can do any non-real-
time I/O.
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 real-
time (steps 11-14). In the example, Client C responds to the second callback, so the FSM will not send
out any more callbacks. The stripe group is back in non-real-time mode.
Note that this can have interesting repercussions with file systems that are soft mounted by default
(such as Windows). When the caller times out because other clients are not responding and then
gives up and returns an error to the application, if at some point the FSM is able to process the rtio
request it may result in the stripe group being put into 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:
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.
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.
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 non-
real-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.
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
Note failover.
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.
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.
Drive Pool
A grouping of drives for use in storing and retrieving data.
Managed Directory
A directory that has a policy class relationship.
MediaClass
A grouping of media used for storing or retrieving data.
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).
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.
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 affinities report . . . . . . . . . . . . . . . . . . . . . . 192
ATAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
/usr/cvfs/bin/ . . . . . . . . . . . . . . . . . . . . . . . . 283 auditing, library . . . . . . . . . . . . . . . . . . . . . 126
/usr/cvfs/CLIENTS/ . . . . . . . . . . . . . . . . . . . 284
/usr/cvfs/config/ . . . . . . . . . . . . . . . . . . . . . 283 B
/usr/cvfs/data//log/ . . . . . . . . . . . . . . . . . . . 283
/usr/cvfs/debug/ . . . . . . . . . . . . . . . . . . . . . 283 backup report . . . . . . . . . . . . . . . . . . . . . . 197
/usr/cvfs/docs/ . . . . . . . . . . . . . . . . . . . . . . 284 basic tasks . . . . . . . . . . . . . . . . . . . . . . . . . . 39
/usr/cvfs/examples/ . . . . . . . . . . . . . . . . . . . 284
/usr/cvfs/lib/ . . . . . . . . . . . . . . . . . . . . . . . . 284 C
/usr/cvfs/src/ . . . . . . . . . . . . . . . . . . . . . . . . 284
changing log rolling . . . . . . . . . . . . . . . . . . 274
A cleaning tape drive . . . . . . . . . . . . . . . . . . 136
configuration file
accessing filesize.config . . . . . . . . . . . . . . . . . . . . 273
SNMS GUI . . . . . . . . . . . . . . . . . . . . . . . 21 fs sysparm . . . . . . . . . . . . . . . . . . . . . . 272
StorNext FS GUI . . . . . . . . . . . . . . . . . . . 43 log params . . . . . . . . . . . . . . . . . . . . . . 273
adding conventions in document . . . . . . . . . . . . . . . 19
disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 creating
drive pool . . . . . . . . . . . . . . . . . . . . . . . 137 policy class . . . . . . . . . . . . . . . . . 184, 188
FC drive . . . . . . . . . . . . . . . . . . . . . . . . 273 customer assistance . . . . . . . . . . . . . . . . . 227
library . . . . . . . . . . . . . . . . . . . . . . . . . . 111 cvadmin command . . . . . . . . . . . . . . . . . . 229
stripe group . . . . . . . . . . . . . . . . . . . . . . . 90 cvaffinity command . . . . . . . . . . . . . . . . . . 232
adding media . . . . . . . . . . . . . . . . . . . . . . . 142 cvcp command . . . . . . . . . . . . . . . . . . . . . 233
policy class . . . . . . . . . . . . . . . . . . . . . . 182 cvfsck command . . . . . . . . . . . . . . . . . . . . 235
advanced pages cvfsid command . . . . . . . . . . . . . . . . . . . . 236
admin cvlabel command . . . . . . . . . . . . . . . . . . . 236
StorNext SM . . . . . . . . . . . . . . . . . 38 cvmkdir command . . . . . . . . . . . . . . . . . . . 237
file cvmkfile command . . . . . . . . . . . . . . . . . . . 238
StorNext SM . . . . . . . . . . . . . . . . . 36 cvmkfs command . . . . . . . . . . . . . . . . . . . 238
media cvupdatefs command . . . . . . . . . . . . . . . . 239
StorNext SM . . . . . . . . . . . . . . . . . 37 cvversions command . . . . . . . . . . . . . . . . . 240
reports
StorNext SM . . . . . . . . . . . . . . . . . 39
304 Index
H media . . . . . . . . . . . . . . . . . . . . . . . . . . 141
policy class . . . . . . . . . . . . . . . . . . . . . . 174
help, website . . . . . . . . . . . . . . . . . . . . . . . 227 media
home page adding . . . . . . . . . . . . . . . . . . . . . . . . . . 142
SNMS GUI . . . . . . . . . . . . . . . . . . . . . . . 23 managing . . . . . . . . . . . . . . . . . . . . . . . 141
StorNext FS . . . . . . . . . . . . . . . . . . . . . . 45 mounting . . . . . . . . . . . . . . . . . . . . . . . . 158
StorNext SM on the SNMS GUI . . . . . . 35 moving . . . . . . . . . . . . . . . . . . . . . . . . . 147
how this guide is organized . . . . . . . . . . . . . 18 removing . . . . . . . . . . . . . . . . . . . . . . . . 147
transcribing . . . . . . . . . . . . . . . . . . . . . . 160
I media class grouping, reclassifying . . . . . . 161
media class report . . . . . . . . . . . . . . . . . . . 207
installed files media report . . . . . . . . . . . . . . . . . . . . . . . . 204
/usr/cvfs/bin/ . . . . . . . . . . . . . . . . . . . . 283 menu options
/usr/cvfs/CLIENTS/ . . . . . . . . . . . . . . . 284 admin
/usr/cvfs/config/ . . . . . . . . . . . . . . . . . . 283 SNMS GUI . . . . . . . . . . . . . . . . . . . 27
/usr/cvfs/data//log/ . . . . . . . . . . . . . . . . 283 StorNext FS GUI . . . . . . . . . . . . . . 47
/usr/cvfs/debug/ . . . . . . . . . . . . . . . . . . 283 config
/usr/cvfs/docs/ . . . . . . . . . . . . . . . . . . . 284 StorNext FS GUI . . . . . . . . . . . . . . 46
/usr/cvfs/examples/ . . . . . . . . . . . . . . . 284 reports
/usr/cvfs/lib/ . . . . . . . . . . . . . . . . . . . . . 284 SNMS GUI . . . . . . . . . . . . . . . . . . . 28
/usr/cvfs/src/ . . . . . . . . . . . . . . . . . . . . 284 StorNext FS GUI . . . . . . . . . . . . . . 48
intended audience . . . . . . . . . . . . . . . . . . . . 17 StorNext FS . . . . . . . . . . . . . . . . . . . . . . 45
introduction . . . . . . . . . . . . . . . . . . . . . . . . . 17 modifying
drive pool . . . . . . . . . . . . . . . . . . . . . . . 139
L global settings . . . . . . . . . . . . . . . . . . . . 73
library . . . . . . . . . . . . . . . . . . . . . . . . . . 124
libraries report . . . . . . . . . . . . . . . . . . . . . . 202 policy class . . . . . . . . . . . . . . . . . .179, 188
library stripe group . . . . . . . . . . . . . . . . . . . . . . 93
adding . . . . . . . . . . . . . . . . . . . . . . . . . 111 monitor, library . . . . . . . . . . . . . . . . . . . . . . . 25
auditing . . . . . . . . . . . . . . . . . . . . . . . . 126 mounting
deleting . . . . . . . . . . . . . . . . . . . . . . . . 125 file system . . . . . . . . . . . . . . . . . . . .82, 83
managing . . . . . . . . . . . . . . . . . . . . . . . 111 mounting media . . . . . . . . . . . . . . . . . . . . . 158
modifying . . . . . . . . . . . . . . . . . . . . . . . 124 moving media . . . . . . . . . . . . . . . . . . . . . . . 147
sharing between applications . . . . . . . 271
library monitor . . . . . . . . . . . . . . . . . . . . . . . 25 N
library space used report . . . . . . . . . . . . . . 203
license, entering . . . . . . . . . . . . . . . . . . . . . 39 name servers . . . . . . . . . . . . . . . . . . . . . . . . 76
log params configuration file . . . . . . . . . . . 273 navigating
logging on . . . . . . . . . . . . . . . . . . . . . . . . . . 66 SNMS GUI . . . . . . . . . . . . . . . . . . . . . . . 23
logs StorNext FS GUI . . . . . . . . . . . . . . . . . . 45
changing log rolling . . . . . . . . . . . . . . . 274
log rolling options . . . . . . . . . . . . . . . . 274 O
306 Index
accessing . . . . . . . . . . . . . . . . . . . . . . . 43 V
menu options
admin . . . . . . . . . . . . . . . . . . . . . . 47 vsarchiveqry command . . . . . . . . . . . . . . . 261
config . . . . . . . . . . . . . . . . . . . . . . 46 vsdriveqry command . . . . . . . . . . . . . . . . . 263
reports . . . . . . . . . . . . . . . . . . . . . 48 vsdrivevary command . . . . . . . . . . . . . . . . 265
navigating . . . . . . . . . . . . . . . . . . . . . . . 45 vsmedclassqry command . . . . . . . . . . . . . . 266
using . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 vsmedqry command . . . . . . . . . . . . . . . . . . 267
StorNext GUI, overview . . . . . . . . . . . . . . . . 21 vspoolcfg command . . . . . . . . . . . . . . . . . . 268
StorNext license, entering . . . . . . . . . . . . . . 39 vsreclassify command . . . . . . . . . . . . . . . . 269
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 perfor-
mance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
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