thin provisioning

HP StorageWorksXP24000/XP20000 Thin ProvisioningSoftware User Guide

AbstractThis guide describes how to use HP StorageWorks XP Thin Provisioning Software to create virtual storage pools on HPStorageWorks XP24000/XP20000 storage systems and dynamically allocate volumes as applications need them. Topicsinclude how to monitor virtual capacity and add to the pool without downtime. The intended audience is a storage systemadministrator or authorized service provider with independent knowledge of HP StorageWorks XP storage systems and software,including Remote Web Console, LUN Manager, and Virtual LVI/LUN.

HP Part Number: T5227-96015Published: May 2011Edition: Fifteenth

© Copyright 2007, 2011 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, CommercialComputer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government undervendor'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 expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shallnot be liable for technical or editorial errors or omissions contained herein.

Acknowledgments

Windows is a registered trademark of Microsoft Corporation.

Hitachi and Universal Replicator are registered trademarks of Hitachi, Ltd.

ShadowImage and TrueCopy are registered trademarks of Hitachi, Ltd. and Hitachi Data Systems Corporation.

Export Requirements

You may not export or re-export this document or any copy or adaptation in violation of export laws or regulations.

Without limiting the foregoing, this document may not be exported, re-exported, transferred or downloaded to or within (or to a national residentof) countries under U.S. economic embargo, including Cuba, Iran, North Korea, Sudan, and Syria. This list is subject to change.

This document may not be exported, re-exported, transferred, or downloaded to persons or entities listed on the U.S. Department of CommerceDenied Persons List, Entity List of proliferation concern or on any U.S. Treasury Department Designated Nationals exclusion list, or to parties directlyor indirectly involved in the development or production of nuclear, chemical, biological weapons, or in missile technology programs as specifiedin the U.S. Export Administration Regulations (15 CFR 744).

Revision History

DescriptionDateEdition

This edition applies to microcode version 60-01-31-00/00 or later.June 2007First

This edition applies to microcode version 60-01-68-00/00 or later.September 2007Second

This edition applies to microcode version 60-02-04-00/00 or later.November 2007Third

This edition applies to microcode version 60-02-25-00/00 or later.January 2008Fourth

This edition applies to microcode version 60-02-48-00/00 or later.April 2008Fifth

This edition applies to microcode version 60-03-04-00/00 or later.June 2008Sixth

This edition applies to microcode version 60-03-24-00/00 or later.September 2008Seventh

This edition applies to microcode version 60-04-04-00/00 or later.December 2008Eighth

This edition applies to microcode version 60-04-13-00/00 or later.February 2009Ninth

This edition applies to microcode version 60-05-00-00/00 or later.June 2009Tenth

This edition applies to microcode version 60-05-00-00/00 or later.August 2009Eleventh

This edition applies to microcode version 60-06-05-00/00 or later.December 2009Twelfth

This edition applies to microcode version 60-07-00-00/00 or later.June 2010Thirteenth

This edition applies to microcode version 60-07-50-00/00 or later.October 2010Fourteenth

This edition applies to microcode version 60-08-01-00/00 or laterMay 2011Fifteenth

Contents

1 Overview of HP StorageWorks XP Thin Provisioning Software...........................6XP Thin Provisioning Features......................................................................................................6XP Thin Provisioning Benefits......................................................................................................6

Nondisruptive Addition of Physical Disks.................................................................................7Improved Performance..........................................................................................................7Reduced Storage Acquisition Costs........................................................................................7Simplified Replication Planning..............................................................................................7

Complementary Software..........................................................................................................8

2 About XP Thin Provisioning Operations..........................................................9XP Thin Provisioning Components................................................................................................9

Relationship between XP Thin Provisioning volumes and pools...................................................9Supported Configurations.....................................................................................................9Pools................................................................................................................................10V-VOLs.............................................................................................................................10

Growing a V-VOL .........................................................................................................10Reclaiming Pages from a V-VOL......................................................................................11

V-VOL Management Table...................................................................................................11Managing Pool Capacity.........................................................................................................12

Monitoring Pool Usage Levels..............................................................................................13Full Pool Handling..............................................................................................................14Thresholds.........................................................................................................................15SIM Reference Codes.........................................................................................................16Pool Status........................................................................................................................17Balancing I/O Load Across the Pool.....................................................................................18

Interoperability with Other Products and Functions......................................................................18Using XP Continuous Access Software..................................................................................21Using XP Continuous Access Journal Software........................................................................21Using XP Business Copy Software........................................................................................22Using XP Disk/Cache Partition.............................................................................................23Using XP Auto LUN............................................................................................................23

3 Preparing for XP Thin Provisioning Operations..............................................24Preparing the Storage System and Remote Web Console Computers.............................................24

Hardware and Software Requirements..................................................................................24License Requirements..........................................................................................................24Shared Memory Requirements.............................................................................................24Operating System and File System Capacity..........................................................................24Volume and Pool Requirements............................................................................................26

Installing and Uninstalling XP Thin Provisioning...........................................................................28Installing XP Thin Provisioning..............................................................................................28Uninstalling XP Thin Provisioning..........................................................................................28

4 Using the XP Thin Provisioning GUI.............................................................29Pool Window.........................................................................................................................29V-VOL Window......................................................................................................................34XP Thin Provisioning Window...................................................................................................38New Pool Dialog Box..............................................................................................................40Change Pool Information Dialog Box.........................................................................................41

Contents 3

New V-VOL Group Dialog Box.................................................................................................42Create V-VOL Dialog Box (1)....................................................................................................42Create V-VOL Dialog Box (2)....................................................................................................44Create V-VOL Dialog Box (3)....................................................................................................47Create V-VOL Confirmation Dialog Box......................................................................................48Connect Pool Dialog Box.........................................................................................................49Change Threshold Dialog Box..................................................................................................50Associate V-VOL Groups with Pool Dialog Box............................................................................51Release V-VOL Groups from Pool Dialog Box..............................................................................52Delete V-VOL Groups Dialog Box..............................................................................................54

5 Performing XP Thin Provisioning Operations.................................................57XP Thin Provisioning Flow Chart................................................................................................57Managing Pools.....................................................................................................................57

Viewing Pool Information....................................................................................................58Creating a Pool.................................................................................................................58Associating the Pool-VOL with the Pool..................................................................................60Changing the Pool Threshold...............................................................................................60Deleting Pools...................................................................................................................61

Deleting a Single Pool...................................................................................................61Deleting Multiple Pools..................................................................................................61

Recovering Pools in Blocked Status.......................................................................................61Recovering a Single Blocked Pool....................................................................................61Recovering Multiple Blocked Pools...................................................................................62

Managing V-VOLs and V-VOL Groups.......................................................................................62Creating a V-VOL Group.....................................................................................................62Changing the V-VOL Settings...............................................................................................65

Associating a V-VOL with a Pool......................................................................................65Releasing a V-VOL from a Pool........................................................................................67Changing the V-VOL Threshold........................................................................................67Increasing V-VOL Capacity.............................................................................................67Releasing Pages in a V-VOL............................................................................................71

Changing the V-VOL Settings of Multiple V-VOL Groups..........................................................72Associating Multiple V-VOL Groups with a Pool.................................................................72Releasing Multiple V-VOL Groups from a Pool...................................................................74

Deleting V-VOL Groups.......................................................................................................76Deleting a V-VOL Group.................................................................................................76

Deleting Multiple V-VOL Groups...........................................................................................76Deleting V-VOLs.................................................................................................................77

6 Troubleshooting........................................................................................79XP Thin Provisioning Troubleshooting.........................................................................................79Managing Pool-Related SIMs....................................................................................................83Troubleshooting when using XP RAID Manager..........................................................................84Calling HP Technical Support...................................................................................................86

7 Support and Other Resources.....................................................................87Related Documentation............................................................................................................87Conventions for Storage Capacity Values...................................................................................87HP Technical Support..............................................................................................................88Subscription Service................................................................................................................88HP Websites..........................................................................................................................88Documentation Feedback.........................................................................................................88

4 Contents

Glossary....................................................................................................89

Index.........................................................................................................91

Contents 5

1 Overview of HP StorageWorks XP Thin ProvisioningSoftware

This chapter describes the general features and functions of HP StorageWorks XP Thin ProvisioningSoftware.• “XP Thin Provisioning Features” (page 6)

• “XP Thin Provisioning Benefits” (page 6)

• “Complementary Software” (page 8)Unless otherwise specified, the term storage system in this guide refers to the following disk arrays:

• HP StorageWorks XP24000 Disk Array

• HP StorageWorks XP20000 Disk ArrayThe GUI illustrations in this guide were created using a Windows computer with the Internet Explorerbrowser. Actual windows may differ depending on the operating system and browser used. GUIcontents also vary with licensed program products, storage system models, and firmware versions.

XP Thin Provisioning FeaturesXP Thin Provisioning is a new advanced thin provisioning software product that provides virtualstorage capacity to simplify administration and addition of storage, eliminate application serviceinterruptions, and reduce costs.For companies faced with ongoing rapid growth of their data storage requirements and escalatingstorage and storage management expenses, XP Thin Provisioning greatly simplifies the applicationstorage provisioning process and saves money on storage purchases.XP Thin Provisioning allows storage to be allocated to an application without actually beingphysically mapped until it is used. This as-needed method means storage allocations can exceedthe amount of storage physically installed. It also decouples the provisioning of storage to anapplication from the physical addition of storage capacity to the storage system. Both significantlysimplify the storage provisioning process.As it is needed, physical storage is nondisruptively added to the storage system and placed in acentral pool available to all thin provisioned volumes. As an application requires additionalcapacity, the storage system automatically allocates the needed additional physical storage to thevolume. Behind the scenes, XP Thin Provisioning monitors storage resources and proactively alertsyou before more physical storage is required.XP Thin Provisioning also simplifies performance optimization by transparently spreading manyhosts’ individual I/O patterns across many physical disks, thereby reducing performancemanagement concerns and optimizing performance/throughput.With XP Thin Provisioning, overall storage utilization rates improve and the entire storage systemis tuned for maximum efficiency. In addition, in tiered storage environments, it offers a usefullow-cost tier option.Coupled with the advanced features and reliability of the HP storage system, XP Thin Provisioningoffers reduced capital and management expenses, and an improved return on your storageinvestment.

XP Thin Provisioning BenefitsIn a traditional volume, when you need more storage, you must install additional disks andsimultaneously change the configuration of both the storage system and the host. This requiresextensive careful orchestration, and is disruptive to application I/O.

6 Overview of HP StorageWorks XP Thin Provisioning Software

With XP Thin Provisioning, when configuring additional storage for an application, the administratordraws from the XP Thin Provisioning pool without immediately adding physical disks. Coordinationbetween the creation of a volume and the physical disk layout are no longer a consideration.

Nondisruptive Addition of Physical DisksAn XP Thin Provisioning volume will be displayed as a Virtual LVI/LUN volume that has no actualstorage capacity. Actual storage capacity from the XP Thin Provisioning pool is assigned when thedata is written. Because the application only sees the amount of virtual capacity that is allocatedto it, additional physical disk capacity can be installed transparently when needed, without anapplication service interruption.

Improved PerformanceXP Thin Provisioning Software effectively combines many program products' I/O patterns andspreads the I/O activity across all available physical resources. Prior to XP Thin ProvisioningSoftware, optimizing to use all spindles was a complex manual task requiring considerable expertise.Avoiding disk hot spots has always been challenging because of the complexity of spreading anapplication over many spindles as well as predicting when multiple program products that sharea limited number of spindles may generate I/O patterns that cause contention and performancebottlenecks.XP Thin Provisioning Software does this automatically. By evenly spreading out hundreds of users’I/O patterns over all available spindles, XP Thin Provisioning Software will optimize aggregatethroughput and generally deliver the best performance. Balancing individual program productsand manually matching up drive spindles is no longer necessary.

Reduced Storage Acquisition CostsDefining a volume larger than the physical disk allows you to plan for additional future storageneeds during an initial installation, purchase only the physical disk capacity required at the start,and add physical storage capacity incrementally over time. This approach also provides savingsin space, power, and cooling requirements.Figure 1 (page 7) illustrates the difference between purchases made before and after installingXP Thin Provisioning.

Figure 1 Effects of XP Thin Provisioning

Simplified Replication PlanningYou can define the desired volume capacity without regard to the physical disk capacity. Forvolumes of 4.0 TB and smaller, you no longer need to use LUSE for volume expansion, which alsosimplifies creating replication pairs.

XP Thin Provisioning Benefits 7

Complementary SoftwareHP StorageWorks XP Replication SoftwareThe high-speed, nondisruptive technology of HP StorageWorks replication software rapidly createsmultiple copies of mission-critical information within XP storage systems. It keeps data RAID-protectedand fully recoverable without affecting service or performance levels. For more information aboutHP StorageWorks Replication Manager Software, HP StorageWorks XP Business Copy, HPStorageWorks XP Continuous Access, or HP StorageWorks XP Continuous Access Journal, see therespective product user guide.Performance MonitorPerformance Monitor gives you detailed point-in-time reporting of the performance metrics of thestorage system, so that you can promptly investigate threshold warnings and determine both yourvirtual and physical storage needs. For more information about Performance Monitor, see the HPStorageWorks XP24000/XP20000 Performance Monitor User's Guide.HP StorageWorks P9000 or XP Command View Advanced Edition Software Device ManagerHP StorageWorks P9000 or XP Command View Advanced Edition Software Device Managersupports the consolidation of storage operations and management functions in a system that containsmultiple heterogeneous HP StorageWorks storage systems (for example, HP XP24000/XP20000disk arrays, HP XP12000/XP10000 disk arrays, HP XP1024/XP128 disk arrays, and HPXP512/XP48 disk arrays). With regard to XP Thin Provisioning Software, Device Manager givesstorage administrators easy access to monitoring functions, including generating email alerts forthreshold punctures and issuing reports on XP Thin Provisioning virtual volumes, pool volumes, andpools.For information about using Device Manager to perform alert notification, see the administratorguide that came with Device Manager.For information about using Device Manager with XP Thin Provisioning Virtual Volumes and PoolVolumes, see the user guide that came with Device Manager.HP StorageWorks XP Performance Advisor SoftwareXP Performance Advisor Software is an Internet application that collects and monitors real-timeperformance of HP StorageWorks XP disk array products, including XP Thin Provisioning and XPSnapshot pools. You can use the simple, browser-based interface to customize data collection, setalarms, and view volumes that belong to XP Thin Provisioning and XP Snapshot pools. Using thecommand line interface and program products programming interface, you can integrate XPPerformance Advisor Software with third-party program products. XP Performance Advisor Softwarereports include the XP Thin Provisioning pool occupancy report, showing the usage of the busiestXP Thin Provisioning pools.For information about using XP Performance Advisor Software to monitor XP Thin Provisioning poolusage, see the HP StorageWorks XP Performance Advisor Software user guide .

8 Overview of HP StorageWorks XP Thin Provisioning Software

2 About XP Thin Provisioning OperationsThis chapter contains a technical overview of XP Thin Provisioning.• “XP Thin Provisioning Components” (page 9)

• “Managing Pool Capacity” (page 12)

• “Interoperability with Other Products and Functions” (page 18)

XP Thin Provisioning Components

Relationship between XP Thin Provisioning volumes and poolsFigure 2 (page 9) illustrates the relationship between an XP Thin Provisioning volume and an XPThin Provisioning pool.

Figure 2 XP Thin Provisioning

Supported ConfigurationsTable 1 Supported XP Thin Provisioning Configurations

Supported ConfigurationsItems

46 MB to 4.0 TB:• 46 MB to 4,194,303 MB, or

• 96,000 blocks to 8,589,934,592 blocks, or

• 50 to 4,473,924 cylinders

V-VOL capacity

8192 per poolMaximum number ofV-VOLs

128 per subsystem, 128 deducted from the maximum number of XP Snapshotpools.

Maximum number of pools

XP Thin Provisioning Components 9

Table 1 Supported XP Thin Provisioning Configurations (continued)

Supported ConfigurationsItems

1024 per poolMaximum number ofpool-VOLs

8 GB to 4 TBCapacity per Pool-VOL

PoolsXP Thin Provisioning requires the use of pools. A storage system supports up to 128 pools, eachof which can contain up to 1,024 pool-VOLs and 8,192 V-VOLs. Each pool requires a uniquepool ID.XP Snapshot also uses pools. The 128-pool maximum per storage system applies to the total numberof both XP Snapshot pools and XP Thin Provisioning pools. For more information about XP Snapshot,see the HP StorageWorks XP24000/XP20000 Snapshot User Guide.The total pool capacity is the total capacity of the registered XP Thin Provisioning pool-VOLs.Pool capacity is calculated by the following formula:• Total Number of pages = ( pool-VOL number of blocks 512 168 ) for each pool-VOL

• The capacity of the pool (MB) = Total number of pages x 42 − (4116 + 84 x Number ofpool-VOLs)

: truncate the part of the formula between the arrows after the decimal point. If you increasepool capacity by adding a pool-VOL, existing data in the pool automatically migrates from olderpool-VOLs to the newly added pool-VOL, balancing the usage levels of all pool-VOLs. If you donot want to automate balancing of the usage levels of pool-VOLs, consult HP technical support (see“Calling HP Technical Support” (page 86)).XP Thin Provisioning Software automatically balances the usage levels among pool-VOLs in thepool created with microcode version 60-05-0x or later. XP Thin Provisioning Software does notautomatically balance the usage levels among pool-VOLs if the cache memory is not redundant orif the pool usage level is more than the pool thresholds.For more information about pools, including a description of the Pool window, see “Pool Window”(page 29). For instructions on managing pools, see “Managing Pools” (page 57).

V-VOLsXP Thin Provisioning requires the use of V-VOLs, which are virtual volumes with no physical memoryspace. V-VOLs can be 46 MB to 4 TB.To create a V-VOL, use the Remote Web Console V-VOL window (see “V-VOL Window” (page 35)).OPEN-V is the only supported emulation type. You can define multiple V-VOLs and assign them asV-VOLs to a storage pool. A V-VOL cannot be associated with more than one pool. For moreinformation, see “V-VOL Window” (page 34) and “Managing V-VOLs and V-VOL Groups”(page 62).If the system option mode 726 is enabled, you can set only one V-VOL in one V-VOL group.Therefore, the number of V-VOL groups that can be defined in the whole storage system is thesame as the number of LDEVs that can be defined in the whole storage system. For details on thenumber of definable V-VOL groups in the whole system, see the explanation about the Copy ofV-VOL Groups number text box in the New V-VOL Group dialog box.

Growing a V-VOLYou can grow (dynamically increase the LUN capacity of) a V-VOL without migrating the data.For instructions, see “Increasing V-VOL Capacity” (page 67).

10 About XP Thin Provisioning Operations

Reclaiming Pages from a V-VOLA V-VOL used as a migration target from a traditional nondynamic provisioned volume may havelarge amounts of capacity dedicated to data that is all binary zeros. The XP Thin Provisioning poolcapacity used for the binary zero data written to the V-VOL can be reclaimed and returned asavailable pool capacity. Capacity is provided to V-VOLs from the XP Thin Provisioning pool in42-MB sized pages. Reclaiming capacity requires that these pages have only binary zero datawritten to it. For instructions on how to reclaim pages containing binary zero data, see “ReleasingPages in a V-VOL” (page 71).Note that while releasing pages in a V-VOL, performance of host I/O to the V-VOL temporarilydecreases.You cannot reclaim pages taken up by a V-VOL if any nonbinary zero data has been written tothem. In this case, the pages can be reclaimed only when the V-VOL is no longer needed and isdeleted.If you perform the binary zero data discard operation, XP Thin Provisioning automatically rebalancespool-VOL usage levels. If you do not want to automatically balance the usage levels of pool-VOLs,consult HP technical support (see “Calling HP Technical Support” (page 86)).XP Thin Provisioning Software automatically balances the usage levels among pool-VOLs in a poolcreated with microcode version 60-05-0x or later. XP Thin Provisioning Software does notautomatically balance the usage levels among pool-VOLs if the cache memory is not redundant orif the pool usage level is more than the pool thresholds.

V-VOL Management TableBefore you can use XP Thin Provisioning, a V-VOL management table is created. The V-VOLmanagement table associates V-VOLs (virtual volumes) with a pool. The V-VOL management tableis created automatically when the required additional shared memory is installed by your HP servicerepresentative.If data is lost from shared memory, the V-VOL management table will be restored using data storedin reserved system areas inside the Pool. If this restore is unsuccessful, a stored copy of sharedmemory will be copied from the SVP. This process is explained in Table 2 (page 12).

XP Thin Provisioning Components 11

Table 2 How the V-VOL Management Table Is Stored When Data Is Lost From the Shared Memory

Microcode VersionItems

60–02–xx or later60–01–xx

In addition to the SVP HDD, adedicated area that is automaticallycreated in the pool when the pool iscreated.If the area is already created withmicrocode version 60-01-xx, there isno need to create the pool again, etc.,after upgrading to micro-version60-02-xx or later.

SVP HDD.The system option mode 460 of theSVP must be set to ON. You are notrequired to set the system optionbecause this is a factory setting.

Location where V-VOLmanagement tablememory is stored in sharedmemory

When you switch off the power supply.When the V-VOL management table isupdated, such as during pageallocation, pool creation, and so on.It is also stored for any pool createdwith microcode version 60-01-xx whenthe microcode exchange is replaced.

When you switch off the power supply.When the V-VOLmanagement table inshared memory is stored

When you switch on the power supplyafter shared memory was volatilizedRestoring the data from the dedicatedarea in the pool may take more timecompared to restoring data from theSVP HDD. Therefore, mode 460 = ONis recommended. When mode 460 =ON, the data is stored in both the SVPHDD and the dedicated area in thepool.The time required for restoring themanagement table from the dedicatedarea in the pool depends on the poolusage or the V-VOL usage. Forexample, when the pool usage or theV-VOL usage is 100 TB, powering ontakes at least 20 minutes more thanusual, depending on the condition ofthe storage system.

When you switch on the power supplyafter shared memory was volatilized.

When the V-VOLmanagement table inshared memory is restored

NOTE: Pools are blocked when an attempt to restore data from both the SVP HDD and thededicated area in the pool fails (for example due to a HDD failure). If the pools are blocked, callHP technical support (see “Calling HP Technical Support” (page 86)).

Managing Pool CapacityOne of the key features of XP Thin Provisioning is that you can define V-VOLs that have a greatercapacity than the pool capacity. However, if you run out of free space in the pool, the host cannotexpand the data written to the V-VOLs. It is therefore essential to closely monitor pool capacity, sothat you can increase it as needed.You can monitor pool capacity directly with the XP Thin Provisioning window (see “XP ThinProvisioning Window” (page 38)). You can also use Performance Monitor, RAID Manager, P9000or XP Command View Advanced Edition software Device Manager, and XP Performance AdvisorSoftware to monitor used pool capacity. For more information on Performance Monitor, see HPStorageWorks XP24000/XP20000 Performance Monitor User Guide.


Device Manager can be configured to output SNMP traps as a log file so you can monitor devicescentrally in storage areas and program products. In addition, the Device Manager can send alertsby email.For more information on Device Manager SNMP traps and email notification, see the administratorguide that came with Device Manager.

Monitoring Pool Usage LevelsSeveral tools allow you to view both the current pool usage rates and the changes over time forthose usage rates. These tools allow you to monitor the pool free space and estimate when youwill need to increase the pool capacity.

• You can use the XP Thin Provisioning window. For more information, see “XP Thin ProvisioningWindow” (page 38).

• You can use RAID Manager. For more information, see the HP StorageWorks RAID ManagerUser Guide.

• You can use Device Manager. For more information, see the user guide that came with DeviceManager.

Figure 3 (page 13) shows a sample display of the changes in pool usage levels.

Figure 3 Sample Pool Information

You can use both XP Performance Advisor and Performance Monitor to collect I/O data on V-VOLand pool usage:• Using XP Performance Advisor:

The current used pool capacity and the chronological changes in the used pool capacity◦◦ The current used V-VOL capacity (ratio of the stored data) and the chronological changes

in the used V-VOL capacity

• Using Performance Monitor:Frequency of V-VOL access, read hit ratio, and write hit ratio◦

◦ Pool I/O rates in the parity group

Figure 4 (page 14) shows management of usage levels and operation information.

Managing Pool Capacity 13

Figure 4 Managing Usage Rates and I/Os

Full Pool HandlingFull Pool conditions can be managed in two ways. The difference between the two handlingmethods is how a V-VOL is treated if it requires new pool capacity when no capacity is available.The default method used during a full pool condition is to fail some read and write operations toV-VOLs using the pool. Read and write operations are handled in the following way:• Successfully read data that already exists in the V-VOL. Reads to Pool Pages already assigned

to the V-VOL are successful.• Successfully update (write) data that already exists in the V-VOL. Writes to Pool Pages already

assigned to the V-VOL are successful.• Fail a read operation that specifies an LBA address that is not assigned to a page. This read

would be for an area that has never been written to the V-VOL.• Fail a write operation that species an LBA address that is not assigned to a page. This write

operation requires free pool capacity that is not available.The second method used during a full pool condition is enabled using System Option Mode 729.Call HP Technical Support to inquire how to enable this option (see “Calling HP Technical Support”(page 86)). This method uses Data Retention Utility to manage V-VOLs that are impacted by thepool full condition. Only V-VOLs that have required free pool capacity during a pool full conditionare impacted. All V-VOLs that have not requested free capacity continue to operate without anyread or write problems imposed by the pool full condition.Using the second method, a V-VOL that requests a free page from the pool to support a write toan LBA address that is not mapped to an existing allocated page to the V-VOL is immediatelychanged to Protect status using Data Retention Utility. In this case, the V-VOL becomes read andwrite protected when a write fails due to the pool-full condition. This protection status preservesthe integrity of the V-VOL by making it inaccessible.If a V-VOL is set to Protect status, the Remote Web Console Data Retention window indicates thatthe Protection attribute was added to the V-VOL, the S-VOL column displays Enable, and theRetention Term column displays 0 days. However, if the Protect attribute is added to a V-VOL withthe S-VOL Disable attribute, the S-VOL column remains Disable.


To set the pool capacity to a sufficient level when the hosts write to the V-VOL, call HP TechnicalSupport. You can make such settings if the pool is not associated with V-VOLs exceeding the poolcapacity. If the total V-VOL capacity exceeds the pool capacity after you perform such settings,you cannot associate V-VOLs with the pool or increase the V-VOL capacity.Once capacity has been added to the pool then the administrator should use the Remote WebConsole Data Retention window to view the V-VOLs impacted by the previous pool-full conditionand also to reset the protection status of the V-VOL. Once the protection status is reset, normaloperations can be returned to the hosts.

ThresholdsXP Thin Provisioning monitors V-VOLs capacity and pools capacity by thresholds. There are twotypes of thresholds: V-VOL thresholds and pool thresholds.

• Pool thresholds: A pool threshold is the proportion (%) of used capacity of the pool to the totalpool capacity. Each pool has its own Pool threshold values that are divided into a variablethreshold and a fixed threshold, for example:◦ Threshold 1: You can set it between 5% and 95%, in 5% increments. The default value

is 70%.◦ Threshold 2: Fixed at 80%.Pool usage over either threshold will cause a warning to be issued via a SIM and an SNMPtrap.Example: When the total pool capacity is 1 TB and threshold 1 is 50%Figure 5 (page 15) shows the pool capacity (when pool threshold 1 is 50%). If the usedcapacity of the pool is larger than 50% (500 GB) of the total pool capacity, a SIM and anSNMP trap are reported. If the used capacity of the pool increases and it exceeds threshold2 (80%), a SIM and an SNMP trap are reported again.

Figure 5 Pool Capacity (When Pool Threshold 1 Is 50%)

• V-VOL thresholds:The V-VOL threshold is the ratio (%) of the unassigned pool capacity to the unassigned V-VOLcapacity. The threshold can be specified from 5% to 300%.If the following formula is true, a SIM and an SNMP trap are reported:

Unassigned V-VOL capacity x threshold > unassigned pool capacity

Example: When the V-VOL threshold is 300%Figure 6 (page 16) shows the V-VOL capacity and the pool capacity (when the V-VOL thresholdis 300%). When a V-VOL capacity is 1 TB and the assigned capacity is 500 GB, theunassigned capacity of the V-VOL is 500 GB. Therefore, if free space of the pool is smallerthan 1.5 TB (500 GB x 300%) of the unassigned capacity of the pool, a SIM and an SNMPtrap are reported.Because a pool is sometimes used by multiple V-VOLs, the pool sometimes requires free spacelarger than the unassigned capacity of the V-VOL. So, you can specify the V-VOL thresholdto a value more than 100%.


Figure 6 V-VOL Capacity and Pool Capacity (When V-VOL Threshold Is 300%)

Example 2: When the V-VOL threshold is 90%Figure 7 (page 16) shows the V-VOL capacity and the pool capacity (when the V-VOL thresholdis 90%). If free space of the pool is smaller than 450 GB (500 GB x 90%) of the unassignedcapacity of the pool, a SIM and an SNMP trap are reported.

Figure 7 V-VOL Capacity and Pool Capacity (When V-VOL Threshold is 90%)

SIM Reference CodesTable 3 (page 16) lists the SIM reference codes pertaining to XP Thin Provisioning. For moreinformation on completing SIMs, see “Managing Pool-Related SIMs” (page 83).

Table 3 SIM Reference Codes

Various Types ofReports

Thresholds orValues

EventsCodes (XXX ispool ID)

Report to the host: YesCompletion report toRemote Web Console:YesInformation to theoperator: No

5% to 95% in 5%incrementsDefault: 70%.

Pool usage levelexceeded pool threshold1.

620XXX(XXX is poolID)


80% fixed.Pool usage levelexceeded pool threshold2.



Table 3 SIM Reference Codes (continued)

Various Types ofReports

Thresholds orValues

EventsCodes (XXX ispool ID)

Report to the host: YesCompletion report toRemote Web Console:Yes.Information to theoperator: No

100%.Pool is full.622XXX(XXX is poolID)

Report to the host: YesCompletion report toRemote Web Console:NoInformation to theoperator: Yes

Not applicable.Error occurred in thepool.


Report to the host: YesCompletion report toRemote Web Console:YesInformation to theoperator: Yes

Not applicable.No space in the sharedmemory.

624XXX

Report to the host: Yes.Completion report toRemote Web Console:Yes.Information to theoperator: Yes withSOM741.

Highest Poolthreshold (80% to95%).

Pool usage levelcontinues to exceed thehighest pool threshold.

625000


5% to 300% in 5%incrementsDefault: 5%If pool IDs are thesame, only oneSIM is reportedeven if the V-VOLsare different

Level of free poolcapacity to free V-VOLcapacity exceededV-VOL threshold


Report to the host: NoCompletion report toRemote Web Console:NoInformation to theoperator: Yes

Not applicableV-VOL managementarea cannot be saved toa pool

640XXX (XXXis pool ID)

Pool Status“Pool Status” (page 18) lists the pool status definitions.


Table 4 Pool Status

SIM CodesDefinitionStatus

If the pool usage level exceeds eitherthe variable or the fixed poolthreshold, the following SIM occurs.620XXX or 621XXX (XXX is pool ID)

Normal status. The pool usage level may exceed thevariable or fixed pool threshold.

Normal

NonePool-VOL in the pool is blocked or being formatted.Warning

If the pool is full or an error occurs inthe pool, the following SIM occurs.622XXX or 623XXX (XXX is pool ID)

The pool is full or an error occurred in the pool,therefore the pool is blocked.

Blocked

Balancing I/O Load Across the PoolWhen defining a pool, dedicate as many array groups as needed to support the I/O load of theplanned V-VOLs.When adding capacity to an XP Thin Provisioning pool defined using firmware 60-05-0X or later,the rebalancing function moves some existing data for V-VOLs from older pool volumes to thenewest pool volumes. The rebalance function rebalances each V-VOL's data (pages assigned)evenly across each pool volume in the pool.When adding capacity to the pool defined using firmware earlier than 60-05-0X, typically addabout the same amount of space as defined originally.

Interoperability with Other Products and FunctionsIn certain cases, XP Thin Provisioning V-VOLs and pool-VOLs can be used in conjunction with otherXP software products. Table 5 (page 18) lists the operations that are permitted and not permitted.Note that XP Thin Provisioning supports OPEN-V volumes only.

Table 5 Using XP Thin Provisioning with Other Products

Not PermittedPermittedOption Name

NoneCache Residency ManagerFor more information, see the HPStorageWorksXP24000/XP20000 CacheResidency Manager User Guide.

Using a V-VOL as a SnapshotS-VOL, or Pool-VOL.Using an XP Thin Provisioningpool-VOLs as a Snapshot P-VOL,S-VOL, or Pool-VOL.Increasing the capacity of V-VOLused by this program productDiscarding zero data, and runningXP Snapshot to the same V-VOL(This operation will be prohibitedby the microcode).

Using a V-VOL as a SnapshotP-VOL.The maximum total number of bothXP Snapshot and XP ThinProvisioning pools per storagesystem is 128. Snapshot pool limitsare reduced by the number of XPThin Provisioning pools.

XP SnapshotFor more information, see the HPStorageWorksXP24000/XP20000 SnapshotUser Guide.

Use on XP Thin Provisioningpool-VOLs.

Performing operations on V-VOLs.Data Retention UtilityFor more information, see the HPStorageWorksXP24000/XP20000 DataRetention Utility User Guide.


Table 5 Using XP Thin Provisioning with Other Products (continued)



Performing operations on V-VOLs.Database Validator

Use on XP Thin Provisioningpool-VOLs or V-VOLs.

NoneLUN Expansion (LUSE)For more information, see the HPStorageWorksXP24000/XP20000 LUNExpansion User Guide.


Performing operations on V-VOLs.LUN Manager, LUN SecurityFor more information, see the HPStorageWorksXP24000/XP20000 LUNManager User Guide.


Performing operations on V-VOLs.XP Performance ControlFor more information, see the HPStorageWorksXP24000/XP20000 PerformanceControl User Guide.

Use an XP Thin ProvisioningPool-VOL as an XP Business CopyP-VOL or S-VOL.Increasing the capacity of V-VOLused by this program product.Discarding zero data, and runningXP Business Copy to the sameV-VOL (This operation will beprohibited by the microcode).

Using a V-VOL as an XP BusinessCopy P-VOL or S-VOL. See “UsingXP Business Copy Software”(page 22) for more information.

XP Business CopyFor more information, see the HPStorageWorksXP24000/XP20000 BusinessCopy Software User Guide.

Using an XP Thin Provisioningpool-VOL as an XP ContinuousAccess P-VOL or an S-VOL.Increasing the capacity of V-VOLused by this program product.

Using a V-VOL as an XPContinuous Access P-VOL or anS-VOL.

XP Continuous AccessFor more information, see the HPStorageWorksXP24000/XP20000 ContinuousAccess Software User Guide.

Use on XP Thin Provisioningpool-VOLs or V-VOLs.Increasing the capacity of V-VOLused by this program product.

NoneXP Continuous AccessAsynchronousFor more information, see HPStorageWorksXP24000/XP20000 ContinuousAccess Software User Guide.

Using a V-VOL as an XPContinuous Access Journal journalvolume.Use on XP Thin Provisioningpool-VOLs.Increasing the capacity of V-VOLused by this program product.

Using a V-VOL as an XPContinuous Access Journal P-VOLor S-VOL. In this case, both the XPContinuous Access Journal P-VOLand S-VOL must be V-VOLs.

XP Continuous Access JournalFor more information, see theXP24000/XP20000 ContinuousAccess Journal Software UserGuide.

Interoperability with Other Products and Functions 19

Table 5 Using XP Thin Provisioning with Other Products (continued)


Increasing the capacity of V-VOLmapped to another storage system.If you try to increase the capacityof the external volume, thecapacity of the volume will be thesame capacity as the formercapacity. To increase the capacity,release the mapping to the V-VOLfrom the mapping device.

Enabling volumes created by XPExternal Storage Software to beused as pool-VOLs.

HP StorageWorks XP ExternalStorage

Performing Virtual LUN operationson volumes that are alreadyregistered in an XP ThinProvisioning pool.

Registering Virtual LUN volumes inXP Thin Provisioning pools.

Virtual LUNFor more information, see the HPStorageWorksXP24000/XP20000 VirtualLVI/LUN (VLL) and VolumeShredder User Guide.

Performing operations on XP ThinProvisioning V-VOLs andpool-VOLs. See “Using XPDisk/Cache Partition” (page 23)for more information.

XP Disk/Cache PartitionFor more information, see the HPStorageWorksXP24000/XP20000 Disk/CachePartition User Guide.

Use on XP Thin Provisioningpool-VOLs.Increasing the capacity of V-VOLused by this program product.Discarding zero data, and runningXP Auto LUN to the same V-VOL(This operation will be prohibitedby the microcode).

Using a V-VOL as a migrationsource or a migration target.

XP Auto LUNFor more information, see the HPStorageWorksXP24000/XP20000 Auto LUNSoftware User Guide.

Use on XP Thin Provisioningpool-VOLs.Increasing the capacity of V-VOLused by this program product.Discarding zero data, and runningVolume Shredder to the sameV-VOL (This operation will beprohibited by the microcode).

Use on V-VOLs.Volume ShredderFor more information, see the HPStorageWorksXP24000/XP20000 VirtualLVI/LUN (VLL) and VolumeShredder User Guide.


Using XP Continuous Access SoftwareYou can use XP Thin Provisioning in combination with XP Continuous Access to replicate V-VOLs.You can also use XP Continuous Access as a tool to move the data of the V-VOL for I/O loadreasons. The recommended movement is between the P-VOL in pool A and S-VOL in pool B.Figure 8 (page 21) illustrates the interaction when the XP Continuous Access P-VOL and S-VOL arealso XP Thin Provisioning V-VOLs. Table 6 (page 21) lists the specifics.

Figure 8 Using XP Thin Provisioning Software

Table 6 Supported XP Continuous Access Software and XP Thin Provisioning Combinations

ExplanationXP Continuous Access S-VOLXP Continuous Access P-VOL

SupportedAt initial PAIR create time, pages in theS-VOL are freed if not needed forreplicating the P-VOL.

XP Thin Provisioning V-VOLsXP Thin Provisioning V-VOLs

Supported, but the Quick Restorefunction is not available.

Normal volumesXP Thin Provisioning V-VOLs

Supported, but the Quick Restorefunction is not available.This combination consumes the sameamount of pool capacity as the originalnormal volume (P-VOL).

XP Thin Provisioning V-VOLsNormal volumes

NOTE: You cannot specify an XP Thin Provisioning pool-VOL as an XP Continuous Access P-VOLor S-VOL. If the cache write pending rate exceeds 55%, the copy process stops temporarily.

If you retry the Quick Restore or XP Auto LUN function on V-VOLs where Quick Restore has beenalready been performed, error 5208 65714 may occur. If the error occurs, use the followingequation to calculate how long to wait before retrying:(Pool Capacity in terabytes x 3 seconds) + 40 minutesHeavy workload on the storage system could add additional time to the wait period. If the V-VOLoperation status is in Processing state, then wait for the state to change to Ready before attemptingAuto LUN or Quick Restore.

Using XP Continuous Access Journal SoftwareYou can use XP Thin Provisioning in combination with XP Continuous Access Journal to replicateV-VOLs. You can also use XP Continuous Access Journal as a tool to move the data of the V-VOLfor I/O load reasons. The recommended movement is between the P-VOL in pool A and S-VOL inpool B. Figure 9 (page 22) illustrates the interaction when the XP Continuous Access Journal P-VOLand S-VOL are also XP Thin Provisioning V-VOLs. Table 7 (page 22) lists the specifics.


Figure 9 Using XP Thin Provisioning and XP Continuous Access Journal

Table 7 Supported XP Continuous Access Journal and XP Thin Provisioning Combinations

ExplanationXP Continuous Access Journal S-VOLXP Continuous Access Journal P-VOL

SupportedAt initial PAIR create time, pages in theS-VOL are freed if not needed forreplicating the P-VOL.

XP Thin Provisioning V-VOLsXP Thin Provisioning V-VOLs

SupportedNormal volumesXP Thin Provisioning V-VOLs

SupportedThis combination consumes the sameamount of pool capacity as the originalnormal volume (P-VOL).


NOTE: You cannot specify an XP Thin Provisioning pool-VOL as an XP Continuous Access Journal P-VOL or S-VOL.If the cache write pending rate exceeds 55%, the copy process stops temporarily.

Using XP Business Copy SoftwareYou can use XP Thin Provisioning in combination with XP Business Copy Software to replicateV-VOLs. You can also use XP Business Copy as a tool to move the data of the V-VOL for I/O loadreasons. HP recommends movement between the P-VOL in pool A and the S-VOL in pool B.Figure 10 (page 22) illustrates the interaction when the XP Business Copy P-VOL and S-VOL arealso XP Thin Provisioning V-VOLs. Table 8 (page 22) lists the specifics.

Figure 10 Using XP Thin Provisioning and XP Business Copy

Table 8 Supported XP Business Copy and XP Thin Provisioning Combinations

ExplanationBusiness Copy S-VOLXP Business Copy P-VOL

SupportedXP Thin Provisioning V-VOLsXP Thin Provisioning V-VOLs

Supported, but the Quick Restorefunction is not available.

Normal volumesXP Thin Provisioning V-VOLs

NOTE: This combination consumesthe same amount of pool capacity asthe normal volume (P-VOL).



NOTE: You cannot specify an XP Thin Provisioning pool-VOL as an XP Business Copy P-VOL orS-VOL.Zero page Reclaim (zero page discard) will not operate on a V-VOL being used as a P-VOL orS-VOL. Also you cannot make a P-VOL or S-VOL from a volume currently undergoing Zero PageReclaim.

Using XP Disk/Cache PartitionYou can assign V-VOLs and pool-VOLs to XP Disk/Cache Partition SLPRs and CLPRs, with thefollowing restrictions:• All pool-VOLs in a pool must be allocated to the same CLPR.

• HP recommends that V-VOLs and the associated pool are allocated to the same CLPR.For more information, see HP StorageWorks XP24000/XP20000 Disk/Cache Partition User Guide.

Using XP Auto LUNConsider the following when you move V-VOLs using XP Auto LUN or XP Tiered Storage Manager:

• V-VOLs have two emulation types, OPEN-0V and OPEN-V. You can check the emulation typeof V-VOLs in the LDEV window of the Report Display window of Remote Web Console. Formore information about the LDEV window, see the HP StorageWorks XP24000/XP20000Remote Web Console User Guide.

• You cannot move OPEN-0V V-VOLs to OPEN-V normal volumes. Conversely, you cannot moveOPEN-V normal volumes to OPEN-0V V-VOLs. If you need to move volumes in this way, changethe emulation type from OPEN-0V to OPEN-V. For more information about changing anemulation type, see “V-VOL Window” (page 34).When both migration source volume and the migration destination volume are V-VOLs, theycan be moved regardless of emulation types such as OPEN-0V or OPEN-V.For more information about XP Auto LUN, see the HP StorageWorks XP24000/XP20000Auto LUN User Guide.

• If you retry the XP Auto LUN or Quick Restore function on V-VOLs where XP Auto LUN hasalready been performed, error 5208 65714 may occur. If the error occurs, use the followingequation to calculate how long to wait before retrying:(Pool Capacity in terabytes x 3 seconds) + 40 minutesHeavy workload on the storage system could add additional time to the wait period. If theV-VOL operation status is in Processing state, then wait for the state to change to Ready beforeattempting Auto LUN or Quick Restore.


3 Preparing for XP Thin Provisioning OperationsThis chapter describes the necessary environment for XP Thin Provisioning.• “Preparing the Storage System and Remote Web Console Computers” (page 24)

• “Installing and Uninstalling XP Thin Provisioning” (page 28)

Preparing the Storage System and Remote Web Console Computers

Hardware and Software RequirementsBefore launching XP Thin Provisioning, you must take several preliminary steps. These include thefollowing:

• Install the storage system.

• Install the Remote Web Console computers, and connect them to the storage system internalLAN.

• Enable XP Thin Provisioning on each storage system where you intend to use the option.

• If you intend to use XP Thin Provisioning V-VOLs as XP Business Copy P-VOLs or S-VOLs, youmust also install XP Business Copy Software. For detailed instructions on enabling RemoteWeb Console product options, see the HP StorageWorks XP24000/XP20000 Remote WebConsole User Guide.

• If you intend to increase the capacity of V-VOL, XP RAID Manager must be installed on yourhost server.

License RequirementsYou will need an XP Thin Provisioning license for the total pool capacity. Licensed capacity for XPThin Provisioning Software is priced per storage system. If you are using XP Disk/Cache Partition,you are not charged for license capacity per storage logical partition (SLPR).If you are using XP Business Copy, XP Continuous Access, or XP Continuous Access Journal, youneed a license for the total consumed pool capacity in use by all P-VOLs and S-VOLs. If the totalused pool capacity exceeds the licensed capacity, the additional capacity is treated as a temporarylicense. You will be able to use the additional capacity for 30 days. After 30 days, you will notbe able to perform XP Business Copy operations except for deleting pairs. After 30 days, you willnot be able to perform XP Continuous Access or XP Continuous Access Journal operations exceptfor suspending copy operations and deleting pairs. For more information about temporary licensecapacity, see the HP StorageWorks XP24000/XP20000 Remote Web Console User Guide.

Shared Memory RequirementsXP Thin Provisioning requires its own dedicated shared memory for the V-VOL management area,which is separate from the shared memory for XP Snapshot. The required shared memory will beinstalled by your HP service representative.

Operating System and File System CapacityInitializing a P-VOL in most operating systems and file systems consumes some XP Thin Provisioningpool space. Some operating system—file system combinations initially take up little pool spacewhile other combinations take as much pool space as the virtual capacity of the V-VOL.Table 9 (page 25) shows the effects of those combinations. For more information, contact your HPservice representative.

24 Preparing for XP Thin Provisioning Operations

Table 9 Operating System and File System Capacity

Pool Capacity ConsumedMetadata WritingFile SystemOperatingSystem

Size of V-VOL.If you change the Allocation GroupSize settings when you create thefile system, the metadata can bewritten to a maximum of 64 MB.Approximately 65% of the pool isused.

Writes metadata in 8 MB intervals.JFSAIX

Small (one page).Writes metadata to first block.JFS2

Small (one page).Writes metadata to first block.VxFS

Small (one page).Writes metadata to first block.JFS (VxFs)HP-UX

Size of V-VOL.Writes metadata in 10 MBintervals.

HFS

Depends on allocation group size.The amount of pool spaceconsumed is approximately [V-VOLSize]*[42 MB/Allocation GroupSize].

Writes metadata in AllocationGroup Size intervals.

XFSLinux

About 33 % of the size of theV-VOL.The default block size for these filesystems is 4 KB. This results in 33%of the V-VOL acquiring pool pages.If the file system block size ischanged to 2 KB or less, the V-VOLPage consumption becomes 100%.

Writes metadata in 128 MBintervals.

Ext2Ext3

Size of V-VOL.Writes metadata in 52 MBintervals.

UFSSolaris

Small (one page).Writes metadata to first block.VxFS

Small (one page).The allocated capacity increases ifthe update of the file is repeated,and the effectiveness of reducingthe pool capacity consumptiondecreases.

Writes metadata to first block.NTFSWindowsServer 2003

Small (one page).If you perform the standard formatoperation when creating the filesystem, the size of the poolcapacity as same as the file systemcapacity is consumed. In this case,we recommend the quick format.The allocated capacity increases ifthe update of the file is repeated,and the effectiveness of reducingthe pool capacity consumptiondecreases.

Writes metadata to first block.NTFSWindowsServer 2008

Small (one page).Writes metadata to first block.VFSTru64

Small (one page).Writes metadata to first block.AdvFS

Small (one page).Writes metadata to first block.VMSOpenVMS

Preparing the Storage System and Remote Web Console Computers 25

Table 9 Operating System and File System Capacity (continued)

Pool Capacity ConsumedMetadata WritingFile SystemOperatingSystem

Small (one page).Writes metadata to first block.NSKNonStop

Small (one page).VMware eager-zeroed thickformatting is not recommendedbecause it forces the volume to fullyallocate space in the pool.VMware thin formatting is notsupported due to unpredictableresults.

Writes metadata to first block.VMWVMware (ESXServer)

Volume and Pool RequirementsPool-VOL requirements are described in Table 10 (page 26). Pool requirements are described in“Pool Requirements” (page 27). V-VOL requirements are described in “V-VOL Requirements”(page 27).

Table 10 Pool-VOL Requirements

RequirementItem

Logical volume (LDEV). Separating pool-VOLs from other volumes into differentparity groups is recommended for best performance.You cannot specify the following volumes as XP Thin Provisioning pool-VOLs:

• Volumes used by XP Business Copy, XP Auto LUN, XP Continuous Access, XPContinuous Access Asynchronous, or XP Continuous Access Journal

• LUSE volumes

• Volumes defined by Cache Residency Manager

• Volumes already registered in XP Snapshot or XP Thin Provisioning pools

• Volumes used as XP Snapshot P-VOLs or S-VOLs

• Data Retention Utility volumes with a Protect, Read Only, or S-VOL Disableattribute

• Volumes whose LDEV attribute is other than normal or Normal (Quick Format)

• System disks

• Command devices

• Quorum disks

You cannot store any pool-VOLs in a pool, including external volumes with a cachemode attribute.

Volume type

OPEN-VEmulation type

Any RAID level.• Volumes with different RAID levels in a pool is not recommended.

• RAID-6 is recommended for large pools and where recovery time due to drivefailure may be unacceptable.

RAID level

FC, SATA, and flash drive can be used as drive type.Internal Volume pool-VOLs: Cannot be intermixed in the same pool if drive typesare different.External Volume pool-VOLs: Cannot be intermixed in the same pool if drive typesare different; however, this configuration is not recommended for performancereasons.

Drive type

8 GB to 4 TB.Volume capacity


Table 10 Pool-VOL Requirements (continued)

RequirementItem

You must perform LDEV formatting before the volume is registered in a pool. Youcannot format pool-VOLs.

LDEV format

You cannot remove pool-VOLs registered in pools. You need to delete the pool inorder to free the volumes.

Deleting pool-VOLs

You cannot specify a volume with a path definition as a Pool-VOL.Path definition

Table 11 Pool Requirements

RequirementItem

See “Pools” (page 10) for the formula for calculating capacity. The upper limit oftotal capacity of all pools is 1.1 PB.

Pool capacity

Up to 1024 per pool.Max number ofpool-VOLs

Up to 128 total pools maximum per storage system for XP Thin Provisioning. PoolIDs (0 to 127) are assigned as pool identifiers. The number of XP Thin Provisioningpools reduces the total availability of XP Snapshot pools.

Max number of Pools

You can increase Pool-VOL capacity dynamically; increasing capacity by one ormore parity groups is recommended.

Increasing capacity

You cannot reduce pool capacity. You must delete and then reconfigure the pool.Reducing capacity

You can delete pools that are not associated with any V-VOLs.Deleting

Pool threshold 1: Default value is 70%. You can set it between 5% and 95%, in5% increments.Pool threshold 2: Fixed at 80%.Pool usage over either threshold will cause a warning to be issued using a SIMand an SNMP trap.

Thresholds

42 MBData allocation unit

Table 12 V-VOL Requirements

RequirementItem

V-VOL. The LDEV number is the same as for normal volumes.Volume type

Servers (including XP RAID Manager) will show emulation types as follows:• OPEN-0V for V-VOLs created with microcode version 60.02.06 or earlier

• OPEN-V for V-VOLs created with microcode version 60-02-25 or later

Emulation type

Up to 8,192 volumes per poolUp to 1,024 volumes per volume groupUp to 63,232 volume groups per system

Maximum number ofV-VOLs

46 MB to 4 TB per volumeTotal maximum volume capacity of 1.1 PB per storage system.

Volume capacity

The V-VOL threshold is the proportion of the potential demand a V-VOL can consumeof the pool capacity.The default value is 5% of the potential capacity. You can set it between 5% and300%, in 5% increments. The default value is recommended.

Threshold

Preparing the Storage System and Remote Web Console Computers 27

Table 12 V-VOL Requirements (continued)

RequirementItem

Available. However, you cannot define paths unless you first associate the V-VOLwith a pool.

Path definition

Available.When you perform LDEV formatting on the V-VOLs, the storage system initializesdata only in the consumed pool pages of the V-VOLs. However, after you performan LDEV format, the free space in the pool does not increase because the pagesare not released.

LDEV format

Installing and Uninstalling XP Thin ProvisioningGeneral installation instructions are contained in the HP StorageWorks XP24000/XP20000 RemoteWeb Console User Guide. This section contains an outline of the additional instructions that arespecific to XP Thin Provisioning.

Installing XP Thin Provisioning1. Your HP service representative will install the additional shared memory for the V-VOL

management area. This is separate from the shared memory for XP Snapshot.2. Make sure that you have sufficient license capacity for the pool and any near-term pool growth.

For specific instructions on installing license capacity, see the HP StorageWorksXP24000/XP20000 Remote Web Console User Guide.

3. Add parity groups, and add the volumes that will be used as pool-VOLs. You can use volumesin existing unused parity groups, in which case you would delete the path definition andperform an LDEV format. For specific instructions on LDEV formatting, see the HP StorageWorksXP24000/XP20000 Virtual LVI/LUN (VLL) and Volume Shredder User Guide.

4. Create the pools. For specific instructions, see “ Creating a Pool” (page 58).5. Create V-VOLs. For specific instructions, see “Creating a V-VOL Group” (page 62). After

creation, they are V-VOLs.6. Associate V-VOLs to the pools. For specific instructions, see “Changing the V-VOL Settings”

(page 65).7. Define the paths for the V-VOLs. For specific instructions, see the HP StorageWorks

XP24000/XP20000 LUN Manager User Guide.

Uninstalling XP Thin Provisioning1. Delete the path definition for the V-VOLs. For specific instructions, see the HP StorageWorks

XP24000/XP20000 LUN Manager User Guide.2. Perform LDEV formatting on the V-VOLs. For specific instructions on LDEV formatting, see the

HP StorageWorks XP24000/XP20000 Virtual LVI/LUN (VLL) and Volume Shredder UserGuide.

3. Release the association between the V-VOLs and the pools. For specific instructions, see“Deleting a Single Pool” (page 61).

4. Delete all V-VOLs. For specific instructions, see “Delete V-VOL Groups Dialog Box” (page 54).5. Delete all pools. For specific instructions, see “Deleting Pools” (page 61).6. Uninstall the XP Thin Provisioning license. For specific instructions on uninstalling license

capacity, see the HP StorageWorks XP24000/XP20000 Remote Web Console User Guide.


4 Using the XP Thin Provisioning GUIThis chapter describes the XP Thin Provisioning windows and dialog boxes.• “Pool Window” (page 29)

• “V-VOL Window” (page 34)

• “XP Thin Provisioning Window” (page 38)

• “New Pool Dialog Box” (page 40)

• “Change Pool Information Dialog Box” (page 41)

• “New V-VOL Group Dialog Box” (page 42)

• “Create V-VOL Dialog Box (1)” (page 42)

• “Create V-VOL Dialog Box (2)” (page 44)

• “Create V-VOL Confirmation Dialog Box” (page 48)

• “Connect Pool Dialog Box” (page 49)

• “Change Threshold Dialog Box” (page 50)

• “Associate V-VOL Groups with Pool Dialog Box” (page 51)

• “Release V-VOL Groups from Pool Dialog Box” (page 52)

• “Delete V-VOL Groups Dialog Box” (page 54)

Pool WindowAccess the Pool window by selecting Go Volume Manager Pool (see Figure 11 (page 30)).The Pool window provides information about both XP Thin Provisioning pools and XP Snapshotpools.

Pool Window 29

Figure 11 Pool Window

DescriptionItem

Shows the XP Thin Provisioning and XP Snapshot pools. The Pool tree contains one or more offollowing icons:• : A folder is used to indicate the storage system, the group of XP Thin Provisioning pools,

or the group of XP Snapshot pools

• Pool: X: A pool in normal status (X indicates the pool ID)

• Pool: X: A pool whose usage level exceeds the threshold (X indicates the pool ID)

• pool: X: A blocked pool or a pool where a pool-VOL is blocked or being formatted (Xindicates the pool ID)

• : A normal pool in the process of being deleted

• : A blocked pool or a pool where a pool-VOL is blocked or being formatted, which is inthe process of being deleted

• : A pool with a usage level that exceeds a threshold, in the process of being deleted

Pool tree

The Pool Management Capacity information, in the upper right corner of the window abovethe pool-VOL table, indicates the capacity for both XP Snapshot and XP Thin Provisioning pools.

CAUTION: When you add or delete pool-VOLs, the total capacity and used capacity valueschange after you click Apply.• Used indicates the capacity, in GB, of the pools that are in use.

• Total indicates the total capacity, in GB, of the pools that are in use plus those that can becreated. The capacity of the pools that can be created is derived from the available sharedmemory capacity. Available pool capacity decreases when a V-VOL is added, and increaseswhen a V-VOL is deleted.

CAUTION: Do not exceed the total capacity for pool management blocks in use.

Pool Mng. Capacity(Pool ManagementCapacity)

Pool-VOL table

30 Using the XP Thin Provisioning GUI

DescriptionItem

The pool-VOL table contains one or both of the following icons:• : Pool-VOLs having the V-VOL management area

• : Pool-VOLs not having the V-VOL management area

The pool-VOL table, in the upper right corner of the Pool window, displays the followinginformation about the selected pool-VOLs:

• LDKC:CU:LDEV: Unique address, consisting of the logical DKC (LDKC) number, CU number,and LDEV number.

• Capacity: LDEV capacity.

• Emulation: Emulation type.

• RAID: RAID level. As a best practice, always specify the same RAID level for all pool-VOLsregistered to the same pool. RAID-6 is recommended for large pools and where recoverytime due to drive failure may be unacceptable.

• Protection: Data protection level. If Data Retention Utility is installed, the Protection attributeis set using the Data Retention window in Remote Web Console.◦ SATA-W/V: Write & Verify method on SATA drives

◦ SATA-E: Enhancing method on SATA drives

◦ Standard: FC drives, flash drives, external volumes, or V-VOLs

It is recommended that the data protection level of the pool-VOLs in the same pool be thesame.

• PG: Parity group.

• Int. VOL Info: Drive type of internal volumes.◦ Nothing is displayed for FC drives.

◦ An asterisk (*) is displayed for a SATA drive.

◦ A dollar sign ($) is displayed for an SSD drive.

◦ Three consecutive hyphens (- - -) are displayed for an external volume.

CAUTION: Pool-VOLs with different drive types cannot be intermixed in the same pool.

• Ext. VOL Info: Drive type of external volumes.◦ Nothing is displayed for FC drives.

◦ An asterisk (*) is displayed for a SATA or BD drive.

◦ A dollar sign ($) is displayed for an SSD drive.

◦ Three consecutive hyphens (- - -) are displayed for an internal volume.

• Cache Mode: If the volume is an external volume, cache mode is displayed. This cachemode is specified automatically when the external volume is mapped.

CAUTION: Pool-VOLs with different cache modes cannot be intermixed in the same pool.

• Total Capacity: Total capacity of the pool-VOLs in the pool.

• Used LDEVs: Total number of pool-VOLs.

• Remaining LDEVs: Total number of pool-VOLs that you can add to the pool.

Pool Window 31

DescriptionItem

The Pool Information box, in the lower left corner of the Pool window, provides the followinginformation.• Pool ID: Pool identifying number.

• Status: Pool status.◦ Normal: Normal status. The pool usage level may exceed the variable or fixed pool

threshold.◦ Warning: Pool-VOL in the pool is blocked or being formatted.

◦ Blocked: The pool is full or an error occurs in the pool, therefore the pool is blocked. Ifthe pool is in both Warning and Blocked statuses, only Warning is displayed.

• Total Capacity: Total pool capacity. Total Capacity is calculated from the number of pages(42 MB per page).

• Used Capacity: Used pool capacity. Used Capacity is calculated from the number of pages(42 MB per page).

• Usage Rate: Pool usage level as a percentage of the current used pool capacity to the totalpool capacity.

• Threshold1: Variable threshold compared to usage level. The default setting is 70%. Youcan set it from 5% to 95% in 5% increments.

• Threshold2: Fixed threshold compared to usage level. Threshold2 is always fixed at 80%.◦ Warning: Usage level exceeds a threshold.

◦ Error: Usage level has reached 100%.

• Threshold: Pool usage threshold (%).

• Attribute: Program product that uses the pool.◦ XP Thin Provisioning

◦ XP Snapshot

• CLPR: CLPR number of the pool volume.

Pool Information box

If there is no pool in the storage system, this button initializes the entire V-VOL managementarea. If there are one or more pools in the storage system, this button optimizes the unallocatedpage management table in the pool management area. This process could take up to 30minutes.

CAUTION: Clicking the Optimize button will cancel any other pending operations in thiswindow.

Initialize or Optimizebutton

Completes the pool-related SIMs, including threshold warnings and blocked pool warnings.For more information, see“Managing Pool-Related SIMs” (page 83). All outstanding SIMs willbe marked completed after clicking Apply. Before using the SIM Complete Request check box.Make certain that all the outstanding SIM conditions are cleared. For example, Pool Spacehas been added to lower the usage level below all defined threshold settings.

SIM Complete Requestcheck box

Adds the volumes you selected in the Free LDEVs list (below) to the Pool-VOL table.• The LDKC list limits the display to CUs in the selected LDKC.

• The CU list limits the free LDEVs display to volumes in the selected CU.

Add Pool VOL button


DescriptionItem

The Free LDEVs table, in the lower right corner of the Pool window, displays the volumes thatcan be specified as pool-VOLs. The following information is displayed for each volume:• LDKC:CU:LDEV: Logical DKC (LDKC) number, CU number and LDEV number.

• Capacity: LDEV capacity.


• RAID: RAID level. HP recommends that you specify the same RAID level for pool-VOLsregistered in the same pool for best performance. RAID-6 is recommended for large poolsand where recovery time due to drive failure may be unacceptable.

• Protection: Data protection level. If Data Retention Utility is installed, the Protection attributeis set using the Data Retention window in Remote Web Console.◦ SATA-W/V: Write & Verify method on SATA drives

◦ SATA-E: Enhancing method on SATA drives

◦ Standard: FC drives, flash drives, external volumes, or V-VOLs

It is recommended that the data protection level of the pool-VOLs in the same pool be thesame.

• PG: Parity group.

• Int. VOL Info: Drive type of internal volumes.◦ Nothing appears for FC drives.

◦ An asterisk (*) indicates a SATA drive.

◦ A dollar sign ($) indicates an SSD drive.

◦ Three consecutive hyphens (- - -) are displayed for an external volume.

CAUTION: Pool-VOLs with different drive types cannot be intermixed in the same pool.

Free LDEVs table

• Ext. VOL Info: Drive type of external volumes.◦ Nothing appears for FC drives.

◦ An asterisk (*) indicates a SATA or BD drive.

◦ A dollar sign ($) indicates an SSD drive.

◦ Three consecutive hyphens (- - -) indicate an internal volume.

• Cache Mode: if the volume is an external volume, cache mode appears.

CAUTION: This cache mode is automatically specified when the external volume is mapped.Pool-VOLs with different cache modes cannot be intermixed in the same pool.

• CLPR: CLPR number

• Selected LDEVs: Total number of selected volumes.

Implements all pending operations.Apply

Cancels all pending operations.Cancel

Table 13 Pop-up Menu Commands

FunctionCommand Menu

Opens the New Pool dialog box (see “Defining a New Pool”(page 59))

New PoolWhen youright-click the XPThin Provisioningicon Deletes one or more pools. This command is only available when

there are pools that can be deleted.Delete Pool(s)

Returns one or more blocked pools to normal status. This commandis only available when blocked pools exist. If the pool usage level is100% (POOL FULL), or a pool-VOL in the pool is blocked or beingformatted, this command is not available

Restore Pool(s)

Pool Window 33

Table 13 Pop-up Menu Commands (continued)


Opens the Change Pool Information dialog box (see “Change PoolInformation Dialog Box” (page 60)).

Change PoolInformation

When youright-click a Poolicon

Deletes the selected poolDelete Pool

Returns one or more blocked pools to normal status. This commandis only available when blocked pools exist. If the pool usage level is100% (POOL FULL), or a pool-VOL in the pool is blocked or beingformatted this command is not available

Restore Pool

V-VOL WindowAccess the V-VOL window by selecting Go Volume Manager V-VOL. This window displaysboth XP Thin Provisioning and XP Snapshot V-VOLs.


Figure 12 V-VOL Window

DescriptionItem

Provides the following information about V-VOLs of XP Thin Provisioning:• used: Total capacity (GB) of V-VOLs associated with Pools.

• remaining: Total capacity (GB) of V-VOLs that can be associated with pools. Thiscapacity is calculated based on the assumption that V-VOLs of 1024 GB areassociated with pools.If V-VOLs of another size are associated with pools, calculate the total capacityof V-VOLs that can be associated with pools from the remaining value by thefollowing formulas.

X1 = (remaining (GB) 1024)

S1 = (X1 x 14 + (remaining (GB) - (X1 x 1024) ) 84)

S2 = ( ( Capacity of one V-VOL (GB) 84) + 1)

Total capacity of V-VOLs that can be associated with pools = (S1 S2) xCapacity of one V-VOL:

◦ indicates that the number enclosed by two downward arrows should berounded down to the nearest whole number.

◦ indicates that the number enclosed by two upward arrows should berounded up to the nearest whole number.

CAUTION: The values of used and remaining are not reflected in the windowuntil you click the Apply button.

Connect Pool Capacity

Shows the V-VOL groups in the storage system. The following icons can appear:• : The folder for a storage system or a program product

• : V-VOL group◦ A V-VOL group icon followed by a V indicates an XP Snapshot V-VOL, which

cannot be used for XP Thin Provisioning operations.◦ A V-VOL group icon followed by an X indicates an XP Thin Provisioning V-VOL

(XP Snapshot also uses V-VOL).

◦ : V-VOL group (in the process of being deleted)

◦ : VDEV

“V-VOL Window Pop-up Menu Commands” (page 37) lists the commands availablefrom the pop-up menu.

V-VOL Group - V-VOL tree

V-VOL Window 35

DescriptionItem

Provides the following information about the selected V-VOL:• LDKC:CU:LDEV: Logical DKC (LDKC) number, CU number and LDEV number

◦ A number followed by an X indicates an XP Thin Provisioning V-VOL.

◦ A number followed by a V indicates an XP Snapshot V-VOL.

• Capacity: Volume capacity

• Emulation: Emulation type. CVS, indicates a Virtual LVI/LUN volume. For moreinformation, see the HP StorageWorks XP24000/XP20000 Virtual LVI/LUN (VLL)and Volume Shredder User Guide.

• Status: V-VOL status◦ Normal

◦ Blocked

• CLPR: CLPR number.

• Access Attribute: Access attribute of V-VOL.

• Path: V-VOL LU path.

• Threshold: Potential demand capacity warning threshold.

V-VOL list

• Pool ID: Pool identifying number.

• Usage Rate: Pool usage level as a percentage of the consumed V-VOL capacityto the total V-VOL capacity.

• Used Page Num: Number of pages used in V-VOL.

• Page Status: Current page status of V-VOL.◦ Discarding Zero Data: Zero data is being discarded and the pages are being

released.◦ Discard Zero Data: XP Thin Provisioning is ready to discard zero data and

release pages. This status appears in blue bold italics until Apply is clicked.◦ Stop Discarding Zero Data: XP Thin Provisioning is ready to stop discarding

zero data and releasing pages. This status appears in blue bold italics untilApply is clicked.

◦ Releasing: Disassociation of the V-VOL from the pool is applied, and the pageis being released.

◦ A hyphen (-) appears when the page status is other than listed above.


DescriptionItem

Changes the emulation type OPEN-0V of the V-VOL to OPEN-V. Also, the contentsthat were displayed in blue bold italics on the V-VOL group tree or V-VOL list aredeleted.Clicking the Emulation button, opens a window (see “Remote Web Console WindowShowing Two Emulation Modes” (page 38)) in which Normal mode and Force modeare selectable. These two options, Normal and Force, further restrict which V-VOLswill be changed. Selecting Normal mode or Force mode determines the scope ofthe emulation change process, as follows:

• Normal mode: In Normal mode, XP Thin Provisioning V-VOLs that do not havea defined LU path are changed. All OPEN-0V V-VOLs without a path assignedare changed to OPEN-V.

• Force mode: In Force mode, all XP Thin Provisioning V-VOLs, regardless of whetheran LU path is defined, are changed. All OPEN-0V V-VOLs are changed toOPEN-V. Since the Force mode also changes XP Thin Provisioning V-VOLs onwhich a LU path is defined, the emulation type recognized by the server willchange suddenly for these volumes. Use the Force mode only when you are sureno problem will occur on the server, even if the emulation type is changed.Therefore, it is possible that the LU cannot be recognized by the host and thatI/O stops. While the host is online and I/O occurs, it is strongly recommendedyou avoid using Force mode.If you use Force mode and change the emulation type already recognized bythe host, reconfigure the LU from the host so that the LU should be recognizedby the host.

These modes and the execution of the emulation process are not restricted by anyselection or highlighting of V-VOL entries in the list. All V-VOLs are considered foran OPEN-V change during the emulation process.Volume migration cannot be performed between volumes with different emulationtypes. For example, volume migration is not available between an XP ThinProvisioning V-VOL recognized as OPEN-0V and a normal volume.

Emulation

Implements all pending operationsApply

Cancels all pending operationsCancel

Table 14 V-VOL Window Pop-up Menu Commands


Opens the New V-VOL Group dialog box (see “Creatinga New V-VOL Group (1)” (page 64)).

New V-VOL GroupWhen you right-clickthe XP ThinProvisioning folder

Opens the Associate V-VOL Groups with Pool dialog box(see “Associate V-VOL Groups with Pool Dialog Box”(page 51)). Associates V-VOLs in multiple V-VOL groupswith a pool at the same time.

Associate V-VOLGroups with Pool

Opens the Release V-VOL Groups from Pool dialog box(see “Release V-VOL Groups from Pool Dialog Box”(page 53)). Releases V-VOLs in multiple V-VOL groups froma pool at the same time.

Release V-VOL Groupsfrom Pool

Opens the Delete V-VOL Groups dialog box (see “DeleteV-VOL Groups Dialog Box” (page 77)). Deletes multipleV-VOL groups and the V-VOLs that are in that V-VOL groupat the same time.

Delete V-VOL Groups

Deletes the V-VOL group and associated V-VOLs.Delete V-VOL GroupWhen you right-clickthe V-VOL Group icon

V-VOL Window 37

Table 14 V-VOL Window Pop-up Menu Commands (continued)


Displays the Connect Pool dialog box (see “Selecting thePool” (page 66)).

Associate V-VOL withPool

When you right-clickan XP ThinProvisioning V-VOL

Releases the V-VOL from the XP Thin Provisioning pool.Release V-VOL fromPool

Displays the Change Threshold dialog box (see “Changingthe Threshold” (page 67)).

Change Threshold

Releases pages if all the data in the pages of the V-VOLare zero.

Discard Zero Data

Stops discarding zero data and releasing the pages.Stop Discarding ZeroData

Figure 13 Remote Web Console Window Showing Two Emulation Modes

XP Thin Provisioning WindowAccess the XP Thin Provisioning window by selecting File Report Display XP Thin Provisioning.The XP Thin Provisioning window allows you to display and manage V-VOLs, pools, and the V-VOLmanagement area.Figure 14 (page 38) shows the default view, which is with the LDKC:CU button selected.

Figure 14 XP Thin Provisioning Window (LDKC:CU View)

Figure 15 (page 39) shows the XP Thin Provisioning window with the Pool button selected.


Figure 15 XP Thin Provisioning Window (Pool View)

DescriptionItem

Use these options to filter the data to be displayed to vieweither LDKC:CU information or Pool information.

LDKC:CU or Pool

Provides information about the selected V-VOL:• LDKC:CU:LDEV: Logical DKC (LDKC) number, CU

number, and LDEV number. The icons can include thefollowing:◦ indicates a normal LDEV.

◦ indicates a secured volume.

◦ indicates a remote command device.

◦ indicates a command device.

◦ indicates a secured command device.A number followed by an X is an XP ThinProvisioning V-VOL.A number followed by a V is an XP Snapshot V-VOL.

V-VOL list

XP Thin Provisioning Window 39

DescriptionItem

• Emulation: Emulation type. OPEN-V is the onlysupported emulation type. CVS indicates a VirtualLVI/LUN volume. For more information, see HPStorageWorks XP24000/XP20000 Virtual LVI/LUN(VLL) and Volume Shredder User Guide.

• Capacity: V-VOL capacity, in GB.

• Parity Group: Parity group number.

• Usage Rate: Pool usage level as a percentage of theused capacity compared to the total capacity.

• Threshold: Potential demand capacity consumedpercentage at which a warning will be issued. Availablevalues are from 5% to 300%, in 5% increments.

• Paths: Number of LU paths to the volume, from 0 to65,280.

• Operation: Whether or not you can perform anoperation on the V-VOL.◦ Ready: You can perform an operation on the V-VOL.

◦ Processing: You cannot perform any operation onthe V-VOL because another operation is beingperformed on the V-VOL.

◦ Discarding Zero Data: You cannot start a newoperation for discarding zero data becausediscarding of zero data is currently taking place.

◦ Releasing: You cannot perform any operation on theV-VOL because another operation is being performedon the V-VOL.

• Pool ID: Pool identifying number.

• Used Page Num: Number of pages used in V-VOL.

Provides the following information about the selectedpool-VOL:• LDKC:CU:LDEV: Logical DKC (LDKC) number, CU

number, and LDEV number. The icon will be one of thefollowing:◦ A normal LDEV

◦ A secured volume

◦ A remote command device

◦ A command device.

◦ A secured command device.

• Emulation: Emulation type. OPEN-V is the onlysupported emulation type

• Capacity: Pool-VOL capacity, in GB

• Parity Group: Parity group number

Pool-VOL list

Implements all pending operationsApply

Cancels all pending operationsCancel

New Pool Dialog BoxThe New Pool dialog box opens when you right-click the XP Thin Provisioning icon in the Poolwindow and select New Pool on the pop-up menu.


Figure 16 New Pool Dialog Box

DescriptionItem

Enter the pool ID number using numbers from 0 to 127.Do not use a number that is already in use as a pool IDnumber.

Pool ID

Select the pool usage warning threshold, which is specifiedas a percentage. The range can be between 5 and 95.The default value is 70.If the pool usage level exceeds the threshold, the pool statuschanges to Warning status, when the pool is in Warningstatus, additional pool volumes should be added to thepool.

Threshold

XP Thin Provisioning should already be selected.Attribute

Creates the new pool and closes the dialog box. The settingwill not be implemented until you click Apply on the Poolwindow.

Set

Cancels the settings and closes the dialog box. No poolwill be created.

Cancel

Change Pool Information Dialog BoxAccess the Change Pool Information dialog box by right-clicking the selected pool, then selectingChange Pool Information from the pop-up menu.

Figure 17 Change Pool Information Dialog Box

The features of the Change Pool Information dialog box are the same as those for the New Pooldialog box, except that only the Threshold field is available.

Change Pool Information Dialog Box 41

New V-VOL Group Dialog BoxFigure 18 New V-VOL Group Dialog Box

DescriptionItem

Select the V-VOL group ID using numbers from 1 to 65,535.Do not use a number that is already in use as a V-VOLgroup ID.

V-VOL Group

Select the emulation type. Open-V is the only type that issupported.

Emulation Type

Select the cache logical partition. For more information oncache logical partitions, see the HP StorageWorksXP24000/XP20000 Disk/Cache Partition User Guide.

CLPR

Shows either XP Snapshot or XP Thin ProvisioningAttribute

Enter the number of V-VOL groups to be created. You canenter numbers from 0 to 63,231. This is the maximum perstorage system.If you have any external volumes or XP Snapshot volumes,this maximum is decreased accordingly. If you enter 0, noV-VOL group will be created.

Copy of V-VOL Groups

Implements the setting in the New V-VOL Group dialogbox and opens the Create V-VOL dialog box (1)

Next

Cancels the settings and closes the dialog boxCancel

Create V-VOL Dialog Box (1)Access the Create V-VOL dialog box (1) by clicking the Next button on the New V-VOL Groupdialog box (see Figure 18 (page 42)).


Figure 19 Create V-VOL Dialog Box (1)

DescriptionItem

Shows the V-VOL group ID set in the New V-VOL Groupdialog box

V-VOL Group

Select the emulation type. OPEN-V is the only type that issupported.

Emulation Type

Select the capacity unit:• MB (megabyte)

• Block

• Cyl (cylinder)

Capacity Unit

Enter the V-VOL capacity.• If you selected MB in the Capacity Unit drop-down list,

you can enter numbers from 46 to 4,194,303.• If you selected block in the drop-down list, you can enter

numbers from 96,000 to 8,589,934,592.• If you selected Cyl in the Capacity Unit drop-down list,

you can enter numbers from 50 to 4,473,924.When you specify the Capacity Unit as MB or Cyl, thestorage system optimally corrects the capacity. Therefore,to set the capacity accurately to the largest value of theVDEV capacity, specify the Capacity Unit as block.

Capacity

Enter the number of V-VOLs that you want to add, from 1to 1,024. See System Option Mode 726, explained“V-VOLs” (page 10).The number of V-VOLs that you can enter in this dialog boxcan vary, depending on the number of the V-VOL groupsto be copied in New V-VOL group dialog box (see“Creating a New V-VOL Group (1)” (page 64)). Forexample, if you specified 100 V-VOL groups in this dialogbox, you can specify 10 V-VOLs per V-VOL group, becausethe maximum total is 1,024. In this case, the displayedrange would be 1 to 10.

Number of V-VOL

Adds the V-VOLs to the listSet

Create V-VOL Dialog Box (1) 43

DescriptionItem

Deletes the V-VOLs from the listDelete

Shows the following information about the selectedV-VOL(s):• No.: Number

• Emulation: Emulation type

• Capacity: Capacity

V-VOL information setting list

Keeps the settings in this dialog box, but returns you to theNew V-VOL group dialog box (see “New V-VOL GroupDialog Box” (page 42))

Back

Opens the Create V-VOL dialog box (2) (see “Create V-VOLDialog Box (2)” (page 45))

Next

Cancels the operation and closes the dialog boxCancel

Create V-VOL Dialog Box (2)Access the Create V-VOL dialog box (2) by selecting Next on the Create V-VOL dialog box (1) (see“Create V-VOL Dialog Box (1)” (page 43)).


Figure 20 Create V-VOL Dialog Box (2)

DescriptionItem

Information about each V-VOL in the list:• No.: Number.

• V-VOL Group: Group ID.


• Capacity: Capacity.

• LDCK:CU:LDEV: LDKC number, CU number, and LDEVnumber. XP Thin Provisioning LDEV numbers arefollowed by an X. XP Snapshot LDEV numbers arefollowed by a V.

V-VOL list

Select the LDKC.Select LDKC No.

Select the CU.Select CU No.

Select the interval between the LDEV numbers that will beassigned to the newly created V-VOLs. If you select 0, theLDEV numbers will be sequential.The value you specify as the interval between LDEVnumbers counts only the available LDEV numbers and skipsthose that are not selectable. Even when you use multipleCUs, LDEV numbers will be assigned according to theInterval list.

Interval


DescriptionItem

The LDEV number grid.• The location on the grid indicates the LDEV number.

The numbers across the top (CU number), combinedwith the numbers on the left side, indicate the LDEVnumber. For example, the LDEV number of the cell witha CU number of +2 and an LDEV number of +10 is 12.

• Gray cells indicate LDEV numbers that are already inuse.

• White cells indicate unused LDEV numbers.

• Blue cells indicate LDEVs that have been selected forthe V-VOLs in this procedure.

Select LDEV No.

If checked, allows you to select CU numbers from anotherSLPR.

CU number of another SLPR is used

Maintains the settings in this dialog box while returningyou to the Create V-VOL dialog box (1) (see “Create V-VOLDialog Box (1)” (page 43)).

Back

Implements the settings in this dialog box and opens theCreate V-VOL Confirmation Dialog Box (see “Create V-VOLConfirmation Dialog Box” (page 49)).The Create V-VOL dialog box (3) (see “Create V-VOL DialogBox (3)” (page 47)) appears only when SSID is notassigned to the boundary area that contains LDEV numbersyou set in this dialog box. The Create V-VOL dialog box(4) appears when SSID is assigned.

Next

Cancels the operation and closes the dialog box.Cancel


Create V-VOL Dialog Box (3)Figure 21 Create V-VOL Dialog Box (3)

DescriptionItem

Shows the LDKC numbers, CU numbers, SSID boundaryand SSID in a hierarchical tree structure.The boundary area is a collection of LDEV numbers thatSSID is assigned to. For example, taking the boundaryarea 00–FF, you assign a SSID among the LDEV numbersfrom 00 to FF. A CU contains one or four boundary areas,which are fixed per CPU by factory settings.The parenthesized SSID is to the right of the boundaryarea. When SSID is not assigned to the boundary area,an exclamation point is added to the LDKC number, CUnumber, and boundary area icon, and “- - -” appears onthe right side of the boundary area.

: LDKC number or CU number. Indicates that SSIDis assigned to the all boundary areas.

: LDKC number or CU number. Indicates the boundaryarea with no SSID.

: Indicates that no SSID is assigned to the boundaryarea.

Set SSID tree

Assigns SSID to the boundary area that contains LDEVnumbers you set.Information about the Set SSID list:• LDKC: LKDC number of CU number where SSID is not

assigned.• CU: CU number where SSID is not assigned.

• LDEV boundary: Boundary area of LDEV number whereSSID is not assigned.

• SSID: Assigned SSID, The initial value is blank.

Set SSID list

Select or enter the SSID you want.You can enter SSID only when logged in as a storageadministrator.

Input SSID list


DescriptionItem

• Input SSID: Sets SSID you select or input from the InputSSID list.

• Set SSID: Updates SSID you select or input from theInput SSID list.

Set

If checked, you can enter SSID excluding SLPR that containsa parity group of your operation in the Input SSID list. Ifnot checked, you can only select SSID of SLPR that containsa parity group of your operation.SSID number of another SLPR is used appears only whenyou are logged in as a storage administrator and morethan two SLPRs exist. If not checked, Input SSID is notavailable.

SSID number of another SLPR is used

Maintains the settings in this dialog box while returningyou to the Create V-VOL dialog box (1) (see “Create V-VOLDialog Box (1)” (page 43)).

Back

Implements the settings in this dialog box and opens theCreate V-VOL Confirmation Dialog Box (see “Create V-VOLConfirmation Dialog Box” (page 49)).

Next


Create V-VOL Confirmation Dialog BoxAccess the V-VOL Confirmation Dialog Box by selecting Next on the Create V-VOL Dialog Box (2)(see “Create V-VOL Dialog Box (2)” (page 45)).


Figure 22 Create V-VOL Confirmation Dialog Box

DescriptionItem

V-VOL group IDV-VOL Group

Information about each V-VOL in the group that you arecreating:• VDEV: V-VOL group ID and VDEV number.


• Capacity: Capacity.

• LDKC:CU:LDEV: LDKC number, CU number, and LDEVnumber.

V-VOL information

Maintains the settings in this dialog box while returningyou to the Create V-VOL Dialog box (2) (see “Create V-VOLDialog Box (2)” (page 45)).

Back

Implements the settings and closes the dialog box. Thesettings are not applied to the subsystem until you clickApply in the V-VOL window.

Yes


Connect Pool Dialog BoxAccess the Connect Pool dialog box by opening the V-VOL window (see “V-VOL Window”(page 35)), right-clicking on the V-VOL group that you want to associate with the pool, and thenselecting Associate V-VOL with Pool from the pop-up menu.

Connect Pool Dialog Box 49

Figure 23 Connect Pool Dialog Box

DescriptionItem

Pool ID.Pool ID

Pool status (Normal or Blocked).Status

The total pool capacity (value is truncated to 2 decimalplaces).

Total Capacity

Used pool capacity (value is truncated to 2 decimal places).Used Capacity

Pool usage level threshold.Threshold

Opens the Change Threshold dialog box, provided thatyou have selected a row.

Next


Change Threshold Dialog BoxAccess the Change Threshold dialog box by selecting Next on the Connect Pool dialog box.

Figure 24 Change Threshold Dialog Box

DescriptionItem

Select the V-VOL potential demand capacity threshold.Select values from 5% to 300%, in 5% increments. Thedefault is 5%.

Threshold

Implements the threshold setting for that V-VOL.Set



Associate V-VOL Groups with Pool Dialog BoxAccess the Associate V-VOL Groups with Pool dialog box by opening the V-VOL window (see“V-VOL Window” (page 35)), right-clicking the XP Thin Provisioning icon, and then selectingAssociate V-VOL Groups with Pool.

Figure 25 Associate V-VOL Groups with Pool Dialog Box

DescriptionItem

The name of the application that is going to use the V-VOL groups. This is thename of the application whose icon you right-clicked in order to display theAssociate V-VOL Groups with Pool dialog box.

Attribute

Select the CLPR of the V-VOL group that you want to associate with a pool.CLPR

Information about the V-VOL groups:• V-VOL Group: V-VOL group ID.

• CLPR: CLPR number.

• V-VOL Cnt.: Number of V-VOLs in the V-VOL groups.

• LDEV: LDKC number, CU number, and LDEV number of the first LDEV in theV-VOL group. These numbers are separated by colons.

V-VOL information

Associate V-VOL Groups with Pool Dialog Box 51

DescriptionItem

• Pool ID: Pool ID of the first LDEV in the V-VOL group. The following symbolsare used to display status:◦ If a V-VOL group is associated with a pool, a Pool ID is displayed in a

blue bold italics.◦ If a V-VOL group is released from a pool, a hyphen (-) is displayed.

◦ If the V-VOL group is not associated with a pool, a space is displayed.

• Threshold: Threshold (5% to 300%) that applies to the first LDEV in the V-VOLgroup. The following symbols are used to display status:◦ If the V-VOL group is associated with a pool, the Threshold is displayed

using blue bold italics.◦ If the V-VOL group is released from a pool, a hyphen (-) is displayed.

◦ If the V-VOL group is not associated with a pool, a space is displayed.

The following icon is displayed in the dialog box:

• : V-VOL group

Icons

The number of the current page. You can use the following items to changepages:• Previous button allows you to display the previous 4,096 V-VOL groups.

• N/M list: The N displays the number of the current page. The M displays thetotal number of pages. You can click the drop-down list and choose thenumber of the page you want to display.

• Next displays the next 4,096 V-VOL groups.

Page

Specifies that the V-VOL groups selected in the V-VOL information setting list willbe associated with a pool. The V-VOL groups to be associated with a poolappear in blue bold italics. The Connect Pool dialog box (see “Connect PoolDialog Box” (page 50)) is also displayed.

Set

Clears each setting in the V-VOL information setting list.Clear

Closes the Associate V-VOL Groups with Pool dialog box and displays aconfirmation message appears asking whether it is OK to apply the setting tothe storage system.

OK

Cancels all the settings in the Associate V-VOL Groups with Pool dialog box.Cancel

Release V-VOL Groups from Pool Dialog BoxAccess the Release V-VOL Groups from Pool dialog box by opening the V-VOL window (see “V-VOLWindow” (page 35)), then right-clicking on the XP Thin Provisioning icon, and selecting ReleaseV-VOL Groups from Pool.


Figure 26 Release V-VOL Groups from Pool Dialog Box

DescriptionItem

The name of the application that is going to use the V-VOLgroups is displayed. This is the name of the applicationwhose icon you right-clicked in order to display the ReleaseV-VOL Groups from Pool dialog box.

Attribute

Select the CLPR of the V-VOL group that you want to releasefrom a pool. If All is selected, all V-VOL groups associatedwith a pool are displayed.

Pool ID

Release V-VOL Groups from Pool Dialog Box 53

DescriptionItem

Information about the V-VOL groups:• V-VOL Group: V-VOL group ID.

• CLPR: The number of the CLPR.

• V-VOL Cnt.: The number of V-VOLs in the V-VOL groups.

• LDEV: LDKC number, CU number, and LDEV number ofthe first LDEV in the V-VOL group. These numbers areseparated by colons.

• Pool ID: Pool ID of the first LDEV in the V-VOL group.The following symbols are used to display status:◦ If the V-VOL group is associated with a pool, the

Pool ID is displayed in a blue bold italic.◦ If the V-VOL group is released from pool, a hyphen

(-) is displayed.◦ If the V-VOL group is not associated with a pool, a

space is displayed.

• Threshold: Threshold (5% to 300%) that applies to thefirst LDEV in the V-VOL group. The following symbolsare used to display status:◦ If the V-VOL group is associated with a pool, the

Threshold is displayed in blue bold italics.◦ If the V-VOL group is released from a pool, a hyphen

(-) is displayed.◦ If the V-VOL group is not associated with a pool, a

space is displayed.

V-VOL information

The number of the current page. You can use the followingitems to change pages:• Previous button allows you to display the previous

4,096 V-VOL groups.• N/M list: The N displays the number of the current page.

The M displays the total number of pages. You can clickthe drop-down list, and choose the number of the pageyou want to display.


Page

Specifies that the V-VOL groups selected in the V-VOLinformation setting list will be released from a pool. TheV-VOL groups to be released from a pool appear in bluebold italics.

Set

Clears each setting in the V.Clear

Closes the Release V-VOL Groups from Pool dialog boxand a confirmation message appears asking whether it isOK to apply the setting to the storage system.

OK

Cancels all the settings in the Release V-VOL Groups fromPool dialog box.

Cancel

Delete V-VOL Groups Dialog BoxAccess the Delete V-VOL Groups dialog box by opening the V-VOL window (see “V-VOL Window”(page 35)), then right-clicking on the XP Thin Provisioning icon, and selecting Delete V-VOL Groups.


Figure 27 Delete V-VOL Groups Dialog Box

DescriptionItem

The name of the application that is going to use the V-VOLgroups is displayed. This is the name of the applicationwhose icon you right-clicked in order to display the DeleteV-VOL Groups dialog box.

Attribute

Select the CLPR of the V-VOL groups. If All is selected, allV-VOL groups in all CLPRs are displayed.

CLPR

Information about the V-VOL groups that you are going todelete.• V-VOL Group: V-VOL group ID.

• CLPR: The number of the CLPR.

• V-VOL Cnt: The number of V-VOLs in the V-VOL groups.

V-VOL information

The following icons are displayed in the dialog box:

• : V-VOL group

• : V-VOL group (in the process of being deleted)

Icons

The number of the current page. Use the following itemsto change pages of list:• Previous button allows you to display the previous

4,096 V-VOL groups.• N/M list: The N displays the number of the current page.

The M displays the total number of pages. You can openthe drop-down list, and choose the number of the pageyou want to display.


Page

Delete V-VOL Groups Dialog Box 55

DescriptionItem

Specifies that the V-VOL groups selected in the V-VOLinformation setting list will be deleted. The V-VOL groupsto be deleted appear in blue bold italics.

Set

Clears each setting in the V-VOL information setting list.Clear

Closes the Delete V-VOL Groups dialog box and aconfirmation message appears asking whether it is OK toapply the setting to the storage system.

OK

Cancels all the settings in the Delete V-VOL Groups dialogbox.

Cancel


5 Performing XP Thin Provisioning OperationsThis chapter gives instructions for performing XP Thin Provisioning operations.• “XP Thin Provisioning Flow Chart” (page 57)

• “Managing Pools” (page 57)

• “Managing V-VOLs and V-VOL Groups” (page 62)

XP Thin Provisioning Flow ChartOnly Storage Administrators can perform XP Thin Provisioning operations. Figure 28 (page 57)illustrates the XP Thin Provisioning functions.

Figure 28 XP Thin Provisioning Flow Chart

Managing PoolsThis section discusses the following topics:• “Viewing Pool Information” (page 58)

• “ Creating a Pool” (page 58)

• “Associating the Pool-VOL with the Pool” (page 60)

• “Changing the Pool Threshold” (page 60)

• “Deleting Pools” (page 61)

• “Recovering Pools in Blocked Status” (page 61)

XP Thin Provisioning Flow Chart 57

Viewing Pool InformationTo view the pool information:1. From the File menu, select Basic Information. The Report Display window opens. The Port tab

is the default view.2. Click the XP Thin Provisioning tab to display the XP Thin Provisioning window (see

Figure 29 (page 58)). Select the LDKC:CU button to view information sorted by CU number.Select the Pool button to view information sorted by pool.

Figure 29 Viewing the XP Thin Provisioning Information

3. Additional XP Thin Provisioning information is available using Go —> Volume Manager —>Pool (see “Accessing the Pool Window” (page 59)).

Creating a PoolThe first step in using XP Thin Provisioning is to create one or more pools.

WARNING! Make sure that the blocks-in-use capacity is less than the total capacity.

NOTE: Total capacity is the total pool storage capacity.The value for pool management blocks in use will increase if you add pool-VOLs.

To create a pool:1. Access the Pool window by selecting Go Volume Manager Pool (see “Accessing the Pool

Window” (page 59)).2. In the Pool tree, on the upper left corner of the Pool window, right-click the XP Thin Provisioning

folder, and then select New Pool.

58 Performing XP Thin Provisioning Operations

3. In the New Pool dialog box (see “Defining a New Pool” (page 59)), do the following:• In the Pool ID text box, enter the number for the pool ID. Use numbers from 0 to 127 and

do not select a number that is already in use for any other pool (XP Thin Provisioning orXP Snapshot).

• In the Threshold list, select the pool usage level threshold. This is expressed as a percentageof pool usage over pool capacity.

CAUTION: If the usage level of the pool exceeds a threshold, the pool status warnsagainst adding new pool-VOLs. Be sure that you do not set the threshold value too small.

• In the Attribute list, select XP Thin Provisioning.4. Verify that the settings are correct, and select Set.5. The New Pool dialog box closes and the new pool is displayed in the Pool tree, in the upper

left corner of the window.6. To create another pool, repeat the preceding steps.7. Click Apply, and then click OK to create the new pool.

This operation may take up to 20 minutes, depending on the number and capacity of thepools and pool-VOLs.

NOTE:• Total capacity is the total pool storage capacity.

• The value for pool management blocks in use will increase if you add pool-VOLs.

• Make sure that the blocks in use capacity is less than the total capacity.

Figure 30 Accessing the Pool Window

Figure 31 Defining a New Pool

Managing Pools 59

Associating the Pool-VOL with the PoolTo associate one or more pool-VOLs to a pool:1. Access the Pool window by selecting Go Volume Manager Pool (see “Accessing the Pool

Window” (page 59)).2. In the Pool tree, in the upper left corner of the Pool window, select a pool.3. In the Free LDEVs list, in the bottom right corner of the window, select the volumes that you

want to register in the pool as pool-VOLs.• If you select an LDKC number from the list, the CU list will contain CUs only within that

LDKC.• If you select a CU number from the CU list, the Free LDEVs list will contain the LDEVs only

in that CU. Within the same CU, you can select multiple LDEVs at a time.

CAUTION: As a best practice, use the same drive type for all pool-VOLs in the same pool.

4. Right-click the selected volumes and select Add Pool-VOL.5. Check the list of the volumes, and then click OK. The dialog box closes and the selected

volumes will be displayed in the Pool-VOL list.

CAUTION: You cannot delete pool-VOLs after you add them. Be sure to verify that the settingsare correct.

6. To add more pool-VOLs, repeat the preceding steps.7. In the Pool window, click Optimize.

You do not need to initialize or optimize the pool created with the microcode version 60-05-0Xor later.

8. Click Apply, and then click OK to associate the pool-VOL to the pool.

Changing the Pool ThresholdOnce you create a pool, the only setting you can change is the threshold. To change the thresholdof a pool:1. Access the Pool window by selecting Go Volume Manager Pool (see “Accessing the Pool

Window” (page 59)).2. In the Pool tree in the upper left corner of the window, right-click the selected pool, and then

select Change Pool Information to display the Change Pool Information dialog box (seeFigure 32 (page 60)). If the pool usage level is 95% or higher, the pop-up menu will notappear.

3. Select the value for the threshold from the Threshold list.4. Click Set to close the Change Pool Information dialog box.5. Click Apply, and then click OK to change the pool threshold.

Figure 32 Change Pool Information Dialog Box


Deleting PoolsAs a general rule, you will specify and delete a single pool. If you choose to delete multiple pools,all pools that can be deleted will be deleted.

Deleting a Single PoolA pool can be deleted only when there are no V-VOLs associated with the pool. Confirm that thepool usage is 0 and the pool association with V-VOL has been deleted, and then you can deletea single pool.To delete a pool:1. Access the Pool window by selecting Go Volume Manager Pool (see “Accessing the Pool

Window” (page 59)).2. If the pool is associated with any V-VOL, disassociate it and confirm that the pool usage is 0

(see “Releasing a V-VOL from a Pool” (page 67)).For details about how to delete the association, see “Changing the V-VOL Settings” (page 65).

3. In the pool tree, in the upper left corner of the window, right-click the selected pool, and thenselect Delete Pool. If the pool is associated with V-VOLs, the pop-up menu will not appear.

4. Click OK on the confirmation message. The icon of the selected pool changes to indicate thatthe pool will be deleted.

5. Click Apply, and then click OK to delete the pool.

Deleting Multiple Pools

CAUTION: This operation will delete all pools that can be deleted. To delete a single pool, see“Deleting a Single Pool” (page 61) for instructions.

To delete multiple pools:1. Access the Pool window by selecting Go Volume Manager Pool (see “Accessing the Pool

Window” (page 59)).2. If the pool is associated with any V-VOL, disassociate it and confirm that the Pool usage is 0

(see “Releasing a V-VOL from a Pool” (page 67)).For details about how to delete the association, see “Releasing a V-VOL from a Pool” (page 67).

3. In the Pool tree, in the upper left corner of the window, right-click the selected pools, and thenselect Delete Pool(s).

4. Click OK on the confirmation message. The icon of the selected pools changes to indicatethat the pools will be deleted.

5. Click Apply, and then click OK to delete the pools.6. Click Cancel to cancel the operation.

Recovering Pools in Blocked StatusThis operation is for failure recovery of a blocked pool. Ordinarily, you should not need to performthis operation.Recovering a blocked pool is equivalent to initializing the pool. Data loss will occur.The recovery time for pools varies depending on pool usage or V-VOL usage. Calculate roughly20 minutes of recovery time for every 100 TB of pool or V-VOL usage. Recovery time may varydepending on the workload of the storage system at the time of recovery.

Recovering a Single Blocked PoolTo recover a blocked pool:

Managing Pools 61

1. Access the Pool window by selecting Go Volume Manager Pool (see “Accessing the PoolWindow” (page 59)).

2. In the Pool tree, in the upper left corner of the window, select and right-click the blocked poolyou want to recover to display the Restore Pools pop-up menu.

3. Select Restore Pools, and then select OK on the confirmation message. The pool icon willchange to indicate a normal pool. Pool icons are described in “Pool Window” (page 29).

4. Click Apply, and then click OK to restore the pool.

Recovering Multiple Blocked PoolsTo recover multiple blocked pools:1. Access the Pool window by selecting Go Volume Manager Pool (see “Accessing the Pool

Window” (page 59)).2. In the Pool tree, in the upper left corner of the window, select and right-click the XP Thin

Provisioning icon, select Restore Pools, and then select OK on the confirmation message. Thepool icon will change to indicate a normal pool.

3. Click Apply, and then click OK to restore the pool.

Managing V-VOLs and V-VOL GroupsThis section discusses the following topics:• “Creating a V-VOL Group” (page 62)

• “Changing the V-VOL Settings” (page 65)

• “Changing the V-VOL Settings of Multiple V-VOL Groups” (page 72)

• “Deleting V-VOL Groups” (page 76)

• “Deleting V-VOLs” (page 77)You will need to use Virtual LVI/LUN for the following V-VOL operations:

• Adding V-VOLs to an existing V-VOL group.

• Deleting V-VOLs from an existing V-VOL group.For more information on Virtual LVI/LUN, see the HP StorageWorks XP24000/XP20000 VirtualLVI/LUN (VLL) and Volume Shredder User Guide.

Creating a V-VOL GroupWhen creating a V-VOL group, define the V-VOLs for the group at the same time. Although multipleV-VOLs can be defined to a V-VOL group, the recommendation is to define just one V-VOL perV-VOL group. The number of V-VOL groups allowed is the same as the maximum number of V-VOLsin the system.If you plan to increase the capacity of a V-VOL, free space is needed in the V-VOL group immediatelyadjacent to the V-VOL. The recommendation to define a single V-VOL per V-VOL group allows forany V-VOL to be expanded to its maximum allowed capacity. For more information about increasingV-VOL capacity, see “Increasing V-VOL Capacity” (page 67).To create a V-VOL Group:1. Access the Pool window by selecting Go Volume Manager Pool (see “Accessing the Pool

Window” (page 59)).2. In the pool tree, in the upper left corner of the window, right-click the XP Thin Provisioning

folder, and then select New V-VOL Group.


3. In the New V-VOL Group dialog box (see “Creating a New V-VOL Group (1)” (page 64)),do the following:• In the V-VOL Group list, select or enter the V-VOL group ID. Use numbers from 1 to 65,535,

and do not enter a number that is already in use.• In Emulation Type, select OPEN-V.

• In CLPR, select the CLPR number.

• In Copy of V-VOL Groups, enter the number of V-VOL groups to be created. You canenter numbers from 0 to 63,231. This is the maximum per storage system. If you haveany external volumes or any XP Snapshot volumes, this maximum is decreased accordingly.If you enter 0, no V-VOL group will be created.

4. Click Next.5. In the Create V-VOL dialog box (2) (see “Creating a New V-VOL Group (1)” (page 64)), do

the following:• In Emulation Type, select OPEN-V.

• In Capacity Unit, select one of the following:MB (megabyte)◦

◦ Block

◦ Cyl. (cylinder)

• In Capacity, enter the capacity:If you selected MB in the Capacity Unit list, enter numbers from 46 to 4,194,303.◦

◦ If you selected block, enter numbers from 96,000 to 8,589,934,592.

◦ If you selected Cyl, enter numbers from 50 to 4,473,924.When you specify the Capacity Unit as MB or Cyl, the storage system optimally correctsthe Capacity. Therefore, to set Capacity accurately to the largest value of the VDEVcapacity, specify the Capacity Unit as block.

• In Number of V-VOL, enter the number of the V-VOLs you want to create, from 1 to 1024.See System Option Mode 726 explained in “V-VOLs” (page 10).The number of V-VOLs that you can enter in this dialog box can vary, depending on thenumber of V-VOL groups that you specified in the New V-VOL Group dialog box (see“New V-VOL Group Dialog Box” (page 42)). For example, if you specified 100 V-VOLGroups, in this dialog box you can specify 10 V-VOLs per V-VOL Group, because themaximum total is 1024. In this case, the displayed range would be 1 to 10.

• Click Set to add these V-VOLs to the V-VOL list. To add more V-VOLs, repeat this step.6. Click Next.7. In the Create V-VOL dialog box (3) (see “Creating a New V-VOL Group (2)” (page 64)):

• In the Volume list in the upper part of the dialog box, select a volume.

• In Select LDKC No., select the LDKC number.

• In Select CU No., select the CU number. This will show the selected volume in the LDEVlist, in the bottom of the dialog box.

• In Interval, select the interval between the LDEV numbers. If you select 0, the LDEV numberswill be sequential.

Managing V-VOLs and V-VOL Groups 63

• To select a CU that belongs to another SLPR, select the CU number of another SLPR isused check box.Only the areas displayed by the white cells are available for the V-VOLs. Once the areais selected, it turns blue, and the CU and LDEV number are added to the V-VOL list onthe top of the dialog box, in blue bold italics.

• To add another V-VOL, repeat this step.8. Click Next.9. In the Create V-VOL Group Confirmation dialog box (see “Confirming V-VOL Group Creation”

(page 65)), verify that the settings are correct, and then click OK. The new V-VOLs appear inblue bold italics.

10. Click Apply, and then click OK to create the V-VOLs.

Figure 33 Creating a New V-VOL Group (1)




Figure 36 Confirming V-VOL Group Creation

Changing the V-VOL Settings

Associating a V-VOL with a PoolTo associate a V-VOL with a pool:


1. Access the V-VOL window by selecting Go Volume Manager V-VOL (see “Selecting theV-VOL Group” (page 66)).

2. In the V-VOL Group–V-VOL tree on the left side of the window, select the V-VOL group thatcontains the V-VOLs that you want to associate with a pool. This will display the informationfor the individual V-VOLs on the right side of the window.

3. In the right side of the window, right-click one or more V-VOLs, and select Associate V-VOLwith Pool to display the Connect Pool dialog box (see “Selecting the Pool” (page 66)). Youcan only select from rows with black font.

4. Select the pool ID that you want to associate with the V-VOL group, and then select Next todisplay the Change Threshold dialog box (see “Changing the Threshold” (page 67)).

5. Select the threshold from the list, and then click Set to implement the settings and return to theV-VOL window. You can set thresholds from 5% to 300% in 5% increments.

6. Click Apply, and then click OK to associate the V-VOL with the pool.

Figure 37 Selecting the V-VOL Group

Figure 38 Selecting the Pool


Figure 39 Changing the Threshold

Releasing a V-VOL from a PoolIf you release a V-VOL from the pool, the free space is added back into the pool.To release a V-VOL from a pool:1. Release the path definitions to the V-VOLs to be deleted. For instructions, see the HP

StorageWorks XP24000/XP20000 LUN Manager User Guide.2. Access the V-VOL window by selecting Go Volume Manager V-VOL (see “Selecting the

V-VOL Group” (page 66)).3. In the V-VOL Group–V-VOL tree in the left side of the window, select the V-VOL group that

contains the V-VOLs that you want to release from a pool. This will display the information forthe individual V-VOLs in the right side of the window.

4. In the right side of the window, right-click one or more V-VOLs, and select Release V-VOL fromPool.

CAUTION: A V-VOL cannot be released from a pool if the volume is a volume with pathdefinition or reserved volume of XP Auto LUN Software.

5. Select Apply and then OK to release the V-VOL from the pool. The space assigned to theV-VOLs will be returned back to the pool as free space.

Changing the V-VOL ThresholdTo change the threshold of a V-VOL that is already associated with a pool:1. Access the V-VOL window by selecting Go Volume Manager V-VOL (see “Selecting the

V-VOL Group” (page 66)).2. In the V-VOL Group–V-VOL tree in the left side of the window, select the V-VOL group that

contains the V-VOLs that you want to associate with a pool. Selecting a V-VOL group displaysthe information for the individual V-VOLs in the right side of the window.

3. In the right side of the window, right-click one or more V-VOLs, and select Change Thresholdto display the Change Threshold dialog box (see “Changing the Threshold” (page 67)). Besure to select V-VOLs that are already associated with a pool.

4. Select the threshold from the list, and then click Set to implement the settings and return to theV-VOL window. You can set thresholds from 5% to 300%,, in 5% increments. The default is5%. You can only select from rows with black font.

5. Click Apply, and then click OK to change the V-VOL threshold.

Increasing V-VOL CapacityIf you increase the V-VOL capacity, you must use the raidvchkset command of XP RAID Manager.XP RAID Manager version 01-22-03/06 supports the option for increasing capacity, but does notsupport the option for decreasing capacity.You can increase the capacity of V-VOLs used online for the following operating systems:• Windows Server 2008

• Windows 2003


• AIX: Ver. 5.3 and 6.1

• HP-UX 11.31

• OpenVMS 8.3

• Red Hat Enterprise Linux 5.1Do not increase the capacity of V-VOLs used online to any other host. Any V-VOL's capacity canbe increased if the V-VOL is offline to all hosts. Always check that the host operating system, volumemanager, and file system accept that a LUN’s capacity can be increased before attempting aV-VOL capacity increase. Also review and test the proper procedure documented by the hosts’soperating system concerning increasing a LUN’s capacity.

CAUTION: The processing differs as follows, depending on the value of host mode option 40:• When the value of host mode option 40 is not enabled, the host will not be notified that the

V-VOL capacity has been increased. Therefore, the V-VOL data has to be read again by thestorage system after the capacity has been increased.

• When the value of host mode option 40 is enabled, the host will be notified that the V-VOLcapacity has been increased. If the operating system cannot recognize the value of capacitythat was increased, the V-VOL data has to be read again by the storage system.

To increase the V-VOL capacity, the following conditions must be satisfied:

• Free space exists immediately below the V-VOL in the V-VOL window. In the V-VOL capacity,only the free space capacity can be increased. You can see the free space in the V-VOLwindow of Remote Web Console.

Figure 40 (page 68) illustrates displaying free space.

Figure 40 Example of Displaying Free Space

In this example, you can increase the capacity of the LDEV shown as 00:10:00 by 1,024.75 MB,and the capacity of the LDEV shown as 00:10:67 by 4,087,730.00 MB. You can increase theV-VOL capacity while the free space exists.


NOTE:• If system option mode 726 is enabled (not the default setting), you can set only one V-VOL in

one V-VOL group. You can increase the size of the V-VOL without first migrating the V-VOL,but you cannot use the V-VOL as a custom-sized volume (CVS).

• If system option mode 726 is disabled (the default setting), you can set more than one V-VOLin one V-VOL group.

• The V-VOL to be increased is not shared with an XP product that cannot increase the V-VOL(see the “Using XP Thin Provisioning with Other Products” (page 18)).

• The V-VOL is not undergoing the LDEV format operation.

• The capacity to be added to the V-VOL is smaller than the capacity displayed below theremaining label in the V-VOL window.

• If you increase the V-VOL capacity, the ratio of the free space capacity of the pool to the freespace capacity of the V-VOL is equal to or more than the V-VOL threshold.For details about the relation between increasing V-VOL capacity and the V-VOL threshold,see “Relation Between Increasing V-VOL Capacity and V-VOL Threshold” (page 70).Examples 1 and 2 illustrate whether the capacity of a V-VOL can be increased if the V-VOLthreshold is 50 percent.

◦ In Example 1, the ratio of the free space capacity of the pool to the free space capacityof the V-VOL is 200 percent before the capacity increase and about 56% after the capacityincrease. These percentages exceed the threshold (50 percent). Therefore, the capacityof the V-VOL can be increased.

◦ In Example 2, the ratio of the free space capacity of the pool to the free space capacityof the V-VOL is about 133 percent before the capacity increase and 40% after the capacityincrease. Since the ratio goes below threshold (50 percent) after the capacity increase,the capacity of the V-VOL cannot be increased.

◦ In Example 3, the ratio of the free space capacity of the pool to the free space capacityof the V-VOL is 200 percent, which is lower than the threshold (250 percent). Therefore,the capacity of the V-VOL cannot be increased.

For details about how to calculate the V-VOL threshold, see “V-VOL Requirements” (page 27).


Figure 41 Relation Between Increasing V-VOL Capacity and V-VOL Threshold


For more information on the raidvchkset command for increasing V-VOL capacity, see the HPStorageWorks XP RAID Manager User Guide.

CAUTION: When increasing the V-VOL capacity, do not perform the following operations. Whenperforming the following operations, do not increase the V-VOL capacity.• Operations using the Virtual LVI/LUN function

• Operations using the Cache Residency Manager function

• Creating V-VOLs

• Associating a V-VOL with a pool

• Deleting the association between a V-VOL and a pool

• Restoring pools

• Deleting V-VOLs

• Operations to increase the V-VOL capacity in another instance of XP RAID Manager

• Maintenance of the storage system

CAUTION: After increasing the V-VOL capacity, click Refresh in the Remote Web Console tomake sure that the V-VOL is increased. If the V-VOL is not increased, wait a while, and then clickRefresh again and make sure that the V-VOL is increased. If you perform a Remote Web Consoleoperation without making sure that the V-VOL is increased, the operation from Remote Web Consolecan fail.

CAUTION: Using system option 733 deters simultaneous execution of the maintenance operationand one of the following operations:• Volume migration by XP Auto LUN

• Quick Restore by XP Business CopyIf this system option is in effect and an XP Auto LUN or Quick Restore operation is being performed,you may fail to increase the V-VOL capacity. To confirm whether the V-VOL capacity is increased,click Refresh in Remote Web Console. If the V-VOL capacity is not increased, click Refresh againafter XP Auto LUN or Quick Restore is finished to confirm the capacity.

Releasing Pages in a V-VOLIf all the data written to a page assigned to a V-VOL is binary zeros, you can reclaim the pageand return it to the pool’s available capacity. See “Reclaiming Pages from a V-VOL” (page 11)for restrictions. Select the V-VOLs that you suspect have a several pages written with binary zeros,and use the discard zero data operation, which scans the selected V-VOL's pages and finally freesup those with all binary zeros.Zero data can be discarded if all the following conditions are satisfied:

• The page is completely written with only binary zeros.

• The V-VOL is not used in conjunction with another application that cannot perform discardingzero data.

• LDEV formatting is not being performed on the V-VOL.

• The V-VOL is not blocked.

• The V-VOL is associated with a pool.

• The pool associated with the V-VOL is not blocked, or is full and blocked.


Zero data cannot be discarded if all the following conditions are satisfied:

• The V-VOL status is normal.

• The V-VOL is not associated with a pool.

• Zero data in the V-VOL are already being discarded.To release the pages in a V-VOL:1. In the Remote Web Console, access the V-VOL window by selecting Go Volume Manager

V-VOL (see “Selecting the V-VOL Group” (page 66)).2. In the V-VOL Group - V-VOL tree in the left side of the window, select the V-VOL group

containing the V-VOLs where the pages should be released. This will display the informationabout the individual V-VOLs on the right side of the window.

3. On the right side of the window, right-click one or more V-VOLs, and select Discard Zero Datafrom the pop-up menu. This may take some time as the software scans the entire V-VOL lookingfor pages with zero data, marking them for release when you later click Apply.

4. After selecting Discard Zero Data (and before clicking Apply), if you want to stop releasingpages, right-click one or more V-VOLs, and select Stop Discarding Zero Data. The discardingof zero data stops, but the already discarded zero data cannot be restored, and the pagesmarked for release will be released when you click Apply.You cannot stop releasing pages if the page status for the V-VOL is not Discarding Zero Data.

5. Click Apply, and then click OK to release pages in the V-VOL in the background.6. After discarding zero data and releasing pages in the V-VOL is complete, click Refresh in the

Remote Web Console to update the Page Status. If the Page Status is not immediately updated,wait awhile, and then click Refresh again.

If you have started a discard zero data operation, and the storage system loses power, which thendisrupts shared memory, the discard zero data operation will not automatically continue after thestorage system restarts.In any of the following cases, discarding of zero data will stop and V-VOL pages will not bereleased:

• LDEV formatting was performed while discarding zero data.

• The pool-VOL that is being accessed by the target V-VOL was blocked.

• The pool associated with the target V-VOL was blocked while discarding zero data.

• The pool-VOL accessed by the target V-VOL cannot be used temporarily.

• Cache memory failure occurred while discarding zero data.

• The association between the target V-VOL and the pool was released when zero data wasdiscarded.

• An attempt was made to perform XP Continuous Access or XP Continuous Access Journal initialcopy operations on the V-VOL when zero data was discarded from the V-VOL.

Changing the V-VOL Settings of Multiple V-VOL GroupsYou can change information about V-VOLs in multiple V-VOL groups, such as the pool associationand the threshold.

Associating Multiple V-VOL Groups with a PoolYou can associate multiple V-VOL groups with a pool. The time required to associate changesbetween V-VOLs in multiple V-VOL groups with a pool can vary greatly depending on the V-VOLcapacity and the quantity of V-VOLs being associated.To associate multiple V-VOL groups with a pool:


1. Access the V-VOL window (see “Selecting the V-VOL Group” (page 66)) by selecting GoVolume Manager V-VOL .

2. Right-click XP Thin Provisioning in the V-VOL group tree of the V-VOL window, and then selectAssociate V-VOL Groups with Pool. The Associate V-VOL Groups with Pool dialog box opens(see Figure 42 (page 74)). Depending on your environment, it may take up to 30 seconds toopen the Associate V-VOL Groups with Pool dialog box.

3. In the V-VOL groups information setting list in the Associate V-VOL Groups with Pool dialogbox, select the V-VOL groups you want to associate with a pool.Display the list of V-VOL groups that are included in the CLPR by selecting a specific CLPRfrom the CLPR list. The groups will be displayed in the V-VOL groups information setting list.Find V-VOL groups by clicking the button in the page area under the list. The page that includesthe V-VOL groups will be displayed. The list displays V-VOL groups up to a maximum of 4,096at a time. For lists that exceed this maximum, click Previous and Next to display the remainingV-VOL groups.The following V-VOL groups will not be displayed in the Associate V-VOL Groups with Pooldialog box:

• A V-VOL group in which the first LDEV has been associated with a pool.

• A V-VOL group lacking any V-VOLs.4. Click Set. The specified V-VOL groups are displayed in blue bold italics and the Connect Pool

dialog box opens (see “Selecting the Pool” (page 66)).5. Click Clear to clear the specified V-VOL groups. To specify more V-VOL groups, repeat Step

3 and Step 4.6. Select the pool ID with which you want to associate the V-VOL groups in the Connect Pool

dialog box, and then select Next to display the Change Threshold dialog box (see “Changingthe Threshold” (page 67)). If you clear the information and return to the Associate V-VOLGroups with Pool dialog box, click Cancel.

7. In the Change Threshold dialog box, select the threshold from the list, then click Set to implementthe settings and return to the V-VOL window. If you want to clear the information and returnto the Associate V-VOL Groups with Pool dialog box, click Cancel.The pool ID and the threshold that you set are displayed in blue bold italics. To specify otherV-VOL groups, repeat Step 3.

8. Click OK. The Associate V-VOL Groups with Pool dialog box closes and a confirmation messageis displayed to ask if it is OK to apply the setting to the storage system.

9. Click OK. The confirmation message closes and the V-VOL groups are associated with thepool. If you click the Cancel button in this message, the Associate V-VOL Groups with Pooldialog box is displayed again. If the specified V-VOL groups cannot be associated with apool, a message box is displayed.


Figure 42 Associate V-VOL Groups with Pool Dialog Box

Releasing Multiple V-VOL Groups from a PoolBefore releasing V-VOL groups from a pool, confirm that the pool-VOLs added to the pool are notblocked. If the pool-VOLs are blocked, restore the volume status, then release the V-VOLs from apool.Also, if the cache write pending rate exceeds 55%, the pool usage may not be 0, because theV-VOL cannot be released from the pool.After a V-VOL is released from a pool, performance of the initial copy may be lowered if the XPContinuous Access pair or the XP Continuous Access Journal pair is in the same pool as the V-VOL.You can prevent the performance from being lowered in one of the following ways:• Do not release the V-VOL from the same pool where the initial copy of the XP Continuous

Access pair V-VOL or the XP Continuous Access Journal pair V-VOL is performed.• Before making an initial copy of the XP Continuous Access pair or the XP Continuous Access

Journal pair, reserve enough pool capacity so that the threshold will not be reached duringthe initial copy.

If you attempt to release a V-VOL using the Quick Restore feature of XP Business Copy or XP AutoLUN Software, error 3005 68727 may occur if the V-VOL had been previously used in a QuickRestore or XP Auto LUN Software migration. If the error occurs, use the following equation tocalculate how long to wait before attempting to release the V-VOL again:(Pool Capacity in terabytes x 3 seconds) + 40 minutes.Heavy workload on the storage system could add additional time to the wait period. If the V-VOLoperation status is in Processing state, then wait for the state to change to Ready before attemptingAuto LUN or Quick Restore.


To release multiple V-VOL groups from a pool:

CAUTION: Confirm that the pool-VOLs that are added to a pool are not blocked. If the pool-VOLsare blocked, restore the volume status, and then release the V-VOLs from a pool.


2. Right-click XP Thin Provisioning in the V-VOL group tree of the V-VOL window, and selectRelease V-VOL Groups from Pool. The Release V-VOL Groups from Pool dialog box (see“Release V-VOL Groups from Pool Dialog Box” (page 76)) is displayed. Depending on yourenvironment, it may take up to 30 seconds to open the Release V-VOL Groups from Pool dialogbox.

3. In the V-VOL groups information setting list in the Release V-VOL Groups from Pool dialogbox, select the V-VOL groups you want to release from a pool.In the Pool ID list, specify a pool ID. The list of V-VOL groups associated with the selected poolID is displayed in the V-VOL groups information setting list. Find V-VOL groups by clicking thebutton in the page area under the list. The page that includes the V-VOL groups is displayed.The list displays V-VOL groups up to a maximum of 4,096 at a time. For lists that exceed thatnumber, click Previous and Next to display the remaining V-VOL groups.The following V-VOL groups will not be displayed in the Release V-VOL Groups from Pooldialog box:

• A V-VOL group in which the first LDEV has been associated with a pool

• A V-VOL group lacking any V-VOLs4. Click Set. The specified V-VOL groups are displayed in a blue, italic font. Click Clear to clear

the specified V-VOL groups. To specify more V-VOL groups, repeat Step 3 and Step 4.5. Click OK. The Release V-VOL Groups from Pool dialog box closes and a confirmation message

is displayed to ask if it is OK to apply the setting to the storage system.6. Click OK. The confirmation message closes and the V-VOL groups are released from the pool.

If you click the Cancel button in this message, the Release V-VOL Groups from Pool dialogbox is displayed again. If the specified V-VOL groups cannot be released from a pool, amessage dialog box appears.


Figure 43 Release V-VOL Groups from Pool Dialog Box

Deleting V-VOL GroupsTypically you specify and delete a single V-VOL group. If you choose to delete multiple V-VOLgroups, all V-VOLs in multiple V-VOL groups will be deleted.

Deleting a V-VOL GroupYou can delete a V-VOL group and all V-VOLs in the V-VOL group.V-VOL groups associated with a pool ID cannot be deleted. To delete such a group, first releasethe V-VOL group from a pool, then delete it.To delete a V-VOL group:1. Access the V-VOL window by selecting Go Volume Manager V-VOL (see “Selecting the

V-VOL Group” (page 66)).2. In the V-VOL Group–V-VOL tree in the left side of the window, right-click the V-VOL group that

contains the V-VOL group and V-VOLs that you want to delete, and then select Delete V-VOLGroup.

3. Click OK on the confirmation message. The icon of the selected V-VOL group changes toindicate that deletion is in process.

4. Click Apply, and then click OK to delete the V-VOL group.

Deleting Multiple V-VOL GroupsYou can delete multiple V-VOL groups and the V-VOLs in all the V-VOL groups.V-VOL groups associated with a pool ID cannot be deleted. To delete such a group, first releasethe V-VOL groups from a pool, then delete it.To delete selected multiple V-VOL groups:



2. Right-click XP Thin Provisioning in the V-VOL group tree of the V-VOL window, and then selectDelete V-VOL Groups. The Delete V-VOL Groups dialog box opens (see “Delete V-VOL GroupsDialog Box” (page 55)). Depending on your environment, it may take 30 seconds to openthe Delete V-VOL Groups dialog box.

3. Select the V-VOL groups you want to delete from the V-VOL groups information setting list inthe Delete V-VOL Groups dialog box. In the CLPR list, select a CLPR, and the list of V-VOLgroups that are included in the CLPR is also displayed in the V-VOL groups information settinglist. Find the V-VOL groups that you want to delete by clicking the button in the page areaunder the list. The page that includes the V-VOL groups that you want to delete is displayed.The list displays V-VOL groups up to a maximum of 4,096 at a time. For lists that exceed thismaximum, click Previous and Next to display the remaining V-VOL groups.

4. Click Set. The specified V-VOL groups are displayed in blue bold italics. Click Clear if youwant to clear the specified V-VOL groups. To specify more V-VOL groups, repeat Step 3 andStep 4.

5. Click OK. The Delete V-VOL Groups dialog box closes and a confirmation message is displayedto ask if it is OK to apply the setting to the storage system.

6. Click OK. The confirmation message closes and the deletion of the V-VOL groups is appliedto the subsystem. If you click the Cancel button in this message, the Delete V-VOL Groupsdialog box is displayed again. If the specified V-VOL groups are not deleted, a messagedialog box appears.

Figure 44 Delete V-VOL Groups Dialog Box

Deleting V-VOLsThis operation deletes selected V-VOLs in the V-VOL group.


To delete selected V-VOLs:1. Delete the selected V-VOLs using the Virtual LVI/LUN Volume to Space function. For more

information, see the HP StorageWorks XP24000/XP20000 Virtual LVI/LUN (VLL) and VolumeShredder User Guide.

2. In the VLL tree in the upper left corner of the VLL window, select the XP Thin Provisioning folderand then select the parity group.

3. From the V-VOL list on the upper right, select the target V-VOL groups from the list of the V-VOLgroups, and then select the LDEV to be deleted.


6 TroubleshootingThis chapter describes how to troubleshoot XP Thin Provisioning problems.• “XP Thin Provisioning Troubleshooting” (page 79)

• “Managing Pool-Related SIMs” (page 83)

• “Troubleshooting when using XP RAID Manager” (page 84)

• “Calling HP Technical Support” (page 86)

XP Thin Provisioning TroubleshootingTable 15 (page 79) provides troubleshooting instructions for XP Thin Provisioning operations.

Table 15 Troubleshooting for XP Thin Provisioning

Causes and SolutionsProblems

Cause:• Shared memory for the V-VOL management area is not

installed.Solution:

• Call HP technical support and check if the shared memoryfor the V-VOL management area is installed.

Cannot install XP Thin Provisioning.

Causes:• Capacity of the pool is insufficient.

• The threshold of the pool is too low.

Solutions:

• Add some pool-VOLs to increase the capacity of the pool.See “Viewing Pool Information” (page 58). Also, consult HPfor best practices on adding capacity.

• Set a larger value to the threshold of the pool. See “Changingthe Pool Threshold” (page 60).

After the causes of SIMs 620XXX and 621XXX are resolved, youwill need to complete the SIMs. If you do not complete the SIMs,no new SIMs will occur ( even if the usage level increases andagain exceeds the threshold).SIMs 620XXX, 621XXX, and 625000 are automaticallycompleted if you increase pool capacity by adding pool-VOLsbecause the condition that caused the SIM is removed.For details about how to complete SIMs, see “ManagingPool-Related SIMs” (page 83).You need free volumes to add as pool-VOLs. If there are no freevolumes, you need to create new volumes or ask HP technicalsupport to add hard disks. Therefore, it may take time to solvethe problem.

Pool usage level exceeds the threshold.

XP Thin Provisioning Troubleshooting 79

Table 15 Troubleshooting for XP Thin Provisioning (continued)


Causes:• 1024 pool-VOLs are already defined in the pool.

• There is no available free LDEV to add to the pool.

• Something in the storage system is blocked.

Solutions:

• Add free LDEVs to another pool. See “Viewing PoolInformation” (page 58).

• Confirm that the pool-VOL meets the pool requirements. See“Volume and Pool Requirements” (page 26).

• Ask HP technical support to solve the problem.

Cannot add pool-VOLs.

Causes:• The pool usage level is 100%. Also the maximum of V-VOLs

is currently associated with the pool.• Something in the storage system is blocked.

Solutions:

• Add some pool-VOLs to increase the available capacity ofthe pool. See “Viewing Pool Information” (page 58).


Cannot assign a V-VOL to a pool.

Cause:• A failure occurred in two or more hard disk drives.

Solution:


A pool-VOL is blocked.

Cause:• The breaker has been turned off and the shared memory has

been lost, and then the system has been started.Solution:


A pool is blocked.

Causes:• Processing takes time, because something in the storage

system is blocked.• The pool-VOL is blocked.

• Although you increased the V-VOL capacity, it has beenreduced back to the previous V-VOL capacity.

Solutions:

• After waiting awhile, select Refresh or Refresh All from theFile menu at the top left of the Remote Web Console window,and then check the pool status.

• If you increased the V-VOL capacity and it has been reducedback to the previous V-VOL capacity, follow the instructionsin “Increasing V-VOL Capacity” (page 67) to make sure thatthe capacity is increased, and then restore the pool.


A pool cannot be restored.

80 Troubleshooting



Cause:• After the pool is disassociated from any V-VOL, the pool usage

is not 0.• External volumes were not removed from the pool.

Solutions:

• Confirm that the pool usage is 0, and then delete the pool.

• Ask HP Technical Support to solve the problem.

A pool cannot be deleted.

Cause:• Because the cache write pending rate exceeds 55 %, the

V-VOL cannot be disassociated from the pool.Solution:

• Decrease the cache write pending rate to less than 55% byreducing the host I/O.

A pool usage cannot be 0.

Causes:• Free space for the pool is completely exhausted. The pool

usage level is at 100%.• Something in the storage system is blocked.

Solutions:

• Check the free space of the pool and increase the capacityof the pool.


I/O errors on some writes occur onV-VOLs

Causes:• The load on the Remote Web Console computer is too heavy,

so the Remote Web Console computer cannot respond to theSVP.

• The period of time until a time-out occurs is set too short.

Solutions:

• Wait for awhile, and then try the operation again.

• Verify the setting for the environment parameter of the RemoteWeb Console RMI time-out period.For information about how to set the RMI time-out period, seethe HP StorageWorks XP24000/XP20000 Remote WebConsole User Guide.

When you are operating Remote WebConsole, a time-out occurs frequently.

Causes:• Free space for the pool is insufficient.

• Something in the storage system is blocked.

Solutions:

• Check the free space for the pool and increase the capacityof the pool.


When the host computer tries to accessthe port, an error occurs and the hostcannot access the port.

XP Thin Provisioning Troubleshooting 81



Causes:See “Troubleshooting when using XP RAID Manager” (page 84)to identify the cause.Solutions:

• After selecting the Refresh or Refresh All command from theFile menu at the top left of the Remote Web Console window,make sure that the processing for increasing V-VOL capacitymeets conditions described in “Increasing V-VOL Capacity”(page 67).

• Retry the operation in 10 minutes.


V-VOL capacity cannot be increased.

Cause:• Zero data in the V-VOL cannot be discarded from Remote

Web Console because the V-VOL does not meet the conditionsdescribed in “Releasing Pages in a V-VOL” (page 71).

Solution:

• Make sure that the V-VOL meets the conditions described in“Releasing Pages in a V-VOL” (page 71).

Cannot discard zero data in a V-VOL.

Cause:• Pages of the V-VOL are not released because the process of

discarding zero data was interrupted. For details, see“Releasing Pages in a V-VOL” (page 71).

Solution:• Make sure that the V-VOL meets the conditions described in

Releasing Pages in a V-VOL and perform the solution.

The V-VOL cannot not be released thoughzero data in the V-VOL is discarded.

Cause:• The pool is full.

• The pool-VOL is blocked.

• The pool-VOL of the external volume is blocked.

Solutions:

• Add pool-VOLs to the pool to increase the free space in thepool. For more information, see “ Creating a Pool” (page 58).

• To restore the pool-VOL, contact the Hitachi Data SystemsTechnical Support Center.

• If the pool-VOL is an external volume, check the condition ofthe external storage system, for instance the path blockade.

• After performing the above-mentioned solutions, release theProtection attribute of the V-VOLs using the Data Retentionwindow of Remote Web Console (if the Data Retention Utilityis installed).

For information about operating procedures, see the HPStorageWorks XP24000/XP20000 Data Retention Utility UserGuide.

Cannot release the Protection attribute ofthe V-VOLs.

82 Troubleshooting



Cause:• Pool usage level exceeds the threshold.Solution:• Add pool-VOLs to the pool to increase the free space in the

pool. For more information, see “ Creating a Pool” (page 58).

SIM code such as 620XXX, 621XXX,622XXX, or 625000 was issued.

Cause:• You disassociated a V-VOL from a pool that contains other

V-VOLs in XP Continuous Access pair or XP Continuous AccessJournal pairs. The initial copy is slow because the clean-upprocedure for the removed V-VOL is consuming systemresources.

Solutions:

• Do not disassociate a V-VOL from the pool where the Initialcopy of the XP Continuous Access pair V-VOL or the XPContinuous Access Journal pair V-VOL is performed.

• Before you perform the Initial copy of an XP ContinuousAccess pair or XP Continuous Access Journal pair, reserveenough pool capacity so that the threshold will not be reachedduring the initial copy.

Performance of the initial copy has beenreduced.

If you are unable to solve a problem using the above suggestions, or if you encounter a problemnot listed, contact HP technical support.If an error occurs during the operations, the error code and error message are displayed in theerror message box. For more information about error messages, see the HP StorageWorksXP24000/XP20000 Remote Web Console Error Codes.

Managing Pool-Related SIMsWhen the usage level of the pool exceeds the threshold, or when the potential demand of theV-VOL exceeds the threshold, the following SIMs (Service Information Message) occur.

Reference code 620XXXWhen the usage level of the pool exceeds pool threshold1:

Reference code 621XXXWhen the usage level of the pool exceeds pool threshold2:

Reference code 625000When pool usage level continues to exceed the highestpool threshold:

Reference code 622XXXWhen the pool is full:

Reference code 623XXXWhen an error occurs in the pool:

Reference code 630XXXWhen the level of free pool capacity to potential demandof a V-VOL exceeds the V-VOL threshold:

Reference code 640XXXWhen the V-VOL management area cannot be saved topools:

To complete a SIM that occurs when the usage level for the pool exceeds the threshold or whenthe usage level for the V-VOL exceeds the threshold:1. Change the status of the pool or the V-VOL whose usage level exceeds the threshold to normal.

For information about the solutions when the pool usage level or the V-VOL potential demandexceeds the threshold, see “Troubleshooting for XP Thin Provisioning” (page 79).

Managing Pool-Related SIMs 83

2. Change the mode of Remote Web Console to Modify.For information about how to change the mode, see the HP StorageWorks XP24000/XP20000Remote Web Console User Guide.

3. Display the Pool window.4. Select the SIM Complete Request check box in the Pool window.5. Click Apply. A confirmation message is displayed, asking if it is OK to apply the setting to

the storage system.6. Click OK.

The confirmation message closes and the SIM complete process begins. It takes time if thereare many SIMs to be completed.

If you complete a SIM, the status of the SIM changes to completed. After the problem that causedthe SIM is solved, complete the SIM and change its status to completed. If you complete the SIMbefore the underlying problem is solved, the SIM may occur again.After correcting the causes of SIMs 620XXX and 621XXX, you will need to complete the SIMs. Ifyou do not complete the SIMs, no new SIMs will occur ( even if the usage level increases andagain exceeds the threshold).SIMs 620XXX, 621XXX, and 625000 are automatically completed if you increase pool capacityby adding pool-VOLs because the condition that caused the SIM is removed.You can check whether SIMs complete successfully in the Remote Web Console window. Fordetails, see the HP StorageWorks XP24000/XP20000 Remote Web Console User Guide.

Troubleshooting when using XP RAID ManagerIf an error has occurs when increasing V-VOL capacity using XP RAID Manager, you may be ableto identify the cause of the error by referring to the log displayed in the XP RAID Manager windowor XP RAID Manager operation log file. The log file is stored in the following directory by default:/HORCM/log*/curlog/horcmlog_HOST/horcm.log

Where:

• * is the instance number.

• HOST is the host name.To identify the error code using the log file, use the following the procedure:1. Open the XP RAID Manager log file and find the error code.

Example:09:06:18-82a22-10228- SSB = 0xb96b,af2a

Error codes appear on the right of the equal symbol (=). SSB1 appears on the left of thecomma (,), and SSB2 appears on the right of the comma (,).

2. See Table 16 (page 85) to find the meaning of the error code.For details about the error codes that are not described in Table 16 (page 85), contact HPtechnical support (see “Calling HP Technical Support” (page 86)).

To identify the error code using the log displayed on the XP RAID Manager window, follow theprocedure below.1. Find the error code from the logs displayed on the XP RAID Manager window.

Example:It was rejected due to SKEY=0x05,ASC=0x20,SSB=0xB9E1,0xB901 on Serial#(64015)

84 Troubleshooting

Error codes appear on the right of SSB=. The left of the comma (,) contains SSB1, and theright of the comma (,) contains SSB2.

2. See Table 16 (page 85) and find the meaning of the error code.For details about the error codes that are not described in Table 16 (page 85), contact HPtechnical support (see “Calling HP Technical Support” (page 86)).

Table 16 Error Code and Error Contents When Operating XP RAID Manager

SolutionError ContentsError Code (SSB2)Error Code (SSB1)

Ask HP technical support tosolve the problem.

Error occurred whenincreasing V-VOL capacityoperation.

0xb9000xb9010xaf28

0xb96b

Increase the V-VOL capacityafter finishing operations suchas the Virtual LVI/LUNoperation or the maintenanceoperation on your storagesystem. See the Caution in“Increasing V-VOL Capacity”(page 67).

Because the configurationwas being changed by theSVP or Remote Web Console,the operation was rejected.

0xb9020xb96b

Make sure that the total V-VOLcapacity does not exceed thepool capacity after the V-VOLcapacity increases.

The operation was rejectedbecause the total V-VOLcapacity exceeds the poolcapacity after the V-VOLcapacity increases.

0xaf240xb96b

Reexecute the operation aftera brief interval.

The operation was rejectedbecause releasing pages inthe specified volume has notbeen completed.

0xaf250xb96b

Makes sure that the volume isa V-VOL.

Because the specified volumewas not a V-VOL, theoperation was rejected.

0xaf290xb96b

When increasing capacity,specify that the capacity doesnot exceed the free spacecapacity displayed in theV-VOL window. For details, seethe conditions for increasingthe V-VOL capacity in“Increasing V-VOL Capacity”(page 67).

Because the specifiedcapacity exceeded the freespace size immediately belowthe V-VOL, the operation wasrejected.

0xaf2a0xb96b

Re-execute the operation aftera brief interval.

Because the specified volumeoperation was not finished,the operation was rejected.

0xaf2b0xb96b

Make sure the value ofremaining in the V-VOLwindow is enough.

Because the shared memorycapacity is not enough toincrease the specifiedcapacity, the operation wasrejected.

0xaf2c0xb96b

Troubleshooting when using XP RAID Manager 85

Table 16 Error Code and Error Contents When Operating XP RAID Manager (continued)

SolutionError ContentsError Code (SSB2)Error Code (SSB1)

When increasing capacity,make sure that the ratio of freespace in the pool to free spacein the V-VOL is not below theV-VOL threshold. For details,see the conditions forincreasing the V-VOL capacityin “Increasing V-VOL Capacity”(page 67).

Because the ratio of the freespace capacity of the pool tothe free space capacity of theV-VOL was less than theV-VOL threshold, theoperation was rejected.

0xaf2d0xb96b

Wait until formatting of thespecified volume is finished, orsee “Using XP Thin Provisioningwith Other Products” (page 18)and confirm whether the V-VOLis used with the applicationthat the V-VOL capacity cannotbe increased.

Because the specified V-VOLwas used by anotherapplication or was beingformatted, the operation wasrejected.

0xaf2e0xb96b

Re-execute the operation afterthe microcode is replaced.

Because the V-VOL capacitywas increased when themicrocode was replaced, theoperation was rejected.

0xaf2f0xb96b

Calling HP Technical SupportIf you need to call HP technical support, make sure to provide as much information about theproblem as possible, including:• The circumstances surrounding the error or failure

• The exact content of any error messages displayed on the host systems

• The exact content of any error messages displayed by Remote Web Console

• The Remote Web Console configuration information (use the FD Dump Tool)

• The service information messages (SIMs), including reference codes and severity levels,displayed by Remote Web Console

For worldwide technical support information, see the HP support website:http://www.hp.com/support

86 Troubleshooting

http://www.hp.com/support

7 Support and Other ResourcesRelated Documentation

• HP StorageWorks XP24000/XP20000 Cache Residency Manager User Guide

• HP StorageWorks XP RAID Manager User Guide

• HP StorageWorks XP24000/XP20000 Snapshot User Guide

• HP StorageWorks XP24000/XP20000 Data Retention Utility User Guide

• HP StorageWorks XP24000/XP20000 LUN Expansion User Guide

• HP StorageWorks XP24000/XP20000 LUN Manager User Guide

• HP StorageWorks XP24000/XP20000 Performance Monitor User Guide

• HP StorageWorks XP24000/XP20000 Auto LUN Software User Guide

• HP StorageWorks XP24000/XP20000 Performance Control User Guide

• HP StorageWorks XP24000/XP20000 Business Copy Software User Guide

• HP StorageWorks XP24000/XP20000 SNMP Agent Reference Guide

• HP StorageWorks XP24000/XP20000 Remote Web Console User Guide

• HP StorageWorks XP24000/XP20000 Continuous Access Software User Guide

• Hitachi TrueCopy™ for Mainframe User Guide: HP XP24000 Disk Array, HP XP20000 DiskArray

• HP StorageWorks XP24000/XP20000 Continuous Access Journal Software User Guide

• HP StorageWorks XP24000/XP20000 External Storage Software User Guide

• HP StorageWorks XP24000/XP20000 Disk Array Owner Guide

• HP StorageWorks XP24000/XP20000 Virtual LVI/LUN (VLL) and Volume Shredder UserGuide

• HP StorageWorks XP24000/XP20000 Disk/Cache Partition User GuideYou can find these documents on the HP Manuals website:

http://www.hp.com/support/manuals

In the Storage section, click Storage Software, and then select a product.

Conventions for Storage Capacity ValuesHP XP storage systems use the following values to calculate physical storage capacity values (harddisk drives):

• 1 KB (kilobyte) = 1,000 bytes

• 1 MB (megabyte) = 1,0002 bytes

• 1 GB (gigabyte) = 1,0003 bytes

• 1 TB (terabyte) = 1,0004 bytes

• 1 PB (petabyte) = 1,0005 bytesHP XP storage systems use the following values to calculate logical storage capacity values (logicaldevices):

• 1 KB (kilobyte) = 1,024 (210) bytes

• 1 MB (megabyte) = 1,024 KB or 1,0242 bytes

Related Documentation 87


• 1 GB (gigabyte) = 1,024 MB or 1,0243 bytes

• 1 TB (terabyte) = 1,024 GB or 1,0244 bytes

• 1 PB (petabyte) = 1,024 TB or 1,0245 bytes

• 1 block = 512 bytes

HP Technical SupportFor worldwide technical support information, see the HP support website:


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

Subscription ServiceHP recommends that you register your product at the Subscriber’s Choice for Business website:

http://www.hp.com/go/e-updates

After registering, you will receive email notification of product enhancements, new driver versions,firmware updates, and other product resources.

HP WebsitesFor additional information, see the following HP websites:

• http://www.hp.com

• http://www.hp.com/go/storage

• http://www.hp.com/support/manuals

• http://www.hp.com/storage/spock

Documentation FeedbackHP welcomes your feedback.To make comments and suggestions about product documentation, send a message [email protected]. All submissions become the property of HP.

88 Support and Other Resources


http://www.hp.com/go/e-updates

http://www.hp.com

http://www.hp.com/go/storage


http://www.hp.com/storage/spock

mailto:[email protected]

GlossaryC

CLPR Cache logical partition.CU Control unit.CV Custom-sized volume.CYL Cylinder.

D

DKA Disk adapter.DKC Disk controller.DKCMAIN Disk controller main.

G

G-ID Host group ID.

L

LD, LDEV Logical device. An LDEV is created when a RAID group is carved into pieces according to theselected host emulation mode (that is, OPEN-3, OPEN-8, OPEN-9). The number of resulting LDEVsdepends on the selected emulation mode. The term LDEV is also known as term volume.

LDKC Logical disk controller.LUN Logical unit number.LUSE Logical Unit Size Expansion. The LUSE feature is available when the HP StorageWorks LUN

Manager product is installed, and allows a LUN, normally associated with only a single LDEV,to be associated with 1 to 36 LDEVs. Essentially, LUSE makes it possible for applications to accessa single large pool of storage.

M

Mng. Management.

P

P-VOL Primary volume.PDEV Physical device.Pool-VOL Pool volume.

S

S-VOL Secondary or remote volume. The copy volume that receives the data from the primary volume.SI Hitachi ShadowImage. Also known as HP StorageWorks XP Business Copy.SIM Service information message.SLPR Storage logical partition.SM Shared memory.SMPL Simplex.SSID Subsystem identifier; storage system identifier.SVP Service processor. A computer built into a disk array. The SVP, used only by an HP service

representative, provides a direct interface to the disk array.

89

V

V-VOL Virtual volume.VDEV Virtual device.VLL Virtual LVI/LUN.VMA Volume management area.

90 Glossary

Index

Aa V-VOL management area, 11associating V-VOLs in multiple V-VOL Groups with a pool,

51

Cchanging the pool information, 60Changing the V-VOL Information, 65changing the V-VOL settings of multiple V-VOL groups, 72changing threshold of the V-VOL, 67conventions

storage capacity values, 87creating pools, 10, 58creating V-VOLs, 10

Ddelete V-VOL groups dialog box, 76deleting a pool, 61deleting multiple pools, 61deleting pools, 61deleting V-VOLs, 77document

related documentation, 87documentation

HP website, 87providing feedback, 88

Hhelp

obtaining, 88HP

technical support, 88

Iincreasing V-VOL capacity, 67installing, 24, 28interoperability with other products and functions, 18

Llicense requirements, 24

Mmanaging pool-related SIMs, 83managing pools, 57managing V-VOLs, 62monitoring the available pool capacity, 12Monitoring Usage Rates, 13

Nnew pool dialog box, 40

Oos and file system reducing capacity effectively, 24

Ppool, 10Pool and Virtual Volumes, 9pool requirements, 26, 27Pool Status, 17pool window, 29, 34pool-VOL requirements, 27pool-VOLs, 10pools, 29, 34pop-up menu

V-VOL group tree and the V-VOL list, 38pop-up menus

pool tree, 34

Rrecovering a pool, 61recovering multiple pools, 62recovering pools in blocked status, 61related documentation, 87

Ssetting the pool association information to the V-VOL, 65setting up

storage system and Remote Web Console, 24shared memory, 11shared memory requirements, 24SIM codes, 16SIMs, 83SLPR, 64storage capacity values

conventions, 87storage systems

supported models, 6subscriber's choice, HP, 88Support Configuration, 9

Ttechnical support, 88

HP, 86, 88technical support, HP, 86, 88troubleshooting RAID manager, 84

Uuninstalling, 24, 28using XP Thin Provisioning, 57

VV-VOL, 10V-VOL list, 36V-VOL requirements, 28V-VOLs, 34viewing pool information, 58volume requirements, 26

91

Wwebsites

HP, 88HP Subscriber's Choice for Business, 88product manuals, 87

XXP Business Copy, 22XP Disk/Cache Partition, 23XP Thin Provisioning Components, 9XP Thin Provisioning troubleshooting, 79XP Thin Provisioning window, 38

92 Index

thin provisioning

Documents