Installation Guide Installation Guide Installation Guide Installation Guide StorNext® 3.1.
StorNext 3.1.3 Installation Guide, 6-00360-15 Rev B, September 2009, Made in USA. Quantum Corporation provides this publication “as is” without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability or fitness for a particular purpose. Quantum Corporation may revise this publication from time to time without notice. COPYRIGHT STATEMENT © Copyright 2000 - 2009 Quantum Corporation. All rights reserved. US Patent No: 5,990,810 applies.
Contents Chapter 1 Installing StorNext File System and Storage Manager 1 Storage Manager System Requirements......................................................... 2 Operating System Requirements.............................................................. 2 Hardware Requirements ........................................................................... 2 LAN Requirements..................................................................................... 4 Getting Ready to Install .................
Contents Hardware Requirements ......................................................................... 20 LAN Requirements................................................................................... 20 Getting Ready to Install .................................................................................. 21 Configuring Storage Devices .................................................................. 21 Planning for LUNs Larger than 1 TB .....................................................
Contents Configuring a Distributed LAN Client on Linux................................. 68 Configuring a Distributed LAN Server on Linux ................................ 68 Windows Configuration Utilities .................................................................. 72 Client Configuration................................................................................. 73 Disk Device Labeler.................................................................................. 83 License Identifier........
Contents Log Rolling Options ............................................................................... 123 Avoiding Poor System Performance........................................................... 124 Appendix C StorNext Files 125 The example.cfg File ...................................................................................... 125 Commonly Used SNFS Files ........................................................................ 132 Appendix D Quality of Service Guide 135 Overview..
Figures StorNext 3.1.3 Installation Guide Figure 1 Pre-Installation Script ................................................................ 10 Figure 2 StorNext Installation Script....................................................... 13 Figure 3 Configuration Menu .................................................................. 15 Figure 4 StorNext Installation Status ...................................................... 17 Figure 5 SNFS Installation Script...................................
Figures StorNext 3.1.3 Installation Guide Figure 18 Import/Export Client Configuration Window...................... 35 Figure 19 Select Platform Window............................................................ 40 Figure 20 Download Client Software Window ....................................... 41 Figure 21 StorNext Installation Window: Remove StorNext ................ 52 Figure 22 StorNext Installation Window: Install StorNext.................... 53 Figure 23 SNFS Setup: Welcome .............
Figures StorNext 3.1.3 Installation Guide Figure 47 File System Startup List ............................................................. 90 Figure 48 Server Administration ............................................................... 92 Figure 49 Server Administration: File System Properties...................... 93 Figure 50 Server Administration: Stripe Group Properties ................... 94 Figure 51 Server Administration: Quota Properties ...............................
Tables StorNext 3.1.3 Installation Guide Table 1 Storage Manager Supported Platforms.................................... 2 Table 2 Storage Manager Hardware Requirements.............................. 3 Table 3 Required Disk LUN Labels ......................................................... 6 Table 4 StorNext Support Directories ..................................................... 8 Table 5 Pre-Installation Script Recommendation Types ....................
Tables StorNext 3.1.3 Installation Guide Table 18 Disk Labeler Dialog Box ............................................................ 85 Table 19 Simple File System Configuration ........................................... 87 Table 20 File System Startup List ............................................................. 90 Table 21 Server Administration: File System Properties...................... 93 Table 22 Server Administration: Stripe Group Properties ...................
Preface StorNext provides high performance data sharing and intelligent archiving that is compatible with an industry-leading range of operating systems, server platforms, and storage devices. StorNext includes two main components: • StorNext File System (SNFS) is high performance data sharing software that lets applications on multiple operating systems access a single data set.
Preface Audience Audience This document is intended for service professionals and system administrators who install StorNext software. The installer should have strong familiarity with the operating system on which StorNext is installed. Only service professionals, experienced StorNext users, or individuals who have successfully completed StorNext training should configure StorNext.
Preface Document Organization Document Organization This document contains the following chapters: • Chapter 1, “Installing StorNext File System and Storage Manager,” provides system requirements, pre-installation information, and instructions for installing StorNext File System and Storage Manger on a metadata controller (MDC).
Preface Notational Conventions Notational Conventions This manual uses the following conventions: Convention Example User input is shown in Arial regular font. ./install.stornext User input variables are enclosed in angle brackets and are shown in Arial italic font. mkdir -p For UNIX and Linux commands, the command prompt is implied. ./install.stornext is the same as # ./install.
Preface Related Documents Warning: Warnings indicate potential hazards to personal safety and are included to prevent injury. Related Documents Documents related to StorNext are shown below: 0 Quantum StorNext Documentation StorNext 3.1.3 Installation Guide Document No. Document Title Document Description 6-01658-06 StorNext User’s Guide Provides in-depth information about using StorNext to create and manage StorNext File Systems.
Preface Contacting Quantum Document No. Document Title Document Description 6-01564-02 AMASS Conversion Guide Provides information about migrating systems running AMASS to StorNext. 6-00431-23 StorNext 3.1.3 Release Notes Includes the latest product information, fixes, and issues. Contacting Quantum More information about this product is available on the Quantum Service and Support website at www.quantum.com/ServiceandSupport.
Chapter 1 1 Installing StorNext File System and Storage Manager This chapter describes how to install StorNext File System (SNFS) and StorNext Storage Manager (SNSM) on a metadata controller (MDC). Install both SNFS and SNSM for storage systems that require policybased data movement (for example, systems that include tape drives or libraries).
Chapter 1 Installing StorNext File System and Storage Manager Storage Manager System Requirements Storage Manager System Requirements To run StorNext File System and Storage Manager, the metadata controller must meet all operating system, hardware, and LAN requirements. Operating System Requirements 1 Table 1 Storage Manager Supported Platforms The operating systems, kernel versions, and hardware platforms supported by StorNext SNFS and SNSM are presented in Table 1.
Chapter 1 Installing StorNext File System and Storage Manager Storage Manager System Requirements Note: Table 2 Storage Manager Hardware Requirements The RAM requirements in Table 2 are for running StorNext File System and Storage Manager only. Running additional software (including the StorNext client software) requires additional RAM.
Chapter 1 Installing StorNext File System and Storage Manager Storage Manager System Requirements Partitioning Local Hard Disks 1 StorNext can be installed on any local file system (including the root file system) on the MDC. However, for optimal performance, as well as to aid disaster recovery, follow these recommendations: • Avoid installing StorNext on the root file system.
Chapter 1 Installing StorNext File System and Storage Manager Getting Ready to Install Getting Ready to Install Before installing StorNext SNFS and SNSM, complete the following tasks to ensure successful installation: • Correctly configure all storage devices (see Configuring Storage Devices). • If using LUNs larger than 1 TB, decide on a label type and install any necessary operating system patches (see Planning for LUNs Larger than 1 TB).
Chapter 1 Installing StorNext File System and Storage Manager Getting Ready to Install of the operating system running on the MDC as well as the operating system running on all connected clients. Disk LUNs can have one of three labels: VTOC, EFI, or sVTOC (short VTOC). Required disk LUN label settings based on operating system and LUN size are presented in Table 3.
Chapter 1 Installing StorNext File System and Storage Manager Getting Ready to Install Operating System Label for LUNs < 1 TB Label for LUNs 1–2 TB Label for LUNs > 2 TB Apple Xsan 1.2a VTOC VTOC sVTOC a. b. c. d. Supports only the first 2 TB of LUNs larger than 2 TB. Support for EFI labels requires the Multiterabyte Disk Support patch. Support for 2 TB or larger LUNs requires Solaris 10 Update 2 (06/06). Supports only LUNs of 2.2 TB or less.
Chapter 1 Installing StorNext File System and Storage Manager Pre-Installation Script Pre-Installation Script The StorNext pre-installation script (snPreInstall) is included on the StorNext installation CD. When you run snPreInstall, you are prompted for information about your system. The pre-installation script uses this information to estimate the amount of local disk space required for SNFS and SNSM support directories. In addition, the script recommends the optimal locations for support directories.
Chapter 1 Installing StorNext File System and Storage Manager Pre-Installation Script • What is the maximum number of directories expected (in millions)? • What is the maximum number of files expected (in millions)? • How many copies will be stored for each file? • How many versions will be retained for each file? Running snPreInstall 1 Note: Keep in mind that storage needs typically grow rapidly. Consider increasing the maximum number of expected directories and files by a factor of 2.
Chapter 1 Installing StorNext File System and Storage Manager Pre-Installation Script Figure 1 Pre-Installation Script 6 Follow the onscreen instructions, and answer each question when prompted. The script outputs results based on the information you entered. Interpreting snPreInstall Output 1 After you enter all requested information, the pre-installation script outputs the following results: • Estimated disk space required for each support directory.
Chapter 1 Installing StorNext File System and Storage Manager Pre-Installation Script Table 5 Pre-Installation Script Recommendation Types Type Description RECOMMEND The suggested directory locations will result in optimal system performance. NOTE The suggested directory locations are valid but system performance will not be optimal. SPACE Additional hard disk space is required to store the required support directories.
Chapter 1 Installing StorNext File System and Storage Manager StorNext Installation Script StorNext Installation Script When you are ready to install StorNext, use the StorNext installation script to install StorNext File System and Storage Manager on the metadata controller. The installation script also installs the client software on the MDC. Launching the StorNext Installation Script 1 The StorNext installation script lets you choose installation configuration options and install StorNext.
Chapter 1 Installing StorNext File System and Storage Manager StorNext Installation Script Figure 2 StorNext Installation Script StorNext 3.1.
Chapter 1 Installing StorNext File System and Storage Manager StorNext Installation Script 6 Type the number corresponding to a menu option and press . Installation menu options are described in Table 6. Table 6 StorNext Installation Main Menu Options Changing Installation Configuration Options 1 Menu Option Description 1 Change installation options, including the location of application directories and the default media type (see Changing Installation Configuration Options).
Chapter 1 Installing StorNext File System and Storage Manager StorNext Installation Script Figure 3 Configuration Menu Changing Application Directory Locations 1 When you first enter the Configuration Menu, it displays recommended locations for StorNext application directories based on the available file systems detected by the installation script. To accept the recommended directory locations and return to the Main Menu, press .
Chapter 1 Installing StorNext File System and Storage Manager StorNext Installation Script 3 To confirm the change, type yes and press . To customize additional directory locations, repeat steps 1–3. 4 When you are done customizing the installation, press to return to the Main Menu. Note: To help determine the optimal location for StorNext support directories, use the StorNext pre-installation script. For more information, see Pre-Installation Script on page 8.
Chapter 1 Installing StorNext File System and Storage Manager StorNext Installation Script Performing an Installation Operation 1 To install StorNext using the options specified on the Configuration Menu, perform an installation operation. 1 On the Main Menu, type 2 and press . The StorNext installation script runs (figure 4). The script displays the current progress of the installation.
Chapter 2 2 Installing StorNext File System This chapter describes how to install StorNext File System (SNFS) on a metadata controller (MDC). Install SNFS to create data sets that can be shared by clients and applications running on multiple operating systems. To ensure successful operation, do the following tasks before installing StorNext: • Make sure the MDC meets all operating system and hardware requirements (see File System Requirements).
Chapter 2 Installing StorNext File System File System Requirements File System Requirements To run StorNext File System, the metadata controller must meet all operating system and hardware requirements. Operating System Requirements 2 Table 7 File System Supported Platforms The operating systems, releases and kernels, and hardware platforms supported by StorNext SNFS are presented in Table 7.
Chapter 2 Installing StorNext File System File System Requirements Hardware Requirements 2 The minimum amount of RAM and available hard disk space required to run StorNext SNFS are presented in Table 8. If necessary, upgrade the RAM and local disk storage in the MDC to meet the minimum requirements before installing StorNext. Note: Table 8 File System Hardware Requirements The RAM requirements in Table 8 are for running StorNext File System only.
Chapter 2 Installing StorNext File System Getting Ready to Install • If using Gigabit Ethernet, disable jumbo frames and TOE (TCP offload engine). Note: StorNext does not support file system metadata on the same network as iSCSI, NFS, CIFS, or VLAN data when 100 Mbit/s or slower networking hardware is used.
Chapter 2 Installing StorNext File System Getting Ready to Install Caution: Planning for LUNs Larger than 1 TB 2 StorNext does not support the connection of multiple devices through fibre channel hubs. Multiple devices must be connected using fibre channel switches. StorNext supports LUNs greater than 1 TB in size if they are allowed by the operating system.
Chapter 2 Installing StorNext File System Getting Ready to Install Operating System Label for LUNs < 1 TB Label for LUNs 1–2 TB Label for LUNs > 2 TB IBM AIXd VTOC, EFI VTOC, EFI EFI, sVTOC SGI IRIX VTOC VTOC Not supported Apple Xsan 1.3 (MacOS X 10.4 Tiger) VTOC, EFI VTOC, EFI EFI, sVTOC Apple Xsan 1.3 (MacOS X 10.3 Panther)a VTOC, EFI VTOC, EFI EFI, sVTOC Apple Xsan 1.2a VTOC VTOC sVTOC a. b. c. d. Supports only the first 2 TB of LUNs larger than 2 TB.
Chapter 2 Installing StorNext File System Installing StorNext File System on Linux or Unix Installing StorNext File System on Linux or Unix When you are ready to install StorNext, use the SNFS installation script to install StorNext File System on a metadata controller running Linux or Unix. The installation script also installs the client software on the MDC. StorNext can be installed on any local file system (including the root file system) on the MDC.
Chapter 2 Installing StorNext File System Installing StorNext File System on Linux or Unix Figure 5 SNFS Installation Script 6 Type the number corresponding to a menu option and press . Installation menu options are described in Table 10. Table 10 SNFS Installation Main Menu Options Changing Installation Configuration Options 2 Menu Option Description 1 Change installation options for the location of application directories (see Changing Installation Configuration Options on page 25).
Chapter 2 Installing StorNext File System Installing StorNext File System on Linux or Unix Figure 6 Configuration Menu When you first enter the Configuration Menu, it displays recommended locations for StorNext application directories based on the available file systems detected by the installation script. To accept the recommended directory locations and return to the Main Menu, press .
Chapter 2 Installing StorNext File System Installing StorNext File System on Windows Figure 7 StorNext Installation Status 2 When the installation is complete, press to return to the Main Menu. 3 To exit the installation script, type 4 and press . Note: The script displays the URL at which the MDC can be accessed. Make a note of this information. You can now access StorNext File System and run the configuration wizard. For more information, see Chapter 4, “Configuring StorNext.
Chapter 2 Installing StorNext File System Installing StorNext File System on Windows Note: Removing a Previous Version of StorNext 2 You must log on as an Administrator to install StorNext. If a previous version of StorNext exists on the system, you must remove it before installing the new version. 1 Insert the StorNext installation CD. 2 Browse to the root directory of the installation CD and double-click the file SnfsSetup32.exe (32-bit systems) or SnfsSetup64.exe (64-bit systems).
Chapter 2 Installing StorNext File System Installing StorNext File System on Windows Note: Running the Setup Wizard 2 After installing the new version of StorNext, you can restore the saved client configuration (see Restoring a Previous Client Configuration on page 33). To launch the setup wizard, use the correct StorNext installation CD for your operating system. 1 Insert the StorNext installation CD. 2 Browse to the root directory of the installation CD and double-click the file SnfsSetup32.
Chapter 2 Installing StorNext File System Installing StorNext File System on Windows Figure 10 SNFS Setup: Welcome 4 Click Next to continue. The License Agreement window appears (figure 11). Figure 11 SNFS Setup: EndUser License Agreement 5 Click the option to accept the license agreement, and then click Next to continue. The Customer Information window appears (figure 12). StorNext 3.1.
Chapter 2 Installing StorNext File System Installing StorNext File System on Windows Figure 12 SNFS Setup: Customer Information 6 Type your name and the name of your company or organization in the boxes, and then click Next to continue. The Choose Setup Type window appears (figure 13). Figure 13 SNFS Setup: Choose Setup Type 7 Click an installation option: • StorNext 3.1.
Chapter 2 Installing StorNext File System Installing StorNext File System on Windows • Custom: Lets you choose which components to install and specify an installation location. When ready, click Next. • Complete: Same as a typical installation. The Ready to Install window appears (figure 14). Figure 14 SNFS Setup: Ready to Install 8 Click Install to continue. Wait while the setup wizard installs StorNext. When installation is complete, the Finish window appears (figure 15).
Chapter 2 Installing StorNext File System Installing StorNext File System on Windows 9 Click Finish to close the setup wizard. 10 On the StorNext Installation window, click Exit. You are prompted to reboot the system. 11 Click Yes to reboot. You can now configure StorNext File System. For more information, see Chapter 4, “Configuring StorNext.” Or, to restore a previous client configuration, see the next section.
Chapter 2 Installing StorNext File System Installing StorNext File System on Windows Figure 17 StorNext Configuration Window 4 Click Import/Export Client Settings. The Import/Export Client Configuration window appears (figure 18). StorNext 3.1.
Chapter 2 Installing StorNext File System Installing StorNext File System on Windows Figure 18 Import/Export Client Configuration Window 5 Under Import, click Browse. Locate the client configuration (*.reg) file to import, and then click Open.
Chapter 3 3 Installing the StorNext Client This chapter describes how to install the StorNext client software. The StorNext client software lets you mount and work with StorNext file systems. To ensure successful operation, make sure the client system meets all operating system and hardware requirements (see Client System Requirements). To install the StorNext client software, first download the client software from the metadata controller (MDC) (see Downloading the StorNext Client Software on page 39).
Chapter 3 Installing the StorNext Client Client System Requirements Client System Requirements To run the StorNext client software, the client system must meet all operating system and hardware requirements. Operating System Requirements 3 Table 11 StorNext Client Supported Platforms The operating systems, releases and kernels, and hardware platforms supported by the StorNext client software are presented in Table 11.
Chapter 3 Installing the StorNext Client Client System Requirements Hardware Requirements 3 Operating System Release or Kernel Platform Sun Solaris 10 Generic 120011-14 SPARC 64-bit Generic 127128-11 Opteron and Intel x86 64-bit HP-UX 11i v2 Itanium 64-bit IBM AIX 5.3 64-bit Power Architecture SGI-IRIX 6.5.30 64-bit MIPS Apple MacOS X 10.5 With Xsan 1.4.2 or Xsan 2.1.
Chapter 3 Installing the StorNext Client Downloading the StorNext Client Software Downloading the StorNext Client Software The StorNext client software can be downloaded from a metadata controller. (To download the client software, the client system must have network access to the MDC.) Note: You can download the client software only from MDCs running Linux or Unix. 1 On the client system, point a web browser to the URL (host name and port number) of the MDC.
Chapter 3 Installing the StorNext Client Downloading the StorNext Client Software Figure 19 Select Platform Window 4 In the list, click the operating system running on the client system, and then click Next. The Download Client Software window appears (figure 20). StorNext 3.1.
Chapter 3 Installing the StorNext Client Downloading the StorNext Client Software Figure 20 Download Client Software Window 5 Click the download link that corresponds to your operating system version and hardware platform. (Depending on the operating system, you may have only one choice.) For example, for Red Hat Linux 4 running on an x86 64-bit platform, click Linux Redhat AS 4.0 (Intel 64bit). 6 When prompted, click Save or OK to download the file to the client system.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Linux or Unix Installing the StorNext Client on Linux or Unix After downloading the StorNext client software from the metadata controller, install it on the client system using the correct procedure for your operating system: • Installing the StorNext Client on Linux on page 42 • Installing the StorNext Client on Sun Solaris on page 44 • Installing the StorNext Client on HP-UX on page 46 • Installing the StorNext Client on IBM AIX o
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Linux or Unix Note: The file that ends with .rpm.md5sum is a checksum file, not the client software package. 5 Install the client software package. At the command prompt, type: rpm -ivh where is the name of the client software package you identified in step 4. 6 Configure the boot order for system services.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Linux or Unix 9 Configure the file system to automatically mount after reboot. To do this, edit the /etc/fstab file so that it contains the following line: cvfs verbose=yes 0 0 where is the name of the StorNext file system and is the directory path created in step 8. 10 Reboot the client system.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Linux or Unix 7 Edit the /usr/cvfs/config/fsnameservers text file to contain the IP address of the MDC the client will connect to. The fsnameservers file on the client must be exactly the same as on the MDC. If the fsnameservers file does not exist, use a text editor to create it. Note: The fsnameservers file only needs to contain the name of the MDC.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Linux or Unix Installing the StorNext Client on HP-UX 3 To run the StorNext client software on HP-UX, first install the client software package, and then configure the client. 1 Log on to the client system as root. 2 Change to the directory where the client software archive file you downloaded from the MDC is located. 3 Extract the software archive file.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Linux or Unix 7 Create a mount point for the file system. At the command prompt, type: mkdir -p chmod 777 where is the directory path where you want the file system to be mounted. For example: /stornext/snfs1 8 Configure the file system to automatically mount after reboot.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Linux or Unix 4 List the packages extracted from the software archive file. At the command prompt, type: ls -l Identify the correct package to install. The correct package begins with snfs and ends with the .bff file name extension. 5 Install the client software package. At the command prompt, type: installp -ac -d all . where is the name of the client software package you identified in step 4.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Linux or Unix Note: To manually mount a file system, at the command prompt, type: mount where is the directory path where you want the file system to be mounted. Installing the StorNext Client on SGI IRIX 3 To run the StorNext client software on SGI IRIX, first install the client software package, and then configure the client. 1 Log on to the client system as root.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Linux or Unix Note: The fsnameservers file only needs to contain the name of the MDC. For example, if the MDC is named snserver, then the fsnameservers file should contain a single line with a single word: snserver 8 Create a mount point for the file system. At the command prompt, type: mkdir -p chmod 777 where is the directory path where you want the file system to be mounted.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Windows Installing the StorNext Client on Windows The StorNext setup wizard guides you through the process of installing the StorNext client software on Windows XP, Windows 2003 Server, or Windows Vista. Before installing StorNext, remove any previously installed versions (see Removing a Previous Version of StorNext on page 51). When you are ready, use the setup wizard to install StorNext (see Running the Setup Wizard on page 52).
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Windows Figure 21 StorNext Installation Window: Remove StorNext 3 Click Remove StorNext. A dialog box appears informing you that the current client configuration has been saved. 4 Note the name and location of the saved configuration file, and then click OK. 5 If prompted, click Yes to continue, and then click OK to finish the removal. 6 When the removal is complete, click Yes to reboot the system.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Windows Figure 22 StorNext Installation Window: Install StorNext 3 Click Install StorNext to begin installation. The StorNext setup wizard appears (figure 23). Figure 23 SNFS Setup: Welcome 4 Click Next to continue. The License Agreement window appears (figure 24). StorNext 3.1.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Windows Figure 24 SNFS Setup: EndUser License Agreement 5 Click the option to accept the license agreement, and then click Next to continue. The Customer Information window appears (figure 25). Figure 25 SNFS Setup: Customer Information 6 Type your name and the name of your company or organization in the boxes, and then click Next to continue. The Choose Setup Type window appears, (figure 26). StorNext 3.1.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Windows Figure 26 SNFS Setup: Choose Setup Type 7 Click an installation option: • Typical: (Recommended) Installs the StorNext client software and help files in the default location (C:\Program Files\StorNext). • Custom: Lets you choose which components to install and specify an installation location. When ready, click Next. • Complete: Same as a typical installation. The Ready to Install window appears (figure 27).
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Windows 8 Click Install to continue. Wait while the setup wizard installs StorNext. When installation is complete, the Finish window appears (figure 28). Figure 28 SNFS Setup: Finish 9 Click Finish to close the setup wizard. 10 On the StorNext Installation window, click Exit. You are prompted to reboot the system. 11 Click Yes to reboot. You can now configure StorNext File System.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Windows Figure 29 StorNext Installation Window: Configure StorNext 3 Click Configure StorNext. The StorNext Configuration window appears (figure 30). Figure 30 StorNext Configuration Window 4 Click Import/Export Client Settings. The Import/Export Client Configuration window appears (figure 31). StorNext 3.1.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Windows Figure 31 Import/Export Client Configuration Window 5 Under Import, click Browse. Locate the client configuration (*.reg) file to import, and then click Open.
Chapter 4 4 Configuring StorNext This chapter describes how to configure StorNext after installation. To configure StorNext, enter license information and create one or more file systems. In addition, on metadata controllers (MDCs) running StorNext Storage Manager, you can add storage devices and media, create storage policies, and set up e-mail notifications. In addition, Linux or Windows SAN clients can be configured as a distributed LAN client or a distributed LAN server.
Chapter 4 Configuring StorNext StorNext GUI StorNext GUI The StorNext GUI provides access to StorNext features and displays system status information. Use the StorNext GUI to create and work with file systems. In addition, on metadata controllers running Storage Manager, you can use the StorNext GUI to configure storage devices and media, and to set up storage policies. Note: Accessing the StorNext GUI 4 The StorNext GUI is available only for MDCs running on Unix or Linux.
Chapter 4 Configuring StorNext StorNext GUI Figure 32 StorNext Home Page: File System and Storage Manager Figure 33 StorNext Home Page: File System Only StorNext 3.1.
Chapter 4 Configuring StorNext Configuration Wizard Configuration Wizard The first time you log onto the StorNext GUI, the Configuration Wizard appears. The wizard guides you step-by-step through the process of configuring StorNext. The appearance of the wizard differs depending on if both Storage Manager and File System are installed on the MDC, or if File System only is installed. The Configuration Wizard for an MDC running File System and Storage Manager is shown in figure 34.
Chapter 4 Configuring StorNext Configuration Wizard Figure 35 StorNext Configuration Wizard: File System Only Displaying the Configuration Wizard 4 The Configuration Wizard appears each time you log on to StorNext until all steps of the wizard are completed. You can also control the wizard manually: • To set the Configuration Wizard to not appear the next time you log in, select the Don’t Show CW Again check box.
Chapter 4 Configuring StorNext Configuration Wizard The following sections describe each step of the Configuration Wizard. Each step consists of a separate wizard that guides you through a task. To complete a task, follow the onscreen instructions. To see more detailed instructions for completing a task, refer to the indicated section in the StorNext User’s Guide. Note: Using the Configuration Wizard to configure StorNext is optional.
Chapter 4 Configuring StorNext Configuration Wizard To display the Add New File System Wizard at any time, on the Config menu, click Add File System. For more information about adding file systems, see Chapter 6, “Managing the File System,” in the StorNext User’s Guide. 4 Step 3: Add Library The Add Library wizard guides you through the steps of adding and configuring a tape library or vault.
Chapter 4 Configuring StorNext Configuration Wizard 4 Step 6: Add Storage Disks The Add Storage Disk wizard guides you through the steps of adding external storage disks to a managed system. The wizard lets you specify which file systems to define as storage disks. Once defined, storage disks can be used as a target media type when creating storage policies. To display the Add Storage Disk Wizard at any time, on the Config menu, click Add Storage Disk.
Chapter 4 Configuring StorNext Configuring a Distributed LAN Client Server Configuring a Distributed LAN Client Server Traditional StorNext SAN clients access data disks using a high throughput, low-latency fibre channel connection. In addition, using the distributed LAN client and server feature, StorNext clients can access data disks over a network instead of directly accessing disks. A StorNext client running on Linux or Windows can be configured as a distributed LAN client or a distributed LAN server.
Chapter 4 Configuring StorNext Configuring a Distributed LAN Client Server Configuring a Distributed LAN Client on Linux 4 To configure a StorNext client as a distributed LAN client, edit mount options in the /etc/fstab file. 1 Stop the StorNext client. At the command prompt, type: /etc/init.d/cvfs stop 2 Configure the client to mount a file system as a distributed LAN client.
Chapter 4 Configuring StorNext Configuring a Distributed LAN Client Server Figure 36 sndpscfg Configuration Utility 5 Edit the default distributed LAN server configuration: • (Required) Uncomment (delete the # next to) the line that corresponds to the network interface used by the distributed LAN server when connecting to distributed LAN clients. (For best performance, do not choose the network used for metadata.
Chapter 4 Configuring StorNext Configuring a Distributed LAN Client Server Table 12 Distributed LAN Server Parameters Field / Button Description tcp_window_size_kb The TCP window size (in KB) used by the distributed LAN server. (Default: 64) transfer_buffer_size_kb The transfer buffer size (in KB) used by the distributed LAN server. A larger buffer may increase performance for larger files. (Default: 256) transfer_buffer_count The number of transfer buffers used by the distributed LAN server.
Chapter 4 Configuring StorNext Configuring a Distributed LAN Client Server 4 Creating an Override Configuration By default, the settings specified in the dpserver configuration file are used for all file systems mounted by the distributed LAN server. To use different settings for a file system, create an override configuration file for that file system. At the command prompt, type: ./sndpscfg -E where is the name of the file system to which the override settings apply.
Chapter 4 Configuring StorNext Windows Configuration Utilities Windows Configuration Utilities To configure StorNext File System or the StorNext client software on Windows operating systems, use the Windows configuration utilities. The configuration utilities let you set up a Windows-based metadata controller, configure a StorNext client, and work with StorNext file systems. To run a configuration utility, on the Windows Start menu, click All Programs > StorNext File System, and then click the utility.
Chapter 4 Configuring StorNext Windows Configuration Utilities Client Configuration 4 The Client Configuration utility lets you view and modify properties for the StorNext client software. Use the utility to add name servers, map file systems to drives, and configure a distributed LAN server or a distributed LAN client. To run the Client Configuration utility, on the Windows Start menu, click All Programs > StorNext File System > Client Configuration.
Chapter 4 Configuring StorNext Windows Configuration Utilities Note: You must disable the Windows Recycle Bin for each local drive that is mapped to a file system. Right click the Recycle Bin icon and click Properties. On the Global tab, click Configure Drives Independently. On the appropriate Local Disk tab, select the Do not move files to the Recycle Bin check box, and then click OK. Figure 37 Client Configuration: Drive Mappings Table 14 Client Configuration: Drive Mappings StorNext 3.1.
Chapter 4 Configuring StorNext Windows Configuration Utilities Field / Button Description Select Drive - Drive Select the mapped drive to configure on the other tabs of the Client Configuration utility. Unmap Drive Select a drive to unmap. Unmap Click to unmap the selected drive. Display File System Critical Events to Desk Top Select to display a notification dialog box if a critical event occurs. Disable SNFS ONC Portmapper Process Select to disable the SNFS portmapper service.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 38 Client Configuration: FS Name Servers Table 15 Client Configuration: FS Name Servers Field / Button Description Add Click to add the name server entered in the box. Remove Click to remove the name server selected in the list. Move Up Click to move the selected name server up in the list. Move Down Click to move the selected name server down in the list.
Chapter 4 Configuring StorNext Windows Configuration Utilities user to a user ID and group on the SAN. (Changes are applied when you click Apply. You do not need to restart the client system.) Use the Authentication tab (figure 39) to specify an authentication method. Table 16 describes the fields on the Authentication tab. Note: If your StorNext installation is Windows-only and you do not plan to add non-Windows clients, you do not need to specify an authentication method.
Chapter 4 Configuring StorNext Windows Configuration Utilities Field / Button Description Use Active Directory Click to use LDAP to obtain the Active Directory/Services for UNIX (SFU) mapping for the selected user. (The client system must be part of an Active Directory domain.) User Name Type the user name that should be sent to the authentication server. (PCNFSD and NIS methods only.) PCNFSD Click to use a PCNFSD server for authentication. PCNFSD - Server Type the IP address of the PCNFSD server.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 40 Client Configuration: Mount Options Note: Selecting the Read Only check box has no effect. This feature has been disabled. Syslog Level 4 The system log level determines the types of messages the file system records in the system event log. Use the Syslog Level tab (figure 41) to specify the system log level. The None level setting provides the least amount of logging and the Debug level provides the most.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 41 Client Configuration: Syslog Level Cache Parameters 4 The Cache Parameters tab (figure 42) displays performance values that control how many file system lookup names are kept in memory. Caution: StorNext 3.1.3 Installation Guide Changing the values on the Cache Parameters tab can affect system performance and stability. Do not change cache parameters unless instructed to do so by the Quantum Technical Assistance Center.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 42 Client Configuration: Cache Parameters Distributed LAN 4 A StorNext client running on Windows can be configured as a distributed LAN client or a distributed LAN server. (This is a licensed feature.) • Distributed LAN Server: A distributed LAN server has direct access to data disks (using fibre channel) and makes the shared storage pool available to distributed LAN clients over a network.
Chapter 4 Configuring StorNext Windows Configuration Utilities Use the Distributed LAN tab (figure 43) to configure a distributed LAN server or a distributed LAN client. Table 17 describes the fields on the Distributed LAN tab. Figure 43 Client Configuration: Distributed LAN Table 17 Client Configuration: Distributed LAN Field / Button Description Enable Client Select to configure the StorNext client as a distributed LAN client.
Chapter 4 Configuring StorNext Windows Configuration Utilities Disk Device Labeler 4 Field / Button Description Number of Transfer Buffers Type the number of transfer buffers used by the distributed LAN server. (Default: 16) Transfer Buffer Size (kb) Type the transfer buffer size (in KB) used by the distributed LAN server. A larger buffer may increase performance for larger files. (Default: 256) TCP Window Size (kb) Type the TCP window size (in KB) used by the distributed LAN server.
Chapter 4 Configuring StorNext Windows Configuration Utilities Caution: Modifying the label of a system disk may render the system inoperable and require you to repair the volume. Only label disk devices that are intended for use with the StorNext File System SAN. To run the Disk Device Labeler utility, on the Windows Start menu, click All Programs > StorNext File System > Disk Device Labeler. The Disk Labeler window (figure 44) appears.
Chapter 4 Configuring StorNext Windows Configuration Utilities 4 Labeling Disks When you select one or more disks and click Label, a confirmation screen appears asking if you are sure you want to proceed. Click OK to continue. The Disk Labeler dialog box appears (figure 45). Table 18 describes the fields on the on the Disk Labeler dialog box. Figure 45 Disk Labeler Dialog Box Table 18 Disk Labeler Dialog Box StorNext 3.1.
Chapter 4 Configuring StorNext Windows Configuration Utilities License Identifier 4 Use the License Identifier utility to display the host license identifier. The host license identifier is required to obtain a permanent license for StorNext. To run the License Identifier utility, on the Windows Start menu, click All Programs > StorNext File System > License Identifier. A dialog box displays the host license identifier. Record this information. To obtain a license, use the Configuration Wizard.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 46 Simple File System Configuration Table 19 Simple File System Configuration StorNext 3.1.3 Installation Guide Field / Button Description Clear Selections Click to deselect all devices in the list. Select All Click to select all devices in the list. File System Name Type the name of the file system. This is the name used by clients when establishing a mount point for the file system.
Chapter 4 Configuring StorNext Windows Configuration Utilities Start File System Services 4 The Start File System Services utility starts all StorNext services on an MDC or StorNext client. The StorNext services must be running on the MDC for file systems to be active and available. In addition, the StorNext services must be running to use the StorNext configuration utilities and to mount file systems using the client software.
Chapter 4 Configuring StorNext Windows Configuration Utilities Check (Read-Only) a File System 4 The Check (Read-Only) a File System utility allows you to check a StorNext file system for metadata corruption (due to a system crash, bad disk, or other failure). Run the utility on an MDC that contains the file system you want to check. To check a file system, on the Windows Start menu, click All Programs > StorNext File System > Check (Read-Only) a File System.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 47 File System Startup List Table 20 File System Startup List StorNext 3.1.3 Installation Guide Field / Button Description New Click to add a file system to the FSM services list. Type the name of the file system and click OK. Delete Click to remove the selected file system from the FSM services list. Host Name (Optional) Type the name of the host on which the file system is running.
Chapter 4 Configuring StorNext Windows Configuration Utilities Re-initialize a File System 4 The Re-initialize a File System utility allows you to initialize an existing file system. Initializing a file system prepares it for use. Caution: Re-initializing a file system will destroy all data on the file system. To initialize a file system, on the Windows Start menu, click All Programs > StorNext File System > Re-initialize a File System.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 48 Server Administration On the Administrator window, do one of the following: • To connect to an MDC, click File > Connect to. Type the host name and click OK. File systems on the server appear in the left pane. • To start a file system, click it in the left pane. Click File > Start File System, and then click Start. • To activate a file system, click it in the left pane. Click File > Activate File System, and then click Activate.
Chapter 4 Configuring StorNext Windows Configuration Utilities 4 File System Properties To view or change file system properties, click a file system in the left pane, and then click the file system name in the right pane. The File System Properties dialog box appears (figure 49). Table 21 describes the fields on the File System Properties dialog box. After making changes, click OK. (Not all fields can be modified on this dialog box.
Chapter 4 Configuring StorNext Windows Configuration Utilities Field / Button Description Distributed Locking Indicates if distributed locking is enabled or disabled. Windows Security Indicates if Windows security is enabled or disabled. Global Superuser Indicates if the global superuse is enabled or disabled. Quality-of-Service Indicates if Quality of Service is enabled or disabled. Usage Displays the amount of used and free storage space in the file system.
Chapter 4 Configuring StorNext Windows Configuration Utilities Table 22 Server Administration: Stripe Group Properties Field / Button Description Stripe Group Name The name of the stripe group. Status Shows the current status of the stripe group. Click Up to make the stripe group active or click Down to make the strip group inactive. Stripe Breadth The number of file system blocks to write before switching to the next disk in the stripe group. Stripe Depth The number of disks in the stripe group.
Chapter 4 Configuring StorNext Windows Configuration Utilities Table 23 describes the fields on the User Quotas and Group Quotas tabs. After making changes, click OK. (Not all fields can be modified on this dialog box.) Figure 51 Server Administration: Quota Properties Table 23 Server Administration: Quota Properties StorNext 3.1.3 Installation Guide Field / Button Description User Name / Group Name Type the name of the user or group to set a quota for.
Chapter 4 Configuring StorNext Windows Configuration Utilities Field / Button Description Time Limit Specify the amount of time it takes for the soft limit to turn into a hard limit. Get Quota Click to get quota settings for the specified user or group. Set Quota Click to set a quota for the specified user or group using the current settings. Quality of Service Information 4 To view Quality of Service (QOS) information for a file system, expand a file system in the left pane, and then click QOS.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 52 Configuration Administrator On the Configuration Administrator window, do one of the following: • Click New to create a new configuration file. • Click Modify to edit an existing configuration file. Browse for the configuration (*.cfg) file and click Open. • Click Exit to close the Configuration Administrator window.
Chapter 4 Configuring StorNext Windows Configuration Utilities 4 Global Settings Use the Global Settings tab (figure 53) to specify general file system properties. Table 24 describes the fields on the Global Settings tab. Figure 53 Server Configuration: Global Settings Table 24 Server Configuration: Global Settings StorNext 3.1.3 Installation Guide Field / Button Description Global Superuser (Optional) Select to allow a user with superuser privileges to have global access rights on the file system.
Chapter 4 Configuring StorNext Windows Configuration Utilities StorNext 3.1.3 Installation Guide Field / Button Description Quotas (Optional) Select to enforce file system quotas and track storage usage for individual users and groups. Cluster File Locking (Optional) Select to send a warning when a user attempts to access a file that is locked or already in use. File Size Dynamic Expansion - Minimum Type the minimum number (in blocks) to allocate when a file is created.
Chapter 4 Configuring StorNext Windows Configuration Utilities Field / Button Description Allocation Strategy Select the method of allocation for new disk blocks: • Round: Alternate between similar stripe groups. (Default) • Fill: Fill the first stripe group before using the second. • Balance: Use the stripe group with the most free space. “Nobody” UID Type the Windows user ID to use when no user ID can be found using Active Directory.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 54 Server Configuration: Disk Types On the Disk Types tab, do one of the following: • To add a new disk type, click New. • To modify a disk type, select the disk type in the list and click Edit. • To delete a disk type, select it in the list and click Delete. When you add or modify a disk type, the Enter New Disk Type dialog box appears (figure 55). Table 25 describes the fields on the Enter New Disk Type dialog box. Note: StorNext 3.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 55 Server Configuration: Enter New Disk Type Table 25 Server Configuration: Enter New Disk Type Field / Button Description Disk Type Type a descriptive name for the disk. Sectors Type the number of physical sectors on the disk. Sector Size Type the size of sectors on the disk. OK Click to create the new disk type with the specified properties. Cancel Click to close the Enter New Disk Type dialog box without saving changes.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 56 Server Configuration: Disk Definitions Table 26 Server Configuration: Disk Definitions StorNext 3.1.3 Installation Guide Field / Button Description Disks Available - New Click to create a new disk definition. Type a name for the disk and click OK. Disks Available Delete Click to delete the selected disk definition. Status: Up Select to enable the selected disk definition.
Chapter 4 Configuring StorNext Windows Configuration Utilities Field / Button Description Device Names - Delete Click to delete the selected device name. Stripe Groups 4 Use the Stripe Groups tab (figure 57) to define stripe groups. (A stripe group is a logical storage unit consisting of one or more disk drives.) Table 27 describes the fields on the Stripe Groups tab. Figure 57 Server Configuration: Stripe Groups StorNext 3.1.
Chapter 4 Configuring StorNext Windows Configuration Utilities Table 27 Server Configuration: Stripe Groups Field / Button Description Stripe Groups Available - New Click to create a new stripe group. Type a name for the stripe group and click OK. Stripe Groups Available - Delete Click to delete the selected stripe group. Status: Up Select to enable the selected stripe group. When enabled, the stripe group is available to the configured file system for I/O.
Chapter 4 Configuring StorNext Windows Configuration Utilities Field / Button Description RtTokenTimeout Type the number of seconds to wait for clients to respond to a token callback. Rtmb Type the number of MBs per second available to real-time applications using the Quality of Service (QOS) API. RtmbReserve Type the minimum number of MBs per second reserved for non-real-time applications. Modify Drive List Click to add or remove disks for the selected stripe group.
Appendix A Uninstalling StorNext A If you no longer need to use StorNext, uninstall the software to remove it from your system. To uninstall StorNext, use the appropriate method for your operating system: • Uninstalling StorNext on Unix and Linux on page 108 • Uninstalling StorNext on Windows on page 111 Uninstalling StorNext on Unix and Linux To uninstall StorNext on a metadata controller (MDC), use the installation script (see Uninstalling SNSM and SNFS on page 109).
Appendix A Uninstalling StorNext Uninstalling StorNext on Unix and Linux Uninstalling SNSM and SNFS 1 To uninstall StorNext File System and Storage Manager on an MDC running Unix or Linux, run the installation script with the -remove option. To launch the script, use the correct StorNext installation CD for your operating system. 1 Log on to the MDC as root. 2 Mount the StorNext installation CD and change to the CD root directory.
Appendix A Uninstalling StorNext Uninstalling StorNext on Unix and Linux Figure 58 StorNext Remove Main Menu 6 Type 2 and press . 7 After the uninstall process is complete, type 4 and press to exit the installation script. Uninstalling the StorNext Client Software 1 To uninstall the StorNext client software, unmount all file systems and stop StorNext software. Then remove the client software package using the appropriate command for your operating system.
Appendix A Uninstalling StorNext Uninstalling StorNext on Windows swremove –x mount_all_filesystems=false snfsclient • IBM AIX: installp –u where is the name of the client software package that was installed. • SGI IRIX: Inst remove cv_base remove cv_clnt go Note: If you do not know the package name, you can download the client software for your operating system and check the package name (see Downloading the StorNext Client Software on page 39).
Appendix B StorNext Administration Tasks B Use the following information to perform specific file system configuration tasks that do not apply to a typical StorNext set up. Sharing a Library Between Applications If two or more software applications (on one or multiple machines), are configured to use the same library, then you must use the following procedure to enable the library to be shared and to prevent media being overwritten when these applications are used.
Appendix B StorNext Administration Tasks Sharing a Library Between Applications 1 When you match hardware devices to their correct slots on the Matched Devices With Slots screen (you will see this screen during the execution of Step 4 of the Configuration Wizard, Add Tape Drive), only configure the tape drives that your software application will use. You do not need to configure all tape drives listed as part of the library.
Appendix B StorNext Administration Tasks Manually Modifying Storage Manager Configuration Manually Modifying Storage Manager Configuration StorNext employs global parameters that define the Storage Manager configuration. Although the default values in these files are sufficient for most installations, you can edit the files to customize the StorNext software for your specific installation.
Appendix B StorNext Administration Tasks Manually Modifying Storage Manager Configuration filesize.config Configuration File 2 The filesize.
Appendix B StorNext Administration Tasks Connecting to a StorNext Network Using Xsan 1.4.2 Connecting to a StorNext Network Using Xsan 1.4.2 If you are using Apple Xsan 1.4.2, follow the procedure below to connect to a StorNext network. The procedure consists of mounting the StorNext file system onto the OSx computer, and then creating an automount.plist to enable mounting the StorNext file system whenever the Macintosh is rebooted.
Appendix B StorNext Administration Tasks Connecting to a StorNext Network Using Xsan 1.4.2 On Windows: the fsnamerservers file is located at \%cvfsroot%\config\ (where %cvfsroot% is the directory where the StorNext software is installed). This directory is usually located in C:\Program Files\Stornext\config\. 5 Create a new plaintext file called fsnameservers in the /Library/ FileSystems/Xsan/config/ directory. Populate the file with the content of the StorNext file you printed in the previous step.
Appendix B StorNext Administration Tasks Connecting to a StorNext Network Using Xsan 1.4.2 sudo mount -t acfs fsname /Volumes/fsname (where is the name of the file system). The SNFS filesystem should now be mounted on the OS X computer. Creating the automount.plist File 2 In order to mount the StorNext file system whenever the Macintosh client is rebooted, configure the automount.plist file. Xsan 1.4.2 uses the automount.plist file to mount SAN volumes.
Appendix B StorNext Administration Tasks Connecting to a StorNext Network Using Xsan 2 Connecting to a StorNext Network Using Xsan 2 If you are using Apple Xsan 2.2 or earlier, follow the procedure below to connect to a StorNext network. The procedure consists of mounting the StorNext file system onto the Mac OS X computer, and then creating an automount.plist to enable mounting the StorNext file system whenever the Macintosh is rebooted. Do not use the procedure if you are using Xsan 1.4.
Appendix B StorNext Administration Tasks Connecting to a StorNext Network Using Xsan 2 Note: Items in red indicate data you should enter which applies to your configuration. Do not enter the literal red text shown in the template. For example, for My IP Address you would enter the netmask in the format X.Y.Z.0/24 (for example, 10.65.182.0/24) not the words “My IP Address.”
Appendix B StorNext Administration Tasks Connecting to a StorNext Network Using Xsan 2 Note: Items in red indicate data you should enter which applies to your configuration. Do not enter the red text shown in the template. For example, for file system you would enter the name of your file system, not “file system.” PAGE 139Appendix B StorNext Administration Tasks Viewing a Fibre Channel Device 8 Run the following in Terminal to update Xsan with the new file system information: launchctl unload /System/Library/LaunchDaemons/com.apple.xsan.plist launchctl load /System/Library/LaunchDaemons/com.apple.xsan.plist Note: Unload will fail if plist is not loaded. If the file system does not mount automatically, manually mount the StorNext file system.
Appendix B StorNext Administration Tasks StorNext Log Rolling Administration StorNext Log Rolling Administration Use the following procedures to configure StorNext log rolling options. Changing Log Rolling Times 2 Use this procedure to change the frequency of rolling the StorNext logs. This process requires that you edit the tldm crontab to set log times. Use this procedure to edit tdlm crontab. 1 Log on as root. 2 Edit the tdlm crontab and update the sn_log_update script.
Appendix B StorNext Administration Tasks Avoiding Poor System Performance Avoiding Poor System Performance Most systems run administrator scripts to rebuild namespace databases and/or to remove certain files. Unfortunately, running these scripts can degrade StorNext performance. It is recommended that you review administrator scripts to determine if they may adversely affect your StorNext installation and its performance.
Appendix C StorNext Files C StorNext creates a series of files that are used and modified to configure a file system. This section includes an expanded example.cfg file and a listing of the most commonly used StorNext files with descriptions and locations for each. The example.cfg File The following is listing of the configuration file created by StorNext. This file is modified during the configuration of a file system. The location for this file is: /usr/cvfs/examples/example.
Appendix C StorNext Files The example.
Appendix C StorNext Files The example.
Appendix C StorNext Files The example.cfg File Status UP Type VideoDrive [Disk CvfsDisk3] Status UP Type VideoDrive [Disk CvfsDisk4] Status UP Type VideoDrive [Disk CvfsDisk5] Status UP Type VideoDrive [Disk CvfsDisk6] Status UP Type VideoDrive [Disk CvfsDisk7] Status UP Type VideoDrive [Disk CvfsDisk8] Status UP Type VideoDrive [Disk CvfsDisk9] Status UP Type VideoDrive [Disk CvfsDisk10] Status UP Type AudioDrive StorNext 3.1.
Appendix C StorNext Files The example.cfg File [Disk CvfsDisk11] Status UP Type AudioDrive [Disk CvfsDisk12] Status UP Type AudioDrive [Disk CvfsDisk13] Status UP Type AudioDrive [Disk CvfsDisk14] Status UP Type DataDrive [Disk CvfsDisk15] Status UP Type DataDrive [Disk CvfsDisk16] Status UP Type DataDrive [Disk CvfsDisk17] Status UP Type DataDrive # ************************************************************************* # A stripe section for defining stripe groups.
Appendix C StorNext Files The example.
Appendix C StorNext Files The example.
Appendix C StorNext Files Commonly Used SNFS Files Commonly Used SNFS Files The following is a list of commonly used SNFS files and provides the name and location of the files installed during a SNFS installation. Each entry also includes a brief description of the file’s utility in SNFS functionality. • /usr/cvfs/bin/ cvadmin — Allows you to view and modify the active SNFS system(s). cvaffinity — Associates a stripe group with a media type. cvcp — A high-speed file copy utility.
Appendix C StorNext Files Commonly Used SNFS Files fsnameservers — Identifies the SNFS name service coordinators. license.dat — The SNFS license file. • /usr/cvfs/data//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.
Appendix C StorNext Files Commonly Used SNFS Files cvlabels.example cvpaths.example example.cfg fsmlist.example fsnameservers.example fsports.example fsroutes.example • /usr/cvfs/lib/ cvextapi.a — A SNFS API library. • libcvfsdmapi.a — A SNFS DMAPI library. • /usr/cvfs/src/ cvapi.c — A sample API application. StorNext 3.1.
Appendix D D Quality of Service Guide This appendix describes how to configure and use the StorNext File System (SNFS) Quality of Service (QOS) feature. QOS allows real-time applications to reserve some amount of bandwidth on the storage system. This is known as real-time I/O (RTIO). SNFS gates (that is, throttles) nonreal-time applications so their I/O accesses do not interfere with the realtime application.
Appendix D Quality of Service Guide Overview Overview QOS is stripe-group centric; all configuration and operations act on a specific stripe group. This allows stripe groups with differing access characteristics to use different real-time settings. When a client requests a certain amount of real-time I/O, the FSM informs all connected clients of the amount remaining and available for non-real-time I/O accesses. This information is encapsulated in a token.
Appendix D Quality of Service Guide Configuration Configuration The primary configuration for QOS is in the FSM configuration file. No client configuration is required, although there is a QOS tuning parameter that can be specified when the file system is mounted. Unit of I/O 4 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.
Appendix D Quality of Service Guide Configuration ios_sec = mb_sec / (stripe_breadth * stripe_depth *fs_blocksize) For example, with a file system blocksize of 4k, a stripe_breadth of 384, and a stripe_depth of four, the equivalent number of I/Os/sec for each wellformed I/O would be 216 Mb/sec / (384 * 4 * 4k). This is equivalent to 221184 k/sec / 6144k= 36 I/O/sec.
Appendix D Quality of Service Guide Configuration Name Description Default RtiosReserve Amount of reserve in I/Os/sec from the maximum allowed for non-real-time I/Os. Must be greater than the equivalent to 1MB/sec or the amount that can be transferred to a single stripe line. Equivalent to 1MB/sec RtmbReserve Amount to reserve in MB/sec from the maximum allowed for non-real-time I/O. Must be greater than 1. 1MB/sec RtTokenTimeout Time in seconds to wait for clients to respond to a token callback.
Appendix D Quality of Service Guide Configuration Note: It is important to realize that the rtios and rtmb settings refer to the total amount of sustained bandwidth available on the disk subsystem. Any I/O, either real-time or non-real-time, will ultimately be deducted from this overall limit. The calculations of available real-time and non-real-time are discussed later. Specifying rtmb in the FSM configuration file is only recommended if all I/Os are well formed (that is, a full stripe width).
Appendix D Quality of Service Guide Configuration Token Timeouts 4 The RtTokenTimeout parameter controls the amount of time the FSM waits for clients to respond to callbacks. In most normal SANs, the default twosecond 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.
Appendix D Quality of Service Guide Real-time I/O Real-time I/O A process requests real-time (ungated) I/O by using the SNFS External API SetRtio call (F_SETRIO ioctl). A library function is included in the External API sample source code that provides all the required crossplatform 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.
Appendix D Quality of Service Guide Real-time I/O SetRtio 4 Initially, all stripe groups in the file system are in non-real-time mode. Clients make their requests directly to the I/O subsystem without any gating. In our example, the process requires 186 MB/sec and the system designers know there will never be a need to support more than one stream at 186 MB/sec. The SetRtio request has a number of flags and parameters to control its operation. These are all documented in the external_api.
Appendix D Quality of Service Guide Real-time I/O This automatic clearing of real-time I/O is carried out in the context of the process that is closing the file. If the FSM cannot be reached for some reason, the request is enqueued on a daemon and the process closing the file is allowed to continue. In the background, the daemon attempts to inform the FSM that the real-time I/O has been released. Different processes can share the same file in real-time and non-real-time mode.
Appendix D Quality of Service Guide Callbacks Calculating Available RTIO 4 When the FSM receives a request for rtio, it takes the amount reserved into consideration. The reserve amount functions as a soft limit beyond which the FSM will not traipse. The calculation for rtio is as follows: avail_rtio = rtio_limit - rtio_current avail_rtio -= rtio_reserve All internal calculations are done in terms of I/O/sec.
Appendix D Quality of Service Guide Callbacks Figure 60 Callback Flow for Initial RTIO Request In the above diagram, a process on client A requests some amount of RTIO in Step 1. Since this is the first request, the FSM issues callbacks to all connected clients (Steps 2-5) informing them that the stripe group is now in real-time mode. The clients respond to the FSM in Steps 6-9. After all the clients have responded, the FSM responds to the original requesting client in Step 10.
Appendix D Quality of Service Guide Callbacks Callback Failures 4 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.
Appendix D Quality of Service Guide Callbacks real-time mode after the original caller has received an error code. Both the FSM and clients log their actions extensively to syslog, so if this situation arises it can be detected. In Figure 61, if the stripe group were already in real-time mode the FSM would only send out callbacks to those clients that already have tokens. Once all clients responded to the token callbacks, the stripe group would be back in its original state.
Appendix D Quality of Service Guide Callbacks Figure 62 Non-Real-time Token Adjustments In Figure 62, assume the stripe group is already in real-time mode as a result of an rtio request from client A. Clients B and D are doing non-realtime 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.
Appendix D Quality of Service Guide Callbacks FSM Failures 4 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. Non-real-time I/O will be pended until the FSM is re-connected.
Appendix D Quality of Service Guide Monitoring to all clients that have tokens informing them of the new amount of nonreal-time I/O available. Client Token Releases 4 While it is not a failure case, the handling of a client token release is exactly the same as in the case where the client disconnected. All clients retain non-real-time tokens for a fixed amount of time. The default is 60 seconds. This can be controlled via the nrtiotokentimeout mount option. After the specified period of inactivity (i.e.
Appendix D Quality of Service Guide Sharing Disk Resources Performance counters are not enabled by default in the client. To enable them, you must execute cvdb -P ; this toggles the state of collection. To turn off the perfmon counters, do another cvdb -P. To re-enable, again do cvdb -P, and so on. To clear all client counters to zero, disable, then reenable the counters with cvdb -P.
