SGI® InfiniteStorage NAS System Storage Subsystem Guide 007-5597-002
COPYRIGHT © 2010 SGI. All rights reserved; provided portions may be copyright in third parties, as indicated elsewhere herein. No permission is granted to copy, distribute, or create derivative works from the contents of this electronic documentation in any manner, in whole or in part, without the prior written permission of SGI.
Record of Revision Version Description 001 October 2009. Original publication. 002 January 2010. Updated publication, replaces 007-5597-001.
iv SGI InfiniteStorage NAS Server and Titan Server
Table of Contents 1 About This Guide Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Chapter Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Related Publications ..................................2 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Browser Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Product Support . . . . . . . . . . . . . .
Table of Contents The SGI InfiniteStorage 15000 Controller Enclosure . . . . . . . . . . . . . . . . . . . 13 The SGI InfiniteStorage 15000 Drive Shelf Expansion . . . . . . . . . . . . . . . . . . 13 3 Configuring SGI InfiniteStorage Arrays Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Storage Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 RAID Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Audience 1 About This Guide This guide provides an overview of the storage subsystems supported for use with the SGI® InfiniteStorage NAS Server (IS‐NAS Server). This guide also provides information and instructions for managing the storage subsystems attached to your IS‐NAS Server. License keys are required to enable the usage of storage subsystems, and are also used to control the availability of some system features and functionality.
About This Guide Related Publications The following documents are relevant to the SGI InfiniteStorage NAS Server: • SGI InfiniteStorage NAS Server System Administration Guide: In PDF format, this guide provides information about the features, configuration, administration, and maintenance of an SGI InfiniteStorage NAS Server or cluster.
Browser Support Convention Meaning GUI element This font denotes the names of graphical user interface (GUI) elements such as windows, screens, dialog boxes, menus, toolbars, icons, buttons, boxes, fields, and lists. Tip: A tip contains supplementary information that is useful in completing a task. Note: A note contains information that helps to install or operate the system effectively. Caution: A caution indicates the possibility of damage to data or equipment.
About This Guide Reader Comments If you have comments about the technical accuracy, content, or organization of this document, contact SGI. Be sure to include the title and document number of the manual with your comments. (Online, the document number is located in the front matter of the manual. In printed manuals, the document number is located at the bottom of each page.) You can contact SGI in any of the following ways: Send e‐mail to the following address: techpubs@sgi.com.
2 The SGI InfiniteStorage NAS Storage System System Overview The InfiniteStorage NAS Server and the Titan Server are highly scalable and modular network attached storage (NAS) servers, with multi‐gigabit throughput from network to disk.
The SGI InfiniteStorage NAS Storage System without compromising performance. Each storage server can be configured as a single stand alone server or as a node of a cluster. All network clients communicate directly with the storage server. The server processes file access requests from network clients via Gigabit Ethernet (GE) or 10 Gigabit Ethernet (10GbE) links, reading and writing from/ to one or multiple storage devices, connected through Fibre Channel (FC) links.
System Overview Public Data Network The public data network, from the storage server perspective, consists of the public Ethernet port on the SMU, and management access can be enabled on individual Gigabit Ethernet (GE) interfaces on the storage server. Clients connect to the SMU through the public data network, and client connections are made through the public data network.It is also possible to configure storage servers/clusters so that they can be managed using the public data network.
The SGI InfiniteStorage NAS Storage System If it is necessary to remove and replace a failed disk, some storage subsystems support “hot swap” operations. In a hot swap, an offline or failed disk is removed and a replacement disk is inserted while the power is on and the system is operating. Understanding Tiered Storage Tiered storage allows you to connect multiple diverse storage subsystems behind a single server (or cluster).
Understanding Tiered Storage Tier Performance Disk Type Disk RPM 4 Archival SATA or SAS 7,200 5 Long‐term storage N/A (Tape) NA The storage server supports tiers of storage, where each tier is made up of devices with different performance characteristics or technologies.
The SGI InfiniteStorage NAS Storage System following illustration shows a complete path from the server to each of the SDs on the storage subsystem: You can view information about the FC paths on the server/cluster through the command line interface (CLI), using the fc-host-port-load, fctarget-port-load, and the sdpath commands.
Supported Storage Subsystems • Balancing load on RAID controller target ports takes precedence over balancing load on server FC host ports. • Balancing load among an subsystem’s RAID controllers takes precedence over balancing among ports on those controllers. • In a cluster, choice of RAID controller target port is coordinated between cluster nodes, so that I/O requests for a given SD do not simultaneously go to multiple target ports on the same RAID controller.
The SGI InfiniteStorage NAS Storage System Enclosure Typically used in Tier(s) SGI InfiniteStorage 220 Tier 1, Tier 2, and Tier 3 This enclosure has several configurations, and is suitable for use in several tiers, based on configuration of the individual storage array. SGI InfiniteStorage 15000 Tier 1, Tier 2, and Tier 3 This enclosure has several configurations, and is suitable for use in several tiers, based on configuration of the individual storage array.
Supported Storage Subsystems Drive shelf enclosures containing FC disks and drive shelf enclosures containing SATA disks may be connected to the same InfiniteStorage 220 storage controller enclosure. The following configurations are supported: The SGI InfiniteStorage 15000 Controller Enclosure The SGI InfiniteStorage 15000 Drive Shelf Expansion • All SAS configuration: InfiniteStorage 220 and up to 3 drive shelf expansion enclosures with SAS drives.
The SGI InfiniteStorage NAS Storage System 14 SGI InfiniteStorage NAS Server and Titan Server
3 Configuring SGI InfiniteStorage Arrays Specifications The specifications for each supported RAID controller enclosure or drive shelf expansion may be found as described below: Enclosure Enclosure Type Page InfiniteStorage 220 RAID Controller 12 InfiniteStorage 220 Drive Shelf Expansion 12 InfiniteStorage 15000 RAID Controller 13 InfiniteStorage 15000 Drive Shelf Expansion 13 Storage Characteristics The SGI InfiniteStorage family of storage controller enclosures use hardware RAID controlle
Configuring SGI InfiniteStorage Arrays a replacement disk is inserted while the power is on and the system is operating. Note: When replacing disk drives, allow at least a one‐minute interval between disk removal and disk replacement. This interval allows the RAID controller to recognize the change in the RAID rack’s configuration. Managing the Storage Subsystem InfiniteStorage RAID racks can be managed using Web Manager.
Managing the Storage Subsystem In the Choose Racks to Monitor area, check the checkboxes in the Rack Name column to be added to the currently managed server. Use the Rack Password field for racks with configured passwords. Then, click OK. If no racks appear, the SMU was unable to find any supported racks on its network. In this case, verify that the RAID racks have their network settings properly configured.
Configuring SGI InfiniteStorage Arrays Listing Installed RAID Racks To list installed RAID racks: 1. Navigate to the RAID Racks page (Storage Management > RAID Racks). The following actions are available and apply to racks selected by filling the checkbox for the RAID rack: 18 • Delete removes the RAID rack from the list. Deleting the rack just removes the rack as a managed rack, it does not affect the system drives configured on the storage enclosures in the rack.
Managing the Storage Subsystem In any individual row, clicking the details button brings up a RAID Rack Details page. This page provides information on the RAID rack.
Configuring SGI InfiniteStorage Arrays The following table describes fields and columns in this page: Area Field Identification Description This area displays identification information, including: Rack Status Summary • Name. The name of the RAID rack. You can change this name to make it easier to identify the RAID rack. • Rack WWN. Worldwide name for the RAID rack, set by the manufacturer.
Managing the Storage Subsystem Area Field Batteries Description Batteries maintain data held in the RAID controller’s cache, preserving data in the event of a power failure. The information for each battery within the RAID rack: • Power Supplies Green – OK • Amber – Warning • Red – Severe Location. The location of the batteries within the RAID rack. • Age. The number of days that the batteries have been in the RAID rack. • Life Remaining.
Configuring SGI InfiniteStorage Arrays The following shortcuts are available: Performing a Media Scan on a System Drive • Physical Disk Status. Click the Physical Disk Status link to display the Physical Disks on RAID Rack page for the RAID rack. • Active Tasks. Click the Active Tasks link to display the Active Tasks page for the RAID rack. • Event Log. Click the Event Log link to display the Rack Event Log page. • System Drives. Click the System Drives link to display the System Drives page.
Managing the Storage Subsystem Note: Some tasks will report a Percentage Complete but not a Time Re‐ maining. In this case, Time Remaining will be shown as Not Known. Reviewing Events Logged The SMU monitors events, such as failure conditions, logged by the RAID rack. The SMU is connected to the storage subsystem through an “out‐of‐ band” Ethernet link (the private management network is typically used for this purpose). Severe events are immediately forwarded to the server’s event log.
Configuring SGI InfiniteStorage Arrays severe). Up to 3,000 events are archived on the SMU and are available for download using the download button. This table can also be filtered to view the event log based on severity level: All, Info, or Severe. Item/Field Description Severity The level of severity is displayed for each event. Severity might be either Info (informational), or severe (error). Date/Time The date and time at which the event was logged.
Monitoring Physical Disks Check the checkbox for the RAID rack with physical disks of interest and click View Physical Disks. The following table describes the columns in this page: Storage Subsystem Guide Item/Field Description Enclosure The ID of the enclosure housing the disk. Slot The slot number in the storage enclosure in which the physical disk resides. Capacity The storage capacity of the disk. Type The type of physical disk in the enclosure, typically either Fibre Channel or SATA.
Configuring SGI InfiniteStorage Arrays Within the Physical Disk page, physical disks which are shown as available can be assigned or unassigned as hot spares. Note: SGI requires that at least one disk be marked as a hot spare by the time the first system drive is created.
4 System Drives and System Drive Groups System Drives Logically, system drives (SDs) are the basic storage element used by the storage server. The server assigns each system drive a unique identifying number (ID) and, once assigned, the SD is referenced by that ID number, and the ID number may not be changed. Physically, each SD is made up of several physical disks. The size of the system drive depends on factors such as the RAID level, the number of disks, and their capacity.
System Drives and System Drive Groups The SMU cannot group or ungroup system drives that are used in open Storage Pools. A Storage Pool is open if it has any file system that is mounted or is being checked or fixed anywhere on the cluster. During EVS migration, the SMU automatically copies the groups from the source storage server or cluster and adds them to the target storage server or cluster. See Managing System Drive Groups, on page 34 for information on creating and modifying system drive groups.
System Drives The file system data redistribution utility is designed to operate when a file system is expanded into new storage after SDs have been added to a Storage Pool when the file system is nearly full. However, storage may also be added to a Storage Pool for other reasons: • To increase performance. • To prevent the file system from becoming 100% full.
System Drives and System Drive Groups Creating System Drives When your system was first installed, SDs were pre‐configured by SGI. You can, however, create additional SDs as needed when adding disks to partially‐ populated enclosures, adding expansion enclosures, upgrading to higher‐ capacity disks, or when you have unused disks in an enclosure and you need to use that capacity. After creating additional SDs, you should place them in appropriate SD groups as described in System Drive Groups, on page 27.
Creating System Drives In the RAID Level page, select a RAID level, then click Next. For information about RAID levels 1, 5 and 6, refer to the following table. RAID Level System Drive Size Description and Failover Advantages/Disadvantages 1 2 to 32 disks, up to 2 TB or, >2 TB with the proper controller firmware and disk type (contact SGI Global Services for more information) Provides mirroring and duplexing.
System Drives and System Drive Groups RAID Level System Drive Size Description and Failover Advantages/Disadvantages 6 3 to 16 disks, >2 TB Provides a combination of striping and two disk parity checking. All parity data is distributed on two disks (dual parity), and parity checking provides redundancy without the overhead of having to double the disk capacity. Provides fault tolerance for two drive failures, making larger RAID groups more practical, especially for high availability systems.
Creating System Drives a. Select SD size. In the Capacity column, click the radio button for the desired size of the SD. (The server calculates SD capacity based on the number of physical disks specified in the Number of Physical Disks column.) Caution: To ensure optimal performance of the storage subsystem, do not change the value specified in the System Drive Capacity field except under the direction of SGI Global Services. b. Specify stripe size.
System Drives and System Drive Groups The newly added system drive should appear in the list. Format and initialization data can be viewed in real time under the Status column. 8. Create a new file system. Once the system drive has been initialized, a file system can be created. Refer to the System Administration Guide. Managing System Drive Groups After system drives (SDs) are created, they should be placed into system drive groups to optimize system performance.
Managing System Drive Groups Creating SD Groups Automatically The following steps describe how to create system drive groups automatically. 1. Navigate to the System Drives Group page (Home > Storage Management > System Drive Groups). The System Drive Groups page indicates the number of SDs not in groups and lists the SD groups that have already been created. 2. Start auto‐grouping the system drives.
System Drives and System Drive Groups tact SGI Global Services for more information about which storage subsystems can provide that information to the SMU. Without such infor‐ mation, you will need to group system drives manually (see Creating SD Groups Manually, on page 36). The storage server cannot automatically group SDs on certain storage subsystems, because those SDs (LUNs) are not directly managed by the storage server.
Managing System Drive Groups The System Drive Groups page indicates the number of SDs not in groups and lists the SD groups that have already been created. 2. Create the System Drives Group. In the System Drives Group page, click create (if the ʺNumber of System Drives Not In Groupsʺ is zero, the create button is unavailable because no groups can be created). The Create System Drive Group page opens, allowing you to manually group system drives.
System Drives and System Drive Groups Backing up or Restoring SD Groups Backing up and restoring SD groups is a simple, quick, and error‐free method of transferring SD group definitions among clusters or servers that share storage or when moving storage between servers/clusters. SD groups are backed up as a part of the normal server/cluster configuration backup process, so backing up SD groups is not necessary for failure recovery.
Managing System Drive Groups SD_GROUPSyyyy-mm-dd_time-UTC-offset.txt, where the following example illustrates the appropriate syntax: SD_GROUPS2008-0430_1729-0700.txt • To restore: Click Browse to display a dialog you can use to choose the backup file, navigate to the directory where the backup file is stored, select the backup text file (SD_GROUPS2008-04-30_1729-0700.txt) for the specific export(s) you want to restore, then click Open.
System Drives and System Drive Groups displaying the system drives that are available to be grouped and the SDs in the selected group. The Available System Drives list shows all SDs in the storage server or cluster that are not already in a group. The Selected System Drives list shows the SDs that are already included in the selected group. 3. Modify the SD group.