Installation Guide Installation Guide Installation Guide Installation Guide StorNext® 3.
StorNext 3.5 Installation Guide, 6-00360-14 Rev B, October 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 - 2008 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 Operating System Requirements............................................................ 19 Hardware Requirements ......................................................................... 19 LAN Requirements................................................................................... 20 Getting Ready to Install .................................................................................. 20 Configuring Storage Devices ..................................................................
Contents Using the Configuration Wizard ............................................................ 61 Configuring a Distributed LAN Client Server ............................................ 65 Configuring a Distributed LAN Client on Linux................................. 66 Configuring a Distributed LAN Server on Linux ................................ 66 Windows Configuration Utilities .................................................................. 70 Client Configuration.............................
Contents Viewing a Fibre Channel Device ................................................................. 124 StorNext Log Rolling Administration......................................................... 125 Changing Log Rolling Times ................................................................ 125 Log Rolling Options ............................................................................... 125 Avoiding Poor System Performance...........................................................
Figures StorNext 3.5 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.5 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 ................ 50 Figure 22 StorNext Installation Window: Install StorNext.................... 51 Figure 23 SNFS Setup: Welcome ...............
Figures StorNext 3.5 Installation Guide Figure 47 Server Administration: Stripe Group Properties ................... 93 Figure 48 Server Administration: Quota Properties ............................... 95 Figure 49 Configuration Administrator ................................................... 97 Figure 50 Server Configuration: Global Settings..................................... 98 Figure 51 Server Configuration: Disk Types..........................................
Tables StorNext 3.5 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.5 Installation Guide Table 18 Client Configuration: Advanced Cache Options................... 80 Table 19 Disk Labeler Dialog Box ............................................................ 84 Table 20 Simple File System Configuration ........................................... 86 Table 21 File System Startup List ............................................................. 89 Table 22 Server Administration: File System 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.5 Installation Guide Document No. Document Title Document Description 6-01658-05 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-22 StorNext 3.5 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 Hardware Requirements 1 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 Table 2 Storage Manager Hardware Requirements File Systems RAM Disk Space 1–4* 2 GB 5–8** 4 GB • For application binaries, log files, and documentation: up to 30GB (depending on system activity) • For support directories: 3 GB per million files stored† • For metadata: 25GB minimum * Two CPUs recommended for best performance. ** Two CPUs required for best performance.
Chapter 1 Installing StorNext File System and Storage Manager Storage Manager System Requirements Note: LAN Requirements 1 You can run the pre-installation script to help determine the estimated size of and optimal location for StorNext support directories. For more information, see Pre-Installation Script on page 8.
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.
Chapter 1 Installing StorNext File System and Storage Manager StorNext Installation Script Note: When you mount a CD in a Red Hat 4 or 5 system, CDs are mounted by default with a noexec (non-executable) option which prevents you from proceeding with the installation. For Red Hat users only, before proceeding you must remount the CD by typing mount -o remount, exec ... 3 List the installation directories on the CD.
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 Hardware Requirements 2 The operating systems, releases and kernels, and hardware platforms supported by StorNext SNFS are presented in Table 7.
Chapter 2 Installing StorNext File System Getting Ready to Install Table 8 File System Hardware Requirements File Systems RAM Disk Space 1–4* 2 GB 2 GB 5–8** 4 GB 4 GB * Two CPUs recommended for best performance. ** Two CPUs required for best performance.
Chapter 2 Installing StorNext File System Getting Ready to Install • Correctly configure all storage devices (see Configuring Storage Devices on page 21). • 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 on page 21). • (Linux only) Install the kernel source code (see Installing the Linux Kernel Source Code on page 23).
Chapter 2 Installing StorNext File System Getting Ready to Install patches or updates (for both MDC and client) as indicated in the notes for Table 9. Note: Table 9 Required Disk LUN Labels StorNext 3.5 Installation Guide After labeling a disk LUN, you must reboot systems running Solaris before they can access the disk LUN.
Chapter 2 Installing StorNext File System Installing StorNext File System on Linux or Unix Operating System a. b. c. d. 2 Label for LUNs 1–2 TB Label for LUNs > 2 TB 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 2 Installing StorNext File System Installing StorNext File System on Linux or Unix 2 Mount the StorNext installation CD and change to the CD root directory. Note: When you mount a CD in a Red Hat 4 or 5 system, CDs are mounted by default with a noexec (non-executable) option which prevents you from proceeding with the installation. For Red Hat users only, before proceeding you must remount the CD by typing mount -o remount, exec ... 3 List the installation directories on the CD.
Chapter 2 Installing StorNext File System Installing StorNext File System on Linux or Unix 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). 2 Install StorNext using the installation options specified on the Configuration Menu (see Performing an Installation Operation on page 26).
Chapter 2 Installing StorNext File System Installing StorNext File System on Linux or Unix 1 On the Configuration Menu, type the number that corresponds to the directory location you want to customize (1–6), and then press . A list of available local file systems is shown. 2 To change the file system where the directory is located, type the name of the file system and press . 3 To confirm the change, type yes and press . To customize additional directory locations, repeat steps 1–3.
Chapter 2 Installing StorNext File System Installing StorNext File System on Windows 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 Removing a Previous Version of StorNext 2 • Manually configuring the TCP/IP information, which disables DHCP. You should use this method if any static IP addresses have been configured. • Editing the Windows registry to disable automatic IP address configuration but not disable DHCP. To use this method, follow the procedure outlined in Microsoft article 220874 available here: http:// support.microsoft.com/kb/220874.
Chapter 2 Installing StorNext File System Installing StorNext File System on Windows 4 Note the name and location of the saved configuration file, and then click OK. 5 If prompted, click Yes to continue, and then click OK to finish the removal. 6 When the removal is complete, click Yes to reboot the system. Note: 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).
Chapter 2 Installing StorNext File System Installing StorNext File System on Windows Figure 9 StorNext Installation Window: Install StorNext 3 Click Install StorNext to begin installation. The StorNext setup wizard appears (figure 10). Figure 10 SNFS Setup: Welcome 4 Click Next to continue. The License Agreement window appears (figure 11). StorNext 3.
Chapter 2 Installing StorNext File System Installing StorNext File System on Windows 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). 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). StorNext 3.
Chapter 2 Installing StorNext File System Installing StorNext File System on Windows Figure 13 SNFS Setup: Choose Setup Type 7 Click an installation option: • Typical: (Recommended) Installs StorNext File System, 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.
Chapter 2 Installing StorNext File System Installing StorNext File System on Windows 8 Click Install to continue. Wait while the setup wizard installs StorNext. When installation is complete, the Finish window appears (figure 15). Figure 15 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 2 Installing StorNext File System Installing StorNext File System on Windows Figure 16 StorNext Installation Window: Configure StorNext 3 Click Configure StorNext. The StorNext Configuration window appears (figure 17). Figure 17 StorNext Configuration Window 4 Click Import/Export Client Settings. The Import/Export Client Configuration window appears (figure 18). StorNext 3.
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 StorNext 3.5 Installation Guide 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 IBM AIX 5.3 64-bit Power Architecture To install and run the StorNext client software, the client system must meet the following minimum hardware requirements.
Chapter 3 Installing the StorNext Client Downloading the StorNext Client Software Table 12 Default Memory Consumed by cachebufsize Platform Type <=2GB Memory >2GB Memory 32-bit Windows 32MB 64MB 32-bit Linux 64MB 128MB All other platforms 64MB 256MB To see information about the buffer cache after mounting file systems, use the cvdb(1) command with the -b option. To change the amount of memory used by the buffer cache at mount time, use the buffercachecap parameter.
Chapter 3 Installing the StorNext Client Downloading the StorNext Client Software 2 When prompted, type the username and password for the MDC, and then click OK. (The default value for both username and password is admin.) The StorNext home page appears. 3 Do one of the following: • • For a MDC running SNFS and SNSM: On the Admin menu, click Download Client Software. For a MDC running SNFS only: On the home page, click Download Client Software. The Select Platform window appears (figure 19).
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 Windows 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 Windows The StorNext setup wizard guides you through the process of installing the StorNext client software on Windows XP, Windows 2003 Server, or Windows Vista.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Windows The StorNext Installation window appears (figure 21). 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.
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Windows 2 Open the unzipped folder and double-click the client software installer file. This file is named SnfsSetup32.exe (32-bit systems) or SnfsSetup64.exe (64-bit systems). The StorNext Installation window appears (figure 22). Figure 22 StorNext Installation Window: Install StorNext 3 Click Install StorNext to begin installation. The StorNext setup wizard appears (figure 23).
Chapter 3 Installing the StorNext Client Installing the StorNext Client on Windows The License Agreement window appears (figure 24). 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.
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.
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.
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 13 Distributed LAN Server Parameters Field / Button Description tcp_window_size_kb The TCP window size (in KB) used by the distributed LAN server. (Default: 64) 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 specify mount points and mount options, set various cache settings, and configure a distributed LAN server or a distributed LAN client. To run the Client Configuration utility, on the Windows Start menu, click All Programs > StorNext File System > Client Configuration.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 37 Client Configuration: Mount Point Table 15 Client Configuration: Mount Point Field / Button Description Map to Drive Letter Select Map to Drive Letter to map the drive to a specific drive letter. Drive (Letter) Select the desired drive letter. Map to Directory Instead of selecting Map to Drive Letter, select Map to Directory. Enter a directory path, or click Browse to navigate to the directory path. Note: StorNext 3.
Chapter 4 Configuring StorNext Windows Configuration Utilities 4 Distributed LAN The Distributed LAN tab is used to enable and configure StorNext Distributed LAN (DLAN) Clients and Servers for a file system. The Enable Client and Enable Server radio buttons determine whether the system is a Client or Server. Note that separate licensing is required for DLAN. StorNext Distributed LAN Clients provide the same functionality as normal StorNext Clients but do not need to be connected directly to the SAN.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 38 Client Configuration: Distributed LAN Table 16 Client Configuration: Distributed LAN Field / Button Description Disable Select this option to disable the StorNext client as a distributed LAN client or distributed LANserver. Enable Client Select to configure the StorNext client as a distributed LAN client. The StorNext client will connect to all available distributed LAN servers.
Chapter 4 Configuring StorNext Windows Configuration Utilities Field / Button Description Number of Transfer Buffers Specify the number of socket transfer buffers used for Distributed LAN Client I/O. Read Timeout (sec) Specify how long the Distributed LAN Client will wait for a read operation to complete before retrying it on a different Distributed LAN Server.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 39 Client Configuration: Advanced Mount Options Table 17 Client Configuration: Advanced Mount Options Field / Button Description Mount Retransmit Limit Specify the number of times the driver will retransmit a message to the FSM. After a successful connection, this value is no longer used. The default is 1. Hard Mount When this box is checked, the driver attempts to mount the file system forever. The default is off (Soft Mount).
Chapter 4 Configuring StorNext Windows Configuration Utilities Field / Button Description Allow Diskless Mount When this box is checked, the file system can be mounted and accessed without all the disks being accessible in the file system stripe groups. In this mode, file metadata can be viewed and changed, but no data can be accessed. The default is to not allow a file system to be mounted unless all disks are accessible.
Chapter 4 Configuring StorNext Windows Configuration Utilities Field / Button Description I/O Retry Time Seconds When you choose Allow I/O Timouts, this option controls the I/O retry behavior. This parameter establishes the amount of time that may elapse during an I/O retry sequence. An I/O retry sequence consists of the following: • Retry an I/O request across all available paths that are currently present.
Chapter 4 Configuring StorNext Windows Configuration Utilities Field / Button Description Hard Reconnect When this box is checked, the file system attempts to reconnect to the FSM forever. If this option is not enabled, the file system attempts to reconnect to the FSM for the number of times specified at the Mount Retransmit Limit field before failing the request. The default value is off.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 40 Client Configuration: Advanced Cache Options Table 18 Client Configuration: Advanced Cache Options Field / Button Description Enable Data Buffer Cache When this box is not checked, the file system will not buffer any data. All files will be read directly into the application's memory using DMA. Requests that are not properly aligned will be read into temporary buffers, then copied to the application's buffer.
Chapter 4 Configuring StorNext Windows Configuration Utilities Field / Button Description Individual Buffer Size This option sets the size of each cache buffer. This determines the I/O transfer size used for the buffer cache. For optimal performance, Individual Buffer Size should match the RAID stripe size. If Individual Buffer Size is less than the RAID stripe size write performance may be severely degraded. This size must be divisible by the file system block size.
Chapter 4 Configuring StorNext Windows Configuration Utilities Field / Button Description Seconds for Shared/ Non-Shared The Attribute Flush Time parameters control the length of time attributes are held on the client before they are flushed back to the FSM (unless there is an explicit attribute request from the FSM). The default values are 30 seconds for nonshared files (Attribute Flush Time, non shared), and 2 seconds for shared files (Attribute Flush Time, shared).
Chapter 4 Configuring StorNext Windows Configuration Utilities Disk Device Labeler 4 The Disk Device Labeler utility lets you configure StorNext File System storage area network (SAN) disks. Use the Disk Device Labeler to create a list of disk labels, associated device names, and (optional) the sectors to use. Note: Run the Disk Device Labeler on a system that has visibility to all disk devices on the SAN. The file system uses the volume labels to determine which disk drives to use.
Chapter 4 Configuring StorNext Windows Configuration Utilities • Click Label to write a volume label to the selected device(s) (see Labeling Disks below). • Click UnLabel to remove the existing volume label from the selected device(s). • Click Exit to quit the Disk Device Labeler utility. • Click Probe Disk(s) to pulse the activity light of the selected device(s). Use this feature to correctly identify disks before labeling them. • Click Clear Selections to deselect all devices in the list.
Chapter 4 Configuring StorNext Windows Configuration Utilities License Identifier 4 Field / Button Description Skip Disk Do not write a label to the disk and proceed to the next selected disk. Cancel Close the Disk Labeler dialog box. Use the License Identifier utility to display the host license identifier. The host license identifier is required to obtain a permanent license for StorNext.
Chapter 4 Configuring StorNext Windows Configuration Utilities (figure 43). Table 20 describes the fields on the Simple Configuration Setup window. To configure a simple file system, select the disks to use in the configuration. Specify settings (file system name, block size, stripe size, and maximum connections), and then click Configure. Figure 43 Simple File System Configuration Table 20 Simple File System Configuration StorNext 3.
Chapter 4 Configuring StorNext Windows Configuration Utilities Start File System Services 4 Field / Button Description Maximum Connections Type the maximum number of clients that can simultaneously mount the file system. (This value may be overridden by values in your product license code.) Configure Click to save the configuration using the current settings. The configuration file is saved in the StorNext configuration directory. Exit Click to quit the Simple File System Configuration utility.
Chapter 4 Configuring StorNext Windows Configuration Utilities To stop StorNext File System services, on the Windows Start menu, click All Programs > StorNext File System > Stop System Services. To start the StorNext services again, reboot the system or use the Start File System Services utility. For more information, see Start File System Services.
Chapter 4 Configuring StorNext Windows Configuration Utilities To run the File System Startup List utility, on the Windows Start menu, click All Programs > StorNext File System > File System Startup List. The FSM Services List window appears (figure 44). Table 21 describes the fields on the FSM Services List window. Figure 44 File System Startup List Table 21 File System Startup List StorNext 3.5 Installation Guide Field / Button Description New Click to add a file system to the FSM services list.
Chapter 4 Configuring StorNext Windows Configuration Utilities Re-initialize a File System 4 Field / Button Description Cancel Click to quit the File System Startup List utility without saving changes. 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.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 45 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 46). Table 22 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 23 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 24 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 48 Server Administration: Quota Properties Table 24 Server Administration: Quota Properties StorNext 3.5 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 49 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 50) to specify general file system properties. Table 25 describes the fields on the Global Settings tab. Figure 50 Server Configuration: Global Settings Table 25 Server Configuration: Global Settings StorNext 3.5 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.5 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: Use the stripe group with the least amount of free space (that can accommodate the file) before using the stripe group with the next smallest amount of free space. • Balance: Use the stripe group with the most free space.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 51 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 52). Table 26 describes the fields on the Enter New Disk Type dialog box. Note: StorNext 3.
Chapter 4 Configuring StorNext Windows Configuration Utilities Figure 52 Server Configuration: Enter New Disk Type Table 26 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 53 Server Configuration: Disk Definitions Table 27 Server Configuration: Disk Definitions StorNext 3.5 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 54) to define stripe groups. (A stripe group is a logical storage unit consisting of one or more disk drives.) Table 28 describes the fields on the Stripe Groups tab. Figure 54 Server Configuration: Stripe Groups StorNext 3.
Chapter 4 Configuring StorNext Windows Configuration Utilities Table 28 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 Installing Promise RAID Controller Software 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.
Chapter 4 Configuring StorNext Installing Promise RAID Controller Software The login prompt will not appear after you restart. Instead, the Windows Boot Manager screen appears showing an error message: “Windows cannot verify the digital signature for this file” (\Windows\system32\DRIVERS\ perfectpathdsm.sys) Figure 55 Windows Boot Manager Screen 1 3 From the Windows Boot Manager screen, press Enter to continue.
Chapter 4 Configuring StorNext Installing Promise RAID Controller Software Figure 56 Windows Boot Manager Screen 2 4 On the second Windows Boot Manager screen, press F8 to specify advanced options. The Advanced Boot Options screen appears. Figure 57 Advanced Boot Options Screen StorNext 3.
Chapter 4 Configuring StorNext Installing Promise RAID Controller Software 5 On the Advanced Boot Options screen, use the arrow keys to choose the option Disable Driver Signature Enforcement. Choosing this option will cause the system to display the login prompt normally after you reboot. 6 Restart your system. StorNext 3.
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 110 • Uninstalling StorNext on Windows on page 113 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 111).
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 pkgrm ADICsnfs • HP-UX: 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 141Appendix 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, a clusterwide central control 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.
Appendix C StorNext Files The example.
Appendix C StorNext Files The example.
Appendix C StorNext Files The example.cfg File [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 [Disk CvfsDisk11] StorNext 3.
Appendix C StorNext Files The example.cfg File 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 Cluster-Wide Central Control Cluster-Wide Central Control The purpose of this feature (currently supported on the Linux platform only,) is to provide cluster-wide central control. A central control file called nss-cctl.xml provides a way to restrict the behavior of SNFS cluster nodes (fsm, file system client, cvadmin client) from a central place: an NSS server.
Appendix C StorNext Files Cluster-Wide Central Control there to be overlapping in IP address between an individual host and netgrp, but the individual host should be defined before the netgrp. The following controls are currently supported: 1 mountReadOnly: Control whether a client should mount as readonly. The default is read/write. 2 mountDlanClient: Control whether a client can mount as a proxy client. The default is not allowed.
Appendix C StorNext Files Cluster-Wide Central Control # ownership of file or directory on a Stornext file system. # 4. Whether cvadmin running on certain client is allowed to have super # admin privilege to run destructive commands such start/stop file # system, refresh disks, change quota setting ,etc. # 5. whether cvadmin running on certain client is allowed to connect # to other fsm via "-H" option. # # The control file is in xml format and has hierarchical structure.
Appendix C StorNext Files Cluster-Wide Central Control # to take ownership of file or directory of a stornext file system. The # default is "take ownership not allowed". # 4. snfsAdmin: whether cvadmin running on a host is allowed to have # super admin privilege to run privileged commands such as start/stop fs. # The default is that super admin privilege is not honored. # 5. snfsAdminConnect: whether cvadmin running on a client is allowed to # connect to other fsm via "-H" option.
Appendix C StorNext Files Commonly Used SNFS Files PAGE 156Appendix C StorNext Files Commonly Used SNFS Files 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.
Appendix C StorNext Files Commonly Used SNFS Files nssdbg.out — Displays debug and status messages from fsmpm. • /usr/cvfs/CLIENTS/ — The following are client installation files for various operating systems. sn_dsm_aix52_client.tar sn_dsm_irix65f_client.tar sn_dsm_irix65m_client.tar sn_dsm_linuxRH_80i386smp_client.tar sn_dsm_linuxRH_80i386up_client.tar sn_dsm_linuxRH_AS_3i386smp_client.tar sn_dsm_linuxRH_AS_3ia64smp_client.tar sn_dsm_linuxSuSE_81i386smp_client.tar sn_dsm_linuxSuSE_81i386up_client.
Appendix C StorNext Files Commonly Used SNFS Files • /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.
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 Non-Realtime Operation 4 Beginning with StorNext release 3.5, QOS has been enhanced to reserve bandwidth for non-realtime I/O clients. Differentiating between realtime and non-realtime I/O clients should result in better bandwidth utilization and overall performance. During the mounting process, there is now provision to specify the amount of bandwidth to be reserved.
Appendix D Quality of Service Guide Configuration 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).
Appendix D Quality of Service Guide Configuration 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.
Appendix D Quality of Service Guide Configuration 4 RTIO Upper Bound The limit will be specified in terms of I/Os per second (parameter Rtios) or in terms of MB/sec (parameter Rtmb). Case is not sensitive. Note that I/Os per second are I/Os of any size to the disk subsystem. Either or both may be specified. If both are specified, the lower limit is used to throttle I/O. If neither is specified, no real-time I/O is available on the stripe group. These parameters are applied to a stripe group definition.
Appendix D Quality of Service Guide Configuration 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 nonreal-time applications on each client.
Appendix D Quality of Service Guide Real-time I/O 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.
Appendix D Quality of Service Guide Real-time I/O Also, assume there is only one stripe group for user data in the file system. As recommended by Quantum, there may be other stripe groups for metadata and journal that are not shown. 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.
Appendix D Quality of Service Guide Real-time I/O 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.
Appendix D Quality of Service Guide Non-Realtime I/O Configuration not be counted against the non-real-time I/O. System designers typically allow for some amount of overage in their I/O subsystem to account for non-gated files. Calculating Available RTIO 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.
Appendix D Quality of Service Guide Non-Realtime I/O Configuration time. Non-RTIO requests on clients with an RVIO reservation is subject to the same throttling mechanism as non-RTIO requests on normal clients. 4 Other active non-RTIO clients equally share the bandwidth left over after the possible RTIO and RVIO allocations. If no bandwidth is left, the minimal reserved bandwidth (defined in the stripe group section of the file system configuration file) is used.
Appendix D Quality of Service Guide Callbacks 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.
Appendix D Quality of Service Guide Callbacks 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 Figure 61 Callback Retraction Example In Figure 61, Client A requests some amount of RTIO as in Figure 60. 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).
Appendix D Quality of Service Guide Callbacks 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.
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 nonreal-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-realtime 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.
