HP 3PAR StoreServ Storage Concepts Guide
HP 3PAR OS 3.1.2 MU2

Abstract
This guide is for all levels of system and storage administrators who plan storage policies, configure storage resources, or monitor the storage usage of HP 3PAR storage systems.

HP Part Number: QR482-96384 Published: June 2013

© Copyright 2007, 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 and 12.212, Commercial 1 Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgements Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation. Oracle is a registered trademarks of Oracle and/or its affiliates. UNIX® is a registered trademark of The Open Group. Warranty To obtain a copy of the warranty for this product, see the warranty information website: http://www.hp.com/go/storagewarranty

Contents
1 Overview..................................................................................................7
HP 3PAR Storage Concepts and Terminology...............................................................................7 Physical Disks......................................................................................................................8 Chunklets............................................................................................................................8 Logical Disks.......................................................................................................................8 Common Provisioning Groups................................................................................................8 Virtual Volumes....................................................................................................................8 Fully-provisioned Virtual Volumes.......................................................................................8 Thinly-provisioned Virtual Volumes.....................................................................................8 Physical Copies...............................................................................................................9 Virtual Copy Snapshots....................................................................................................9 Exporting Virtual Volumes............................................................................................9 HP 3PAR Software....................................................................................................................9 HP 3PAR Software Products and Features..............................................................................10 HP 3PAR Software Licensing Requirements.............................................................................13

2 HP 3PAR Storage System Users...................................................................18
User Accounts........................................................................................................................18 Local User Authentication and Authorization...............................................................................19 LDAP User Authentication and Authorization...............................................................................19 Domain User Access...............................................................................................................19

3 Lightweight Directory Access Protocol..........................................................20
Overview..............................................................................................................................20 Active Directory.................................................................................................................20 OpenLDAP........................................................................................................................20 LDAP Users............................................................................................................................20 LDAP Server Data Organization................................................................................................21 LDAP and Domains.................................................................................................................21 LDAP Authentication and Authorization......................................................................................22 Authentication...................................................................................................................22 Simple Binding.............................................................................................................22 SASL Binding................................................................................................................22 Authorization.....................................................................................................................22 Authorization on Systems Using Virtual Domains....................................................................23

4 HP 3PAR Virtual Domains..........................................................................24
Overview..............................................................................................................................24 Domain Types........................................................................................................................24 Domain Type.....................................................................................................................25 Users and Domain Rights.........................................................................................................25 Object and Domain Association Rules.......................................................................................25 The Default and Current Domains.............................................................................................25

5 Ports and Hosts........................................................................................27
Overview..............................................................................................................................27 About Ports............................................................................................................................27 Port Location Formats..............................................................................................................28 Port Target, Initiator, and Peer Modes........................................................................................29 Active and Inactive Hosts.........................................................................................................29 Adding and Removing Hosts....................................................................................................29 Managing Host Personas.........................................................................................................30 Legacy Host Personas..............................................................................................................31
Contents 3

The Host Explorer Software Agent.............................................................................................31

6 Chunklets................................................................................................32
Overview..............................................................................................................................32 Physical Disk Chunklets............................................................................................................32 Spare Chunklets.....................................................................................................................32

7 Logical Disks............................................................................................34
Overview..............................................................................................................................34 Logical Disks and Common Provisioning Groups.........................................................................34 Logical Disk Types..................................................................................................................34 RAID Types............................................................................................................................35 RAID 0.............................................................................................................................35 RAID 1 and 10..................................................................................................................35 RAID 5 and 50..................................................................................................................36 RAID Multi-Parity................................................................................................................37 Logical Disk Size and RAID Types.............................................................................................38

8 Common Provisioning Groups....................................................................39
Overview..............................................................................................................................39 Precautions and Planning.........................................................................................................39 Growth Increments, Warnings, and Limits..............................................................................39 Growth Increment..............................................................................................................40 Growth Warning...............................................................................................................40 Growth Limit......................................................................................................................40 System Guidelines for Creating CPGs........................................................................................41 Volume Types Associated with CPGs.........................................................................................41

9 Virtual Volumes........................................................................................42
Overview..............................................................................................................................42 Virtual Volume Types...............................................................................................................42 Administrative Volumes.......................................................................................................43 Fully-provisioned Virtual Volumes..........................................................................................43 Thinly Provisioned Virtual Volumes........................................................................................43 TPVV Warnings and Limits..............................................................................................44 Virtual Volume Online Conversion.............................................................................................45 Physical Copies......................................................................................................................45 Virtual Copy Snapshots...........................................................................................................46 Virtual Copy Snapshot Relationships.....................................................................................46 Copy-on-Write Function..................................................................................................47 Copy-of and Parent Relationships....................................................................................48 Exporting Virtual Volumes........................................................................................................48 VLUN Templates and Active VLUNs......................................................................................49 VLUN Template Types.........................................................................................................49 Host Sees.....................................................................................................................49 Host Set.......................................................................................................................49 Port Presents.................................................................................................................49 Matched Set.................................................................................................................50

10 Reclaiming Unused Space........................................................................51
Overview..............................................................................................................................51 Reclaiming Unmapped Logical Disk Space from CPGs.................................................................51 Reclaiming Unmapped Logical Disk Space from Volumes.............................................................52 Automatically Reclaiming Unused Snapshot Space from Volumes..................................................52 Manually Reclaiming Unused Snapshot Space from Volumes........................................................52 Deleted Volume Snapshot Space..............................................................................................52 Logical Disks and Chunklet Initialization....................................................................................52
4 Contents

1 Enhanced Storage Applications................................................................53 1
Overview..............................................................................................................................53 HP 3PAR mySnapshot Software................................................................................................53 HP 3PAR Dynamic Optimization Software .................................................................................53 HP 3PAR System Tuner Software...............................................................................................54 HP 3PAR Thin Conversion Software...........................................................................................55 Assessment.......................................................................................................................55 Data Preparation...............................................................................................................55 Zeroing Unused Space.......................................................................................................56 Creating a Physical Copy....................................................................................................56 HP 3PAR Thin Persistence Software............................................................................................56 HP 3PAR Thin Copy Reclamation Software.................................................................................56 HP 3PAR Virtual Lock Software.................................................................................................57 HP 3PAR Adaptive Optimization Software..................................................................................57 HP 3PAR Peer Motion Software................................................................................................58 Data Encryption.....................................................................................................................58 Priority Optimization...............................................................................................................59 Automatic and Transparent Failover .........................................................................................59

12 HP 3PAR Storage System Hardware...........................................................61
Overview..............................................................................................................................61 Identifying System Components................................................................................................61 Physical Disks.........................................................................................................................63 Drive Cage/Enclosure Models..................................................................................................64 HP M6710 Drive Enclosure..................................................................................................64 HP M6720 Drive Enclosure..................................................................................................64 DC4 Drive Cages and Ports and Cabling..............................................................................64 DC3 Drive Cage and Ports and Cabling...............................................................................65 Controller Nodes....................................................................................................................66 Port Numbering.................................................................................................................67 HP 3PAR StoreServ 7000 Controller Node Numbering...........................................................67 HP 3PAR StoreServ 10000 Controller Node Numbering.........................................................68 T-Class Controller Node Numbering.....................................................................................69 F-Class Controller Node Numbering.....................................................................................70

13 HP 3PAR SNMP Infrastructure...................................................................72
Overview..............................................................................................................................72 About SNMP.........................................................................................................................72 SNMP Managers....................................................................................................................72 The HP 3PAR SNMP Agent......................................................................................................72 Standard Compliance.........................................................................................................73 Supported MIBs.................................................................................................................73 MIB-II...........................................................................................................................73 Exposed Objects...........................................................................................................74 System Description....................................................................................................74 System Object ID......................................................................................................74 System Up Time........................................................................................................74 System Contact Information........................................................................................74 System Name..........................................................................................................75 System Location........................................................................................................75 The HP 3PAR MIB..........................................................................................................75 alertNotify Traps......................................................................................................76

14 The HP 3PAR CIM API.............................................................................78
Overview..............................................................................................................................78 About SMI-S..........................................................................................................................78
Contents 5

About the WBEM Initiative.......................................................................................................78 HP 3PAR CIM Support............................................................................................................79 Standard Compliance.........................................................................................................79 SMI-S Profiles....................................................................................................................79 Supported Extensions.........................................................................................................79 CIM Indications.................................................................................................................79

15 Comparing HP 3PAR to EVA Terms............................................................80 16 Support and Other Resources...................................................................81
Contacting HP........................................................................................................................81 HP 3PAR documentation..........................................................................................................81 Typographic conventions.........................................................................................................84 HP 3PAR branding information.................................................................................................84

17 Documentation feedback.........................................................................85 Glossary....................................................................................................86 Index.........................................................................................................94

6

Contents

1 Overview
HP 3PAR Storage Concepts and Terminology
HP 3PAR storage systems include the hardware components that physically store your data and the software applications that manage your data. For more information about hardware platforms, see “HP 3PAR Storage System Hardware” (page 61). For more information about system software applications and features, see “HP 3PAR Software” (page 9). The HP 3PAR storage system is composed of the following logical data layers: • • • • • “Physical Disks” (page 8) “Chunklets” (page 8) “Logical Disks” (page 8) “Common Provisioning Groups” (page 8) “Virtual Volumes” (page 8)

The relationship between HP 3PAR storage system data layers is illustrated in Figure 1 (page 7). Each layer is created from elements of the layer above. Chunklets are drawn from physical disks, logical disks are created from groups of chunklets, common provisioning groups (CPGs) are groups of logical disks, and virtual volumes use storage space provided by CPGs. The virtual volumes are exported to hosts and are the only data layer visible to hosts. Figure 1 HP 3PAR Storage System Data Layers

HP 3PAR Storage Concepts and Terminology

7

Physical Disks
A physical disk is a hard drive mounted on a drive magazine located in an HP 3PAR storage system drive cage. For more information about physical disks and the HP 3PAR storage system hardware platforms, see “HP 3PAR Storage System Hardware” (page 61).

Chunklets
Physical disks are divided into chunklets. Each chunklet occupies contiguous space on a physical disk. On F-Class and T-Class systems all chunklets are 256 MB. On 10000 and 7000 systems all chunklets are 1 GB. Chunklets are automatically created by the HP 3PAR Operating System and they are used to create logical disks. A chunklet is assigned to only one logical disk. For more information about chunklets, see “Chunklets” (page 32).

Logical Disks
A logical disk is a collection of physical disk chunklets arranged as rows of RAID sets. Each RAID set is made up of chunklets from different physical disks. Logical disks are pooled together in Common Provisioning Groups (CPGs) which allocate space to virtual volumes. The underlying logical disks are automatically created by the HP 3PAR OS when you create CPGs. The RAID type, space allocation, growth increments and other logical disk parameters can be set when you create a CPG or modified later. HP 3PAR storage systems support the following RAID types: • • • • RAID 0 RAID 10 (RAID 1) RAID 50 (RAID 5) RAID MP (Multi-Parity) or RAID 6

For a detailed discussion of logical disks and RAID types, see “Logical Disks” (page 34).

Common Provisioning Groups
A CPG is a virtual pool of logical disks that allocates space to virtual volumes on demand. A CPG allows virtual volumes to share the CPG resources. You can create fully provisioned virtual volumes (FPVVs) and thinly-provisioned virtual volumes (TPVVs) that draw space from a CPG logical disk pool. For more information about CPGs, see “Common Provisioning Groups” (page 39).

Virtual Volumes
Virtual volumes draw their resources from CPGs, and volumes are exported as logical unit numbers (LUNs) to hosts. Virtual volumes are the only data layers visible to the hosts. You can create physical copies or virtual copy snapshots of virtual volumes that remain available if the original base volume becomes unavailable. Before creating virtual volumes, you must first create CPGs to allocate space to the virtual volumes. For more information about virtual volumes, see “Virtual Volumes” (page 42).

Fully-provisioned Virtual Volumes
An FPVV is a volume that uses logical disks that belong to a CPG. Unlike TPVVs, FPVVs have a set amount of user space that is allocated for user data. The FPVV size is fixed, and the size limit is 16 TB. For more information about fully provisioned virtual volumes, “Fully-Provisioned Virtual Volumes” (page 43).

Thinly-provisioned Virtual Volumes
A TPVV is a volume that uses logical disks that belong to a CPG. TPVVs associated with the same CPG draw space from the logical disk pool as needed, allocating space on demand in small increments for each controller node. As the volumes that draw space from the CPG require additional storage, the HP 3PAR OS automatically creates additional logical disks and adds them to the pool until the CPG reaches the user-defined growth limit which restricts the CPG maximum size. The
8 Overview

TPVV volume size limit is 16 TB. For more information about TPVVs, see “Thinly-Provisioned Virtual Volumes” (page 43). NOTE: Creating TPVVs requires the HP 3PAR Thin Provisioning Software license. For more information, see “HP 3PAR Software” (page 9).

Physical Copies
A physical copy is a full copy of a volume. The data in a physical copy is static; it is not updated with subsequent changes to the parent volume. The parent volume is the original volume that is copied to the destination volume. The parent volume can be a base volume, volume set, virtual copy, or physical copy. Creating physical copies does not require a separate license. A physical copy can be created only from a parent volume with enough free space to accommodate writes to that volume during the physical copy operation. Physical copies can be online physical copies or offline physical copies. For online physical copies, the destination volume is automatically created and can be exported immediately. Offline physical copies require a destination volume that must have a user space size at least as large as the user space of the base volume being copied, and offline physical copies cannot be exported. For additional information about physical copies, see “Physical Copies” (page 45). NOTE: With an HP 3PAR Remote Copy Software license, physical copies can be copied from one HP 3PAR storage system to another by using Remote Copy. For additional information, see the HP 3PAR Remote Copy Software User’s Guide.

Virtual Copy Snapshots
A snapshot is a virtual copy of a base volume. The base volume is the original volume that is copied. Unlike a physical copy, which is a duplicate of an entire volume, a virtual copy only records changes to the base volume. This allows an earlier state of the original virtual volume to be recreated by starting with the current state of the virtual copy and rolling back all the changes that have been made since the virtual copy was created. You can make snapshots of: FPVVs, TPVVs, physical copies, or another virtual copy snapshot. Snapshots are created by using copy-on-write techniques available only with the HP 3PAR Virtual Copy Software license. Thousands of snapshots of each virtual volume can be created assuming that there is sufficient storage space available. For additional information on virtual copies, see “Virtual Copy Snapshots” (page 46). NOTE: An HP 3PAR Virtual Copy license is required to create virtual copies. For more information, see “HP 3PAR Software” (page 9). Exporting Virtual Volumes For a host to see a virtual volume, the volume must be exported as a LUN. Volumes are exported by creating Virtual Volume-LUN pairings (VLUNs) on the system. When you create VLUNs the system produces both VLUN templates that establish export rules, and active VLUNs that the host sees as a LUN or attached disk device. For more information about active VLUNs, VLUN templates, and VLUN template types, see “Exporting Virtual Volumes” (page 48).

HP 3PAR Software
In addition to HP 3PAR Operating System Software, HP offers separately licensed software suites, optional software features, and a set of host-based software applications. You can use the HP 3PAR Command Line Interface (CLI) Software and the HP 3PAR Management Console Software to view the licenses currently enabled on your system.

HP 3PAR Software

9

IMPORTANT: Optional HP 3PAR software features may not currently be enabled on your system because they require additional licenses and may require separate installations. When features are not available on your system because they are not licensed for use, screens and functionality relating to those features may appear grayed-out or be otherwise inaccessible in the HP 3PAR Management Console and HP 3PAR CLI. To learn about adding optional products and features to enhance your HP 3PAR storage systems, contact your local service provider.

HP 3PAR Software Products and Features
The following HP 3PAR software products and features are available for HP 3PAR storage systems. For more detailed information about all HP 3PAR software suites and standalone software applications, see the QuickSpecs for your product at http://www.hp.com/go/3par/. • • • • • • HP 3PAR Operating System Software: independent instances of the HP 3PAR OS running on each controller node. HP 3PAR Access Guard Software: provides volume security at logical and physical levels by enabling you to secure hosts and ports to specific virtual volumes. HP 3PAR Data Encryption: provides data encryption for HP 3PAR StoreServ arrays using self-encrypting drives. See “Data Encryption” (page 58). HP 3PAR Full Copy Software: thin-aware, point-in-time clones with independent service-level parameters that can be rapidly resynchronized with base volumes as needed. HP 3PAR Rapid Provisioning Software: instant application-tailored volume provisioning. HP 3PAR Autonomic Rebalance Software: provides the ability to analyze how volumes on the system use physical disk space and make intelligent, autonomic adjustments to ensure optimal volume distribution when new hardware is added to the system. HP 3PAR Thin Copy Reclamation Software: reclaims space when snapshots are deleted from an HP 3PAR storage system. As snapshots are deleted, the snapshot space is reclaimed from a TPVV or FPVV and returned to the CPG for reuse by other volumes. To learn more about HP 3PAR thin copy reclamation, see “Enhanced Storage Applications” (page 53). HP 3PAR Persistent Ports Software: eliminates the dependency on multipath software during the process of online software upgrades. Persistent ports enable the host paths to remain online during the online upgrade process. Persistent ports are also called virtual ports. HP 3PAR Persistent Cache Software: allows systems to maintain a high level of performance and availability during node failure conditions, and during hardware and software upgrades. This feature allows the host to continue to write data and receive acknowledgments from the system if the backup node is unavailable. Persistent cache automatically creates multiple backup nodes for logical disks that have the same owner. Persistent cache also maintains service levels by preserving write-caching through rapidly re-mirroring the cache to the other nodes in the cluster in the event of a cache or controller node failure. HP 3PAR System Tuner Software: improves performance by identifying overused physical disks and performing load balancing on those disks without interrupting access. To learn more about the HP 3PAR System Tuner, see “Enhanced Storage Applications” (page 53). HP 3PAR Thin Provisioning Software: allows you to allocate virtual volumes to application servers yet provision only a fraction of the physical storage behind these volumes. By enabling a true capacity-on-demand model, a storage administrator can use HP 3PAR Thin Provisioning to create TPVVs that maximize asset use. To learn more about TPVVs, see “Virtual Volumes” (page 42). HP 3PAR Thin Conversion Software: converts an FTPP to a TPPV. Virtual volumes with large amounts of allocated but unused space are converted to TPVVs that are much smaller than the original volume. To use the thin conversion feature, you must have an F-Class, T-Class, HP

•

•

•

•

•

•

10

Overview

3PAR StoreServ 10000, or HP 3PAR StoreServ 7000 storage system, an HP 3PAR Thin Provisioning license, and an HP 3PAR Thin Conversion license. To learn more about HP 3PAR thin conversion, see “Enhanced Storage Applications” (page 53). • HP 3PAR Thin Persistence Software: keeps TPVVs and read/write snapshots of TPVVs small by detecting pages of zeros during data transfers and not allocating space for the zeros. This feature works in real time and analyzes the data before it is written to the destination TPVV or read/write snapshot of the TPVV. To use the thin persistence feature, you must have an F-Class, T-Class, HP 3PAR StoreServ 10000, or HP 3PAR StoreServ storage system, an HP 3PAR Thin Provisioning license, and an HP 3PAR Thin Conversion license. To learn more about HP 3PAR thin persistence, see “Enhanced Storage Applications” (page 53). HP 3PAR EVA to 3PAR Online Import Software: manages the migration of data from a source HP EVA storage system to a destination HP 3PAR storage system. You can migrate HP EVA virtual disks and host configuration information to an HP 3PAR destination storage system without changing host configurations or interrupting data access. HP 3PAR Service Processor Software: the Service Processor can be deployed as a Virtual Machine or as a physical server and functions as the communication interface between your IP network and HP 3PAR Central by managing all service-related communications. HP 3PAR Management Console Software: graphical user interface for monitoring, managing, and configuring HP 3PAR storage systems. HP 3PAR Command Line Interface Software: command line user interface for monitoring, managing, and configuring HP 3PAR storage systems. HP 3PAR Web Services API Software: well-defined application programming interface that you can use for incorporating the storage infrastructure into your platform for end-to-end automation of your service delivery and management. HP 3PAR SmartStart Software: simplifies system startup and guides the administrator through the configuration of HP 3PAR StoreServ Storage, HP 3PAR Service Processor and production application hosts. HP 3PAR Host Explorer Software: automates host discovery and collection of detailed host configuration information critical to speeding storage provisioning and simplifying maintenance. HP 3PAR Autonomic Groups Software: allows domains, hosts, and volumes to be grouped into a set that is managed as a single object. Autonomic groups also allow for easy updates when new hosts are added or new volumes are provisioned. If you add a new host to the set, volumes from the volume set are autonomically provisioned to the new host without any administrative intervention. If you add a new volume or a new domain to a set, the volume or domain inherits all the rights of the set. HP 3PAR mySnapshot Software: a copy utility designed for non-storage professionals such as database administrators, software developers, and test engineers to safely and easily copy and provision their own test data. With mySnapshot, developers have instant access to test data, thus eliminating the time required to request, justify, and receive these copies from the storage administrator. To learn more about the mySnapshot utility, see “HP 3PAR mySnapshot Software” (page 53). HP 3PAR Policy Manager Software: provides flexibility and control to allow or deny outbound communications or remote service connections to and from HP 3PAR storage systems at the customer site and HP 3PAR Central. HP 3PAR ODM 3.1 Software for IBM MPIO and Veritas VxDMP: a standalone software that delivers a highly available, robust, and trouble-free multipathing solution for IBM AIX deployments. HP 3PAR Multipath IO Software for Microsoft Windows 2003: enables the host to use more than one physical I/O path to the system. Multipathing improves system reliability and availability by providing fault-tolerance and load balancing of I/O traffic.
HP 3PAR Software 1 1

•

•

• • •

•

• •

•

•

•

•

•

HP 3PAR ODM Software for Veritas VxVM: an application for customers using Veritas VxVM/DMP with HP 3PAR storage devices. It provides HP 3PAR device definitions and a message catalog. HP 3PAR NULL INF for SCSI Enclosure Device: HP 3PAR NULL driver for Windows Server 2003 is used to add WHQL signature for Windows Server 2003 environments so that the storage system can be recognized without triggering an “unknown device” message. HP 3PAR Dynamic Optimization Software allows you to improve the performance of virtual volumes without interrupting access. Use this feature to avoid over provisioning for peak system usage by optimizing the layout of your virtual volumes. With HP 3PAR Dynamic Optimization you can change virtual volume parameters, RAID levels, set sizes, and disk filters by associating the virtual volume with a new CPG. You can also use this feature to analyze your entire system and automatically correct space usage imbalances in the system. Virtual volume and physical disk capacity are analyzed and rebalanced for optimal performance. This feature requires an HP 3PAR Dynamic Optimization license. To learn more about HP 3PAR Dynamic Optimization, see “Enhanced Storage Applications” (page 53). HP 3PAR Adaptive Optimization Software gives you a much higher degree of control over disk usage by reserving your faster and more expensive storage resources for the data that is frequently accessed and relegating your slower and less expensive drives to storing data that is only occasionally accessed. To learn more about HP 3PAR Adaptive Optimization, see “Enhanced Storage Applications” (page 53). HP 3PAR Peer Motion Software: allows you to load balance I/O workloads across HP 3PAR storage systems at will, perform technology refresh seamlessly, cost-optimize asset lifecycle management, and lower technology refresh capital expenditure. HP 3PAR Priority Optimization Software: allows you to set service level targets/guarantees to application workload so that applications are guaranteed the I/O quality of service and any interference between the application can be controlled. HP 3PAR Virtual Copy Software: allows you to take instant virtual copy snapshots of existing volumes. It uses copy-on-write technology so that virtual copies consume minimal capacity. Virtual copies are presentable to any host with read and write capabilities. In addition, virtual copies can be made from other virtual copies, providing flexibility for test, backup, and business-intelligence applications. To learn more about virtual copies, see “Virtual Copy Snapshots” (page 46). HP 3PAR Remote Copy Software: a host-independent, array-based data mirroring solution that enables affordable data distribution and disaster recovery for applications. With this optional utility, you can copy virtual volumes from one system to a second system. HP 3PAR Remote Copy is configured and controlled with the HP 3PAR Command Line Interface. For more information about the HP 3PAR Remote Copy application, see the HP 3PAR Remote Copy Software User’s Guide. HP 3PAR Peer Persistence Software: enables federation of HP 3PAR storage systems present at geographically separated data centers and allows applications to move and fail over from one site to another without any application downtime. HP 3PAR GeoCluster Software: simplifies and automates disaster recovery, reducing administration time and improving recovery time objectives (RTOs) in Windows-based environments. HP 3PAR Virtual Domains Software: is used for access control. Virtual Domains allow you to limit the access of users to only subsets of volumes and hosts in an HP Storage System and ensures that virtual volumes associated with a specific domain are not exported to hosts outside of that domain. To learn more about domains, see “HP 3PAR Virtual Domains” (page 24). HP 3PAR Virtual Lock Software: enforces the retention period of any volume or copy of a volume. To learn more about Virtual Lock, see “Enhanced Storage Applications” (page 53).

•

•

•

•

•

•

•

•

•

•

•

12

Overview

•

HP 3PAR System Reporter Software: allows you to monitor performance, create charge back reports, and plan storage resources for systems using either a standard Web browser or the HP 3PAR System Reporter Excel client. HP 3PARInfo Software: a command line utility that provides useful information on the volume mapping between the host and the array. HP 3PAR Management Plug-in for VMware: a Web application that is deployed as a VI Client plug-in. A VI Client plug-in is an external Web application that is configured with the vCenter Server in such a way that VI Clients are able to display their pages. HP 3PAR Management Plug-In for VMware vCenter displays virtual volume mapping for easy identification of HP 3PAR volumes used by virtual machines and datastores. HP 3PAR Recovery Manager for VMware vSphere Software: provides virtual copy management of HP 3PAR virtual copies and recovery of virtual machines and datastores. HP 3PAR VASA Provider Software: enables VMware vCenter to see the capabilities of HP 3PAR storage LUNs and their properties such as RAID level, Thinly Provisioned or fully provisioned virtual volumes, and replication state automatically. HP 3PAR VAAI Plug-in Software for VMware vSphere Software: enables SCSI primitives that allow HP 3PAR storage systems to take advantage of several VMware virtual machine operations at the meta data level to improve performance. HP 3PAR VMware Site Replication Manager (SRM) Adapter Software: Site Replication Adapter integrated with VMware SRM and HP 3PAR Remote Copy Software provides organizations the ability to build resilient virtual and cloud computing infrastructures, protect applications at a lower cost, and recover data more quickly and efficiently than with traditional disaster recovery solutions. HP 3PAR Recovery Manager for Oracle Software: a highly efficient solution for automatically creating and managing hundreds of application-consistent, reservationless, point-in-time snapshots of Oracle and Oracle RAC databases for rapid online recovery. HP 3PAR Recovery Manager for SQL Server Software: is specifically designed to integrate with Microsoft VSS to provide a simple, efficient and highly scalable solution for backup and recovery of SQL Server environments. HP 3PAR Recovery Manager Software intelligently creates, manages, and presents time-consistent snapshot images of SQL Server databases for non-disruptive backup, rapid application recovery, and data sharing. HP 3PAR VSS Provider for Microsoft Windows Software is a server application bundled with HP 3PAR Recovery Manager for Microsoft SQL Software. VSS coordinates the actions of database readers like the HP 3PAR Recovery Manager backup application, database writers like Microsoft Exchange and SQL Server, and providers that create shadow copies. HP 3PAR Recovery Manager for Microsoft Exchange Software: is specifically designed to integrate with Microsoft VSS to provide a simple, efficient and highly scalable solution for backup and recovery of Microsoft Exchange environments. HP 3PAR Recovery Manager intelligently creates, manages, and presents time-consistent snapshot images of Microsoft Exchange databases for non-disruptive backup, rapid application recovery, and data sharing.

• •

• •

•

•

•

•

•

•

HP 3PAR Software Licensing Requirements
The following table provides licensing information for all HP 3PAR software products and features.

HP 3PAR Software

13

Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms
HP 3PAR Software HP 3PAR Access Guard Software HP 3PAR Full Copy Software HP 3PAR Rapid Provisioning Software License Required? Licensing Y Supported Hardware Platforms

Licensed as part of the HP 3PAR OS HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage Licensed as part of the HP 3PAR OS HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage Licensed as part of the HP 3PAR OS HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage Licensed as part of the HP 3PAR OS HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage Licensed as part of the HP 3PAR OS; HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR also available standalone StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage Part of the HP 3PAR OS HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage HP 3PAR StoreServ 10000 Storage and HP 3PAR StoreServ 7000 Storage HP 3PAR StoreServ 10000 Storage and HP 3PAR StoreServ 7000 Storage

Y

Y

HP 3PAR Autonomic Y Groups Software HP 3PAR Thin Copy Y Reclamation Software HP 3PAR Command N Line Interface Software HP 3PAR Web Services API Software N

Part of the HP 3PAR OS

HP 3PAR Autonomic Y Rebalance Software

Licensed as part of the HP 3PAR StoreServ 7000 Storage OS Software Suite and the HP 3PAR StoreServ 10000 Storage OS Software Suite Licensed as part of the HP 3PAR StoreServ 7000 Storage OS Software Suite and the HP 3PAR StoreServ 10000 Storage OS Software Suite; also available standalone Licensed as part of the HP 3PAR StoreServ 7000 Storage OS Software Suite and the HP 3PAR StoreServ 10000 Storage OS Software Suite; also available standalone Licensed as part of the HP 3PAR StoreServ 7000 Storage OS Software Suite and the HP 3PAR StoreServ 10000 Storage OS Software Suite; also available standalone Licensed as part of the HP 3PAR StoreServ 7000 Storage OS Software Suite and the HP 3PAR StoreServ 10000 Storage OS Software Suite; also available standalone Licensed as part of the HP 3PAR StoreServ 7000 Storage OS Software Suite and the HP 3PAR

HP 3PAR System Tuner Software

Y

HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage

HP 3PAR Thin Provisioning Software

Y

All HP 3PAR storage systems

HP 3PAR Thin Conversion Software

Y

HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage

HP 3PAR Thin Y Persistence Software

HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage

HP 3PAR EVA to Y 3PAR Online Import Software 14 Overview

HP 3PAR StoreServ 7000 Storage, HP 3PAR StoreServ 10000 Storage

Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms (continued)
HP 3PAR Software License Required? Licensing StoreServ 10000 Storage OS Software Suite; also available standalone HP 3PAR Management Console Software HP 3PAR Host Explorer Software N Part of the HP 3PAR OS HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage Supported Hardware Platforms

N

Licensed as part of the HP 3PAR StoreServ 7000 Storage OS Software Suite and the HP 3PAR StoreServ 10000 Storage OS Software Suite; also available standalone

HP 3PAR SmartStart N Software HP 3PAR Service Processor Software HP 3PAR Virtual Copy Software N Y

Part of the HP 3PAR StoreServ 7000 HP 3PAR StoreServ 7000 Storage OS Software Suite Part of the HP 3PAR OS All HP 3PAR storage systems

Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 7000 Replication Suite and StoreServ 10000 Storage, HP 3PAR StoreServ the HP 3PAR StoreServ 10000 7000 Storage Storage Replication Suite; also available standalone Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 7000 Replication Suite and StoreServ 10000 Storage, HP 3PAR StoreServ the HP 3PAR StoreServ 10000 7000 Storage Storage Replication Suite; also available standalone Licensed as part of the HP 3PAR StoreServ 7000 Storage OS Software Suite and HP 3PAR StoreServ 10000 Storage OS Software Suite; also available standalone Licensed as part of the HP 3PAR StoreServ 7000 Storage OS Software Suite and HP 3PAR StoreServ 10000 Storage OS Software Suite; also available standalone Licensed as part of the HP 3PAR StoreServ 7000 Storage Replication Suite and the HP 3PAR StoreServ 10000 Storage Replication Suite; also available standalone Licensed as part of the HP 3PAR StoreServ 7000 Storage Data Optimization Suite v2, the HP 3PAR StoreServ 10000 Storage Data Optimization Suite v2, and the HP 3PAR Optimization Suite; also available standalone Licensed as part of the HP 3PAR StoreServ 7000 Data Optimization Suite v2, the HP 3PAR StoreServ 10000 Data Optimization Suite v2, HP 3PAR StoreServ 7000 Storage, HP 3PAR StoreServ 10000 Storage

HP 3PAR Remote Copy Software

Y

HP 3PAR Persistent Ports Software

Y

HP 3PAR Persistent Cache Software

Y

HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage

HP 3PAR Peer Y Persistence Software

HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage

HP 3PAR Dynamic Optimization Software

Y

HP 3PAR StoreServ 7000 Storage, HP 3PAR StoreServ 10000 Storage

HP 3PAR Adaptive Optimization Software

Y

HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage

HP 3PAR Software

15

Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms (continued)
HP 3PAR Software License Required? Licensing and the HP 3PAR Optimization Suite; also available standalone HP 3PAR Peer Motion Software Y Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 7000 Data Optimization StoreServ 10000 Storage, HP 3PAR StoreServ Suite v2 and the HP 3PAR StoreServ 7000 Storage 10000 Data Optimization Suite v2; also available standalone Licensed as part of HP 3PAR Virtual Copy Software Available standalone Licensed as part of the HP 3PAR StoreServ 7000 Security Suite and the HP 3PAR StoreServ 10000 Security Suite; also available standalone Licensed as part of the HP 3PAR StoreServ 7000 Security Suite and the HP 3PAR StoreServ 10000 Security Suite; also available standalone HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage All HP 3PAR storage systems HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage Supported Hardware Platforms

HP 3PAR mySnapshot Software HP 3PAR Policy Manager Software HP 3PAR Virtual Domains Software

Y

Y Y

HP 3PAR Virtual Lock Software

Y

HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage

HP 3PAR System Reporter Software

Y

Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 7000 Reporting Suite and StoreServ 10000 Storage, HP 3PAR StoreServ the HP 3PAR StoreServ 10000 7000 Storage Reporting Suite; also available standalone for other hardware platforms Licensed as part of the HP 3PAR HP 3PAR StoreServ 7000 Storage and HP 3PAR StoreServ 7000 Reporting Suite and StoreServ 10000 Storage the HP 3PAR StoreServ 10000 Reporting Suite; also available standalone for other hardware platforms Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 7000 Application Suite for StoreServ 10000 Storage, HP 3PAR StoreServ VMware and the HP 3PAR StoreServ 7000 Storage 10000 Application Suite for VMware; also available standalone for other hardware platforms Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 7000 Application Suite for StoreServ 10000 Storage, HP 3PAR StoreServ VMware and the HP 3PAR StoreServ 7000 Storage 10000 Application Suite for VMware; also available standalone for other hardware platforms Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 7000 Application Suite for StoreServ 10000 Storage, HP 3PAR StoreServ VMware and the HP 3PAR StoreServ 7000 Storage 10000 Application Suite for VMware; also available standalone for other hardware platforms

HP 3PARInfo Software

Y

HP 3PAR Management Plug-in for VMware

Y

HP 3PAR Recovery Manager for VMware vSphere Software

Y

HP 3PAR VASA Provider Software

Y

16

Overview

Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms (continued)
HP 3PAR Software HP 3PAR Host Explorer for VMware vSphere License Required? Licensing Y Supported Hardware Platforms

Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 7000 Application Suite for StoreServ 10000 Storage, HP 3PAR StoreServ VMware and the HP 3PAR StoreServ 7000 Storage 10000 Application Suite for Exchange; also available standalone for other hardware platforms Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 7000 Application Suite for StoreServ 10000 Storage, HP 3PAR StoreServ Oracle and the HP 3PAR StoreServ 7000 Storage 10000 Application Suite for Oracle; also available standalone for other hardware platforms Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 7000 Application Suite for StoreServ 10000 Storage, HP 3PAR StoreServ SQL and the HP 3PAR StoreServ 7000 Storage 10000 Application Suite for SQL; also available standalone for other hardware platforms Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 7000 Application Suite for StoreServ 10000 Storage, HP 3PAR StoreServ SQL, the HP 3PAR StoreServ 7000 7000 Storage Application Suite for Exchange, the HP 3PAR StoreServ 10000 Application Suite for SQL, and the HP 3PAR StoreServ 10000 Application Suite for Exchange; also available standalone for other hardware platforms Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 7000 Application Suite for StoreServ 10000 Storage, HP 3PAR StoreServ SQL and HP 3PAR StoreServ 10000 7000 Storage Application Suite for Exchange; also available standalone for other hardware platforms Part of the HP 3PAR StoreServ 7000 HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR OS Software Suite and the HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ StoreServ 10000 OS Software Suite; 7000 Storage also available standalone Available standalone HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage HP 3PAR StoreServ 7000, HP 3PAR StoreServ 7450, and HP 3PAR StoreServ 10000

HP 3PAR Recovery Y Manager for Oracle Software

HP 3PAR Recovery Manager for SQL Server Software

Y

HP 3PAR Recovery Y Manager for Microsoft Exchange Software

HP 3PAR VSS Y Provider for Microsoft Windows Software

HP 3PAR Multipath N Software for Microsoft Windows 2003 HP 3PAR ODM 3.1 Software for IBM MPIO and Veritas VxDMP N

HP 3PAR ODM N Software for Veritas VxVM HP 3PAR NULL INF N for SCSI Enclosure Device HP 3PAR Data Encryption Y

Available standalone

Available standalone

Licensed as part of the HP 3PAR StoreServ 7000 OS, the HP 3PAR StoreServ 7450 OS, and the HP 3PAR StoreServ 10000 OS

HP 3PAR Software

17

2 HP 3PAR Storage System Users
User Accounts
In order to access an HP 3PAR storage system you must have a user account. Each HP 3PAR OS user is assigned a role, and each role is assigned a set of rights. The roles and rights assigned to the user determine which tasks the user can perform with a system. Assign roles to users based on the tasks you intend the users to perform. Eight roles are defined in the HP 3PAR OS. See Table 2 (page 18) for a description of each role. There are four standard roles: • • • • • • • • Browse Edit Super Service Create Basic Edit 3PAR AO 3PAR RM

There are also four extended roles:

There is no functional difference between standard and extended roles. The extended roles define a set of rights optimized for users with specialized or restricted tasks. For example, assigning a user the Create role allows the user to create virtual volumes and other objects but does not allow the user to remove virtual volumes. To maintain greater control over your system, assign users roles with the minimum set of rights they need to perform their tasks. To view a list of roles and all of the rights assigned to each role, see the HP 3PAR Command Line Interface Administrator’s Manual. User management tasks can be performed with both the HP 3PAR CLI Software and the HP 3PAR Management Console Software. Refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help for instructions on how to perform user management tasks. Table 2 HP 3PAR OS User Roles
User Roles Browse Edit Rights Assigned to Roles Rights are limited to read-only access. Rights are granted to most operations. For example, creating, editing, and removing virtual volumes and other objects. Rights are granted to all operations. Rights are limited to operations required to service the system. Allows limited access to user information and user group resources. Rights are limited to creating objects. For example, virtual volumes, CPGs, hosts, and schedules. Rights are similar to the Edit role. For example, creating and editing virtual volumes and other objects. The rights to remove objects are more restricted for the Basic Edit role than the Edit role.

Super Service

Create Basic Edit

18

HP 3PAR Storage System Users

Table 2 HP 3PAR OS User Roles (continued)
User Roles 3PAR AO 3PAR RM Rights Assigned to Roles Rights are limited to internal use by HP for Adaptive Optimization operations. Rights are limited to internal use by HP for Recovery Manager operations.

Local User Authentication and Authorization
Users accessing the HP 3PAR storage system with the HP 3PAR CLI client or Secure Shell (SSH) connections are authenticated and authorized directly on the system. These users are referred to as local users. The information used to authenticate and authorize a local user is stored on the system. For instructions on creating a local user, refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help.

LDAP User Authentication and Authorization
An LDAP user is authenticated and authorized using information from a Lightweight Directory Access Protocol (LDAP) server. If multiple systems are configured to use the same LDAP server, a user that can access one system can access all systems with the role and rights assigned to the LDAP group. Local user roles and rights are associated with an individual, LDAP user roles and rights are the same for all members of the group. If you want to authenticate and authorize LDAP users with different roles, you must create an LDAP group for each role. For detailed information about LDAP users and LDAP connections, see “Lightweight Directory Access Protocol” (page 20). For instructions on setting up an LDAP connection, refer to the HP 3PAR Command Line Interface Administrator’s Manual.

Domain User Access
A domain user is a user with access to a specific domain. Local users belonging to a system using HP 3PAR Virtual Domains Software are domain users. In addition to the user’s roles and rights, a domain users’ activities are also limited to the domains to which they have access. A domain user’s assigned user role is applicable only within the domain to which the user has access. For detailed information about virtual domains and domain users, see “HP 3PAR Virtual Domains” (page 24). For instructions on creating a domain user, refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help. NOTE: Virtual domains require an HP 3PAR Virtual Domains Software license. For additional information about the license, see “HP 3PAR Software” (page 9).

Local User Authentication and Authorization

19

3 Lightweight Directory Access Protocol
Overview
The Lightweight Directory Access Protocol (LDAP) is a standard protocol for communication between LDAP clients and LDAP directory servers. Data is stored as a directory hierarchy by the server and clients add, modify, search, or remove the data. The data can be organized using standard schemas understood by clients and servers from different vendors or by an application-specific schema used only by a particular vendor or application. The HP 3PAR OS contains an LDAP client that can be configured to use an LDAP server for authentication and authorization of system users. In an environment where there are multiple systems configured to use the same LDAP server in the same way, a single user with access to one system server can access all of the environment’s systems with the same role. Accessing objects on systems configured to use HP 3PAR Virtual Domains Software requires access to the domain in which those objects reside. The configuration of domains may differ from one system installation to the next. This results in differing levels of access over objects based on mapping between the LDAP configuration and the individual system’s domain configuration. The HP 3PAR LDAP client is designed to work with various LDAP servers and schemas for data organization. However, only use with the Active Directory LDAP directory implementation is currently supported. Configuring the HP 3PAR OS to use LDAP can only be performed with the HP 3PAR Command Line Interface (CLI). Refer to the HP 3PAR OS CLI Administrator’s Manual for instructions on how to perform these tasks. NOTE: • • At the current time, the OpenLDAP directory implementation is also available, however, on a limited basis. Check with your local HP service representative for updates on availability. All LDAP related tasks are performed with the HP 3PAR Command Line Interface (CLI).

Active Directory
Active Directory is an implementation of LDAP directory services by Microsoft for use in Windows environments. An Active Directory server is both an LDAP and Kerberos server. When set up for SASL binding (see “SASL Binding” (page 22)), the Active Directory server and Kerberos server are used for both authorization and authentication of users.

OpenLDAP
OpenLDAP is an open source implementation of LDAP directory services developed by the OpenLDAP Project. OpenLDAP includes a server, client library, and tools that are available for a wide variety of operating systems. Different schemas can be used for user and group information with OpenLDAP. For example, the Posix schema is typically used for user and group information in Linux/Unix systems.

LDAP Users
Users created with the HP 3PAR CLI who access the system using HP 3PAR CLI clients, or with SSH, are authenticated and authorized directly on the system. These users are referred to as local users. An LDAP user is similar to a local user; however, an LDAP user is authenticated and authorized using information from an LDAP server. During authentication, if a user name is not recognized as a local user, that user’s name and password are checked on the LDAP server. The local user’s authentication data takes precedence

20

Lightweight Directory Access Protocol

over the user’s LDAP authentication data. User names not associated with local user names are authenticated using LDAP data. Additionally for local users, during authentication, the password supplied by the user must match the password assigned when that user was initially created or modified. The rights assigned to the user during authorization are the same rights associated with the user role assigned when that user was initially created or modified. See “HP 3PAR Storage System Users” (page 18) for additional information about user roles and rights. LDAP users can access the system using the same methods as a local users, although some user account creation and modification operations are unavailable. Do not create local and LDAP users with the same name. If local and LDAP users have the same name it can cause confusion about where access is controlled. For instructions on using LDAP with the storage system, refer to the HP 3PAR Command Line Interface Administrator’s Manual. Another key difference between local users and LDAP users is that a local user’s rights within the system are assigned on a case-by-case basis. An LDAP user’s rights are dependent on that user’s group association. In other words, groups are assigned specific rights within the system and an individual LDAP user’s rights are dependent upon group membership.

LDAP Server Data Organization
LDAP server data consists of user information, which includes the user’s group associations. Data can be previously existing data used for user account information, or can be data created for specific use with systems. Data on the LDAP server can be organized in two different ways: • • As a list of groups associated with each user. As a list of users associated with each group.

The form in which data is organized is dependent on the type of LDAP server used and the tools used to maintain the data. Programs such as ldp.exe, which is a downloadable Windows Support Tool available from Microsoft, and ldapsearch, which is available for many UNIX and Linux systems, can be used to view data entries in the LDAP server. This can be useful when configuring the HP 3PAR LDAP client with your LDAP server as discussed in the Managing User Accounts and Connections chapter in the HP 3PAR Command Line Interface Administrator’s Manual.

LDAP and Domains
LDAP is also available for systems using virtual domains for access control. As discussed in “HP 3PAR Virtual Domains” (page 24), the Domains facility enables finer grain rights over system objects such as volumes and hosts. Accessing objects on systems configured to use virtual domains requires rights in the domain in which those objects reside. Because the configuration of Domains can differ within an HP storage system, or from one server to another (in configurations with multiple servers), a user can have differing rights between domains in a single system, or across multiple systems. As discussed earlier in “LDAP Users” (page 20), LDAP users must follow a process of authentication and authorization in order to gain access to the system. With Domains in use, in addition to authentication with the system, LDAP users must also be authorized to access domains set up within the system. For additional information, see “LDAP Authentication and Authorization” (page 22). For instructions on setting up LDAP users on systems using Domains, see Chapter 4, Managing User Accounts and Connections in the HP 3PAR Command Line Interface Administrator’s Manual. NOTE: Virtual domains require an HP 3PAR Virtual Domains Software license. For additional information about the license, see “HP 3PAR Software” (page 9).

LDAP Server Data Organization

21

LDAP Authentication and Authorization
As stated earlier, the user’s user name is first checked against the authentication data stored on the local system. If the user’s name is not found, the LDAP authentication and authorization process proceeds as follows: • • • • • The user’s user name and password are used to authenticate with the LDAP server. The user’s group memberships are determined with the data on the LDAP server. A list of groups is compared against mapping rules that specify each group’s associated roles. If virtual domains is in use, the user’s group is mapped to a domain. The user is assigned a system user role, and a domain if domains are in use.

Authentication
Users are authenticated with the LDAP server using a bind operation. The bind operation simply authenticates the HP 3PAR OS LDAP client to the LDAP server. This authentication process is required for all systems using LDAP, including systems using Domains. Several binding mechanisms are supported by the HP 3PAR OS LDAP client. NOTE: The binding mechanism you can use is dependent on your LDAP server configuration.

Simple Binding
With simple binding, the user’s user name and password are sent to the LDAP server in plain text and the LDAP server determines if the submitted password is correct. Simple binding is not recommended unless a secure connection to the LDAP server is established with Secure Sockets Layer (SSL) or Transport Layer Security (TLS).

SASL Binding
In addition to simple binding, the HP 3PAR OS LDAP client also supports the PLAIN, DIGEST-MD5, and GSSAPI SASL binding mechanisms. Generally, DIGEST-MD5 and GSSAPI are more secure methods of authentication as user passwords are not sent to the LDAP server. • The PLAIN mechanism is similar to simple binding where the user’s user name and password are sent directly to the LDAP server for authentication. As with simple binding, the PLAIN mechanism should only be used if there is a secure connection (SSL or TLS) to the LDAP server. The GSSAPI mechanism obtains a ticket from the Kerberos server which validates the user’s identity. That ticket is then sent to the LDAP server for authentication. With the DIGEST-MD5 mechanism, the LDAP server sends the HP 3PAR OS LDAP client one-time data that is encrypted by the client and returned to the server in such a way that the client proves it knows the user's password without having to send the user's password.

• •

Authorization
Once an LDAP user has been authenticated, the next stage is authorization. The authorization process determines what a user is allowed to do within the system. As discussed in “LDAP Users” (page 20), an LDAP user’s role is tied to that user’s group membership, and a user can belong to multiple groups. Each group has an assigned role, see“HP 3PAR Storage System Users” (page 18) for information about user roles. The HP 3PAR OS LDAP client performs group-to-role mapping using the following four mapping parameters: • • • •
22

super-map service-map edit-map browse-map

Lightweight Directory Access Protocol

Each group to which a user is a member is compared against the mapping parameters. Mapping occurs sequentially with a group first compared to the super-map parameter. If no match is made, the group is then compared with the service-map parameter, and so on. For example, if a match is made for group A with the super-map parameter, the user belonging to group A is authorized with Super rights to the system. With this process, a user can be authenticated, but not authorized if no group membership exists. In this case, the user is subsequently denied access to the system.

Authorization on Systems Using Virtual Domains
As discussed in “Authorization” (page 22), a user’s group association determines that user’s role within the system. On systems using virtual domains, this process is taken one step further where the user’s groups are mapped to system domains. Therefore, the user’s role within a specific group is carried over to the domain(s) mapped to that group. For instructions on authorizing LDAP users on systems using Domains, see Chapter 4, Managing User Accounts and Connections in the HP 3PAR OS CLI Administrator’s Manual. The group-to-domain mapping relationship: • • • • LDAP User 1 has membership to Group B. Group-to-role mapping determines that Group B uses the Edit role. Group-to-domain mapping establishes a match between Group B and Domain A. LDAP User 1 has Edit role access to all objects in Domain A.

LDAP Authentication and Authorization

23

4 HP 3PAR Virtual Domains
Overview
When initially setting up the HP 3PAR storage system, the system administrator creates and assigns users with roles and rights in the system. You can create, modify, and remove a user’s access to HP 3PAR Virtual Domains Software in the system with both the HP 3PAR Command Line Interface (CLI) and the HP 3PAR Management Console. Refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help for instructions on how to perform these tasks. NOTE: Virtual domains require an HP 3PAR Virtual Domains Software license. For additional information about the license, see “HP 3PAR Software” (page 9). In addition to the inherent security provided by this hierarchical user structure, finer grain access control of the system can optionally be achieved through the implementation of virtual domains. Domains allow an administrator to create up to 1,024 domains, or spaces, within an system, where each domain is dedicated to a specific application. A subset of the system users have varying rights over the domains. The use of domains can be useful in scenarios where a single system is used to manage data from several different independent applications (Figure 2 (page 24)). Figure 2 Single System Managing Multiple Independent Applications

Each domain allows users with varying levels of accessibility to domain objects. A domain is made of Common Provisioning Groups (CPGs), hosts, and Remote Copy groups. Domains contain derived domain objects such as Virtual Volumes (VVs), Logical Disks (LDs), and volume exports (VLUNs). Because objects are domain-specific, domain users cannot accidentally or deliberately export VVs to hosts outside of their assigned domain. Virtual domains can be grouped into autonomic groups that can be managed as one domain. If you have a group of domains that require the same administrative procedures, it is easier to group those domains into an autonomic group and mange them together. NOTE: Remote Copy requires an HP 3PAR Remote Copy Software license. For additional information about the license, see “HP 3PAR Software” (page 9).

Domain Types
When using domains for access control, accessibility to basic objects and derived objects is limited by a user’s role and domain assignment. For more information about roles and rights, see, “HP 3PAR Storage System Users” (page 18).

24

HP 3PAR Virtual Domains

Domain Type
The first tier of access control is the domain to which a subset of a system’s objects belong. The objects can be assigned to a specific domain, or have no domain association. • • The no domain contains objects that do not belong to any specified domains. For example, objects in an existing system that did not previously use domains do not belong to any domains. specified domains are created by the domain administrator and contain objects specific to that domain. Only users with rights over that domain can work with those objects. For example, User A in Domain A can access objects in Domain A, but not in Domain B. Multiple specified domains can be created. Users with the Super role can browse and edit objects in all domains.

Users and Domain Rights
By default, users with the Super role have rights over the entire system. Only these users and users belonging to the Edit user role in the all domain can create and edit CPGs, hosts, Remote Copy groups, and assign CPGs and hosts to specified domains. Additionally, these users have access to all domains and their objects. When setting up domains and users in the system, some users may require access to multiple domains with different user rights. virtual domains allow users access to more than one domain and a single user can be assigned different user roles in each domain. NOTE: A user having rights over multiple domains cannot perform intra-domain operations between objects in different domains. Users can have access to a maximum of 32 domains.

Object and Domain Association Rules
Domains contain basic objects such as CPGs, hosts, and Remote Copy groups, and derived objects such as VVs, LDs, and VLUNs. Objects and their associations with domains must adhere to the following rules: • • • Objects derived from a CPG inherit the domain of that CPG. VVs can only be exported to hosts belonging to the VVs’ domain. A VLUN inherits the domain of the VV and host from which the VLUN was exported.

The Default and Current Domains
When a user is initially created, the user is able access objects in all assigned domains. The user can browse or edit objects depending on the user’s assigned user role. For example, an Edit user assigned to Domains A and B can view and work on objects in both Domains A and B. However, if it is apparent that a specific domain will receive the majority of attention from a user, virtual domains provide the ability for administrators to set a default domain for that user.

Users and Domain Rights

25

An HP 3PAR CLI user’s default domain is the domain the user accesses at the start of each CLI session. For example, if you have Edit rights to Domains A and B and your default domain has been set to Domain A, each time you start a new CLI session you will view and work with only objects in Domain A. The user’s default domain can be set and reset at any time by the administrator. If you are using the HP 3PAR Management Console, the user selects which domain to connect to and there is no default domain, and no domain session. To change domains, HP 3PAR Management Console users simply select a new domain from a menu of available domains.

26

HP 3PAR Virtual Domains

5 Ports and Hosts
Overview
The HP 3PAR storage system sees a host as a set of initiator port WWNs (World Wide Names) or iSCSI Names. Hosts that are physically connected to ports on the system are automatically detected. The Fibre Channel port WWNs and iSCSI port iSCSI Names are displayed by the user interfaces. You can also add new WWNs or iSCSI Names for unestablished host paths and assign them to a host before they are physically connected. These WWNs or iSCSI Names do not need to be associated with target ports on the system controller nodes. This allows for plug-and-play functionality that avoids the need for manual reconfiguration after connecting new hosts. For instructions on modifying system ports and host configurations, see the HP 3PAR Command Line Interface Administrator’s Manual and HP 3PAR Management Console Online Help. Fibre Channel over Ethernet (FCoE) connectivity is supported on HP 3PAR StoreServ 10000 Storage systems and HP 3PAR StoreServ 7000 Storage systems through the use of Converged Network Adapters (CNA). CNA ports can be configured to be used as FCoE or iSCSI ports. A virtual volume can be exported, or made accessible, to one or more hosts. The host sees the exported virtual volume as a LUN connected to one or more ports. Once the virtual volume is exported to a host, the host can send requests to the LUN. See “Virtual Volumes” (page 42) for more information about virtual volumes and exporting virtual volumes. For instructions on exporting virtual volumes, see the HP 3PAR Command Line Interface Administrator’s Manual and HP 3PAR Management Console Online Help. Persistent ports (also known as virtual ports) allow HP 3PAR storage system host-facing ports to assume the identity of partner ports that are automatically designated by the system. For Fibre Channel and Fibre Channel over Ethernet (FCoE) ports, this is achieved through the use of N_Port ID Virtualization (NPIV). For more information about persistent ports and NPIV, see the HP 3PAR Command Line Interface Administrator’s Manual. NOTE: See the HP 3PAR Implementation Guides for recommended practices and detailed configuration information about using your specific host devices with the system.

About Ports
System controller nodes can use Fibre Channel, Gigabit Ethernet, iSCSI, and Serial Attached SCSI (SAS) , and Fibre Channel over Ethernet (FCoE) ports to connect the storage system to your network, host computers, storage system components, and to other systems. You can use the HP 3PAR CLI and the HP 3PAR Management Console to view port information and modify port settings. For instructions on viewing and modifying port configurations, see the HP 3PAR Command Line Interface Administrator’s Manual and HP 3PAR Management Console Online Help. • Fibre Channel Ports Systems use Fibre Channel ports to connect controller nodes to hosts and drive cages and drive enclosures. On HP 3PAR StoreServ 7000 Storage systems, FC ports are designated for host connection and Remote Copy use only. For information about controller nodes and drive cages, see “HP 3PAR Storage System Hardware” (page 61). • iSCSI Ports Systems use iSCSI ports to connect controller nodes to hosts. For information about controller nodes, see “HP 3PAR Storage System Hardware” (page 61). NOTE: The iSCSI ports in a system controller node can only be used to connect the system to a host computer.

Overview

27

•

Gigabit Ethernet Ports Systems use Gigabit Ethernet ports to enable the Remote Copy over IP (RCIP) solution, and to connect the primary and secondary systems in the Remote Copy pair. For information about Remote Copy, see the HP 3PAR Remote Copy Software User’s Guide.

•

Serial Attached SCSI (SAS) Ports Systems use SAS ports to connect controller nodes to drive enclosures. SAS ports are supported only on HP 3PAR StoreServ 7000 Storage systems. For information about controller nodes and drive enclosures, see “HP 3PAR Storage System Hardware” (page 61).

•

Fibre Channel over Ethernet (FCoE) Ports Systems use FCoE ports in order to run Fibre Channel as a connectivity protocol directly over Ethernet, in parallel with regular IP traffic (as opposed to using Ethernet exclusively for TCP/IP networks and Fibre Channel exclusively for storage area networks (SANs). Converged Network Adapters (CNA) support multiple storage connectivity protocols on a single HBA; CNA ports can be configured to be used as an FCoE or iSCSI port. For information about configuring FCoE ports, see the HP 3PAR Command Line Interface Administrator's Manual.

Port Location Formats
The HP 3PAR CLI and the HP 3PAR Management Console display the controller node Fibre Channel, iSCSI, and Gigabit Ethernet port locations in the following format: ::. For example: 2:4:1. • Node: Valid node numbers are 0-7 depending on the number of nodes installed in your system. When viewing a system from the rear of a cabinet:

◦ ◦ ◦ ◦
•

F-Class nodes are numbered 0-3 from top to bottom. T-Class nodes are numbered 0-7 from left to right, top to bottom. StoreServ 10000 nodes are numbered 0-7 from left to right, bottom to top. StoreServ 7000 nodes are numbered 0–1 or 0–3 from bottom to top.

Slot: Valid node slot numbers are 0-9 depending on the class of nodes installed in your system.

◦ ◦ ◦ ◦
•

F-Class slots are numbered 0-6 from left to right. Slot 6 is reserved for the RCIP Ethernet port. T-Class slots are numbered 0-6 from left to right. Slot 6 is reserved for the RCIP Ethernet port. StoreServ 10000 slots are numbered 0-9 from left to right, bottom to top in a node in the lower chassis. In the upper chassis slots are numbered 0-9 from left to right, top to bottom. HP 3PAR StoreServ 7000 Storage systems have one slot per node. Slot 0 is reserved for onboard SAS, slot 1 is reserved for onboard FC, and slot 2 is reserved for the HBA.

Port: Valid node port numbers are 1-4 for all Host Bus Adapters (HBA).

◦ ◦ ◦ ◦
28 Ports and Hosts

F-Class ports are numbered from top to bottom. T-Class ports are numbered from top to bottom. StoreServ 10000 ports are numbered from bottom to top in a node in the lower chassis. In the upper chassis ports are numbered from top to bottom. StoreServ 7000 ports are numbered 1–4 from left to right in a node in the lower node enclosure. In the upper node enclosure, slots are numbered 1–4 from right to left.

For information about controller nodes, see “HP 3PAR Storage System Hardware” (page 61). For more information about physical port and HBA locations, see the Physical Planning Manual for your system model.

Port Target, Initiator, and Peer Modes
The system controller node ports operate in different modes. Depending on the type of port, the port may operate in target, initiator, or peer mode. Fibre Channel ports use the following firmware mode settings: • • • • • • Target mode for ports that connect to hosts and receive commands from those hosts. Initiator mode for ports that connect to the system physical disks and send commands to those disks. Initiator mode for Remote Copy over FC (RCFC). Target mode for ports that connect to hosts and receive commands from those hosts. Peer mode for Ethernet ports, used for Remote Copy over IP (RCIP). Target mode for ports that connect to hosts and receive commands from those hosts.

iSCSI ports use the following firmware mode settings: Gigabit Ethernet ports use the following firmware mode setting: Fibre Channel over Ethernet (FCoE) ports use the following firmware mode settings: Use the HP 3PAR CLI or the HP 3PAR Management Console to view or change the current port mode settings. For instructions on viewing or changing mode settings, see the HP 3PAR Command Line Interface Administrator’s Manual and HP 3PAR Management Console Online Help.

Active and Inactive Hosts
An active host is a host that is connected to a system port and recognized by the HP 3PAR OS. Under normal operation, an active host may have a number of volumes exported to it and therefore the host has access to those volumes. An inactive host is a host that is known to the HP 3PAR OS but is not recognized as being connected to any system port at the moment. This may be because the host is currently disconnected from the system port, or due to an error condition such as link failure or because the host is offline. When a host on a system port becomes inactive for any reason, the following happens: 1. The HP 3PAR OS recognizes that the host is missing on the port and changes the state of the host from active to inactive. 2. The VLUN becomes a template again until the host returns. 3. If and when the host reappears on the same port, The VLUNs are converted from a template to active again. They do not remain in an active state while the host is unavailable.

Adding and Removing Hosts
The HP 3PAR OS administration tools allow you to create, modify, and remove Fibre Channel and iSCSI host paths and their properties. When creating a new host, you can either create a host with or without assigning WWNs or iSCSI Names. A virtual volume that is exported to a host is exported to all the WWNs that make up the host. If you need to export virtual volumes to particular host computer WWNs or iSCSI Names, you can create separate hosts on the system and assign each WWN or iSCSI Name to its own host. Use the HP 3PAR CLI or the HP 3PAR Management Console to create, modify, and remove hosts. Hosts can be grouped into autonomic groups that can be managed as one host. If you have a group of hosts that require the same administrative procedures, it is easier to group those hosts into an autonomic group and mange them together. For instructions on creating, modifying, and
Port Target, Initiator, and Peer Modes 29

removing hosts, see the HP 3PAR Command Line Interface Administrator’s Manual and HP 3PAR Management Console Online Help.

Managing Host Personas
Host personas are a set of behaviors that permit hosts connected to FC or iSCSI ports on the system to deviate from the default host behavior. By assigning a persona to a host, multiple host types that require distinct customized responses can share a single system port. For example, hosts running Windows, Linux, and AIX operating systems can all connect to the same system port. This simplifies connecting hosts to the system and reduces management costs related to complex host connections. A host persona defines the custom responses for certain iSCSI commands and does not affect any of the FC port settings. Host personas are tied to the host name and identified by the host persona number. You can set the host persona number when the host is created or modify it later. Use the HP 3PAR CLI commands or the HP 3PAR Management Console to display, create, modify, and remove host personas. See the HP 3PAR Command Line Interface Administrator’s Manual or the HP 3PAR Management Console Online Help for instructions on displaying, creating, modifying, and removing host personas. Different host personas have different functions and support different host operating systems. The specific host persona is designated by the host persona number. Depending on the selected host persona number, the following additional capabilities are supported: • • UARepLun - Sends a unit attention when the LUN list changes due to adding or removing VLUNs. ALUA - Enables the Asymmetric Logical Unit Access (ALUA) command and asymmetric state change unit attention when path counts change due to adding or removing ports in the host's definition. VolSetAddr - Enables HPUX Volume Set Addressing (VSA). SoftInq - Enables inquiry data formats for hosts such as Egenera and NetApp. NACA - Enables Normal Auto Contingent Allegiance (NACA) bit for AIX. SESLun - Enables iSCSI Enclosure Services (SES) LUN ID 254 for Host Explorer agent support. SubLun - Enables SCSI two-level LUN addressing.

• • • • •

NOTE: Each host connected to the system must use a host persona with the iSCSI Enclosure Services LUN (SESLun) enabled, or the Host Explorer agent cannot communicate with the system. Table 3 (page 30) describes the specific functionality for each host persona number. For a list of supported host operating systems, go to the Single Point of Connectivity Knowledge (SPOCK) website http://www.hp.com/storage/spock. Table 3 Host Personas
Persona Number 1 2 6 7 8 9 Persona Name Generic Generic-ALUA Generic-Legacy HPUX-Legacy AIX-Legacy Egenera Host Operating System Additional Capabilities

Linux, Windows, and Solaris UARepLun, SESLun Linux, Windows, and Solaris UARepLun, ALUA, SESLun Linux, Windows, and Solaris None HP-UX AIX Egenera, NetApp VolSetAddr NACA SoftInq

30

Ports and Hosts

Table 3 Host Personas (continued)
Persona Number 10 1 1 Persona Name NetApp ONTAP VMware Host Operating System Data ONTAP Linux and Windows Additional Capabilities SoftInq SubLun, ALUA

NOTE: • • • Only the Generic, Generic-ALUA, and Generic-Legacy personas are supported for iSCSI connections. The NetApp host operating system requires unique WWNs for hosts in an FC fabric. A host device must use either iSCSI or Fibre Channel connections. Mixed ports on a single device is not supported.

Legacy Host Personas
A legacy host persona is a host persona that simulates the behavior of a port persona. Prior to the HP 3PAR Operating System 2.3.1 release, port personas were used on system ports. Port personas are no longer supported. Use the HP 3PAR CLI commands or the HP 3PAR Management Console to convert your legacy host personas to new host personas. See the HP 3PAR Command Line Interface Administrator’s Manual or the HP 3PAR Management Console Online Help for instructions on converting your legacy host personas.

The Host Explorer Software Agent
The HP 3PAR Host Explorer Software agent is a program that runs on a host connected to an HP storage system. The Host Explorer agent runs as a service on Windows and as a daemon on Linux and Solaris operating systems. No license is required to use the Host Explorer agent. The Host Explorer agent communicates with the system over an FC or iSCSI connection and enables the host to send detailed host configuration information to the system. The information gathered from the Host Explorer agent is visible for uncreated hosts and assists with host creation and diagnosing host connectivity issues. When a host is created on the system, unassigned WWNs or iSCSI names are presented to the system. Without the Host Explorer agent running on the attached hosts, the system is unable to determine which host the WWN or iSCSI names belongs to and you must manually assign each WWN or iSCSI name to a host. With Host Explorer agents running, the system automatically groups WWNs or iSCSI names for the host together, assisting with creating the host. The Host Explorer agent collects the following information and sends it to the system: • • • • Host operating system and version. Fibre Channel and iSCSI HBA details. Multipath driver and current multipath configuration. Cluster configuration information.

You can install the Host Explorer agent from the HP 3PAR Host Explorer CD. For instructions on installing and using the Host Explorer agent, see the HP 3PAR Host Explorer User’s Guide. For a list of supported host operating systems, go to the Single Point of Connectivity Knowledge (SPOCK) website http://www.hp.com/storage/spock.

Legacy Host Personas

31

6 Chunklets
Overview
Physical disks are divided into chunklets. When a physical disk is admitted to the system it is divided into chunklets that become available to the system. Some chunklets are used by logical disks and other chunklets are designated as spares to hold relocated data during a disk failure or during maintenance procedures. Creating, moving, and removing chunklets and spares can only be performed with the HP 3PAR Command Line Interface (CLI). Refer to the HP 3PAR Command Line Interface Administrator’s Manual for instructions on how to perform these tasks. Viewing chunklets and spares can be performed with both the HP 3PAR Command Line Interface (CLI) and the HP 3PAR Management Console. Refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help for instructions on how to perform this task.

Physical Disk Chunklets
Physical disks are divided into chunklets. Each chunklet occupies contiguous space on a physical disk. Space on a physical disk is allocated as follows: • • On F-Class and T-Class systems all chunklets are 256 MB. On StoreServ 10000 and StoreServ 7000 systems all chunklets are 1 GB. 256 MB of data is reserved for the table of contents (TOC), which contains the internal description of the system. The TOCs on all physical disks in the system contain the same information. 4 MB are reserved for diagnostic use, 2 MB beginning after the TOC and 2 MB from the end of the disk logical block address. One or more chunklets are allocated as spares. These spare chunklets are used to hold relocated data during disk failures and during maintenance procedures. Spares are created during installation and setup. Any chunklet can be reserved as a spare, but the system setup script selects those chunklets as close to the end of the physical disk’s logical block space as possible. The remainder of the disk can be used for logical disks.

• •

•

Spare Chunklets
Some chunklets are identified as spares when the system is first set up at installation. Data from other chunklets is moved or reconstructed onto these spare chunklets in response to a chunklet or disk failure or when a drive magazine needs to be serviced. This initial spare storage totals the amount of storage in a single drive magazine, using the largest size physical disks. How spare chunklets work: • When a connection is lost to a physical disk or a physical disk fails, all future writes to the disk are automatically written to a logging logical disk until the physical disk comes back online or until the time limit for logging is reached. Logging disk space is allocated when the system is set up. This does not apply to RAID 0 chunklets which have no fault-tolerance. If the time limit for logging is reached, or if the logging logical disk becomes full, the relocation of chunklets on the physical disk to free chunklets designated as spares starts automatically. Free chunklets are any chunklets that are not already allocated for use by logical disks.

•

32

Chunklets

• •

For automatic relocations, the system uses up a maximum of one disk worth of chunklets per system node. When selecting a target chunklet for relocation, the system attempts to identify a local spare chunklet, a local free chunklet, a remote spare chunklet, and then finally a remote free chunklet.

NOTE: Local chunklets are chunklets on disks whose primary path is connected to a node that owns the logical disk containing the chunklets being relocated. • • If the system uses up its free or spare chunklets for relocation, an alert is generated. Once the spare and free chunklets are used up, automatic relocation no longer occurs. In most cases, some data redundancy is lost. The system also generates an alert.

Spare Chunklets

33

7 Logical Disks
Overview
A Logical Disk (LD) is a collection of physical disk chunklets arranged as rows of RAID sets. Each RAID set is made up of chunklets from different physical disks. Logical disks are pooled together in Common Provisioning Groups (CPGs) which allocate space to virtual volumes. Creating CPGs maps out the data layout parameters for the creating logical disks. Logical disks are created automatically by the system when virtual volumes are created from CPGs. The RAID type, space allocation, growth increments and other logical disk parameters can be set when you create a CPG or modified after creating a CPG. For information about CPGs, see “Common Provisioning Groups” (page 39).

Logical Disks and Common Provisioning Groups
Creating a Common Provisioning Group (CPG) establishes a virtual pool of logical disks that can grow on demand. When you create virtual volumes, the system creates all underlying logical disks for you automatically. Volumes associated with a CPG draw logical disk space from the virtual pool as needed, allocating space on demand. As the volumes that draw from a CPG require additional storage, the system automatically creates additional logical disks and adds them to the pool. Once you create a CPG, you can add and remove logical disks. You can also specify advanced logical disk parameters when creating CPGs. This allows you to exercise a greater degree of control over how the system creates logical disks within the CPG. NOTE: Creating virtual copies or snapshots requires the HP 3PAR Virtual Copy Software license. For more information, see “HP 3PAR Software” (page 9)

Logical Disk Types
The following logical disk types provide storage space to virtual volumes: • • User logical disks provide user storage space to virtual volumes. The user space contains the user data and is exported as a LUN to the host. Snapshot data logical disks provide the storage space for snapshots or virtual copies. The snapshot space contains copies of user data that changed since the previous snapshot of the volume was created. Snapshot administration logical disks provide the storage space for snapshot administration. The administration space is used to track changes to the volume since the previous snapshot was created.

•

The system sets aside logical disks for logging, for preserved data, and for system administration. These logical disks are multi-level logical disks with three way mirrors for enhanced redundancy and performance. The following logical disk types are created by the system: • logging logical disks are RAID 10 logical disks that are used to temporarily hold data during disk failures and disk replacement procedures. Logging logical disks are created by the system during the initial installation and setup of the system. Each controller node in the system has a 60 GB logging LD. preserved data logical disks are RAID 10 logical disks used to hold preserved data. Preserved data logical disks are created by the system during the initial installation and setup of the storage system. The size of the preserved data LD is based on the amount of data cache in the system.

•

When multiple disk failures during write operations leave data suspended in cache memory, the system temporarily preserves this data by writing it to a preserved data logical disk. By doing so, the system clears the data cache and prevents it from locking up and leading to wider system
34 Logical Disks

failures. When the destination logical disks become available again, the system automatically writes the preserved data from the preserved data logical disks to the destination logical disks. • Administration volume logical disks provide storage space for the admin volume, a single volume created on each system during installation. The admin volume is used to store system administrative data such as the system event log.

RAID Types
The 3PAR storage system supports the following RAID types: • • • • RAID 0 RAID 10 (RAID 1) RAID 50 (RAID 5) RAID Multi-parity (MP)

RAID 0
On a RAID 0 logical disk, data is striped across rows of chunklets on different physical disks. The number of chunklets in a RAID 0 set is known as the set size, which is always 1 for a RAID 0 logical disk. The number of sets in a row is known as the row size. The system accesses data from a RAID 0 logical disk in step sizes, where the step size is the number of contiguous bytes that the system accesses before moving on to the next chunklet. A RAID 0 logical disk improves performance but provides no fault-tolerance. Figure 3 (page 35) shows a RAID 0 logical disk with a set size of 1 and a row size of 3: Figure 3 Data Striped Across Chunklets on a RAID 0 Logical Disk

RAID 1 and 10
On a RAID 10 logical disk, data is striped across RAID 1 (or mirrored) sets. A RAID 1 set is made up of two or more chunklets that contain the same data. The chunklets in each set are distributed across different physical disks, which may be located in different drive magazines or even different drive cages. The number of chunklets in a RAID 1 set is the set size (or mirror depth). The number of sets in each row is the row size. The maximum row size is 40. The system accesses data from a RAID 10 logical disk in step sizes. A step size is the number of contiguous bytes that the system accesses before moving on to the next chunklet. A RAID 1 set can function with the loss of all but one of the chunklets in the set. Figure 4 (page 36) shows a RAID 10 logical disk with a set size of 2 and a row size of 3 in two rows:

RAID Types

35

Figure 4 Data Striped Across RAID 1 Sets on a RAID 10 Logical Disk

RAID 5 and 50
On a RAID 50 logical disk, data is striped across rows of RAID 5 sets. A RAID 5 set, or parity set, must contain at least three chunklets. A RAID 5 set with three chunklets has a total of two chunklets of space for data and one chunklet of space for parity. RAID 5 set sizes with between 3 and 9 chunklets are supported. The data and parity steps are striped across each chunklet in the set. The chunklets in each RAID 5 set are distributed across different physical disks, which may be located in different drive magazines or even different drive cages. The number of sets in a row is the row size. The system accesses the data from a RAID 50 logical disk in step sizes. The step size is the number of contiguous bytes that the system accesses before moving on to the next chunklet. A RAID 5 set can function with the loss of any one of the chunklets in the set. Figure 5 (page 37) shows a RAID 50 logical disk with a set size of 3, and 2 sets in 1 row:

36

Logical Disks

Figure 5 Data Striped Across RAID 5 Sets on a RAID 50 Logical Disk

RAID Multi-Parity
On a RAID Multi-Parity (MP) or RAID 6 logical disk, data is striped across rows of RAID MP sets. A RAID MP set, or double-parity set, must contain at least 8 chunklets. A RAID MP set with 8 chunklets has a total of 6 chunklets of space for data and 2 chunklets of space for parity. RAID MP set sizes of 8 and 16 chunklets are supported. The data and parity steps are striped across each chunklet in the set. The chunklets in each RAID MP set are distributed across different physical disks, which may be located in different drive magazines or even different drive cages. The number of sets in a row is the row size. The system accesses the data from a RAID MP logical disk in step sizes. The step size varies and is dependent on the size of the RAID MP set. A RAID MP set can function with the loss of any two of the chunklets in the set. The following example shows 2 RAID MP sets in one row, the second set is shown below the first set. In the first RAID MP set in the following example, p0 is the parity step for data steps F, L, M, Q, T, V, and X. Figure 6 (page 38) shows a RAID MP logical disk with a set size of 8, and 2 sets in 1 row:

RAID Types

37

Figure 6 Data Striped Across RAID MP Sets on a RAID MP Logical Disk

Logical Disk Size and RAID Types
A logical disk is a collection of physical disk chunklets arranged as rows of RAID sets. On F-Class and T-Class systems all chunklets are 256 MB. On StoreServ 10000 and StoreServ 7000 systems all chunklets are 1 GB. All systems round up so that the logical disk size is divisible by the size of one chunklet, either 1 GB or 256 KB. The total size of the logical disk is determined by the number of data chunklets in the RAID set. • • A RAID 0 or RAID 1 logical disk must contain at least one chunklet. A RAID 5 set, or parity set, must contain at least three chunklets. A RAID 5 set with three chunklets has a total of two chunklets of space for data and one chunklet of space for parity. The system default is four chunklets: three for data and one for parity (3+1). A RAID MP set (RAID 6), or double-parity set, must contain at least 8 chunklets. RAID MP set sizes of 8 and 16 chunklets are supported. The system default is 8 chunklets. A RAID MP set with 8 chunklets has a total of 6 chunklets of space for data and 2 chunklets of space for parity (6+2). On StoreServ 10000 and StoreServ 7000 systems, RAID 6 set sizes of (4+2), (6+2), (8+2), (10+2), and (14+2) are supported.

•

NOTE: The system also rounds up the size of virtual volumes, CPGs, and CPG growth increments to be divisible by the size of one chunklet, either 1 GB or 256 KB.

38

Logical Disks

8 Common Provisioning Groups
Overview
A common provisioning group (CPG) creates a virtual pool of logical disks that allows virtual volumes to share the CPG's resources and allocates space on demand. You can create fully-provisioned virtual volumes and thinly-provisioned virtual volumes (TPVVs) that draw space from the CPG's logical disk pool. CPGs enable fine-grained, shared access to pooled logical capacity. Instead of pre-dedicating logical disks to volumes, the CPG allows multiple volumes to share the buffer pool of logical disks. For example, when a TPVV is running low on user space, the system automatically assigns more capacity to the TPVV by mapping new regions from logical disks in the CPG associated with that TPVV. As a result, any large pockets of unused but allocated space are eliminated. Fully provisioned virtual volumes cannot create user space automatically and the system allocates a fixed amount of user space for the volume. By default, a CPG is configured to auto-grow new logical disks when the amount of available logical disk space falls below a configured threshold. The initial buffer pool of logical disks starts off at a fraction of the exported virtual capacity of mapped volumes and automatically grows over time as required by application writes. Creating CPGs can be performed with both the HP 3PAR Command Line Interface (CLI) and the HP 3PAR Management Console. Refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help for instructions on how to perform these tasks. For more information about TPVVs and fully-provisioned virtual volumes, see “Virtual Volumes” (page 42).

Precautions and Planning
A Common Provisioning Group (CPG) creates a virtual pool of logical disks that allows up to 4,095 volumes to share the CPG's resources and allocate space on demand. However, CPGs still require careful planning and monitoring to prevent them from becoming so large that they set off the system's built-in safety mechanisms. These safety mechanisms are designed to prevent a CPG from consuming all free space on the system, but they only work properly on systems that are planned carefully and monitored closely. The maximum number of CPGs per system is 2,048.

Growth Increments, Warnings, and Limits
You can create several types of volumes that draw space from the CPG's logical disk pool as needed. When creating a CPG, set a growth increment and an optional growth warning and growth limit to restrict the CPG's growth and maximum size. It is important to plan the CPG's growth increment, growth warning, and growth limit carefully and then continue to monitor the CPG closely over time. CAUTION: Use caution in planning CPGs. The system does not prevent you from setting growth warnings or growth limits that exceed the amount of currently available storage on a system. When volumes associated with a CPG use all space available to that CPG, any new writes to TPVVs associated with the CPG will fail and/or snapshot volumes associated with the CPG may become invalid or stale. Under these conditions, some host applications do not handle write failures gracefully and may produce unexpected failures. NOTE: By default, the growth warning and growth limit are set to none, which effectively disables these safety features.

Overview

39

Growth Increment
As volumes that draw from a CPG require additional storage, the system automatically creates additional logical disks according to the CPG's growth increment. The default and minimum growth increments vary according to the number of controller nodes in the system. Table 4 Default and Minimum Growth Increments
Number of nodes 2 4 6 8 Default 32 GB 64 GB 96 GB 128 GB Minimum 8 GB 16 GB 24 GB 32 GB

In some it may be desirable to use a larger growth increment. However, a smaller growth increment can prevent the CPG from automatically allocating too much space. The optimal growth increment depends on several factors: • • • • • Total available space on your system. Nature of the data running on the system. Number of CPGs in the system. Number of volumes associated with those CPGs. Anticipated growth rate of the volumes associated with the CPGs.

NOTE: The system may round up when creating logical disks to support virtual volumes and CPGs, resulting in a discrepancy between the user-specified size or growth increment and the actual space allocated to logical disks created by the system. For a detailed discussion of this issue, see “Logical Disk Size and RAID Types” (page 38).

Growth Warning
When the size of the volumes that draw from a CPG reach the CPG’s growth warning, the system generates an alert to notify you of the CPG's increasing size. This safety mechanism provides the opportunity to take early action that may prevent snapshot volumes associated with the CPG from experiencing failures, causing host or application write failures, and exhausting all free space on the system. When setting growth warnings for CPGs, it is critical to consider the number of CPGs on the system, the total capacity of the system, and the projected rate of growth for all volumes on the system. The storage system does not prevent you from setting growth warnings that exceed the total capacity of the system. For example, on a 3 TB system you can create two CPGs that each have a growth warning of 2 TB. However, if both CPGs grow at a similar rate, it is possible for the volumes that draw from the CPGs to consume all free space on the system before either CPG reaches the growth warning threshold.

Growth Limit
If the volumes that draw from a CPG are allowed to reach the CPG’s growth limit, the system prevents them from allocating additional space. This safety mechanism stops a runaway application or volume from exhausting all free space available to the CPG and causing invalid (stale) snapshot volumes and/or new application write failures for volumes associated with that CPG. However, the storage system does not prevent you from setting growth limits that exceed the total capacity of the system. For example, on a 4 TB system it is possible to create a CPG with a 5 TB growth limit. Likewise, it is possible to create five CPGs, each with a 2 TB growth limit, etc.
40 Common Provisioning Groups

In addition, volumes that draw from a CPG can only use the space available to that CPG based on the CPG's logical disk parameters. For example, if you create a CPG that only uses logical disks that belong to controller node 0, when the virtual volumes that draw from a CPG have filled up all space available to that CPG based on it's logical disk parameters, the following will happen: • • New writes to any TPVVs mapped to that CPG will return write failures. Snapshot volumes mapped to the CPG may become invalid (stale), subject to the virtual copy policy associated with the base volume. For base volumes with a no stale snapshots virtual copy policy, new writes to the base volume will result in write failures. For base volumes with a stale snapshots virtual copy policy, new writes will cause snapshot volumes to become invalid (stale). If the volumes that draw from a CPG reach the CPG’s growth limit, the system generates additional alerts to notify you that all logical capacity for the CPG has been consumed.

• •

System Guidelines for Creating CPGs
Use the following guidelines to ensure maximum performance and optimal reliability in the volumes supported by those logical disks: • • • • • • • To provide the highest availability, chunklets in the same RAID set should be from different drive cages, and then different drive magazines. Physical disks with fewer used chunklets should be used before physical disks with more used chunklets. Chunklets in the same row should be from different physical disks. In other words, a physical disk should not appear twice in the same row. Chunklets should belong to a disk that is connected through the primary path to the logical disk’s owner node. The system should use as many physical disks as possible. The load on all physical disks should be balanced. The system should use the largest possible row size.

NOTE: The system may round up when creating logical disks to support virtual volumes and CPGs, resulting in a discrepancy between the user-specified size or growth increment and the actual space allocated to logical disks created by the system. For more information, see “Logical Disk Size and RAID Types” (page 38).

Volume Types Associated with CPGs
Depending on the products and features licensed for use on the system, after creating a CPG you can create two types of base volumes that draw from the CPG's logical disk pool: Thinly Provisioned Virtual Volumes (TPVVs) and fully provisioned virtual volumes. These two volume types draw from the pool in different ways. For information about TPVVs, see “Thinly-provisioned Virtual Volumes” (page 8). For information about fully provisioned virtual volumes, see “Fully-provisioned Virtual Volumes” (page 8).

System Guidelines for Creating CPGs

41

9 Virtual Volumes
Overview
Volumes draw their resources from Common Provisioning Groups (CPGs), and volumes are exported as Logical Unit Numbers (LUNs) to hosts. Virtual volumes are the only data layer visible to hosts. You can create physical copies or virtual copy snapshots of virtual volumes for use if the original base volume becomes unavailable. Before creating virtual volumes, you must first create CPGs to allocate space to the virtual volumes. For information about CPGs, see “Common Provisioning Groups” (page 39). You can organize volumes into autonomic groups that can be managed as one volume. If you have a group of volumes that require the same administrative procedures, it is easier to group those volumes into an autonomic group and manage them together. Creating virtual volumes can be performed with both the HP 3PAR Command Line Interface (CLI) and the HP 3PAR Management Console. Refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help for instructions on how to perform these tasks. For the maximum number of virtual volumes and virtual volume copies that can be created with your specific system configuration, go to the Single Point of Connectivity Knowledge (SPOCK) website http://www.hp.com/storage/spock. NOTE: Creating Thinly Provisioned Virtual Volumes (TPVVs) requires the HP 3PAR Thin Provisioning Software license. Creating virtual copies requires the HP 3PAR Virtual Copy Software license. For more information, see “HP 3PAR Software” (page 9).

Virtual Volume Types
There are three types of virtual volumes: • • • Fully provisioned virtual volumes Thinly Provisioned Virtual Volumes (TPVVs) Administrative Volumes

Administrative volumes are created by the system and are for system usage only. Fully provisioned virtual volumes and TPVVs have three separate data components: • User space is the area of the volume that corresponds to the logical disk regions in the CPG available to the host. The user space contains the user data and is exported as a LUN to the host. Snapshot space, also known as copy space, is the area of the volume that corresponds to logical disk regions in the CPG containing copies of user data that changed since the previous snapshot of the volume was created. The snapshot space contains the copy data. Administration space, also known as admin space, is the area of the volume that corresponds to logical disk regions in the CPG that track changes to the volume since the previous snapshot was created. The administration space contains pointers to copies of user data in the snapshot space. Administration space is managed by the system, not with the tools you use to manage user and snapshot space.

•

•

You can increase the size of volumes, the amount of user space, and the amount of snapshot space for volumes as the requirements increase. If the user space and snapshot space use all available space, the Virtual Copy feature’s copy-on-write operation will fail. To avoid running out of user space, use TPVVs to automatically draw more user space from a CPG. The HP 3PAR OS automatically reclaims unused snapshot space from TPVVs and fully provisioned virtual volumes and returns the space to the logical disks.
42 Virtual Volumes

For greater administrative flexibility, you can provision the virtual volume’s user space and snapshot space from the same or different CPGs. If the virtual volume’s user space and snapshot space are on different CPGs, the user space remains available to the host if the CPG containing the snapshot space becomes full. To save time by not repeating tasks, you can create many identical virtual volumes at one time. If your system is accessible by an OpenStack cloud, you may see volumes with prefixes indicating that the volumes were created through the OpenStack cloud. Volumes created through the OpenStack cloud use the OpenStack Volume (OSV) and OpenStack Snapshot (OSS) prefixes.

Administrative Volumes
As part of installation and setup process, a volume called the administrative volume, or admin volume, is created on the system. This volume is used by the system to store administrative data such as the system event log. The admin volume is always named admin. This volume cannot be exported and cannot be removed from the system. CAUTION: It is strongly recommended that you do not tamper with the admin volume.

Fully-provisioned Virtual Volumes
A fully provisioned virtual volume is a volume that uses logical disks that belong to a logical disk pool known as a Common Provisioning Group (CPG). Unlike Thinly Provisioned Virtual Volumes (TPVVs), fully provisioned virtual volumes have a set amount of user space allocated in the system for user data. They require the system to reserve the entire amount of space required by the fully provisioned virtual volume whether or not the space is actually used. The fully provisioned virtual volume size is fixed, and the size limit is 16 TB. You can set snapshot space allocation limits and usage warnings to help manage the growth of snapshot space.

Thinly Provisioned Virtual Volumes
With an HP 3PAR Thin Provisioning Software license, you can also create Thinly Provisioned Virtual Volumes (TPVVs). A TPVV uses logical disks that belong to a logical disk pool known as a Common Provisioning Group (CPG). TPVVs associated with the same CPG draw user space from that pool as needed, allocating space on demand in one chunklet increments beginning with either 256 MB or 1 GB per controller node. As the volumes that draw space from the CPG require additional storage, the system automatically creates additional logical disks and adds them to the pool until the CPG reaches the user-defined growth limit that restricts the CPG’s maximum size. The TPVV volume size limit is 16 TB. TPVVs are capable of responding to host write requests by allocating space on demand in one chunklet increments beginning with either 256 MB or 1 GB per controller node. These allocations are adaptive since subsequent allocations are based on the rate of consumption for previously allocated space. For example, if a TPVV is initially allocated 256 MB per node but then consumes that space in less than sixty seconds, the next allocation becomes 512 MB per node. However, if the initial 256 MB per node is consumed more slowly, the next allocation increment remains at 256 MB per node. Under this provisioning scheme, the maximum allocation increment is 1 GB per controller node supporting the TPVV. In addition, as the TPVV reaches either its exported size or its user-defined

Virtual Volume Types

43

allocation limit, the system allows allocation of an additional 128 MB per node beyond these limits in order to ensure that the exported TPVV address space is usable. CAUTION: Use of allocation limits is recommended to prevent consumption of physical raw capacity beyond a tolerable limit. However, you should exercise caution when setting the value of the allocation limit. Upon reaching the allocation limit, any new writes to TPVVs will fail and/or snapshot volumes associated with the CPG may become invalid. Under this condition, some host applications do not handle write failures gracefully and may produce unexpected failures. CAUTION: Do not allow the volumes that draw from a CPG to exceed the CPG’s growth limit. Doing so can invalidate snapshot volumes. Refer to “Common Provisioning Groups” (page 39) for additional cautions and recommendations.

TPVV Warnings and Limits
The TPVV volume size limit is 16 TB. When creating a TPVV, you have the option to set an allocation warning threshold and an allocation limit threshold. • allocation warning threshold: For volumes capable of allocating space on demand, the user-defined threshold at which the system generates an alert. This threshold is a percentage of the volume's virtual size, the size that the volume presents to the host. allocation limit threshold: For volumes capable of allocating space on demand, the user-defined threshold at which writes fail, preventing the volume from consuming additional resources. This threshold is a percentage of the volume's virtual size, the size that the volume presents to the host.

•

When setting TPVV allocation warnings and allocation limits, you must take into account the space to be consumed by both the volume’s user data and the snapshot data. The total amount of snapshot space consumed by a TPVV and its snapshots includes the data written to the base volume and the data written to the snapshots. The size of the data written to the snapshots equals the total writes to the base volume since the oldest existing read-only (RO) snapshot was created. When deciding on the allocation warning and allocation limit thresholds for a TPVV, you can use an estimate of the maximum write rate to compute the snapshot data growth rate. • • • If there are no RO snapshots, and the volume is not a physical copy or used for Remote Copy, use the maximum write rate as the growth rate. If there are RO snapshots, or if the volume is not a physical copy or used for Remote Copy, use twice the maximum write rate as the growth rate. Set the allocation warning and limit thresholds based on the growth rate and how much advance warning you require before the volume reaches its limit and writes fail.

Use the following formula to generate the allocation warning threshold:

where the value of n is as follows: • • for a TPVV without read-only snapshots, and when that TPVV is not a physical copy or used for Remote Copy, n=1. for a TPVV with read-only snapshots, or when that TPVV is a physical copy or used for Remote Copy, n=2.

44

Virtual Volumes

For example, if a 1 TB TPVV with read-only snapshots has a maximum write rate of 1 GB per day and you would like 30 days warning prior to that TPVV reaching the allocation limit, use the following calculation for the allocation warning percentage:

Virtual Volume Online Conversion
You can convert existing fully provisioned virtual volumes to Thinly Provisioned Virtual Volumes and you can convert Thinly Provisioned Virtual Volumes to fully provisioned virtual volumes on the array without disrupting normal storage system operations and without requiring changes to any host applications that access the virtual volumes. If a TPVV is using most of its allocated storage capacity, you might choose to convert the volume to a fully provisioned volume in order to increase its storage capacity and allow for continued growth of the volume. When a TPVV reaches approximately 80% of capacity, the incremental benefit of capacity savings versus accelerating performance is weighted towards performance. In addition, converting volumes from Thinly Provisioned to fully provisioned can free up Thinly Provisioned capacity for other TPVVs. Similarly, if a fully provisioned virtual volume's storage space is largely unused, you might choose to convert it to a thinly provisioned volume in order to save storage space. Converting remote copy virtual volumes and virtual volumes that contain snapshots is not supported. You can, however, convert virtual volumes with snapshots and create a new virtual volume with a new WWN that contains the original logical disks and snapshots. Converting virtual volumes can be performed with both the HP 3PAR Command Line Interface (CLI) and the HP 3PAR Management Console. Refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help for instructions on how to perform these tasks. Converting volumes from thin to full requires the HP 3PAR Dynamic Optimization license. Converting volumes from full to thin requires the HP 3PAR Dynamic Optimization Software license and HP 3PAR Thin Provisioning Software license. For more information, see “HP 3PAR Software” (page 9).

Physical Copies
A physical copy is a full copy of a volume. A physical copy duplicates all the data from one original base volume to another volume called the destination volume. Any changes to either volume causes them to lose synchronization with each other, which is corrected by resynchronizing the two volumes as described in the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help. No special license is required to create a physical copy of a volume. Physical copies can be created and managed in groups to reduce the number of management tasks. You can create a consistent group of physical copies from a list of virtual volumes, and group physical copies into autonomic groups that are managed as one physical copy. A physical copy can only be made from a volume with enough free space to accommodate writes to that volume during the physical copy operation. In addition, the destination volume must meet the following conditions: • • • It must have snapshot space associated with it. It must have at least as much user space as the volume being copied. It must not be exported to a host.

Virtual Volume Online Conversion

45

For the maximum number of physical copies that can be created with your specific system configuration, go to the Single Point of Connectivity Knowledge (SPOCK) website http:// www.hp.com/storage/spock. NOTE: If the base volume and destination volume are both Thinly Provisioned Virtual Volumes (TPVVs), only the space that is actually used is copied. See “Overview” (page 7) for additional information on TPVVs.

Virtual Copy Snapshots
A virtual copy is a snapshot of another virtual volume. You can make virtual copies of base volumes, physical copies, or other virtual copies. Virtual copies are created using copy-on-write techniques available only with the HP 3PAR Virtual Copy Software license. Unlike a physical copy which duplicates the entire base volume, a virtual copy only records the changes to the original volume. This allows an earlier state of the original volume to be recreated by starting with the current state and rolling back all of the changes that have been made since the virtual copy was created. The system allows you to make a maximum of 500 virtual copies of a base volume. Up to 256 virtual copies can be read/write copies. The maximum number of virtual copies that can be created on a system is determined by the system configuration. For the maximum number of virtual copies that can be created with your specific system configuration, go to the Single Point of Connectivity Knowledge (SPOCK) website http://www.hp.com/storage/spock. Virtual copies can be created and managed in groups to reduce the number of management tasks. You can create a consistent group of virtual copies from a list of virtual volumes, and group virtual copies into autonomic groups that are managed as one virtual copy. NOTE: Virtual copies are consistent at the virtual volume level, but not at the host filesystem or application level. In other words, virtual copies only preserve the data that was written on the source virtual volume before the virtual copy is created. Virtual copies do not preserve the data that is resident within the application or filesystem buffers and is not flushed to disk before the virtual copy is created. HP offers optional HP 3PAR Recovery Manager DBA software to enable application-level consistent snapshots. Contact HP Customer Support for more information.

Virtual Copy Snapshot Relationships
Base volumes are always read/write, but virtual copies can be read/write or read-only. The rules that govern the relationships between a base volume and its virtual copies are based upon the difference between read/write and read-only volumes. Read-only and read/write copies must alternate. You can only make a read-only copy of a read/write volume, and you can only make a read/write copy of a read-only volume. Since base volumes are always read/write, you can only create read-only copies of a base volume. See Figure 7 (page 46) for an example of alternating read-only and read/write virtual copy relationships. Figure 7 Alternating Read-only and Read/Write Virtual Copies

46

Virtual Volumes

See Figure 8 (page 47) for a more complex example of the possible relationships between a parent base volume and its virtual copies. Figure 8 Base Volume and Virtual Copy Relationships

Copy-on-Write Function
When a virtual volume or snapshot’s source volume is written to, the copy-on-write function preserves the data that is to be overwritten. The data is copied to the snapshot space associated with the original virtual volume before the write operation is completed, and a pointer in the administration space points to the copied data. See Figure 9 (page 47) for an example of a sequence of snapshots. Figure 9 Snapshot Tree

In the figure above: • • S0 is the first virtual copy made of BaseVV. S2 is the most recent virtual copy.
Virtual Copy Snapshots 47

• •

Each copy tracks changes made to BaseVV from its own creation date until the next snapshot is made. S1_0 can be created at any time after S1 is created.

The relationships between the virtual copies derived from a base volume can be represented as a tree. In the example in Figure 9 (page 47), the base volume BaseVV is the starting point. In this example, each new virtual copy of the original has its name incremented by 1. Each copy of a copy has an additional level added to its name: in this example, the first copy of S1 is S1_0, and a copy of S1_0 is S1_0_0. Unlike the automatic snapshots created for physical copies, these snapshots are not assigned names by the system. NOTE: The naming convention used in the example above is recommended, but it is not enforced by the system. You can name each virtual volume and virtual copy at the time of creation. The following rules are enforced by the system when you create a snapshot: • The tree grows in alternating layers of read/write and read-only snapshots. You can only make a read-only copy of a read/write volume, and you can only make a read/write copy of a read-only volume. A maximum of 256 read/write virtual copies can be made from one read-only virtual volume. A maximum of 500 virtual copies can be made from one base volume. A virtual volume cannot be deleted if a child copy of it exists. For example, S1 cannot be removed unless S1_0, S1_0_0, and S1_0_1 are deleted first.

• • •

Copy-of and Parent Relationships
In the example in Figure 9 (page 47), there are two different tree structures: the solid arrows show the copy-of relationships, and the dashed arrows show the parent relationship. For example, S0 is a read-only copy of BaseVV, and S1 is the parent of S0. The copy-of relationship simply shows that the snapshot was created by copying another virtual volume. The parent relationship refers to the internal organization of the administration space. The parent volume contains information needed to reconstruct the snapshot represented by the child volume. A parent volume can have a creation date after that of its child if the parent volume was modified. The parent relationship is useful for two reasons: • Understanding the performance consequences of virtual copies. The tree representing the parent relationship shows the look-up paths in the administration space needed to reconstruct the earlier state of the virtual volume. The farther away a virtual copy is from the base volume, the longer it will take to retrieve it. If a snapshot is expected to be kept in use for a long time, consider making a physical copy instead of a virtual copy. Understanding which virtual copies become stale if the administration space is full and the copy-on-write data cannot be written. A stale snapshot is one that cannot be completely recreated because the most recent changes will not be included. The current snapshot and all its children become stale when a write fails. For example, if there is no space to write the copy-on-write data when a host writes to S1_0, then S1_0, S1_0_1, and S1_0_0 become stale.

•

Exporting Virtual Volumes
Virtual volumes are the only data layer component visible to hosts. You export a virtual volume to make it available to one or more hosts by creating an association between the volume and a logical unit number (LUN). The characteristics of this association are defined when you create a Virtual Volume-LUN pairing (VLUN). A VLUN is a pairing between a virtual volume and a LUN expressed as either a VLUN template or an active VLUN. For the maximum number of VLUNs supported for each host with your specific system configuration, go to the Single Point of Connectivity Knowledge (SPOCK) website http://www.hp.com/storage/spock.
48 Virtual Volumes

Exporting virtual volumes can be performed with both the HP 3PAR Command Line Interface (CLI) and the HP 3PAR Management Console. Refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help for instructions on how to perform this task.

VLUN Templates and Active VLUNs
A VLUN template sets up an association between a virtual volume and a LUN-host, LUN-port, or LUN-host-port combination by establishing the export rule. When you create a VLUN template, if the current system state meets the conditions established by the VLUN template, that template is immediately applied to create one or more active VLUNs. These active VLUNs enable virtual volumes to be exported to hosts. If the current system state does not meet the conditions of the VLUN template, no active VLUNs are created until the conditions of the template are met. Once a VLUN template is applied to create one or more active VLUNs, hosts continue to be able to access volumes based on the export rule established by that template. Removing VLUNs associated with a volume halts host access to that volume. Removing all VLUNs for a host stops the host from accessing all volumes.

VLUN Template Types
A VLUN template sets up an association between a virtual volume and a LUN-host, LUN-port, or LUN-host-port combination by establishing the export rule, or the manner in which the volume is exported. A VLUN template enables the export of a virtual volume as a VLUN to a host or hosts. Those volume exports, which are seen as LUNs by the host or hosts, are active VLUNs. A VLUN template can be one of the following types: • • • • Host sees allows only a specific host to see a volume. Host set allows any host that is a member of the host set to see a volume. Port presents allows any host on a specific port to see the volume. Matched set allows only a specific host on a specific port to see the volume.

Host Sees
A host sees VLUN template allows only a particular host connected to any port to see a virtual volume. The system makes the virtual volume visible as a LUN to all the host’s WWNs, regardless of which controller node port the WWNs appear on. If the host has more than one WWN, active VLUNs are created for each host WWN. However, for any single host, there can only be one host sees VLUN template for a given LUN. If a WWN is added to an existing host definition, all virtual volumes that are exported to the host using the host-sees VLUN template are exported to the new WWN. However, WWNs cannot be removed from a host definition if a LUN is exported to the host.

Host Set
A host set VLUN template allows any host that is a member of the host set to see a volume. The system makes the virtual volume visible as a LUN to all the members of the host set. Any hosts added to the host set automatically see the VLUN, provided there are no conflicting LUN IDs. If the added host has an exported LUN ID in the LUN ID range of the host set, the host cannot see the LUN and must be assigned a new ID. If a host is removed from a host set, the removed host loses all rights of the host set and cannot access volumes exported to the host set.

Port Presents
A port presents VLUN template allows any host connected to a particular port to see a virtual volume. The system makes the virtual volume visible as a LUN to any of the host’s WWNs that appear on the controller node port. As long as the VLUN template remains on the system, additional
Exporting Virtual Volumes 49

active VLUNs are created when the port is attached to additional hosts. However, there can only be one port presents VLUN template per port LUN combination. The same virtual volume can be exported as different LUNs on the same or different ports.

Matched Set
A matched set VLUN template is a combination of the host sees and port presents template types. A matched set VLUN allows a particular host on a specified port to see a virtual volume. For any single LUN, there can only be one matched set VLUN template with the same host-port combination.

50

Virtual Volumes

10 Reclaiming Unused Space
Overview
The HP 3PAR OS space consolidation features allow you to change the way that virtual volumes are mapped to logical disks in a Common Provisioning Group (CPG). Moving virtual volume regions from one logical disk to another enables you to compact logical disks, and free up disk space so that it can be reclaimed for use by the system. For more information about virtual volumes, see “Virtual Volumes” (page 42). Mapping is the correspondence of Logical Disk (LD) regions to the virtual volume regions. Virtual volumes are made up of multiple logical disks, and each logical disk contains regions that are mapped to the virtual volume. All types of volumes are created by mapping data from one or more logical disks to the virtual volume. Figure 10 (page 51) shows how data mapped in regions from logical disks onto a base volume. Figure 10 Data is mapped from logical disks onto a virtual volume in regions

Logical disks can be shared by multiple virtual volumes. As volumes are deleted or as volume copy space grows and then shrinks, logical disks can use space less efficiently. When logical disks do not efficiently use space, the unused space consumes regions on the LD that are not available for use by the system when creating new logical disks. The space management features enable you to consolidate used space onto fewer fully-used logical disks so that unused regions are forced onto one or more logical disks that are then deleted. Deleting these logical disks frees the unused space for general use by the system. You can also truncate LDs to free up space. The LD’s used regions are compacted by moving them to the beginning of the LD and then the LD is shortened so that unused space can be returned to the system’s free chunklet pool.

Reclaiming Unmapped Logical Disk Space from CPGs
Common Provisioning Groups (CPGs) provide a shared pool of logical disk capacity for use by all virtual volumes that draw space from that pool. See “Virtual Volume Types” (page 42) for a discussion of volumes that can draw space from a CPG. If volumes that draw from a CPG are deleted, or if copy space for these volumes grows and then shrinks, the underlying logical disks in the CPG pool can become less efficient in space usage. One or more logical disks in the CPG pool may have only a small portion of their regions mapped to existing virtual volumes. However, the logical disk’s unused regions are not available for use by the volumes mapped to the CPG. Compacting the logical disk regions mapped to these volumes may recover and free logical disk space. Compacting a CPG allows you to reclaim space from a CPG that has become less efficient in space usage from creating, deleting, and relocating volumes. Compacting consolidates logical disk space in CPGs into as few logical disks as possible. Compacting CPGs can be performed
Overview 51

with both the HP 3PAR Command Line Interface (CLI) and the HP 3PAR Management Console. Refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help for instructions on how to perform this task.

Reclaiming Unmapped Logical Disk Space from Volumes
When multiple identical virtual volumes are created as a result of a single volume creation operation, the underlying logical disks that support those volumes are shared by the volume group. If several of the members of that volume group are later deleted, the underlying logical disks may become less efficient in the usage of space. One or more logical disks shared by the volume group may have only a small portion of their regions mapped to existing virtual volumes. However, their unused regions are not available to the system for use in creating new logical disks. Compacting the logical disk regions mapped to these volumes may recover and free logical disk space. Compacting logical disks can only be performed with the HP 3PAR Command Line Interface (CLI). Refer to the HP 3PAR Command Line Interface Administrator’s Manual for instructions on how to perform this tasks. You can use the optional HP 3PAR Dynamic Optimization Software feature to configure volumes to use space more efficiently. To learn about tuning volumes for optimal performance, see “Enhanced Storage Applications” (page 53).

Automatically Reclaiming Unused Snapshot Space from Volumes
The HP 3PAR OS automatically reclaims unused snapshot and administration space from Thinly-Provisioned Virtual Volumes (TPVVs) and fully-provisioned virtual volumes and returns the space to the LDs. The system examines the snapshot and administration space for large areas of unused space. The identified areas are unmapped from the corresponding LD regions and the space is returned to the LDs.

Manually Reclaiming Unused Snapshot Space from Volumes
You cannot manually remove snapshot and administration space from a Thinly-Provisioned Virtual Volume because the HP 3PAR OS automatically removes any unused space. Reclaiming dormant snapshot and administration space from a fully-provisioned virtual volume and returning the space to the LD can only be performed when the volume is not exported to a host, and if there are no snapshots of the volume. Creating physical copies of the volume does not prevent you from reclaiming space. You can reclaim snapshot space from a virtual volume with both the HP 3PAR Command Line Interface (CLI) and the HP 3PAR Management Console. Refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help for instructions on how to perform this task.

Deleted Volume Snapshot Space
The unused space associated with deleted snapshots of Thinly-Provisioned Virtual Volumes (TPVVs) and fully-provisioned virtual volumes is automatically returned to the pool of logical disks used by the CPG.

Logical Disks and Chunklet Initialization
After deleting Logical Disks, the underlying chunklets must be initialized before their space is available to build LDs. The initialization process for chunklets generally takes about one minute per 1GB chunklet and 20 seconds per 256MB chunklet. To see chunklets that are currently in the process of being initialized, issue the showpd –c command. Chunklets that are uninitialized are listed in the Uninit column.

52

Reclaiming Unused Space

1 Enhanced Storage Applications 1
Overview
HP offers several enhanced storage features for managing data and improving system performance. Optional features require you to purchase a separate license. You can use the HP 3PAR Command Line Interface (CLI) and the HP 3PAR Management Console to view the licenses currently enabled on your systems. For a list of default HP 3PAR OS Software Suite features and optional features, see “HP 3PAR Software” (page 9). NOTE: Contact your local service provider to learn about adding optional features to enhance your HP 3PAR storage systems.

HP 3PAR mySnapshot Software
The HP 3PAR mySnapshot Software utility does not require a separately purchased license. The mySnapshot utility enables safe and easy copy and provisioning access to non-storage professionals such as database administrators, software developers, and test engineers working with systems. Users can safely and easily restore their own copies of test data in seconds without relying on the storage administrator. The mySnapshot utility uses an access control list to associate a user with certain administrative permissions and specified storage resources. Once these administrative permissions are granted for the specified resources, the user can easily replace and restore copies of their own test database. This enables users who normally only have Browse capabilities on the system to be able to update specific snapshots with more recent snapshots. This enables faster turnaround times for developers who need to have their snapshots refreshed and alleviates workload for storage administrators. For more information about roles and rights, see “HP 3PAR Storage System Users” (page 18). Configuring the mySnapshot utility can only be performed with the HP 3PAR Command Line Interface (CLI). Refer to the HP 3PAR Command Line Interface Administrator’s Manual for instructions on how to perform this task.

HP 3PAR Dynamic Optimization Software
HP 3PAR Dynamic Optimization Software is an optional feature that allows you to improve the performance of virtual volumes without interrupting access. Use this feature to avoid over provisioning for peak system usage by optimizing the layout of your virtual volumes. With Dynamic Optimization you can change the virtual volume’s parameters, RAID levels and set sizes by associating the virtual volume with a new CPG. You must purchase an HP 3PAR Dynamic Optimization license to use this feature. Dynamic Optimization enables you to change volume parameters and update the layout of volumes to take advantage of the current system configuration. For example, when a system is upgraded by adding nodes, cages, or physical disks, the initial volume and logical disk layouts may no longer be optimal for the new system configuration. Updating the system layout optimizes the use of all physical resources in the system at a given time.

Overview

53

There are several ways Dynamic Optimization may improve system performance: • Volume layout changes after hardware upgrades. Existing virtual volumes only take advantage of resources that were present at the time of volume creation. When a system is upgraded by adding nodes, cages, or disks, the original volume and logical disk layouts may no longer be optimal. Changing the layout of a virtual volume enables volumes to take full advantage of new system resources. By default, Thinly-Provisioned Virtual Volumes (TPVVs) and their underlying Common Provisioning Groups (CPGs) dedicate space from all available resources as they grow, both from pre-existing and new drive capacity resources. This natural expansion capability of TPVVs reduces the need for Dynamic Optimization to change the layout of TPVVs after adding disks. • Volume RAID level changes. Since different RAID levels have varying capacity requirements and offer different degrees of performance, you may desire to convert volumes from one RAID type to another when system requirements change. Volume fault-tolerance changes. A volume with a cage-level availability can tolerate the failure of a drive cage because its RAID sets use chunklets from different drive cages. A volume with a magazine-level availability can tolerate the failure of a drive magazine because its RAID sets use chunklets from different magazines. As applications and business requirements change, it may be desirable to update the fault-tolerance characteristics of existing virtual volumes. CPG and volume growth configuration changes. Changing the characteristics of CPGs and changing virtual volume growth patterns can also reduce system performance over time. Tuning optimizes the system layout by balancing the use of all available resources.

•

•

With dynamic optimization, you can manually change specific parameters on any specified virtual volumes. This feature also analyzes your entire system and automatically corrects space usage imbalances in the system. Virtual volume and physical disk capacity are analyzed and rebalanced for optimal performance. The dynamic optimization automated tuning process has three phases: 1. Analyze the system and detect virtual volumes which are not correctly balanced between nodes. If virtual volumes are not balanced correctly, the volumes are tuned to correct the imbalance. This is the internode tuning phase. 2. Analyze the system and detect any chunklet imbalance between physical discs associated with the same node. After the analysis, chunklets are moved from overused physical discs to under used physical discs associated with the same node. This is the intranode tuning phase. 3. Analyze the system and verify that logical disks associated with a CPG have the same characteristics as the CPG. If the logical disk characteristics do not match the CPG, the logical disk is modified to match the CPG characteristics. Dynamic Optimization tasks can be performed with both the HP 3PAR Command Line Interface and the HP 3PAR Management Console. Refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help for instructions on how to perform these tasks

HP 3PAR System Tuner Software
HP 3PAR System Tuner Software is an optional feature that improves performance by identifying over-used physical disks, and performing load balancing on those disks without interrupting access. You must purchase the HP 3PAR System Tuner license to use this feature. The HP 3PAR OS automatically creates a balanced system layout by mapping virtual volumes to many logical disks, and creating logical disks from chunklets drawn from many physical disks. The I/O for each volume is striped across many physical disks, increasing the throughput of the volume. As the system grows and new applications are introduced, new storage usage patterns can emerge and the system performance can degrade. System Tuner maintains peak system performance by automatically detecting and resolving bottlenecks without interrupting access.

54

Enhanced Storage Applications

If the performance of one or more physical disks degrades, the throughput of the logical disks is reduced and the entire system performance may decline. There are two general reasons why a physical disk may have degraded performance: • • The physical disk has reached its maximum throughput due to an unbalanced load. A disk in this state typically has unusually high average service times when compared to other disks. The physical disk is a bad disk. A bad disk typically has unusually high maximum service times when compared to other disks. Perform physical disk performance tuning on an entire system or on a specified subset of disks. Set performance thresholds for physical disk tuning. Identify and relocate under-performing chunklets.

System Tuner allows you to: • • •

System Tuner tasks can only be performed with the HP 3PAR Command Line Interface (CLI). Refer to the HP 3PAR Command Line Interface Administrator’s Manual for instructions on how to perform these tasks.

HP 3PAR Thin Conversion Software
HP 3PAR Thin Conversion Software is an optional feature that converts a fully-provisioned volume to a Thinly-Provisioned Virtual Volume (TPVV). Virtual volumes with large amounts of allocated but unused space are converted to TPVVs that are much smaller than the original volume. During the conversion process, allocated but unused space is discarded and the result is a TPVV that uses less space than the original volume. To convert volumes located on a system, you must have an F-Class, T-Class, StoreServ 10000, or StoreServ 7000 Storage system to perform the copy operation. The 1. 2. 3. 4. conversion process has four steps. Assessment. Data preparation. Zeroing unused space. Creating a physical copy.

Assessment
Before converting your volumes you must determine the benefits of the conversion process. The potential benefits of zeroing free space prior to copying or migrating the data to a TPVV depends on the amount of allocated but unused space. If there is relatively little unused space in the allocated physical space then there is little benefit to zeroing the free space to recapture this relatively small amount of space. Many volumes that have been in use for a long time have significant amounts of allocated but unused space. If there is a large amount of unused space in the allocated physical space then zeroing the data prior to copying the data results in a substantial reduction in the amount of used space.

Data Preparation
Prepare your data for copying by removing unnecessary data. Perform clean-up tasks on the source volume by: • • • • Emptying trash cans or permanently deleting files. Archiving unused files. Shrinking databases. Deleting temporary files.

HP 3PAR Thin Conversion Software

55

Zeroing Unused Space
Use a host application to write zeros to the allocated but unused volume space. F-Class, T-Class, StoreServ 10000, and StoreServ 7000 Storage systems detect and discard the zeros during the volume copy operation.

Creating a Physical Copy
After writing zeros to the allocated but unused space, the source volume is ready for the final phase of conversion. You create a TPVV physical copy of the source volume to convert the source volume to a TPVV. When you create a physical copy, F-Class, T-Class, StoreServ 10000, and StoreServ 7000 Storage systems automatically detect the zeros and do not allocate space for them in the physical copy. The result is a TPVV that is much smaller than the original volume. Thin Conversion tasks can be performed with both the HP 3PAR Command Line Interface (CLI) and the HP 3PAR Management Console. See the HP 3PAR Command Line Interface Administrator's Manual and the HP 3PAR Management Console Online Help for instructions on how to perform these tasks. NOTE: Converting fully-provisioned volumes to Thinly-Provisioned Virtual Volumes (TPVVs) with the Thin Conversion feature requires an F-Class, T-Class, StoreServ 10000, or StoreServ 7000 Storage system, an HP 3PAR Thin Provisioning license, and an HP 3PAR Thin Conversion license. Contact your HP representative for more information.

HP 3PAR Thin Persistence Software
HP 3PAR Thin Persistence software is an optional feature that keeps TPVVs and read/write snapshots of TPVVs small by detecting pages of zeros during data transfers and not allocating space for the zeros. This feature works in real-time and analyzes the data before it is written to the source TPVV or read/write snapshot of the TPVV. Freed blocks of 16 KB of contiguous space are returned to the source volume, freed blocks of 128 MB of contiguous space are returned to the CPG for use by other volumes. To use Thin Persistence functions, you must have an F-Class, T-Class, StoreServ 10000, or StoreServ 7000 Storage system. The Thin Persistence feature is automatically enabled on F-Class, T-Class, StoreServ 10000, and StoreServ 7000 Storage systems. Thin Persistence tasks can be performed with both the HP 3PAR Command Line Interface (CLI) and the HP 3PAR Management Console. Refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help for instructions on how to perform these tasks. NOTE: Maintaining TPVV and read/write snapshot size with the Thin Persistence feature requires an F-Class, T-Class, StoreServ 10000, or StoreServ 7000 Storage system, an HP 3PAR Thin Provisioning license, an HP 3PAR Thin Conversion license, and an HP 3PAR Thin Persistence license. Contact your HP representative for more information.

HP 3PAR Thin Copy Reclamation Software
HP 3PAR Thin Copy Reclamation software is an optional feature that reclaims space when snapshots are deleted from a system. As snapshots are deleted, the snapshot space is reclaimed from a Thinly-Provisioned Virtual Volume (TPVV) or fully-provisioned virtual volume and returned to the CPG for reuse by other volumes. Deleted snapshot space can be reclaimed from virtual copies, physical copies, or remote copies. The HP 3PAR Thin Copy Reclamation feature works on any class of system. The HP 3PAR OS automatically reclaims snapshot space if the HP 3PAR Virtual Copy, HP 3PAR Remote Copy, or HP 3PAR Thin Provisioning license is enabled. For more information about snapshots, see “Virtual Copy Snapshots” (page 9). NOTE: Reclaiming space when snapshots are deleted with the HP 3PAR Thin Copy Reclamation feature requires the HP 3PAR Virtual Copy, HP 3PAR Remote Copy, or HP 3PAR Thin Provisioning license. Contact your HP representative for more information.
56 Enhanced Storage Applications

HP 3PAR Virtual Lock Software
HP 3PAR Virtual Lock software is an optional feature that enforces the retention period of any volume or copy of a volume. You must purchase the HP 3PAR Virtual Lock license to use this feature. Locking a volume prevents the volume from being deleted intentionally or unintentionally before the retention period elapses. You can use HP 3PAR Virtual Lock to specify the retention period for each volume or copy of a volume.

HP 3PAR Adaptive Optimization Software
HP 3PAR Adaptive Optimization Software analyzes sub-volume, region-level disk access rates for a given array over a scheduled period of time and then performs a data migration of regions between tiers according to a cost versus performance preference. Disk usage is optimized by having frequently accessed data moved to the higher performance tier (for example, RAID 1 using Solid State Disks, or SSDs) while infrequently accessed data is moved to the lower cost tier (for example, RAID 6 on Nearline disks). Active use of AO requires an Adaptive Optimization license. Contact your local HP representative for information. AO uses System Reporter statistics gathered from logical disks and physical disks to relocate customer data on physical volumes in an optimal way. AO relocation accomplishes two primary goals: • • Increases performance of frequently accessed regions of data by moving those regions to higher-tier storage (for example, moving to solid state drives from normal spinning media). Improves cost-efficiency by moving lightly accessed regions of data to a lower performance and less expensive tier of storage (for example, moving from regular drives to nearline drives).

Because storage tiers can be of different RAID types, capacity efficiency is maximized by using only RAID1 for the most frequently accessed storage and by using RAID5 or RAID6 for less frequently accessed storage. Other benefits include: • • AO can migrate data from a fully occupied tier of storage to another tier that has more available capacity. AO can also be regularly scheduled so that it can adjust the data layout as your data usage changes over time.

AO is built on top of the new version of System Reporter (SR), which also now runs as part of the HP 3PAR OS. SR must have been actively gathering data on VV regions for a period of time. Analysis of the data collected by SR is performed to identify regions within virtual volumes that are either heavily used or lightly used, and then generates a series of secondary tasks to move these regions to faster or slower storage tiers. Running AO on the HP 3PAR OS itself offers these advantages: • • • • AO configurations can now be created, modified, and removed using the CLI or the HP 3PAR Management Console. Beginning with HP 3PAR 3.1.2, the external HP System Reporter is no longer necessary to use Adaptive Optimization The database scheme has been restructured on node to be more efficient and reliable. The actual movement of data can use data from a given time period in the past rather than only from the immediate past. This means data movement can occur at low-utilization time periods while using an analysis of statistics gathered during peak periods. A time limit can be set for data movement so that scheduled data is moved only during low-utilization periods rather than during peak periods.

•

HP 3PAR Virtual Lock Software

57

HP 3PAR Peer Motion Software
HP 3PAR Peer Motion Software controls the migration of a host and its data from a source system to a destination system with as little disruption to the host as possible. With peer motion, you can copy the virtual volumes and system configuration information to a new system with no changes to host configurations, no loss of access by a host to its data in an online migration, and only a minimal outage during a minimally disruptive migration.

Data Encryption
Beginning with HP 3PAR OS 3.1.2 MU2, HP 3PAR encrypted storage systems provide data encryption by using self-encrypting drives (SEDs) with a local key manager (LKM). Data encryption prevents data exposure that might result from the loss of physical control of disk drives when disk drives are: • • • Decommissioned at their end of life. Returned for warranty or repair. Lost or stolen.

The HP 3PAR StoreServ Data Encryption solution uses SED technology to encrypt all data on the physical drives and prevent unauthorized access to data-at-rest (DAR). When encryption is enabled, the SED will lock when power is removed, and it will not be unlocked until the matching key from the HP 3PAR StoreServ system is used to unlock it. SEDs contain special firmware and an application-specific integrated circuit (ASIC) that provides encryption. Each SED has a number of bands that control access to different areas of the drive. Each band has an internal encryption key that is not exposed outside of the drive itself. This encryption key is always used to encrypt and decrypt all data stored on that band. All data encryption is handled at the physical disk layer. System features, such as thin provisioning and dynamic optimization, work independently of encryption. Each band has a single authentication key that controls access to data on the band. In the HP 3PAR StoreServ data-encryption implementation, the entire disk is in one band. Access to data is controlled by setting the authentication key, which locks and unlocks the drive. The LKM, which is part of the HP 3PAR OS that runs on each node in a cluster, maintains the authentication key. You must back up and protect the keystore file; HP does not have access to the key. All drives in the same array will have the same authentication key. The disks become locked whenever they lose power, which guarantees that any disk removed from an HP 3PAR Storage system will not be accessible except in its original array. When the drive is unlocked, all I/O to the drive behaves exactly as it would on a non-SED, and encryption and decryption happen at full interface speed, without data delays. There is a minimal delay for booting (since each drive must be unlocked before the system becomes operational) and for data encryption management functions (since each disk must be updated whenever keys are changed on the system). Each of these operations takes up to 3 seconds per disk, but happens in several threads. On a system with 160 disks, for example, enabling encryption

58

Enhanced Storage Applications

takes about 30 seconds, and booting takes an additional 5 seconds. Rekeying under a light load takes about 15 seconds. CAUTION: Keep the encryption key file and password safe. If you lose the encryption key and the HP 3PAR StoreServ system is still functioning, you can always perform another backup of the encryption key file. However, should you lose the encryption key file or the password, and should the HP 3PAR StoreServ system then fail, the HP 3PAR StoreServ system will be unable to restore access to data. Ensure that backup copies of the latest encryption key file are kept and that the password is known. The importance of keeping the encryption key file and password safe cannot be overstated. HP does not have access to the encryption key or password. Different arrays need separate backups, although the same password can be applied. The SED DataStore provides an open interface for authentication key management. DataStore tracks the serial number of the array that owns each SED, which disallows SEDs from being used in other systems. NOTE: The HP 3PAR data encryption solution will help mitigate breach notifications under the Health Information Technology for Economic and Clinical Health (HITECH) Act, but is not compliant with the Federal Information Processing Standard (FIPS) 140-2.

Priority Optimization
During recent years, consolidation of storage systems has reduced complexity of data storage, delivering efficiency in management, occupied floor space, and energy consumption. However, the consolidation of many disjoint workloads into a single storage system also results in contention for shared system resources on the system. Examples of such shared resources include front-end host Fiber Channel (FC), iSCSI and FCoE adapters, back-end FC or SAS disk connections, physical disks, data and control cache, ASICs, CPUs, and backplane interconnections. Data packets arriving at the front-end FC HBA adapters are handled on a first-come, first-serve basis. On the surface, this may sound fair, but it can lead to unequal and inconsistent throughput for multiple concurrent workloads. HP 3PAR’s Priority Optimization software manages and distributes the I/O capacity of an HP 3PAR StoreServ Storage system across multiple workloads. The tool enables the co-location of the data of workloads of different types, such as sequential, random, online transaction processing (OLTP), with different I/O packet sizes on a single storage system while achieving adequate and stable performance in a multi-tenant environment. HP 3PAR Priority Optimization software introduces quality-of-service rules to manage and control the I/O capacity of an HP 3PAR StoreServ Storage system across multiple workloads. Application of the rules enables co-location of the data from workloads of different types (such as sequential, random, and transactional, among others), with different I/O packet sizes on a single HP 3PAR storage system. The use of QoS rules stabilizes performance in a multi-tenant environment.

Automatic and Transparent Failover
Automatic transparent failover (ATF) technology with HP 3PAR Peer Persistence is available for VMware configurations in version 3.1.2 MU2 of the HP 3PAR OS software. ATF is the ability to automatically redirect host I/O from a failed primary system to the replicant secondary system in a manner that is transparent to the host and causes minimal disruption to service. The failover—in which the target volume group becomes source, and, providing the source array is available, the source volume group becomes the target—is transparent in that it is non-disruptive to the hosts and applications running on them. The failover is automatic in that failover can occur without user intervention as long as the failover conditions are met.

Priority Optimization

59

ATF automatically redirects host I/O from a failed source system to the replicant target system in a manner that is transparent to the host and causes minimal disruption to service. ATF uses the HP 3PAR Quorum Witness to monitor for HP 3PAR StoreServ array failure and to automatically determine whether a failover of host service is required. The HP 3PAR Quorum Witness and related technology provide the automation to trigger the transparent failover technology to execute the migration of the I/O path. To optimize service or facilitate maintainence, transparent failover also provides user-initiated failover of host I/O from one HP 3PAR StoreServ system to its replicant. User-initiated transparent failover is also known as managed transparent failover (MTF). ATF and MTF technology are key elements in providing and maintaining a high-availability storage solution between two sites and are fundamental building blocks in the wider HP 3PAR Peer Persistence technology set. From a technology perspective, ATF can be seen as a super-set of MTF. ATF requires some additional configuration beyond that required for MTF.

60

Enhanced Storage Applications

12 HP 3PAR Storage System Hardware
Overview
HP 3PAR storage systems are available in a variety of hardware configurations. Different models address different levels of storage capacity and anticipated growth requirements. All models use the HP 3PAR Operating System (OS). Hardware monitoring and configuration tasks can be performed with both the HP 3PAR Command Line Interface (CLI) and the HP 3PAR Management Console. Refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help for instructions on how to perform hardware management tasks. For detailed information about ports, network adapters, cabling, and cable configurations, see the physical planning manual for your storage system model. WARNING! With the exception of Customer Self Repair (CSR) parts, the servicing of HP hardware is to be performed by authorized technicians, including HP field engineers, Value Added Resellers (VARs), certified self-maintaining customers, and, in some cases, authorized third-party field technicians, who are authorized by HP to install HP 3PAR storage systems and their hardware components.

Identifying System Components
Figure 1 (page 61) and Figure 12 (page 62) identify the major hardware components of a system. 1 Different models have different hardware configurations. Figure 1 HP 3PAR StoreServ 10000 Front View 1

Overview

61

Table 5 HP 3PAR StoreServ 10000 Front View System Components
Item 1 2 3 4 5 6 7 8 Description HP 3PAR StoreServ 10000 Storage system (V400 model) HP 3PAR StoreServ 10000 Storage system (V800 model) Drive Cage FC-AL Modules Cooling Fans Battery Backup Units Service Processor Drive Chassis Leveling Foot

Figure 12 HP 3PAR StoreServ 10000 Storage System Rear View

Table 6 HP 3PAR StoreServ 10000 Storage System Rear View System Components
Item 1 2 3 4 5 Description Drive Chassis Power Supply Power Distribution Unit Controller Node Controller Node Power Supply Service Processor

62

HP 3PAR Storage System Hardware

Physical Disks
A physical disk is a hard drive mounted on a drive magazine or module located in drive cages in HP 3PAR storage systems. There are three types of physical disks: Fibre Channel (FC), Near Line (NL) and Solid State Drives (SSD). In DC4 drive cages, each drive magazine holds four disks numbered 0 through 3 from the rear to the front of the magazine. The DC4 drive cages contain a maximum of ten drive magazines for a maximum of 40 physical disks in each drive cage. See Figure 13 (page 63). Figure 13 DC4 Drive Magazine with Physical Disks

1. 2.

Front of drive magazine Rear of drive magazine

In a DC3 drive cage, each plug-in drive module holds a single disk numbered 0 through 15. The DC3 drive cage contains 16 drive bays and holds up to 16 drive magazine modules for a maximum of 16 physical disks in each drive cage. See Figure 14 (page 63). Figure 14 DC3 Drive Magazine Module with One Physical Disk

Physical Disks

63

Drive Cage/Enclosure Models
• • • StoreServ 7000 Storage systems contain either the M6710 (2U24) drive enclosure or the M6720 (4U24) drive enclosure. T-Class and StoreServ 10000 Storage systems contain DC4 drive cages. The DC4 is a 40 disk, 4 Gbps drive cage. F-Class systems only contain DC3 drive cages. The DC3 is a 16 disk, 4 Gbps drive cage.

HP M6710 Drive Enclosure
The HP M6710 Drive Enclosure (2U24) holds up to 24, 2.5 inch small form factor (SFF) SAS disk drives arranged vertically in a single row at the front of the enclosure. The back of the enclosure includes two 580W PCMs and two I/O modules. Figure 15 HP M6710 Drive Enclosure

HP M6720 Drive Enclosure
The HP M6720 Drive Enclosure (4U24) holds up to 24, 3.5 inch large form factor (LFF) SAS disk drives, arranged horizontally with four columns of six disk drives. The back of the enclosure includes two 580W PCMs and two I/O modules. Figure 16 HP M6720 Drive Enclosure

DC4 Drive Cages and Ports and Cabling
The DC4 drive cages house ten drive bays numbered 0 through 9. Each drive bay accommodates a single drive magazine that holds four disks. Figure 17 (page 65) shows a DC4 drive cage which contain two Fibre Channel-Arbitrated Loop (FC-AL) modules: • • The left side FC-AL has two ports: A0 and B0. The right side FC-AL has two ports: A1 and B1.

64

HP 3PAR Storage System Hardware

Fibre Channel cables connect the ports in the drive cage to the ports on the controller nodes. Each cable is labeled to indicate the ports it uses. NOTE: Daisy chaining is not supported for the DC4 drive cages.

Figure 17 DC4 Drive Cage

Table 7 DC4 Drive Cage Components
Item 1 2 3 4 5 Description FC-AL Port B0 FC-AL Port A0 FC-AL Modules FC-AL Port A1 FC-AL Port B1

DC3 Drive Cage and Ports and Cabling
The DC3 drive cage contains 16 drive bays at the front, each accommodating the appropriate plug-in drive magazine module. The 16 drive bays are arranged in four rows of four drives. Figure 18 (page 65) shows the front view of a DC3 drive cage. Figure 18 DC3 Drive Cage (Front View)

Drive Cage/Enclosure Models

65

In the DC3 drive cage, two FC-ALs, each providing four small form-factor pluggable (SFP) modules to service the drive cage. Figure 19 (page 66) shows the rear view of a DC3 drive cage. • • FC-AL B has four ports, labeled Port B0 through Port B3, from bottom to top. FC-AL A has four ports, labeled Port A0 through Port A3, from top to bottom.

Fibre Channel cables connect the ports in the drive cage to the ports on the controller nodes. Each cable is labeled to indicate the ports it uses. Figure 19 DC3 Drive Cage (Rear View)

Table 8 DC4 Drive Cage Components
Item 1 2 3 4 5 6 7 8 9 10 1 1 12 Description Drive Chassis Power Supply 1 FC-AL Port B0 FC-AL Port B1 FC-AL Port B2 FC-AL Port B3 FC-AL Port A0 FC-AL Port A1 FC-AL Port A2 FC-AL Port A3 Drive Chassis Power Supply 0 FC-AL A FC-AL B

Controller Nodes
System controller nodes use Fibre Channel, Gigabit Ethernet, and iSCSI ports to connect the storage sever to your network, host computers, storage sever components, and to other systems. Inside each controller node there are slots for network adapters, control cache DIMMs, and data cache DIMMs. The number of controller nodes in each system, and the type and number of network adapters is configurable. The number of controller nodes each system model can accommodate is summarized in Table 9 (page 67).

66

HP 3PAR Storage System Hardware

Table 9 System Models and Number of Controller Nodes
Storage System Model StoreServ 7000 StoreServ 10000 T400 T800 F200 F400 Number of Controller Nodes 2 or 4 2, 4, 6, or 8 2 or 4 2, 4, 6, or 8 2 4

Port Numbering
The number of host ports each storage system model can accommodate is summarized in Table 10 (page 67). Table 10 Storage System Models and Number of Ports
Storage System Model StoreServ 7200 StoreServ 7400 StoreServ 7450 StoreServ 10000 T400 T800 F200 F400 Number of FC Ports 0–12 0–12 (2 node); 0–24 (4 node) 4–12 (2 node); 8–24 (4 node) 0–288 0–64 0–128 0–8 0–16 Number of iSCSI Ports 0–4 (10 Gb/s) 0–8 (10 Gb/s) 0–4 (2 node); 0–8 (4 node) (10 Gb/s) 0–18 0–16 0–32 0–8 (1 Gb/s) 0–16 (1 Gb/s)

NOTE: • • For information about port location and numbering, see “Port Location Formats” (page 28). For information about how to view the control cache DIMM and data cache DIMM configurations for each controller node, see the HP 3PAR Command Line Interface Administrator's Manual and HP 3PAR Management Console Online Help. For information about memory expansion, contact your HP representative. For a complete list of supported third-party hardware and software, go to the Single Point of Connectivity Knowledge (SPOCK) website http://www.hp.com/storage/spock.

•

HP 3PAR StoreServ 7000 Controller Node Numbering
The HP 3PAR StoreServ 7000 Storage system can contain two or four controller nodes per system configuration. Controller nodes are located in the rear of the node enclosure. The HP 3PAR StoreServ 7200 Storage system includes two nodes, which are numbered 0 and 1 from bottom to top. The HP 3PAR StoreServ 7400 Storage system can include two nodes or four nodes. Four-node systems are numbered from 0 to 3 from bottom to top.

Controller Nodes

67

Figure 20 HP 3PAR StoreServ 7200 Storage System

Figure 21 HP 3PAR StoreServ 7400 Storage System (4 Nodes)

HP 3PAR StoreServ 10000 Controller Node Numbering
The HP 3PAR StoreServ 10000 system may contain two, four, six or eight controller nodes per system configuration. The controller node chassis is located at the rear of the storage cabinet. From the rear of the storage cabinet, component numbering starts with zero (0) at the bottom-left corner and advances right and upward. For example, the node in the lower left position is identified as node 0 and the adjacent node (right) is identified as node 1. When two node chassis are present, the orientation of the lower and upper nodes becomes inverted. The node located in upper right corner of a StoreServ 10000 with 8 nodes is identified as node 7. The following figure shows the numbering and positioning of the controller nodes in a StoreServ 10000 chassis. The 4-node model is shown on the left; the 8-node model is shown on the right.

68

HP 3PAR Storage System Hardware

Figure 22 HP 3PAR StoreServ 10000 Controller Node Numbering

T-Class Controller Node Numbering
T-Class systems contain two, four, six, or eight controller nodes per system and only use T-Class controller nodes. Controller nodes are loaded into the system backplane enclosure from bottom to top. For a T800 storage system with only two controller nodes installed, those controller nodes would occupy the lowest 4U of the backplane and would be numbered node 6 and node 7. A controller node takes on the number of the bay that it occupies in the system backplane, as shown in Figure 23 (page 70).

Controller Nodes

69

Figure 23 T-Class Controller Node Numbering

F-Class Controller Node Numbering
The F-Class systems contains two or four nodes per system. Controller nodes are numbered from top to bottom node 0 and node 1 for a two node system, and node 0- 3 for a four node system. See Figure 24 (page 71) for an example of controller node numbering in an F-Class system.

70

HP 3PAR Storage System Hardware

Figure 24 F-Class Controller Node Numbering

Controller Nodes

71

13 HP 3PAR SNMP Infrastructure
Overview
In addition to managing the system with the HP 3PAR Management Console and the HP 3PAR CLI, the HP 3PAR OS includes an SNMP agent that allows you to perform some basic management functions via network management software running on a management station. These SNMP management functions require that you have SNMP management software not provided by HP.

About SNMP
Simple Network Management Protocol (SNMP) is a standard management interface used by many software frameworks to manage hardware devices. Use of SNMP requires two components, an agent and a manager. The manager is the management process that sends requests to the agent. The host that the manager runs on is called the management station.

SNMP Managers
There are four types of requests that an SNMP manager can send to an agent: • SET. The SET request writes an object value in the agent. The SET request includes the object ID and a new value for the object. The agent will change the value of the object and save it in the persistent store. Not all objects are changeable. The MIB contains access information. GET. The GET request reads an object value in the agent. The GET request includes the object ID to be retrieved. The agent returns the value of the object. GETNEXT. The GETNEXT request reads the object instance that is next in lexicographical order to the object ID in the request. For example, if the object ID specified in the request is .12925.0, the returned object ID should be .12925.1, if it exists. GETBULK. The GETBULK operation is an optimization of the GETNEXT operation, that allows multiple instances of objects to be returned.

• •

•

In addition, the manager can register with the agent to receive notifications (traps) for critical events (alerts) and alert state changes. Before an SNMP manager can receive the traps generated by the SNMP agent, you must register your manager with the agent. Refer to Chapter 14, Using SNMP, in the HP 3PAR Command Line Interface Administrator’s Manual for instructions on registering an SNMP manager with the SNMP agent.

The HP 3PAR SNMP Agent
The HP 3PAR SNMP agent runs on the system and provides a management interface to enable other software products to manage HP hardware using SNMP. The SNMP agent responds to GET, SET, GETNEXT, and GETBULK SNMP requests and also generates notification messages (traps) for critical events (alerts) and alert state changes. The SNMP agent converts all system alerts and alert state changes into SNMPv2 traps and forwards them to all SNMP management stations that have previously registered with the agent. These notifications contain detailed information describing critical events and are generated for every alert and alert state change issued by the system. The exact message formats are described in the HP 3PAR MIB. See the Using SNMP chapter in the HP 3PAR Command Line Interface Administrator's Manual for instructions on locating this file.

72

HP 3PAR SNMP Infrastructure

Standard Compliance
The HP 3PAR SNMP agent supports the following standards: • SNMPv2c This version refers to a widely used administrative framework for SNMPv2, also known as “community-based SNMPv2.” Although this version includes SNMPv2 enhancements like notification and GETBULK requests, it still relies on the SNMPv1 community concept for security. • • Standard Management Interface-v2 (SMIv2) SNMPv3 This standard specifies the format of the MIB. The HP 3PAR MIB definition uses SMIv2 conventions. This version provides stronger security with user-based authentication and Protocol Data Unit (PDU) or packet encryption.

Supported MIBs
You can find the MIB files on the HP 3PAR CLI and SNMP CD. The HP 3PAR SNMP agent supports the following MIBs: • • • SNMPv2-MIB Management Information Block-II (MIB-II), system group. snmpTrap group, snmpTrapOID only.

For discovery and basic information, the HP 3PAR SNMP agent supports the MIB-II system group. This is the authoritative identification of the notification currently being sent. This variable occurs as the second varbind in every SNMPv2 trap. • HP 3PAR MIB This is the HP 3PAR proprietary MIB.

MIB-II
MIB-II defines several groups of standard information to be provided by the agent. The SNMP agent supports only the system group objects. Table 1 (page 73) summarizes the MIB-II information 1 provided by the SNMP agent. See the topic Registering a Management Console in the HP 3PAR Command Line Interface Administrator's Manual for detailed descriptions of these MIB-II system group objects. Table 1 MIB-II Objects Supported by the SNMP Agent 1
Object Descriptor sysDescr Description Access

Describes the system using the model Read-only number, system ID, serial number, and master node’s HP 3PAR OS version. The HP registration object ID for the Read-only system is 12925.1. This is comprised of a company-unique ID (12925) and a product ID (1). Gives the time interval (within 1/100 of a second) since the system was initialized. Read-only

sysObjectID

sysUpTime

sysContact

User-defined name of the person or Read/write group responsible for maintaining the system.

The HP 3PAR SNMP Agent

73

Table 1 MIB-II Objects Supported by the SNMP Agent (continued) 1
Object Descriptor sysName Description Access

Name of the system. This helps to Read-only identify the storage system. This name cannot be set via SNMP. User-defined system location. For example: Building 1, room 4, rack 3. Read/write

sysLocation

Exposed Objects
The 3PAR SNMP agent supports MIB-II system group objects. This section describes each of those objects in detail. System Description Access: Read-only MIB definition: sysDescr Data type: Display string (max. 255 characters) Default value: 3PAR InServ Description: Identifies system model, system ID, serial number and HP 3PAR OS version of the master node. For example, if the system has four nodes, the sysDescr may resemble the following: 3PAR InServT400, serial number 876541, HP 3PAR OS version x.x.x. This is only a brief system description. Use the HP 3PAR CLI to obtain further details about the system and each node. This is a read-only attribute. System Object ID Access: Read-only MIB definition: sysObjectID Data type: integer Default value: 12925.1 Description: Identifies the unique product ID for the HP 3PAR storage system. The first part of this ID is the unique enterprise ID assigned to HP, Inc. by ICANN (12925). The second part of this ID is the product ID assigned to the system (1). If there are future products other than the system, they will be assigned incremental integers (2, 3, and so on). The manager uses this ID to identify products manufactured by HP. This is a read-only attribute. System Up Time Access: Read-only MIB definition: sysUpTime Data type: time-tick (1/100 second) Default value: 0 Description: Indicates how long the system has been operational, beginning with system initialization. This is a read-only attribute. System Contact Information Access: Read/write MIB definition: sysContact Data type: Display string (max. 255 characters)

74

HP 3PAR SNMP Infrastructure

Default value: Please provide contact information such as name, phone number, and e-mail address Description: Specifies the name of a person or group responsible for maintaining the storage. This value can be changed via the manager at any time. System Name Access: Read-only MIB definition: sysName Data type: Display string (max. 255 characters) Default value: None Description: Indicates the system name, which is set during initialization and setup of the system. This helps to identify this system from other systems. The value cannot be changed by the manager. System Location Access: Read/write MIB definition: sysLocation Data type: Display string (max. 255 characters) Default value: Please provide location description where the device resides such as building, room, and rack number Description: Contains the user-defined location of the system. This helps to indicate where the storage system is located. For example, the location may be indicated as follows: Building 1, room 4, rack 3. This value can be changed via the manager at any time

The HP 3PAR MIB
The HP 3PAR MIB contains proprietary information that reflects the configuration and behavior of the system and may be useful for network management. Currently, the HP 3PAR MIB only contains the alertNotify trap definition. Table 12 (page 75) summarizes the contents of this trap. Table 12 Contents of the alertNotify trap
Object Descriptor component details Description Tells you which system hardware, software, or logical component caused the alert or alert state change. Access Read-only

Detailed description of the alert or alert state change, displayed as an alert Read-only string (for example: PR table is corrupt). For information about system alerts, go to http://www.hp.com/support/hpgt/ 3par and select your server platform. Node identification number, an integer from 0 through 7 that indicates which Read-only system controller node reported the alert or alert state change. Severity level of the alert or alert state change, which is an integer from 0 to 5. See the HP 3PAR MIB for definitions for each integer. Time the alert or alert state change occurred, in DDD mmm dd hh:mm:ss ZZZ yyyy format (for example: Mon, Jan 01 12:30:34 PST 2005). Read-only Read-only

nodeID severity timeOccurred

id

Alert ID. The alert ID uniquely identifies an outstanding alert on some object Read-only within the system. Alert IDs are automatically generated by the HP 3PAR OS and increment when a new alert on a new object is detected. Note also that if an alert is generated on an object and alerts already exist in the system, the alert ID is removed. For alert state traps, the alert ID will be the same as the ID of the trap that indicated the original problem.

The HP 3PAR SNMP Agent

75

Table 12 Contents of the alertNotify trap (continued)
Object Descriptor messageCode Description Access

Code that identifies the specific type of alert or alert state change. For Read-only example, the message code for the alert state change is 1245186. For information about system alerts, go to http://www.hp.com/support/hpgt/ 3par and select your server platform. Current alert state, which is an integer between 0 and 5. See the HP 3PAR MIB for definitions for each integer. Alert states enable users to maintain detailed tracking of alerts throughout their life cycle. Read-only

state

alertNotify Traps An alertNotify trap contains details about an event that may affect system operations and performance. All alerts generated by the system as well as all alert status change events are translated into alertNotify traps. The following example shows an alertNotify trap translated from an alert: sysUpTime.0:0 hours, 28 minutes, 1 seconds. snmpTrapOID.0:.iso.org.dod.internet.private.enterprises.threepar.inserv.alertNotify component.1:comp_hw_node details.1:Node 7 is offline nodeID.1:0 severity.1:major(2) timeOccurred.1:Wed Dec 15 16:58:20 PST 2004 id.1:647 messageCode.1:1703938 state.1:new(1)

For information about system alerts, go to http://www.hp.com/support/hpgt/3par and select your server platform. NOTE: If you receive a trap with messageCode == 1245186, this is to notify you that an alert has changed state. In order to find out which alert has changed state, you must extract the alert ID from the id trap field. An alert status change event is not an alert. It notifies you that an alert has changed status (e.g., from New to Resolved by System). The following example shows an alertNotify trap translated from an alert status change event: sysUpTime.0:0 hours, 5 minutes, 26 seconds. snmpTrapOID.0:.iso.org.dod.internet.private.enterprises.threepar.inserv.alertNotify component.1:comp_sw_alert details.1:Alert 647 changed from state New to Resolved by System nodeID.1:1 severity.1:info(5) timeOccurred.1:Thu Dec 16 14:06:36 PST 2004 id.1:647 messageCode.1:1245186 state.1:autofixed(5)

76

HP 3PAR SNMP Infrastructure

The following information describes these alert status change events: Message Code 1245186 Severity Info Type Change in alert state Alert String Alert changed from state to Operator Action The alert has changed state. This can be used to track the state of the existing alerts in a system.

The HP 3PAR SNMP Agent

77

14 The HP 3PAR CIM API
Overview
This chapter describes the HP 3PAR CIM Application Programming Interface (API), HP’s industry-standard API based on SNIA’s Storage Management Initiative Specification (SMI-S). For detailed information about the HP 3PAR CIM API, refer to the HP 3PAR CIM API Programming Reference.

About SMI-S
SMI-S enables management of storage area networks (SANs) in a heterogeneous multi-vendor environment. SMI-S uses an object-oriented model based on the Common Information Model (CIM) to define objects and services which comprise a SAN. By leveraging vendor and technology independent standards, SMI-S allows management application vendors to create applications that work across products from multiple vendors. The SMI-S model is divided into several profiles, each of which describes a particular class of SAN entities (such as disk arrays). These profiles allow for differences in implementations but provide a consistent approach for clients to discover and manage SAN resources and facilitate interoperability across vendor products within the SAN. SMI-S also defines an automated resource discovery process using Service Location Protocol version 2 (SLPv2). This allows management applications to automatically find SAN resources and then probe them to determine which of the SMI-S profiles and features they support. For more information about SMI-S, refer to the Storage Management Initiative web site at http:// www.snia.org/smi/home.

About the WBEM Initiative
SMI-S is based on the Web-Based Enterprise Management (WBEM) Initiative, which is defined by the Distributed Management Task Force (DMTF). WBEM is a set of management and Internet standard technologies developed to unify the management of distributed computing environments. The DMTF has developed a core set of standards that make up WBEM: • The Common Information Model (CIM) standard The CIM standard is the data model for WBEM. CIM provides a conceptual framework for describing management data for systems, networks, applications and services, and allows for vendor extensions. SMI-S uses CIM to model those objects and relationships that comprise a SAN. • CIM-XML CIM-XML is a method of exchanging CIM management data. CIM-XML uses an xmlCIM payload and HTTP(s) as the transport mechanism.

78

The HP 3PAR CIM API

This protocol is defined by the following specifications: • Specification for the Representation of CIM in XML Defines a standard for the representation of CIM elements and messages in XML, written in Document Type Definition (DTD). • CIM Operations over HTTP Defines a mapping of CIM Messages onto HTTP that allows implementations of CIM to interoperate in an open, standardized manner. It uses the CIM XML DTD that defines the XML Schema for CIM objects and messages. • WBEM Discovery using Service Location Protocol (SLP) WBEM Discovery using SLP is a method for applications to identify WBEM-based management systems. For more information regarding WBEM and CIM, please refer to the DMTF web site at http:// www.dmtf.org.

HP 3PAR CIM Support
The following sections provide information about the HP 3PAR CIM API provided with HP 3PAR OS Version 3.1.2.

Standard Compliance
• • The HP 3PAR CIM Server supports SMI-S version 1.1.0. The HP 3PAR CIM API passes SNIA-CTP conformance. For additional information, see http:// www.snia.org.

SMI-S Profiles
SMI-S defines a number of profiles that are used to manage elements of a SAN. These SMI-S Profiles are described in detail in the HP 3PAR CIM API Programming Reference.

Supported Extensions
The HP 3PAR CIM Server supports additional classes that provide management for system specific features not covered by SMI-S. Refer to the HP 3PAR CIM API Programming Reference for complete information.

CIM Indications
SMI-S provides for asynchronous notification of events that indicate changes in the CIM server or the managed elements controlled by the CIM server. CIM Indications are the mechanism for delivery of such events. A CIM client must subscribe to indications that it wants to receive the event notifications from the CIM server. For detailed information regarding Indications, refer to SMI-S at http://www.snia.org. The HP 3PAR CIM Server currently supports indication subscriptions for changes in the operational status of fibre channel ports. Refer to the HP 3PAR CIM API Programming Reference for complete information.

HP 3PAR CIM Support

79

15 Comparing HP 3PAR to EVA Terms
This comparison of EVA and HP 3PAR terms is intended to be a general guide to similar concepts. These terms do not necessarily represent exactly the same entities with all the same properties in both product lines. For detailed descriptions of each term, see the EVA or HP 3PAR glossary. Table 13 EVA and HP 3PAR Terms
EVA Term controller EVA firmware (controller software) disk groups host logical unit number (LUN) P6000 Command View ports (iSCSi or FC) presentation (to host) provisioning, thin provisioning redundancy level (Vraid) remote replication snapclone snapshot thinly-provisioned virtual volume (TPVV) 3PAR Term node, controller node HP 3PAR Operating System common provisioning groups (CPGs) host logical unit number (LUN) HP 3PAR Management Console ports (iSCSi or FC) export (to host) provisioning, full provisioning, thin provisioning RAID Remote Copy physical copy virtual copy, snapshot thinly-provisioned virtual volume (TPVV)

80

Comparing HP 3PAR to EVA Terms

16 Support and Other Resources
Contacting HP
For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: • • • • • • Product model names and numbers Technical support registration number (if applicable) Product serial numbers Error messages Operating system type and revision level Detailed questions

Specify the type of support you are requesting:
HP 3PAR storage system HP 3PAR StoreServ 7200, 7400, and 7450 Storage systems HP 3PAR StoreServ 10000 Storage systems HP 3PAR T-Class storage systems HP 3PAR F-Class storage systems Support request StoreServ 7000 Storage 3PAR or 3PAR Storage

HP 3PAR documentation
For information about: Supported hardware and software platforms See: The Single Point of Connectivity Knowledge for HP Storage Products (SPOCK) website: http://www.hp.com/storage/spock Locating HP 3PAR documents The HP 3PAR StoreServ Storage site: http://www.hp.com/go/3par To access HP 3PAR documents, click the Support link for your product. HP 3PAR storage system software Storage concepts and terminology HP 3PAR StoreServ Storage Concepts Guide

Using the HP 3PAR Management Console (GUI) to configure HP 3PAR Management Console User's Guide and administer HP 3PAR storage systems Using the HP 3PAR CLI to configure and administer storage systems CLI commands Analyzing system performance Installing and maintaining the Host Explorer agent in order to manage host configuration and connectivity information HP 3PAR Command Line Interface Administrator’s Manual HP 3PAR Command Line Interface Reference HP 3PAR System Reporter Software User's Guide HP 3PAR Host Explorer User’s Guide

Creating applications compliant with the Common Information HP 3PAR CIM API Programming Reference Model (CIM) to manage HP 3PAR storage systems Contacting HP 81

For information about:

See:

Migrating data from one HP 3PAR storage system to another HP 3PAR-to-3PAR Storage Peer Motion Guide Configuring the Secure Service Custodian server in order to monitor and control HP 3PAR storage systems Using the CLI to configure and manage HP 3PAR Remote Copy Updating HP 3PAR operating systems Identifying storage system components, troubleshooting information, and detailed alert information Installing, configuring, and maintaining the HP 3PAR Policy Server HP 3PAR Secure Service Custodian Configuration Utility Reference HP 3PAR Remote Copy Software User’s Guide HP 3PAR Upgrade Pre-Planning Guide HP 3PAR F-Class, T-Class, and StoreServ 10000 Storage Troubleshooting Guide HP 3PAR Policy Server Installation and Setup Guide HP 3PAR Policy Server Administration Guide

82

Support and Other Resources

For information about:

See: Planning for HP 3PAR storage system setup

Hardware specifications, installation considerations, power requirements, networking options, and cabling information for HP 3PAR storage systems HP 3PAR 7200, 7400, and 7450 storage systems HP 3PAR StoreServ 7000 Storage Site Planning Manual HP 3PAR StoreServ 7450 Storage Site Planning Manual HP 3PAR 10000 storage systems HP 3PAR StoreServ 10000 Storage Physical Planning Manual HP 3PAR StoreServ 10000 Storage Third-Party Rack Physical Planning Manual Installing and maintaining HP 3PAR 7200, 7400, and 7450 storage systems Installing 7200, 7400, and 7450 storage systems and initializing the Service Processor HP 3PAR StoreServ 7000 Storage Installation Guide HP 3PAR StoreServ 7450 Storage Installation Guide HP 3PAR StoreServ 7000 Storage SmartStart Software User’s Guide Maintaining, servicing, and upgrading 7200, 7400, and 7450 storage systems Troubleshooting 7200, 7400, and 7450 storage systems HP 3PAR StoreServ 7000 Storage Service Guide HP 3PAR StoreServ 7450 Storage Service Guide HP 3PAR StoreServ 7000 Storage Troubleshooting Guide HP 3PAR StoreServ 7450 Storage Troubleshooting Guide Maintaining the Service Processor HP 3PAR Service Processor Software User Guide HP 3PAR Service Processor Onsite Customer Care (SPOCC) User's Guide HP 3PAR host application solutions Backing up Oracle databases and using backups for disaster HP 3PAR Recovery Manager Software for Oracle User's recovery Guide Backing up Exchange databases and using backups for disaster recovery Backing up SQL databases and using backups for disaster recovery Backing up VMware databases and using backups for disaster recovery HP 3PAR Recovery Manager Software for Microsoft Exchange 2007 and 2010 User's Guide HP 3PAR Recovery Manager Software for Microsoft SQL Server User’s Guide HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere User's Guide

Installing and using the HP 3PAR VSS (Volume Shadow Copy HP 3PAR VSS Provider Software for Microsoft Windows Service) Provider software for Microsoft Windows User's Guide Best practices for setting up the Storage Replication Adapter HP 3PAR Storage Replication Adapter for VMware for VMware vCenter vCenter Site Recovery Manager Implementation Guide Troubleshooting the Storage Replication Adapter for VMware HP 3PAR Storage Replication Adapter for VMware vCenter Site Recovery Manager vCenter Site Recovery Manager Troubleshooting Guide Installing and using vSphere Storage APIs for Array Integration (VAAI) plug-in software for VMware vSphere HP 3PAR VAAI Plug-in Software for VMware vSphere User's Guide

HP 3PAR documentation

83

Typographic conventions
Table 14 Document conventions
Convention Bold text Element • Keys that you press • Text you typed into a GUI element, such as a text box • GUI elements that you click or select, such as menu items, buttons, and so on Monospace text • File and directory names • System output • Code • Commands, their arguments, and argument values • Code variables • Command variables Bold monospace text • Commands you enter into a command line interface • System output emphasized for scannability

WARNING! Indicates that failure to follow directions could result in bodily harm or death, or in irreversible damage to data or to the operating system. CAUTION: NOTE: Indicates that failure to follow directions could result in damage to equipment or data.

Provides additional information.

Required
Indicates that a procedure must be followed as directed in order to achieve a functional and supported implementation based on testing at HP.

HP 3PAR branding information
• • • • The server previously referred to as the "InServ" is now referred to as the "HP 3PAR StoreServ Storage system." The operating system previously referred to as the "InForm OS" is now referred to as the "HP 3PAR OS." The user interface previously referred to as the "InForm Management Console (IMC)" is now referred to as the "HP 3PAR Management Console." All products previously referred to as “3PAR” products are now referred to as "HP 3PAR" products.

84

Support and Other Resources

17 Documentation feedback
HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.

85

Glossary
Access Guard active VLUN A software component that provides volume security at logical and physical levels. Access Guard is part of the HP 3PAR OS Software Suite. The pairing of a virtual volume and a LUN so the host can access its virtual volume and I/O writes can be saved to the virtual volume. The VLUN parameters determine whether a virtual volume is expressed as an active VLUN. VLUNs that are not active will not communicate with the HP 3PAR StoreServ Storage system. The base volume that is used by the system to store administration data such as the system event log. The admin volume is created as part of the system installation and setup process. Arbitrated Loop Physical Address. A unique 8-bit value used to identify Fibre Channel devices on an arbitrated loop. A system event that requires the immediate attention of the user and might also require user intervention. Area at the bottom of the HP 3PAR Management Console main window that displays information about system alerts. User-defined threshold that can be set for Thinly-Provisioned Virtual Volumes and fully-provisioned virtual volumes to cap their potential size. User-defined threshold that can be set for Thinly-Provisioned Virtual Volumes and fully-provisioned virtual volumes to alert users when the volumes reach a certain size. A cryptographic key that protects data integrity on self-encrypting drives. The authentication key, maintained by a local key manager, and backed up and guarded by system administrators, locks and unlocks the drive. Level of fault-tolerance for a logical disk. For example, magazine-level availability means that the logical disk can tolerate a drive magazine failure. Cage-level availability means that the logical disk can tolerate a drive cage failure. A Thinly-Provisioned Virtual Volume (TPVV) or fully-provisioned virtual volume that has been copied. An enclosure that inserts into an EIA-standard rack to house a maximum of four battery backup units. Battery Backup Unit. A unit containing two batteries. Each Battery Backup Unit supplies two controller nodes with enough current to write the cache to ATA disks if power is interrupted. An enclosure that houses the components of a system. A cabinet is made up of a frame on four wheels, cosmetic panels, a rear door, an EIA-standard rack, PDUs, power cords, and bezels. A virtual volume (virtual or physical copy) created from a parent volume. A block of contiguous storage space on a physical disk. On F-Class and T-Class systems, all chunklets are 256 MB. On HP 3PAR 10000 systems, all chunklets are 1 GB. The process of writing data to a log rather than a chunklet when a chunklet is unavailable (for example, when the disk is not ready). If the chunklet becomes available, the system places the chunklet in playback mode, reads the logged data, and writes the data to the chunklet. The characteristics and guarantees of the transport layer of a Fibre Channel circuit. These classes include connection services (Class 1), guaranteed frame delivery with end-to-end flow control (Class 2), and packetized frame datagrams (Class 3). A chunklet that is set to all zeros, and therefore does not contain any data. A group of controller nodes connected via the same system backplane. The nodes in a cluster operate as a unified system, separate from any other clusters that may share the same service processor. Cache Memory Page. A 16 KB block of control cache memory where I/O requests are stored. HP 3PAR Management Console alert pane icon that represents a logical or physical system component.

admin volume AL_PA alert alert pane allocation limit allocation warning authentication key

availability

base volume battery tray BBU cabinet child volume chunklet chunklet logging

classes of service

clean chunklet cluster

CMP component indicator
86 Glossary

control cache control cache DIMM controller node controller node chassis copy data copy size copy-on-write snapshot CPG

Memory modules that support the microprocessors located in a controller node. A single control cache memory module. An individual device that works with other controller nodes to cache and manage data in a system and to provide hosts with a coherent, virtualized view of the storage system. An enclosure that houses all the controller nodes of a system. Data that occupies the snapshot data space (virtual copy space) on a virtual volume. The amount of snapshot data space (the logical disk space reserved for snapshots) in a virtual volume. A snapshot of a virtual volume made with the copy-on-write technique. This type of snapshot consists of a pointer to the source volume and a record of every change made to the source volume since the snapshot was created. Common Provisioning Group (also known as a storage pool or logical disk pool). A set of logical disks from which you can create virtual volumes and virtual copies that are capable of allocating storage on demand. Common Provisioning Group template. A CPG template contains a set of common provisioning group and logical disk parameters that HP 3PAR Management Console users can apply in order to create a new Common Provisioning Group. A host that is defined on the system but does not necessarily have any physically connected host paths or WWNs assigned to it. A software tool that restricts connections between the service processor and the HP 3PAR technical support center. Customer Controlled Access is independent of the user's network firewall and works whether the connections are made through the Internet or through a point-to-point modem connection. Cabling configuration where components such as BBUs or drive cages are connected in succession. Archived data. Data at rest may also include data that is seldom accessed and that is stored on hard drives, backup disks, or on a storage area network. The dual in-line memory modules (DIMMs) that support the HP 3PAR ASIC located in a controller node. A single data cache memory module. A printed circuit board with DIMM sockets that hold data cache memory modules. The virtual volume to which data is copied during a virtual or physical copy operation. System functionality that scans physical disks for defects by reading and writing to the system's IDE disk. The space in a drive chassis into which a drive magazine is inserted. A component in a rack or chassis that contains a drive. Drive cages connect to nodes for communication with hosts. Drives may be Fibre Channel or iSCSI. An enclosure that houses drive cages. In a multicabinet system, any cabinet that is connected to a node cabinet but does not contain controller nodes. The enclosure that houses the components of a drive chassis. A component used for housing drive cages in the front of the enclosure and nodes and I/O modules in the rear of the enclosure. An electronic circuit board mounted on a mechanical structure that is inserted into a drive bay in a drive cage. A drive magazine holds up to four physical disks. The panel used to seal off an empty drive bay. All drive bays in a drive cage must be sealed for EMI and airflow considerations.

CPG template

created host Customer Controlled Access

daisy chaining data at rest data cache data cache DIMM data cache riser card destination volume disk scrub drive bay drive cage drive chassis drive chassis cabinet drive chassis housing drive enclosure drive magazine drive magazine filler panel

87

drive mount encryption key ESI

A metal bracket used to secure a physical disk to a drive magazine. Each disk must be secured by two drive mounts. A cryptographic key that is not exposed outside of the drive itself. The encryption key is used to encrypt and decrypt all data stored on a drive. Enclosure Services Interface. Interface on the DC2 and DC4 drive cages through which the node software communicates to the cage enclosure services controller to obtain enclosure and cage status and control the cage behaviors. A detectable system occurrence. To present a virtual volume to a host. Exporting makes a volume available to a host by creating an association between the volume's name and a LUN (logical unit number) for the specified host and port. Drive type: either Fibre Channel or Serial Attached SCSI (SAS). With regard to drive types and drive capacities, the abbreviation FC applies to Fast Class. With regard to ports, the abbreviation FC applies to Fibre Channel only. Fibre Channel Arbitrated Loop. A fast serial bus interface standard used to connect storage devices to servers. A Fibre Channel PCI host bus adapter (HBA) located in a controller node. The Fibre Channel adapter connects a controller node to a host or to a drive chassis. A virtual volume (snapshot) with a set amount of user space and for which snapshot administration space and snapshot data space draw resources from a Common Provisioning Group (CPG). A network adapter located in a controller node. The Gigabit Ethernet adapter connects a controller node to a network in order to transfer data via the network. To increase the size of a virtual volume or CPG. The unit of storage space by which the system creates and allocates additional logical disks to a Common Provisioning Group (CPG) when the volumes in that CPG require additional resources. The minimum growth increment varies according to the number of controller nodes in the system (from 8 GB for a two-node system to 32 GB for a eight-node system). An optional setting that enables you to specify the maximum size to which a CPG can grow. An optional setting that enables you to specify the size at which the system alerts you to the amount of CPG growth. A path or set of paths, defined as either WWN or iSCSI names, to one or more ports on a system. The name of the host and the list of the paths (WWN or iSCSI) assigned to the host, if any. If you remove all the paths assigned to the host, the host name becomes the host definition. A VLUN template that allows a specified host connected to any port to see a virtual volume as a specified LUN (logical unit number). A data-protection solution that provides restore operations for a variety of platforms, such as Oracle, SQL Server, Exchange, and more. Software that enables you to create and continually update backup remote copies of virtual volumes and use those copies for disaster recovery, if necessary. The utility that enables the system to reallocate space usage in order to take advantage of additional resources, such as added hardware or updated CPGs. The System Tuner identifies underused chunklets and overused volumes, and balances the usage. Software that enables you to create a virtual volume that allocates resources from the CPG on demand and in small increments. Software that enables you to create virtual copies (aka snapshots) of virtual volumes. To create a virtual copy, the system uses the copy-on-write technique, which creates an up-to-date snapshot at the same time as data is written to the host. Software that enables you to create distinct domains with domain-specific users and objects.

event export

Fast Class

FC-AL Fibre Channel adapter fully provisioned virtual volume Gigabit Ethernet adapter grow growth increment

growth limit growth warning host host definition host-sees VLUN template HP 3PAR Recovery Manager Software HP 3PAR Remote Copy Software HP 3PAR System Tuner Software HP 3PAR Thin Provisioning Software HP 3PAR Virtual Copy Software HP 3PAR Virtual Domains Software

88

Glossary

IMP independent electrical circuit initiator mode initiator port iSCSI adapter iSCSI name LD

Initiator Mode Prohibited. A system setting that, when enabled, prevents a port from being set to initiator mode. An electrical circuit that does not share a circuit breaker with another electrical circuit. The firmware setting for a Fibre Channel port that is connected to a drive cage. A port that is connected to and relays commands to physical disks within a drive cage. Also known as a disk port. An iSCSI PCI host bus adapter (HBA) located in a controller node. An iSCSI adapter connects a controller node on an iSCSI port to a host. The name of an iSCSI path. You use an iSCSI name to identify that iSCSI path to a host. Logical disk. A collection of chunklets that reside on different physical disks and that are arranged as rows of RAID sets. When you create a CPG, the system creates and groups logical disks and assigns those logical disks to the CPG. Loop Initialization Primitive. The protocol by which a Fibre Channel Arbitrated Loop (FC-AL) network initializes upon power up or recovers after a failure or other unexpected condition. During loop initialization, the nodes present on the arbitrated loop identify themselves and acquire addresses on the loop. No data can be transferred on an arbitrated loop until initialization completes. Temporarily saving data to logging logical disks when physical disks are out of service (due to failure or during replacement procedures). Logging logical disk. A logical disk used for logging. During system setup, the system creates a 20 GB RAID 10 logging LD for each controller node in the system. Logical Unit Number. A number used to access a virtual volume that has been assigned to a particular host on a particular port. A laptop computer running Windows 2000 used by a field technician to initiate direct communication with the system service processor and controller nodes. A rule that allows a particular host connected to a particular port to see a virtual volume as a specified LUN. A keycode that identifies a system alert. One member of a group of mirrored chunklets, which is also known as a RAID 1 set. A data redundancy technique used by some RAID levels and in particular RAID 1 to provide data protection on a storage array. The navigation tree appears in a pane that occupies the left side of the HP3PAR Management Console main window. Each system and system object appears as an icon in the navigation tree. Virtual copy policy that prevents changes being written to a base volume when it does not have enough snapshot data or administration space to prevent virtual copies from becoming invalid, or stale, as a result. A cabinet that houses the system backplane and controller nodes. The original base volume from which a series of virtual or physical copies has been created. Any volume can be the parent from which one or more virtual copies is created, but for each set of related copies there is only one original parent base volume. A virtual volume from which a virtual or physical copy is made. A data redundancy technique used by some RAID levels (in particular RAID 5) to provide data protection on a storage array. The group of chunklets that occupy the same position within a RAID 5 logical disk parity set. An electronic circuit board that is inserted into a controller node’s PCI slot. The PCI load card allows the node to recognize an unoccupied PCI slot. Power Cooling Module. A hardware component that includes the battery, fan, and power supply. Power Distribution Unit. A device that takes in AC power from a main power source (for example, an electrical wall outlet) and distributes the power to the power supplies in a system. A point-in-time copy of an entire virtual volume.
89

LIP

logging logging LD LUN maintenance PC matched-set VLUN template message code mirror mirroring navigation tree no stale snapshots

node cabinet original parent base volume parent volume parity parity set position PCI load card PCM PDU physical copy

physical disk physical parent physical size port-presents VLUN template power bank power supply preserved data preserved data logical disks primary path

A dual-ported Fibre Channel disk mounted onto a drive magazine. The source volume for a physical copy. The total actual raw storage allocated to a logical disk, as determined by its size and RAID type. A VLUN template that allows any host connected to a particular port to see a virtual volume as a specified LUN. A group of four connected AC outlets within the power distribution unit (PDU). There are two power banks in each PDU. A device that converts current from an AC line into appropriate DC levels and provides that power to a system component. Data that is suspended in the system’s cache memory due to backend failure. RAID 10 logical disks created by the system during initial system setup to store preserved data. The logical capacity of the preserved data logical disks is equal to the sum of all data cache memory of the system. Connection between a controller node initiator port and a physical disk that is used by default. When the primary path cannot be used (a failure condition), the secondary path is used. The primary and secondary paths are not user configurable and are determined by drive magazine placement. For physical copies: to break the association between a physical copy and a base volume by changing the physical copy into an independent base volume. For virtual copies: to copy the changes from a virtual copy back onto the base volume, therefore overwriting the base volume with the virtual copy. The EIA-standard rack within a cabinet that holds the components of a system. A panel used to seal off an empty 1U, 2U, or 4U space on the rack. All empty spaces in the rack must be sealed for EMI and airflow considerations. The standard unit of height for an EIA-standard rack or components housed in an EIA-standard rack: equivalent to 1.75 in. (4.45 cm). Redundant array of independent disks. Striped rows of chunklets on two or more physical disks. A RAID 0 set offers no data redundancy. A group of mirrored chunklets. A group of parity-protected chunklets. Also known as a parity set. RAID Multi-Parity. A group of double-parity chunklets. A grouping of mirrored or parity-protected chunklets. RAID 0, RAID 10 (1), RAID 50 (5), and RAID MP (6) are all supported RAID types; however, not all RAID types may be available on your system. Remote Copy over Fibre Channel. The use of Remote Copy with two systems that are connected via Fibre Channel ports. Remote Copy over IP. The use of Remote Copy with two systems that are connected via Ethernet ports. A subdivision of a logical disk or virtual volume. The size of a region is always a multiple of 32 MB. To copy changes from one volume in a physical copy pair to the other volume because the original volume was modified at some point after the physical copy operation took place. The roles and rights assigned to a user determine which tasks the user can perform with a system. A grouping of RAID sets. Data is striped across the rows of RAID 10 and RAID 50 logical disks. The number of sets in a row. A row is a grouping of RAID sets. Data is striped across the rows of RAID 10 and RAID 50 logical disks. Registered State Change Notification. A Fibre Channel switch function that allows notification to registered nodes if a change occurs to other specified nodes.

promote

rack rack filler panel rack unit (U) RAID RAID 0 set RAID 10 (RAID 1) set RAID 50 (RAID 5) set RAID MP RAID set RAID type RCFC RCIP region resynchronize roles and rights row row size RSCN

90

Glossary

safety breaker second virtual volume backup node secondary path

The device used to power on and power off the power distribution unit. The safety breaker also prevents power surges in the AC line from damaging a system. The controller node that takes over for the virtual volume backup node if the virtual volume node fails. Connection between a controller node initiator port and a physical disk that is used when the primary path is inaccessible (a failure condition). The primary and secondary paths are not user-configurable; they are determined by drive magazine placement. A self-encrypting drive (SED) uses Advanced Encryption Standard keys to protect data from unauthorized access. SEDs contain special firmware and an application-specific integrated circuit (ASIC) that provides encryption. When encryption is enabled, the SED will lock when power is removed, and it will not be unlocked until the matching key from the HP 3PAR StoreServ system is used to unlock it. A device inserted into a rack or virtual software that enables you to locally and remotely monitor and service systems. The number of chunklets in a set. Also known as mirror depth for RAID 1 sets and parity set for RAID 5 sets. Icon in the HP 3PAR Management Console alert pane or on the HP 3PAR Management Console status bar that shows the seriousness of an alert. Small form-factor pluggable transceiver. A virtual or physical copy of a virtual volume. The space on a virtual volume that is used to track changes to the data from the time that a snapshot of a virtual volume was created. The virtual volume from which a copy is made. A chunklet that is reserved for use in case of a failure in the system. A certain number of chunklets are reserved for use as spares during the system setup and installation process; however, the system may temporarily set aside additional spares even though these chunklets are not permanently designated for use as spares. Indicates whether a chunklet is reserved as a spare or has been selected by the system for use in sparing on a temporary basis. The automatic relocation of chunklets on a physical disk when a logging logical disk becomes full. Service Processor Onsite Customer Care. A suite of service tools applications with a web-based graphical user interface that is used to support the HP 3PAR storage system and its Service Processor. Single Point of Connectivity Knowledge website. SPOCK is the primary portal used to obtain detailed information about supported HP storage product configurations. Snapshot data that is no longer valid because the base volume does not have enough snapshot administration or snapshot data space to record new changes to the base volume. A snapshot that does not track the most recent changes to its base volume. The No Stale Snapshots virtual copy policy halts writing data to the base volume in order to prevent loss of synchronization between the volume and any snapshots. A virtual volume that either passed auto-check upon system startup or was created since the system was last restarted. Started virtual volumes are ready for read/write operations. The bar at the bottom of the HP 3PAR Management Console main window that contains messages and icons. Status bar messages and icons can provide vital information about system status, including the severity level of the most serious new alert in the alert pane. The number of contiguous bytes that the system accesses before moving to the next chunklet. A virtual volume that has not been started and is therefore not ready for read/write operations.

self-encrypting drive

Service Processor set size severity indicator SFP snapshot snapshot administration space source volume spare chunklet

spare status sparing SPOCC

SPOCK stale data stale snapshot

started virtual volume status bar

step size stopped virtual volume

91

system backplane system box system manager system view pane

An electronic circuit board that contains sockets into which power supplies and controller nodes are plugged. Feature on the HP 3PAR Management Console main window toolbar that enables you to move quickly between systems. Software component that negotiates between the system and the user interfaces such as the HP 3PAR Management Console and HP 3PAR OS CLI. Area in the upper right corner of the HP 3PAR Management Console main window that displays information about systems and system objects as you select the corresponding icons in the navigation tree. The firmware setting for a port that is connected to a host. The port that is connected to and receives commands from a host computer. Also known as a host port. Table of Contents. The space on a physical disk that contains the internal description of the system. The TOCs on all physical disks in the system contain the same information. Thinly-Provisioned Virtual Volume. A virtual volume that maps to logical disk space associated with a Common Provisioning Group (CPG) and is therefore capable of growing on demand. Target Session Identifying Handle. An identifier, assigned by the iSCSI target, for a session with a specific named initiator. When using the HP 3PAR Management Console, a property that has been included in a template but does not have a defined value. When applying the template, the system will either use the default value (when applicable) or calculate the optimized setting for you. For standard base volumes, the data that is written to the user space. The amount of user space in a virtual volume, or the size of the volume as presented to the host. The space on a virtual volume that represents the size of the virtual volume as presented to the host. For standard base volumes, the user space holds all user data. For Thinly-Provisioned Virtual Volumes, no storage is actually allocated to user space, so the user space represents the volume's virtual size. A snapshot created using the copy-on-write technique. Policy that determines the course of action to take when a volume's snapshot administration space or snapshot data space becomes depleted. The size that the volume presents to the host. For standard base volumes, the virtual size is equal to the user space. For Thinly-Provisioned Virtual Volumes, no storage is actually allocated to user space, so the virtual size is determined by whatever value is assigned to the user space. A virtual storage unit created by mapping data from one or more logical disks. The controller nodes that take over for the virtual volume master node if the virtual volume master node fails. The controller node that is responsible for a virtual volume from its creation to its deletion. When the system builds a virtual volume, the system begins with the logical disk connected to the master node. A subdivision of a virtual volume. The size of a region is always a multiple of 32 MB. Virtual logical unit number. A VLUN is a virtual volume-LUN pairing expressed as either an active VLUN or as a VLUN template. A rule that sets up the association between the name of the virtual volume and a LUN-host, LUN-port, or LUN-host-port combination. The three types of VLUN templates are host-sees, port-presents, and matched-set. Virtual volume template. The template contains a set of virtual volume parameters that can be applied to create volumes with the same characteristics using the HP 3PAR Management Console. A caching technique in which the completion of a write request is not signaled until data is safely stored. Write performance with a write-through cache is approximately that of a non-cached system, but if the data written is also held in cache, subsequent read performance may be dramatically improved.

target mode target port TOC TPVV TSIH unspecified property user data user size user space

virtual copy virtual copy policy virtual size

virtual volume virtual volume backup nodes virtual volume master node virtual volume region VLUN VLUN template

VV template write-through mode

92

Glossary

WWN

World-Wide Name. A unique 64-bit or 128-bit value used to identify Fibre Channel devices on an arbitrated loop. The WWN consists of a prefix issued by the IEEE to uniquely identify the company and a suffix that is issued by the company. To fill unused storage space with the representation of the character denoting “0”. A unit of physical disk space reserved by a controller node for snapshot or snapshot administration data. A single zone may occupy space on more than one disk.

zero fill zone

93

Index
A
Active Directory Kerberos server, 20 Active Directory LDAP, 20 Active Directory LDAP server, 20 adaptive optimization, 57 admin volume, 43 alerts when spare and free chunklets are used up, 32 allocation limit, 44 allocation warning, 44 authentication, 20

G group-to-domain mapping, 23 group-to-role mapping, 22 growth increment considerations, 40 GSSAPI binding, 22 GSSAPI, 22

H hardware HP 3PAR storage system, 61 HP 3PAR peer persistence, 59 HP 3PAR Quorum Witness, 59 HP 3PAR Thin Copy Reclamation software, 56 HP 3PAR Thin Persistence software, 56 HP 3PAR Virtual Lock Software, 57

B base volumes retrieval time affected by distance from, 48 virtual copy tree relationships, 48

C chunklets, 32 free, defined, 32 conventions text symbols, 84 copy-on-write function, 47

K
Kerberos server, 20

L
LDAP Active Directory, 20 authentication, 22 authorization, 22 binding SASL, 20 data organization, 21 group-to-role mapping, 22 ldapsearch command, 21 ldp.exe, 21 OpenLDAP, 20 overview, 20 SASL binding, 22 schemas, 20 simple binding, 22 user authentication, 20 user roles, 21 LDAP and Domains authorization, 23 group-to-domain mapping, 23 LDAP authentication, 22 LDAP users vs. local users, 21 local key manager, 58 local users, 20 logging logical disk allocated at set up, 32

D data encryption, 58 default domain, 25 degraded performance, 55 DIGEST-MD5 binding, 22 DIGEST-MD5, 22 disks logical, 8 physical, 8 chunklets, 8 documentation providing feedback on, 85 domain default domain, 25 derived objects, 24 no domain, 25 specified domain, 25 types, 25 users, 19 domain users, 19 Domains, 21 Domains and LDAP, 21 drives self-encrypting, 58

M mapping overview, 51 mapping parameters, 23

F failover automatic and transparent, 59 free chunklets, defined, 32
94 Index

N naming conventions, virtual volumes, 48

O
OpenLDAP, 20 optimization adaptive , 57 priority, 59

P peer motion, 58 performance consequences of virtual volumes, 48 PLAIN binding, 22 PLAIN, 22 priority optimization, 59

S schemas, 20 self-encrypting drives, 58 simple binding, 22 snapshots creation rules, 48 stale definition, 48 tree view of, 47 SNMP (Simple Network Management Protocol), 72 symbols in text, 84

T text symbols, 84

U user rights in domains, 25

V virtual columes naming conventions, 48 virtual copies stale definition, 48 virtual volumes base retrieval time affected by distance from, 48 copy-of relationships, 48 definition, 51 deleting limitations when, 48 mapping, definition, 51 parent relationships, 48 performance consequences, 48 performance consequences of, 48

95