Hitachi Virtual Storage Platform G1000 - Hitachi Data · PDF fileProduct Version Contents Getting Help FASTFIND LINKS Hitachi Virtual Storage Platform G1000 Provisioning Guide for

Product Version

Contents

Getting Help

FASTFIND LINKS

Hitachi Virtual Storage Platform G1000Provisioning Guide for Mainframe Systems

MK-92RD8013-02

© 2014 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means,electronic or mechanical, including photocopying and recording, or stored in a database or retrievalsystem for any purpose without the express written permission of Hitachi, Ltd.

No part of this publication may be reproduced or transmitted in any form or by any means,electronic or mechanical, including photocopying and recording, or stored in a database or retrievalsystem for any purpose without the express written permission of Hitachi, Ltd.

Hitachi, Ltd., reserves the right to make changes to this document at any time without notice andassumes no responsibility for its use. This document contains the most current information availableat the time of publication. When new or revised information becomes available, this entiredocument will be updated and distributed to all registered users.

Some of the features described in this document might not be currently available. Refer to the mostrecent product announcement for information about feature and product availability, or contactHitachi Data Systems Corporation at https://portal.hds.com.

Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions ofthe applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products isgoverned by the terms of your agreements with Hitachi Data Systems Corporation.

Notice on Export Controls: The technical data and technology inherent in this Document may besubject to U.S. export control laws, including the U.S. Export Administration Act and its associatedregulations, and may be subject to export or import regulations in other countries. Reader agrees tocomply strictly with all such regulations and acknowledges that Reader has the responsibility toobtain licenses to export, re-export, or import the Document and any Compliant Products.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. HitachiData Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States andother countries.

Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft,Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform areregistered trademarks of Hitachi Data Systems Corporation.

AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON, FICON,FlashCopy, IBM, Lotus, MVS, OS/390, RS/6000, S/390, System z9, System z10, Tivoli, VM/ESA,z/OS, z9, z10, zSeries, z/VM, and z/VSE are registered trademarks or trademarks of InternationalBusiness Machines Corporation.

All other trademarks, service marks, and company names in this document or website areproperties of their respective owners.

Microsoft product screen shots are reprinted with permission from Microsoft Corporation.

iiHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

https://portal.hds.com

Contents

Preface.................................................................................................. xiIntended audience....................................................................................................xiiProduct version........................................................................................................ xiiRelease notes...........................................................................................................xiiDocument revision level............................................................................................ xiiChanges made in this revision................................................................................... xiiReferenced documents.............................................................................................xiiiDocument conventions.............................................................................................xiiiConvention for storage capacity values......................................................................xivAccessing product documentation..............................................................................xvGetting help.............................................................................................................xvComments............................................................................................................... xv

1 Introduction to provisioning...................................................................1-1About provisioning.................................................................................................. 1-3Basic provisioning................................................................................................... 1-3Fixed-sized provisioning.......................................................................................... 1-3Disadvantages .......................................................................................................1-3When to use fixed-sized provisioning........................................................................1-4Custom-sized provisioning....................................................................................... 1-4When to use custom-sized provisioning.................................................................... 1-5Basic provisioning workflow..................................................................................... 1-5Dynamic Provisioning Overview................................................................................1-5Dynamic Provisioning for Mainframe.........................................................................1-5Dynamic Provisioning for Mainframe concepts ..........................................................1-6When to use Dynamic Provisioning for Mainframe..................................................... 1-7Dynamic Provisioning for Mainframe advantages.......................................................1-7Dynamic Provisioning for Mainframe advantage example........................................... 1-8Dynamic Provisioning for Mainframe workflow.......................................................... 1-8Dynamic Tiering for Mainframe................................................................................ 1-9Tiers concept .......................................................................................................1-10When to use Dynamic Tiering for Mainframe...........................................................1-11Resource groups strategies....................................................................................1-11Complimentary strategies...................................................................................... 1-12Key terms.............................................................................................................1-12Before you begin...................................................................................................1-13

iiiHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

About cache management devices..........................................................................1-15Calculating the number of cache management devices required by a DP-VOL..... 1-15

Maximum capacity of cache management device..................................... 1-15Calculating the number of cache management devices required by a volume that is not a DP-VOL..................................................................................... 1-15Viewing the number of cache management devices...........................................1-15

2 Configuring resource groups..................................................................2-1System configuration using resource groups............................................................. 2-3Resource groups examples...................................................................................... 2-3

Example of resource groups sharing a port.........................................................2-3Example of resource groups not sharing ports.................................................... 2-5

Meta_resource........................................................................................................2-7Resource lock......................................................................................................... 2-7User groups............................................................................................................2-7Resource group assignments................................................................................... 2-8Resource group license requirements....................................................................... 2-8Resource group rules, restrictions, and guidelines..................................................... 2-8Creating a resource group....................................................................................... 2-9Adding resources to a resource group.....................................................................2-10Removing resources from a resource group............................................................ 2-11Managing Resource Groups................................................................................... 2-11

Changing the name of a resource group...........................................................2-11Deleting a resource group............................................................................... 2-12

Using Resource Partition Manager and other VSP G1000 products............................ 2-13Compatible PAV.............................................................................................. 2-13Dynamic Provisioning for Mainframe and Dynamic Tiering for Mainframe............ 2-13Compatible Software for IBM® FlashCopy® SE................................................ 2-14Encryption License Key....................................................................................2-14Performance Monitor.......................................................................................2-15ShadowImage for Mainframe...........................................................................2-15TrueCopy for Mainframe..................................................................................2-15Universal Replicator for Mainframe...................................................................2-16Universal Volume Manager.............................................................................. 2-18Virtual LVI......................................................................................................2-19Virtual Partition Manager.................................................................................2-20Volume Shredder............................................................................................2-20

3 Configuring custom-sized provisioning....................................................3-1Virtual LVI functions................................................................................................3-3Virtual LVI requirements..........................................................................................3-3Virtual LVI specifications..........................................................................................3-3

Virtual LVI specifications for mainframe systems.................................................3-3CV capacity by emulation type for mainframe systems........................................ 3-4

SSID requirements .................................................................................................3-5Virtual LVI size calculations......................................................................................3-6

Calculating the size of a 3390-A volume............................................................. 3-6Calculating the size of a 3390-V volume............................................................. 3-7Calculating the size of a 3390-X volume............................................................. 3-7Calculating the size of a 3390-XA, 3390-XB, 3390-XC volume...............................3-8Management area capacity of a mainframe volume.............................................3-8

ivHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Boundary values for RAID levels........................................................................ 3-9Capacity of a slot..............................................................................................3-9Configuring volumes in a parity group ...............................................................3-9

Create LDEV function............................................................................................ 3-10Creating an LDEV............................................................................................3-10Finding an LDEV ID.........................................................................................3-14Finding an LDEV SSID ....................................................................................3-14Editing an LDEV SSID .....................................................................................3-14Changing LDEV settings.................................................................................. 3-15Removing an LDEV to be registered................................................................. 3-15

Blocking LDEVs..................................................................................................... 3-16Blocking LDEVs in a parity group............................................................................3-16Restoring blocked LDEVs....................................................................................... 3-17Restoring blocked LDEVs in a parity group.............................................................. 3-17Editing an LDEV name...........................................................................................3-18Deleting an LDEV (converting to free space)........................................................... 3-18Formatting LDEVs................................................................................................. 3-19

About formatting LDEVs.................................................................................. 3-19Storage system operation when LDEVs are formatted........................................3-20Quick Format function.....................................................................................3-20

Quick Format specifications....................................................................3-21Write to Control Blocks function.......................................................................3-22Formatting a specific LDEV.............................................................................. 3-23Formatting all LDEVs in a parity group..............................................................3-23

Making external mainframe system volumes usable.................................................3-24Registering external volumes...........................................................................3-24Overwriting control blocks in specific external volumes...................................... 3-25

Assigning an MP blade ..........................................................................................3-26Assigning an MP blade to a resource................................................................ 3-26Changing the MP blade assigned to an LDEV.................................................... 3-26

4 Configuring thin provisioning ................................................................ 4-1Dynamic Provisioning for Mainframe overview...........................................................4-3Dynamic Tiering for Mainframe overview.................................................................. 4-3Thin provisioning requirements................................................................................ 4-3

License requirements........................................................................................4-3Pool requirements............................................................................................ 4-4Pool-VOL requirements..................................................................................... 4-5DP-VOL requirements....................................................................................... 4-7Requirements for increasing DP-VOL capacity.....................................................4-7

Using Dynamic Provisioning for Mainframe or Dynamic Tiering for Mainframe with other VSP G1000 products.................................................................................... 4-8

Interoperability of DP-VOLs and pool-VOLs.........................................................4-8TrueCopy for Mainframe..................................................................................4-11Universal Replicator for Mainframe...................................................................4-12ShadowImage for Mainframe...........................................................................4-13Virtual Partition Manager CLPR setting..............................................................4-14Volume Migration............................................................................................4-14Resource Partition Manager.............................................................................4-14

Dynamic Provisioning for Mainframe workflow.........................................................4-14Dynamic Tiering for Mainframe.............................................................................. 4-15

About tiered storage....................................................................................... 4-15

vHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Tier monitoring and data relocation..................................................................4-16Multi-tier pool.................................................................................................4-16Tier monitoring and relocation cycles............................................................... 4-17Tier relocation flow......................................................................................... 4-22Tier relocation rules, restrictions, and guidelines............................................... 4-25Conditions for the discontinuance of performance monitoring or tier relocation... 4-26Buffer area of a tier........................................................................................ 4-29Setting external volumes for each tier.............................................................. 4-30Execution modes for tier relocation.................................................................. 4-31

Execution modes when using Hitachi Device Manager - Storage Navigator.4-31Execution modes when using Command Control Interface........................4-34

Relocation speed............................................................................................ 4-36Monitoring modes........................................................................................... 4-36

Cautions when using monitoring modes.................................................. 4-37Downloading the tier relocation log file.............................................................4-38

Tier relocation log file contents...............................................................4-38Tiering policy..................................................................................................4-43

Tiering policy expansion.........................................................................4-43Tiering policy examples..........................................................................4-44Setting tiering policy on a DP-VOL.......................................................... 4-45Tiering policy levels............................................................................... 4-46Viewing the tiering policy in the performance graph.................................4-47Reserving tier capacity when setting a tiering policy.................................4-48Example of reserving tier capacity.......................................................... 4-49Notes on tiering policy settings...............................................................4-51Execution mode settings and tiering policy.............................................. 4-52New page assignment tier......................................................................4-54Relocation priority................................................................................. 4-56Assignment tier when pool-VOLs are deleted...........................................4-57Formatted pool capacity.........................................................................4-58Rebalancing the usage level among parity groups....................................4-58Changing the tiering policy level on a DP-VOL......................................... 4-59

Changing new page assignment tier of a V-VOL................................................ 4-59Opening the Edit Tiering Policies window..........................................................4-60Changing a tiering policy................................................................................. 4-60

To change the tiering policy................................................................... 4-60Changing relocation priority setting of a V-VOL................................................. 4-61Dynamic Tiering for Mainframe workflow..........................................................4-62Dynamic Tiering for Mainframe tasks and parameters........................................4-64

Task and parameter settings.................................................................. 4-64Display items: Setting parameters.......................................................... 4-66Display items: Capacity usage for each tier..............................................4-67Display items: Performance monitor statistics.......................................... 4-67Display items: Operation status of performance monitor/relocation........... 4-67

Managing Dynamic Tiering for Mainframe.........................................................4-68Changing pool for Dynamic Provisioning for Mainframe to pool for Dynamic Tiering for Mainframe............................................................ 4-68Changing monitoring and tier relocation settings......................................4-69Changing monitoring mode setting......................................................... 4-70Changing relocation speed..................................................................... 4-71Changing buffer space for new page assignment setting.......................... 4-71Changing buffer space for tier relocation setting...................................... 4-72

viHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Changing a pool for Dynamic Tiering for Mainframe to a pool for Dynamic Provisioning for Mainframe.................................................................... 4-72Working with pools............................................................................................... 4-73

About pools....................................................................................................4-73About pool-VOLs.............................................................................................4-74Creating pools................................................................................................ 4-74

Working with DP-VOLs.......................................................................................... 4-85About DP-VOLs...............................................................................................4-85Relationship between a pool and DP-VOLs........................................................4-85Creating V-VOLs............................................................................................. 4-85Editing a DP-VOL's SSID..................................................................................4-88Changing DP-VOL settings...............................................................................4-89Removing the DP-VOL to be registered.............................................................4-89

Monitoring capacity and performance..................................................................... 4-90Monitoring pool capacity..................................................................................4-90Monitoring performance.................................................................................. 4-90

Managing I/O usage rates example.........................................................4-91Tuning with Dynamic Tiering for Mainframe......................................................4-91

Thresholds........................................................................................................... 4-92Pool utilization thresholds................................................................................4-92Pool subscription limit..................................................................................... 4-93Changing pool thresholds................................................................................ 4-94Changing the pool subscription limit.................................................................4-94

Working with SIMs................................................................................................4-95About SIMs.................................................................................................... 4-95SIM reference codes....................................................................................... 4-95Automatic completion of a SIM ....................................................................... 4-96

Manually completing a SIM.................................................................................... 4-96Managing pools and DP-VOLs................................................................................ 4-97

Viewing pool information.................................................................................4-97Viewing used pool capacity..............................................................................4-98

Viewing the used capacity for each pool..................................................4-98Viewing formatted pool capacity...................................................................... 4-99Viewing the progress of rebalancing the usage level among parity groups ........4-100Increasing pool capacity................................................................................ 4-100Changing a pool name...................................................................................4-102Recovering a blocked pool............................................................................. 4-102Decrease pool capacity..................................................................................4-103

About decreasing pool capacity.............................................................4-103Decreasing pool capacity......................................................................4-105Stopping the decrease of pool capacity................................................. 4-105

Deleting a tier in a pool................................................................................. 4-105Deleting a pool............................................................................................. 4-106Changing external LDEV tier rank...................................................................4-107Increasing DP-VOL capacity........................................................................... 4-108Changing the name of a DP-VOL....................................................................4-108About releasing pages in a DP-VOL................................................................ 4-109

Releasing pages in a DP-VOL................................................................4-110Stopping the release of pages in a DP-VOL............................................4-111

Enabling/disabling tier relocation of a DP-VOL.................................................4-112Deleting a DP-VOL........................................................................................ 4-112

Starting pool monitoring manually........................................................................ 4-113

viiHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Stopping pool monitoring manually.......................................................................4-113Starting tier relocation manually...........................................................................4-114Stopping tier relocation manually..........................................................................4-114

5 Configuring access attributes.................................................................5-1Access attributes strategies..................................................................................... 5-2Volume Retention Manager requirements................................................................. 5-2Access attribute restrictions..................................................................................... 5-2Keywords............................................................................................................... 5-3Assigning access attribute....................................................................................... 5-4

Supported volume emulation types.................................................................... 5-4Setting Access Attributes...................................................................................5-4

Specifying the VTOC size.........................................................................................5-6

6 Troubleshooting....................................................................................6-1Troubleshooting Virtual LVI..................................................................................... 6-2Troubleshooting Dynamic Provisioning for Mainframe................................................ 6-2Troubleshooting provisioning while using Command Control Interface........................ 6-7

Errors when operating CCI (Dynamic Provisioning for Mainframe, SSB1:0x2e31/0xb96d) .............................................................................................. 6-7

Troubleshooting Volume Retention Manager............................................................. 6-9Calling the Hitachi Data Systems Support Center.......................................................6-9

A CCI command reference....................................................................... A-1Hitachi Device Manager - Storage Navigator tasks and CCI command list....................A-2

B Resource Partition Manager GUI reference............................................. B-1Resource Group window..........................................................................................B-2Selected resource group window..............................................................................B-3Create Resource Groups wizard............................................................................... B-9

Create Resource Groups window....................................................................... B-9Select Parity Groups window........................................................................... B-12Select LDEVs window......................................................................................B-14Select Ports window........................................................................................B-17Select Host Groups window............................................................................. B-19Create Resource Groups Confirm window......................................................... B-21

Edit Resource Group wizard...................................................................................B-23Edit Resource Group window...........................................................................B-23Edit Resource Group Confirm window...............................................................B-23

Add Resources wizard........................................................................................... B-25Add Resources window................................................................................... B-25Add Resources Confirm window.......................................................................B-25

Remove Resources window................................................................................... B-28Delete Resource Groups window............................................................................B-30Resource Group Properties window........................................................................ B-31

C Volume Retention Manager GUI reference..............................................C-1Volume Retention Manager window......................................................................... C-2VTOC Area dialog box............................................................................................. C-3

viiiHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Error Detail Dialog Box............................................................................................C-4

D LDEV GUI reference.............................................................................D-1Parity Groups window.............................................................................................D-3Parity Groups tab: Internal or external volume......................................................... D-5LDEVs tab: Internal or external volumes.................................................................. D-8Logical Devices window.........................................................................................D-11Create LDEVs wizard.............................................................................................D-16

Create LDEVs window.....................................................................................D-16Create LDEVs Confirm window........................................................................ D-23

Edit LDEVs wizard.................................................................................................D-25Edit LDEVs window.........................................................................................D-25Edit LDEVs Confirm window............................................................................ D-26

Change LDEV Settings window.............................................................................. D-28View SSIDs window.............................................................................................. D-29Select Free Spaces window................................................................................... D-30Select Pool window...............................................................................................D-31View LDEV IDs window......................................................................................... D-32

Emulation groups and types............................................................................D-33View Physical Location window..............................................................................D-34Edit SSIDs window................................................................................................D-35Change SSIDs window.......................................................................................... D-36Format LDEVs wizard............................................................................................D-37

Format LDEVs window....................................................................................D-38Format LDEVs Confirm window........................................................................D-38

Restore LDEVs window......................................................................................... D-40Block LDEVs window.............................................................................................D-41Delete LDEVs window........................................................................................... D-41LDEV Properties window....................................................................................... D-42Components window.............................................................................................D-51DKC: MP Blades tab..............................................................................................D-52Edit MP Blades wizard...........................................................................................D-54

Edit MP Blades window................................................................................... D-54Edit MP Blades Confirm window.......................................................................D-55

Assign MP Blade wizard.........................................................................................D-55Assign MP Blade window.................................................................................D-55Assign MP Blade Confirm window.................................................................... D-56

View Management Resource Usage window............................................................D-57

E Dynamic Provisioning for Mainframe and Dynamic Tiering for Mainframe GUIreference.............................................................................................E-1Pools window......................................................................................................... E-3Pools: Volume tabs................................................................................................. E-9Create Pools wizard...............................................................................................E-19

Create Pools window.......................................................................................E-19Create Pools Confirm window.......................................................................... E-27

Expand Pool wizard...............................................................................................E-30Expand Pool window.......................................................................................E-30Expand Pool Confirm window...........................................................................E-31

Edit Pools wizard...................................................................................................E-33Edit Pools window...........................................................................................E-33

ixHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Edit Pools Confirm window.............................................................................. E-36Delete Pools wizard...............................................................................................E-40

Delete Pools window.......................................................................................E-40Delete Pools Confirm window.......................................................................... E-41

Expand V-VOLs wizard.......................................................................................... E-42Expand V-VOLs window...................................................................................E-42Expand V-VOLs Confirm window...................................................................... E-43

Restore Pools window........................................................................................... E-45Shrink Pool window...............................................................................................E-46Stop Shrinking Pools window................................................................................. E-47Complete SIMs window......................................................................................... E-48Select Pool VOLs window.......................................................................................E-49Reclaim Zero Pages window...................................................................................E-53Stop Reclaiming Zero Pages window.......................................................................E-54Pool Property window............................................................................................E-54View Tier Properties window..................................................................................E-56Monitor Pools window........................................................................................... E-64Stop Monitoring Pools window............................................................................... E-65Start Tier Relocation window................................................................................. E-66Stop Tier Relocation window..................................................................................E-67View Pool Management Status window...................................................................E-68Edit External LDEV Tier Rank wizard.......................................................................E-73

Edit External LDEV Tier Rank window...............................................................E-73Edit External LDEV Tier Rank Confirm window.................................................. E-74

Edit Tiering Policies wizard.....................................................................................E-75Edit Tiering Policies window.............................................................................E-75Edit Tiering Policies Confirm window................................................................ E-76

Change Tiering Policy Window............................................................................... E-77Change Pool Configuration Pattern Window............................................................ E-78

Glossary

Index

xHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Preface

This document describes and provides instructions for using the provisioningsoftware to configure and perform operations on Hitachi Virtual StoragePlatform G1000 systems. Provisioning software includes Hitachi DynamicProvisioning for Mainframe, Dynamic Tiering for Mainframe software, andHitachi Virtual LVI.

Please read this document carefully to understand how to use these products,and maintain a copy for your reference.

□ Intended audience

□ Product version

□ Release notes

□ Document revision level

□ Changes made in this revision

□ Referenced documents

□ Document conventions

□ Convention for storage capacity values

□ Accessing product documentation

□ Getting help

□ Comments

Preface xiHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Intended audienceThis document is intended for system administrators, Hitachi Data Systemsrepresentatives, and authorized service providers who install, configure, andoperate Hitachi Virtual Storage Platform G1000 storage systems.

Readers of this document should be familiar with the following:

• Data processing and RAID storage systems and their basic functions.• The Hitachi Virtual Storage Platform G1000 storage system and the

Hitachi Virtual Storage Platform G1000 Product Overview.• The Hitachi Command Suite software and Hitachi Device Manager -

Storage Navigator and the Hitachi Command Suite User Guide or theHitachi Virtual Storage Platform G1000 Mainframe System AdministratorGuide.

• The concepts and functionality of storage provisioning operations in theuse of Hitachi Dynamic Provisioning for Mainframe, Dynamic Tiering forMainframe software, and Hitachi Virtual LVI.

Product versionThis document revision applies to VSP G1000 microcode 80-02-0x or later.

Release notesThe Hitachi Virtual Storage Platform G1000 Release Notes are available onthe Hitachi Data Systems Portal: https://portal.hds.com. Read the releasenotes before installing and using this product. They may containrequirements or restrictions that are not fully described in this document orupdates or corrections to this document.

Document revision levelRevision Date Description

MK-92RD8013-00 April 2014 Initial release

MK-92RD8013-01 August 2014 Supersedes and replaces MK-92RD8013-00

MK-92RD8013-02 October 2014 Supersedes and replaces MK-92RD8013-01

Changes made in this revision• Added information on assigning CLPRs. See Virtual Partition Manager

CLPR setting on page 4-14.

• Added procedures for viewing pool capacity. See Viewing used poolcapacity on page 4-98.

xii PrefaceHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems


• Added cautions. See Setting Access Attributes on page 5-4 andTroubleshooting Volume Retention Manager on page 6-9.

• Changed topic title. See Conditions for the discontinuance of performancemonitoring or tier relocation on page 4-26.

• Updates made to the Component window. See Components window onpage D-51.

• Added information about Hitachi Tiered Storage Manager for Mainframe.See Dynamic Tiering for Mainframe on page 1-9 and Dynamic Tiering forMainframe tasks and parameters on page 4-64.

• Added the note about the tier relocation log file). See Tier relocation logfile contents on page 4-38.

Referenced documentsHitachi Virtual Storage Platform G1000 documents:

• Hitachi Virtual Storage Platform G1000 Product Overview, MK-92RD8051• Hitachi Command Suite User Guide, MK-90HC172• Hitachi Virtual Storage Platform G1000 Hardware Guide, MK-92RD8007• Hitachi Compatible FlashCopy® User Guide, MK-92RD8010• Hitachi Virtual Storage Platform G1000 Performance Guide, MK-92RD8012• Hitachi SNMP Agent User Guide, MK-92RD8015• Hitachi Virtual Storage Platform G1000 Mainframe System Administrator

Guide, MK-92RD8016• Hitachi TrueCopy® for Mainframe User Guide, MK-92RD8018• Hitachi ShadowImage® for Mainframe User Guide, MK-92RD8020• Hitachi Universal Replicator for Mainframe User Guide, MK-92RD8022• Hitachi Universal Volume Manager User Guide, MK-92RD8024• Hitachi Volume Shredder User Guide, MK-92RD8025• Hitachi Compatible PAV User Guide, MK-92RD8026

For a list of all documents for the Hitachi Virtual Storage Platform G1000storage system, see the Hitachi Virtual Storage Platform G1000 ProductOverview.

Document conventionsThis document uses the following terminology conventions:

Convention Description

Hitachi VirtualStorage PlatformG1000

Unless otherwise noted, these terms refer to all models of theVSP G1000 storage system.

Preface xiiiHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

This document uses the following typographic conventions:

Convention Description

Regular text bold In text: keyboard key, parameter name, property name,hardware label, hardware button, hardware switchIn a procedure: user interface item

Italic Variable, emphasis, reference to document title, called-out term

Screen text Command name and option, drive name, file name, folder name,directory name, code, file content, system and applicationoutput, user input

< > (angle brackets) Variable (used when italic is not enough to identify variable)

[ ] (square brackets) Optional value

{ } (braces) Required or expected value

| (vertical bar) Choice between two or more options or arguments

This document uses the following icons to draw attention to information:

Icon Meaning Description

Tip Provides helpful information, guidelines, or suggestions forperforming tasks more effectively.

Note Provides information that is essential to the completion of atask.

Caution Warns that failure to take or avoid a specified action canresult in adverse conditions or consequences (for example,loss of access to data).

WARNING Warns the user of severe conditions, consequences, or both(for example, destructive operations).

Convention for storage capacity valuesPhysical storage capacity values (for example, disk drive capacity) arecalculated based on the following values:

Physical capacity unit Value

1 kilobyte (KB) 1,000 (103) bytes

1 megabyte (MB) 1,000 KB or 1,0002 bytes

1 gigabyte (GB) 1,000 MB or 1,0003 bytes

1 terabyte (TB) 1,000 GB or 1,0004 bytes

1 petabyte (PB) 1,000 TB or 1,0005 bytes

xiv PrefaceHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Physical capacity unit Value

1 exabyte (EB) 1,000 PB or 1,0006 bytes

Logical storage capacity values (for example, logical device capacity) arecalculated based on the following values:

Logical capacity unit Value

1 KB 1,024 (210) bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

1 block 512 bytes

1 Cyl For open systems:• OPEN-V: 960 KB• Other than OPEN-V: 720 KBFor mainframe systems: 870 KB

Accessing product documentationThe Hitachi Virtual Storage Platform G1000 user documentation is availableon the Hitachi Data Systems Portal: https://portal.hds.com. Check thissite for the most current documentation, including important updates thatmay have been made after the release of the product.

Getting helpThe Hitachi Data Systems customer support staff is available 24 hours a day,seven days a week. If you need technical support, log on to the Hitachi DataSystems Portal for contact information: https://portal.hds.com

CommentsPlease send us your comments on this document: [email protected] the document title, number, and revision, including the revision level(for example, -07), and refer to specific sections and paragraphs wheneverpossible. All comments become the property of Hitachi Data SystemsCorporation.

Thank you!

Preface xvHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems



mailto:[email protected]

xvi PrefaceHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

1Introduction to provisioning

Provisioning a storage system requires balancing the costs of the solutionwith the benefits that the solution provides. The following is an overview ofprovisioning strategies that you can implement on the Hitachi Virtual StoragePlatform G1000 to support your business.

□ About provisioning

□ Basic provisioning

□ Fixed-sized provisioning

□ Disadvantages

□ When to use fixed-sized provisioning

□ Custom-sized provisioning

□ When to use custom-sized provisioning

□ Basic provisioning workflow

□ Dynamic Provisioning Overview

□ Dynamic Provisioning for Mainframe

□ Dynamic Provisioning for Mainframe concepts

□ When to use Dynamic Provisioning for Mainframe

□ Dynamic Provisioning for Mainframe advantages

Introduction to provisioning 1-1Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

□ Dynamic Provisioning for Mainframe advantage example

□ Dynamic Provisioning for Mainframe workflow

□ Dynamic Tiering for Mainframe

□ Tiers concept

□ When to use Dynamic Tiering for Mainframe

□ Resource groups strategies

□ Complimentary strategies

□ Key terms

□ Before you begin

□ About cache management devices

1-2 Introduction to provisioningHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

About provisioningProvisioning is a method of managing storage system devices or volumes.Some provisioning methods are host-based, while others use existing storagesystem capabilities such as concatenated array groups. Some provisioningmethods are hardware-based, and others are software-based. Each techniquehas its particular use and benefit, for example, capacity, reliability,performance, or cost considerations, in a given storage environment. Used inthe wrong scenario, each can be expensive, awkward, time consuming toconfigure and maintain, and can be potentially error prone. Your supportrepresentatives are available to help you configure the highest qualitysolution for your storage environment.

Provisioning strategies falls into two fundamental categories:

• Basic provisioning on page 1-3 (or traditional provisioning).• Dynamic Provisioning Overview on page 1-5 (or virtual provisioning).

Thin provisioning includes pooling physical storage and creating logicaldevices for hosts.

Basic provisioningSeveral basic provisioning techniques traditionally are used to managestorage volumes. These strategies are useful in specific scenarios based onuser needs, such as whether you use open or mainframe storage systems, oryou prefer manual or automated control of your storage resources.

Basic provisioning relies on carving up physical storage into smaller units.Custom sizing is possible, and requires using Virtual LVI software.

Basic provisioning includes:

• Fixed-sized provisioning on page 1-3• Custom-sized provisioning on page 1-4

Fixed-sized provisioningFixed-sized provisioning is the logical choice for mainframe systems that needto be compatible with IBM systems. It is easy to define the storage system,then get on with your business. Later, you can attach additional storage asthe initial volumes fill up.

Fixed-sized provisioning is a good choice for mainframe systems.

DisadvantagesSome disadvantages to using fixed-sized provisioning are:

• If you use only part of the entire capacity specified by an emulation type,the rest of the capacity is wasted.


• After creating fixed-sized volumes, typically some physical capacity will bewasted due to being less than the fixed-size capacity.

• In a fixed-sized environment, manual intervention can become a costlyand tedious exercise when a larger volume size is required.

When to use fixed-sized provisioningFixed-sized provisioning is a best fit in the following scenarios:

• In a mainframe environment in which the simplest form of provisioningcan be utilized at the expense of some efficiency in capacity utilization.

Custom-sized provisioningCustom-sized (or variable-sized) provisioning has more flexibility than fixed-sized provisioning and is the traditional storage-based volume managementstrategy typically used to organize storage space.

To create custom-sized volumes on a storage system, an administratorcreates volumes of the desired size from individual array groups. Thesevolumes are then individually mapped to one or more host ports as a logicalunit.

Following are three scenarios where custom-sized provisioning is anadvantage:

• In fixed-sized provisioning, when several frequently accessed files arelocated on the same volume and one file is being accessed, users cannotaccess the other files because of logical device contention. If the custom-sized feature is used to divide the volume into several smaller volumesand I/O workload is balanced (each file is allocated to different volumes),then access contention is reduced and access performance is improved.

• In fixed-sized provisioning, not all of the capacity may be used. Unusedcapacity on the volume will remain inaccessible to other users. If thecustom-sized feature is used, smaller volumes can be created that do notwaste capacity.

• Applications that require the capacity of many fixed-sized volumes caninstead be given fewer large volumes to relieve device addressingconstraints.

Depending on how the data was copied (for example using software such asTDMF, or internal capability such as FlashCopy) the old device may need tobe varied offline and the new device varied online. This assumes that thesource and target devices are already generated into the mainframe IOconfiguration.

A disadvantage is that this manual intervention can become costly andtedious and this provisioning strategy is appropriate only in certain scenarios.


When to use custom-sized provisioningUse custom-sized provisioning when you want to manually control andmonitor your storage resources and usage scenarios.

Basic provisioning workflowThe following illustrates the basic provisioning workflow:

Virtual LVI software is used to configure custom-sized provisioning. Fordetailed information, see Chapter 3, Configuring custom-sized provisioning onpage 3-1.

Dynamic Provisioning OverviewThin provisioning is an approach to managing storage that maximizesphysical storage capacity. Instead of reserving a fixed amount of storage fora volume, it simply assigns capacity from the available physical pool whendata is actually written to disk.

Thin provisioning includes:

• Dynamic Provisioning for Mainframe concepts on page 1-6

Dynamic Provisioning for MainframeThough basic or traditional provisioning strategies can be appropriate anduseful in specific scenarios, they can be expensive to set up, awkward andtime consuming to configure, difficult to monitor, and error prone whenmaintaining storage.

Although Dynamic Provisioning for Mainframe requires some additional steps,it is a simpler alternative to the traditional provisioning methods. It uses thinprovisioning technology that allows you to allocate virtual storage capacity


based on anticipated future capacity needs, using virtual volumes instead ofphysical disk capacity.

Overall storage use rates may improve because you can potentially providemore virtual capacity to applications while using fewer physical disks. It canprovide lower initial cost, greater efficiency, and storage managementfreedom for storage administrators. In this way, Dynamic Provisioning forMainframe software:

• Simplifies storage management• Provides balanced resources and more optimized performance by default

without inordinate manual intervention.• Maximizes physical disk usage• May reduce device address requirements over traditional provisioning by

providing larger volume sizes.

Dynamic Provisioning for Mainframe conceptsDynamic Provisioning for Mainframe is a volume management feature thatallows storage managers and System Administrators to efficiently plan andallocate storage to users or applications. It provides a platform for the arrayto dynamically manage data and physical capacity without frequent manualinvolvement.

Dynamic Provisioning for Mainframe provides three important capabilities:thin provisioning of storage, enhanced volume performance, and largervolume sizes.

Dynamic Provisioning for Mainframe is more efficient than traditionalprovisioning strategies. It is implemented by creating one or more DynamicProvisioning for Mainframe pools (DP pools) of physical storage space usingmultiple LDEVs. Then, you can establish virtual DP volumes (DP-VOLs) andconnect them to the individual DP pools. In this way, capacity to support datacan be randomly assigned on demand within the pool.

DP-VOLs are of a user-specified logical size without any correspondingphysical space. Actual physical space (in 38-MB pool page units) isautomatically assigned to a DP-VOL from the connected DP pool as thatvolume's logical space is written to over time. A new volume does not haveany pool pages assigned to it. The pages are loaned out from its connectedpool to that DP volume until the volume is reformatted or deleted. At thatpoint, all of that volume's assigned pages are returned to the pool's free pagelist. This handling of logical and physical capacity is called thin provisioning.In many cases, logical capacity will exceed physical capacity.

Dynamic Provisioning for Mainframe enhances volume performance. This isan automatic result of how DP-VOLs map capacity from individual DP pools. Apool is created using from one to 1024 LDEVs (pool volumes) of physicalspace. Each pool volume is sectioned into 38-MB pages. Each page isconsecutively laid down on a number of RAID stripes from one pool volume.The pool's 38-MB pool pages are assigned on demand to any of the DP-VOLsthat are connected to that pool. Other pages assigned over time to that DP-


VOL randomly originate from the next free page of some other pool volume inthe pool.

DP-VOLs are defined as 3390-A volumes that can be larger than traditionalvolumes. This volume type was created to reduce device addressrequirements.

Setting up a Dynamic Provisioning for Mainframe environment requires a fewextra steps. You still configure various array groups to a desired RAID leveland create one or more 3390-V volumes (LDEVs) on each of them (seeCreating an LDEV on page 3-10). Then set up a Dynamic Provisioning forMainframe environment by creating one or more DP pools of physical storagespace that are each a collection of some of these 3390-V LDEVs (DP poolvolumes). This pool structure supports creation of 3390-A DynamicProvisioning for Mainframe virtual volumes (DP-VOLs), where 38-MB pages ofdata are randomly assigned on demand.

For detailed information, see Chapter 4, Configuring thin provisioning on page4-1.

When to use Dynamic Provisioning for MainframeDynamic Provisioning for Mainframe is a best fit in a mainframe environmentin the following scenarios:

• Where the aggregation of storage pool capacity usage across manyvolumes provides the best opportunity for performance optimization.

• For stable environments and large consistently growing files or volumes.• Where device addressing constraints are a concern.

Dynamic Provisioning for Mainframe advantages

Advantages Without Dynamic Provisioningfor Mainframe

With Dynamic Provisioning forMainframe

Reduces initialcosts

You must purchase physical diskcapacity for expected future use.The unused capacity adds costs forboth the storage system andsoftware products.

You can logically allocate morecapacity than is physicallyinstalled. You can purchase lesscapacity, reducing initial costs andyou can add capacity later byexpanding the pool.

Reducesmanagementcosts

You must stop the storage systemto reconfigure it.

When physical capacity becomesinsufficient, you can add poolcapacity without serviceinterruption.

Reducesmanagementlabor andincreasesavailability ofstorage

As the expected physical diskcapacity is purchased, the unusedcapacity of the storage system alsoneeds to be managed on thestorage system and on licensedVSP G1000 products.

You can allocate volumes of up to262,668 cyl (223,257 GB)regardless of the physical diskcapacity. This improvesmanagement flexibility.


Advantages Without Dynamic Provisioningfor Mainframe

With Dynamic Provisioning forMainframe

volumes forreplication

VSP G1000 product licenses arebased on used capacity rather thanthe total defined capacity.

Increases theperformanceefficiency of thedata drive

Because physical disk capacity isinitially purchased and installed tomeet expected future needs,portions of the capacity may beunused. I/O loads may concentrateon just a subset of the storagewhich might decreaseperformance.

Effectively combines I/O patternsof many applications and evenlyspreads the I/O activity acrossavailable physical resources,preventing bottlenecks in paritygroup performance. Configuringthe volumes from multiple paritygroups improves parity groupperformance. This also increasesstorage use while reducing powerand pooling requirements (totalcost of ownership).

Dynamic Provisioning for Mainframe advantage exampleTo illustrate the merits of a Dynamic Provisioning for Mainframe environment,assume you have twelve 3390-V LDEVs from 12 RAID 1 (2D+2D) arraygroups assigned to a DP pool. All 48 disks contribute their IOPS andthroughput power to all 3390-A DP volumes assigned to that pool. Instead, ifmore random read IOPS horsepower is desired for a pool, then it can becreated with 3390-V 32 LDEVs from 32 RAID 5 (3D+1P) array groups, thusproviding 128 disks of IOPS power to that pool. Up to 1024 LDEVs may beassigned to a single pool, providing a considerable amount of I/O capability tojust a few DP volumes.

Dynamic Provisioning for Mainframe workflowThe following illustrates the Dynamic Provisioning for Mainframe workflow.


Dynamic Tiering for MainframeAfter using Dynamic Provisioning for Mainframe software to implement a thinprovisioning strategy, the array now has all the elements in place to offerautomatic self-optimizing storage tiers provided by Hitachi Dynamic Tieringsoftware (HDT). Using Dynamic Tiering for Mainframe, you can configure astorage system with multiple storage tiers using different kinds of datadrives, including SSD, SAS, and external volumes. This helps improve thespeed and cost of performance. Dynamic Tiering for Mainframe extends andimproves the functionality and value of Dynamic Provisioning for Mainframe.Both use pools of physical storage against which virtual disk capacity, or V-VOLs, is defined. Each thin provisioning pool can be configured to operateeither as a DP pool or a Dynamic Tiering for Mainframe pool.

Automated tiering of physical storage is the logical next step for thinprovisioned enterprise arrays. Automated tiering is the ability of the array todynamically monitor and relocate data on the optimum tier of storage. Itfocuses on data segments rather than entire volumes. The functionality isentirely within the array without any mandated host level involvement.Dynamic Tiering for Mainframe adds another layer to the thin provisionedenvironment.

Using Dynamic Tiering for Mainframe you can:

• Configure physical storage into tiers consisting of multiple kinds of datadrives, including SSD, and SAS. Although host volumes are conventionallyconfigured from a common pool, the pool is efficiently configured usingmultiple kinds of disk drives. Placing data that needs high performancewhile reducing storage costs by using high cost disks such as SSDs asefficiently as possible, resulting in data that is accessed infrequently beingplaced on lower cost physical storage.

• Automatically migrate small portions of host volumes to the most suitabledata drive according to access frequency. Frequently accessed data is


migrated to higher speed data drives (for example, SSD). Infrequentlyaccessed data is migrated to lower cost and lower speed data drives (forexample, SAS7.2K) to use the storage efficiently.

Dynamic Tiering for Mainframe simplifies storage administration byautomating and eliminating the complexities of efficiently using tieredstorage. It automatically moves data on pages in Dynamic Provisioning forMainframe V-VOLs to the most appropriate storage media, according toworkload, to maximize service levels and minimize total cost of storage.

Dynamic Tiering for Mainframe gives you:

• Improved storage resource usage• Improved return on costly storage tiers• Reduced storage management effort• More automation• Nondisruptive storage management• Reduced costs• Improved performance

Dynamic Tiering for Mainframe can be used by Storage Navigator, CommandControl Interface, or Hitachi Tiered Storage Manager for Mainframe (HTSM forMainframe).

If Storage Navigator or Command Control Interface is used, followingresources that are assigned to the storage administorator can be used:

• Tiers of pools• Tiers of DP-VOLs

If HTSM for Mainframe is used, following resources that are assigned to themainframe administorator can be used:

• Tiers of storage groups• Tiers of DP-VOLs that are assigned to a host

For details about Hitachi Tiered Storage Manager for Mainframe, see HitachiTiered Storage Manager for Mainframe User Guide.

Tiers conceptWhen not using Dynamic Tiering for Mainframe, data is allocated to only onekind of data drive (typically an expensive high-speed data drive) withoutregard to the workload to the volumes because the volumes are configuredwith only one kind of data drive. When using Dynamic Tiering for Mainframe,the higher speed data drive is automatically allocated to the volumes of highworkload, and the lower speed drive to the volumes of low workload. Thisimproves performance and reduces costs.

Dynamic Tiering for Mainframe places the host volume's data across multipletiers of storage contained in a pool. There can be up to three tiers (high-,medium-, and low-speed layers) in a pool. Dynamic Tiering for Mainframe


determines tier usage based on data access levels. It allocates the page withhigh I/O load to the upper tier, which contains a higher speed drive, and thepage with low I/O load to the lower tier, which contains a lower speed drive.

The following figure illustrates the basic tier concept.

When to use Dynamic Tiering for MainframeDynamic Tiering for Mainframe is the best fit in an environment in whichDynamic Provisioning for Mainframe is a good fit.

For detailed information, see Chapter 4, Configuring thin provisioning on page4-1.

Resource groups strategiesA storage system can connect to multiple hosts and be shared by multipledivisions in a company or by multiple companies. Many storageadministrators from different organizations can access the storage system.Managing the entire storage system can become complex and difficult.Potential problems are that private data might be accessed by other users, ora volume in one organization might be destroyed by mistake by a storageadministrator in another organization.

To avoid such problems, use Hitachi Resource Partition Manager software toset up resource groups that allow you to manage one storage system asmultiple virtual private storage systems. The storage administrator in eachresource group can access only their assigned resources and cannot accessother resources. Configuring resource groups prevents the risk of dataleakage or data destruction by another storage administrator in anotherresource group.

The resources such as LDEVs, parity groups, external volumes or ports can beassigned to a resource group. These resources can be combined to flexiblycompose a virtual private storage system.


Resource groups should be planned and created before creating volumes. Formore information, see Chapter 2, Configuring resource groups on page2-1.

Complimentary strategies

Functions related to provisioning

For the following functions, see the appropriate manuals:

• Replication: ShadowImage for Mainframe, TrueCopy for Mainframe,Universal Replicator for Mainframe, Compatible XRC, CompatibleFlashCopy® V2

• External storage: Universal Volume Manager• Partitioning: Virtual Partition Manager (Hitachi Virtual Storage Platform

G1000 Performance Guide)• TSE-VOL: Compatible Software for IBM® FlashCopy® SE

Note: For information on software that can perform operations on volumesthat connect with zLinux, contact the Hitachi Data Systems Support Center.

Key termsThe following are provisioning key terms:

Term Description

access attributes Security function used to control the access to a logical volume.Access attributes are assigned to each volume: read only, read/write, and protect.

CV (variable volume) Customized Volume. A fixed volume that is divided into arbitrarysizes.

DP pool A group of DP-VOL. The DP pool consists of one or more pool-VOLs.

DP-VOL Dynamic Provisioning for Mainframe virtual volume.

expiration lock Security option used to allow or not allow changing of the accessattribute on a volume.

FV Abbreviation for fixed-sized volume.

meta_resource A resource group in which additional resources (other thanexternal volumes) and the resources existing before installingResource Partition Manager belong.

page In Dynamic Provisioning for Mainframe, a page is 38 MB ofcontinuous storage in a DP-VOL that belongs to a DP-pool.

pool A set of volumes that are reserved for storing DynamicProvisioning for Mainframe write data.


Term Description

pool threshold In a thin provisioned storage system, the proportion (%) of usedcapacity of the pool to the total pool capacity. Each pool has itsown pool threshold values for warning and depletion.

pool-VOL, poolvolume

A volume that is reserved for write data for Dynamic Provisioningfor Mainframe.

resource group A group that is assigned one or more resources of the storagesystem. The resources that can be assigned to the resource groupare LDEV IDs, parity groups, external volumes, and ports.

subscriptionthreshold

In a thin provisioned storage system, the proportion (%) of totalDP-VOL capacity associated with the pool versus the totalcapacity.You can set the percentage of DP-VOL capacity that can becreated to the total capacity of the pool. This can help prevent DP-VOL blocking caused by a full pool.For example, when the subscription limit is set to 100%, the totalDP-VOL capacity that can be created is obtained using thisformula:total DP-VOL capacity <= pool capacity x 100%Using this setting protects the pool when doing the following:• Shrinking a pool• Creating DP-VOL• Increasing DP-VOL capacity

Before you beginBefore you begin provisioning your VSP G1000 storage system, certainrequirements must be met.

System requirements

• The VSP G1000 hardware, microcode, and Hitachi Device Manager -Storage Navigator essential for operating the storage system be installedand configured for use.

• A VSP G1000 storage system.• The storage system must have parity groups installed.• A Storage Navigator client computer.

Shared memory requirements

Caution:

• The required shared memory is installed by your Hitachi Data Systemsrepresentative.

• Before the shared memory is uninstalled, all Dynamic Provisioning forMainframe and Dynamic Tiering for Mainframe pools must be deleted.


If Dynamic Provisioning for Mainframe is used and the total capacity ofDynamic Provisioning for Mainframe, Dynamic Tiering for Mainframe and ThinImage pools is 1.0 PB or more, additional shared memory must be installed.When using Dynamic Provisioning for Mainframe, the following table showsthe required shared memory capacity and the additional shared memory tobe installed.

Total capacity of all pools Required shared memorycapacity

1.0 PB or less None

If the total capacity satisfies both of following:• More than 1.0 PB• 3.0 PB or less

8 GB


24 GB


40 GB

Tip: The V-VOL management area is automatically created when sharedmemory is added. This area is used to store information for associating pool-VOLs and DP-VOLs.

If Dynamic Tiering for Mainframe is used to correspond with DynamicProvisioning for Mainframe, Dynamic Tiering for Mainframe and Thin Imagepools, additional shared memory must be installed. When using DynamicTiering for Mainframe, the following table shows the required shared memorycapacity and the additional shared memory to be installed.

Total capacity of all pools Required shared memorycapacity

1.0 PB or less 8 GB


16 GB


32 GB


48 GB


About cache management devicesCache management devices are associated with volumes (LDEVs) and used tomanage caches. One volume (LDEV) requires at least one cache managementdevice. An entire system can manage up to 65,280 cache managementdevices. A DP-VOL may require more than one cache management device.This topic describes how to calculate the number of cache managementdevices.

Calculating the number of cache management devices required by aDP-VOL

The number of cache management devices that a DP-VOL requires dependson the capacity of the V-VOL (capacity of the user area) and the maximumcapacity of cache management device. The maximum capacity of cachemanagement device depends on the pool attribute (internal volume orexternal volume) associated with V-VOL. The following table explains therelationship between the pool attribute and the maximum capacity of cachemanagement device.

Maximum capacity of cache management device

Pool attributeMaximumcapacity(in MB)

Maximum capacity(in blocks)

Maximum capacity(in cylinders)

Internal volume 711,768.75(695.08 GB)

1,457,702,400 837,760

External volume 949,659.37(927.40 GB)

1,944,902,400 1,117,760

Use the following formula to calculate the number of cache managementdevices that a DP-VOL requires. In this formula, the user-specified capacity isthe user area capacity of a V-VOL.

ceil(user-specified capacity ÷ max-capacity-of-cache-management-device)

The calculated value must be rounded up to the nearest whole number.

Calculating the number of cache management devices required by avolume that is not a DP-VOL

One volume that is not a DP-VOL requires one cache management device.

Viewing the number of cache management devicesClick Actions and select View Management Resource Usage to displaythe number of cache management devices in the View Management ResourceUsage window. For details, see About cache management devices on page1-15 and View Management Resource Usage window on page D-57.



2Configuring resource groups

The Storage Administrator can divide a provisioned storage system intoresource groups that allow managing the storage system as multiple virtualprivate storage systems. Configuring resource groups involves creatingresource groups, moving storage system resources into the resource groups,and assigning resource groups to user groups.

Resource groups can be set up on both open and mainframe systems.Resource Partition Manager software is required.

□ System configuration using resource groups

□ Resource groups examples

□ Meta_resource

□ Resource lock

□ User groups

□ Resource group assignments

□ Resource group license requirements

□ Resource group rules, restrictions, and guidelines

□ Creating a resource group

□ Adding resources to a resource group

□ Removing resources from a resource group

□ Managing Resource Groups

Configuring resource groups 2-1Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

□ Using Resource Partition Manager and other VSP G1000 products

2-2 Configuring resource groupsHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

System configuration using resource groupsConfiguring resource groups prevents the risk of data leakage or datadestruction by another Storage Administrator in another resource group. TheStorage Administrator considers and plans which resource should bemanaged by which user, then the Security Administrator creates resourcegroups and assigns each resource to the resource groups.

A resource group is assigned one or more storage system resources. Thefollowing resources can be assigned to resource groups.

• LDEV IDs*• Parity groups• External volumes• Ports

* Before you create LDEVs, the LDEV IDs can be reserved and assigned to aresource group for future use.

The following tasks provide instructions for configuring resource groups.

• Creating a resource group on page 2-9• Adding resources to a resource group on page 2-10• Removing resources from a resource group on page 2-11• Changing the name of a resource group on page 2-11• Deleting a resource group on page 2-12

Resource groups examplesThe following examples illustrate how you can configure resource groups onyour storage system:

• Example of resource groups sharing a port on page 2-3• Example of resource groups not sharing ports on page 2-5

Example of resource groups sharing a portIf you have a limited number of ports, you can still operate a storage systemeffectively by sharing ports using resource groups.

The following example shows the system configuration of an in-house divisionproviding virtual private storage system for two divisions. Divisions A and Beach use their own assigned parity group, but share a port between the twodivisions. The shared port is managed by the system division.


The Security Administrator in the system division creates resource groups foreach division in the storage system and assigns them to the respectivedivisions. The Storage Administrator in Division A can manage the resourcegroups for Division A, but cannot access the resource groups for Division B.In the same manner, the Storage Administrator in Division B can manage theresource groups for Division B, but cannot access the resource groups forDivision A.

The Security Administrator creates a resource group for managing thecommon resources, and the Storage Administrator in the system divisionmanages the port that is shared between Divisions A and B. The StorageAdministrators in Divisions A and B cannot manage the shared port belongingto the resource group for common resources management.

Configuration workflow for resource groups sharing a port

1. The system division forms a plan about the resource group creation andassignment of the resources.

2. The Security Administrator creates resource groups.See Creating a resource group on page 2-9 for more information.

3. The Security Administrator creates user groups.


See the Hitachi Virtual Storage Platform G1000 Mainframe SystemAdministrator Guide for more information.

4. The Security Administrator assigns the resource groups to user groups.See the Hitachi Virtual Storage Platform G1000 Mainframe SystemAdministrator Guide for more information.

5. The Storage Administrator in the system division sets a port.6. The Security Administrator assigns resources to the resource groups.

See Adding resources to a resource group on page 2-10 for moreinformation.

7. The Security Administrator assigns each Storage Administrator to eachuser group.See the Hitachi Virtual Storage Platform G1000 Mainframe SystemAdministrator Guide for more information.

After the above procedures, the Storage Administrators in A and B divisionscan manage the resource groups assigned to their own division.

Example of resource groups not sharing portsIf you assign ports to each resource group without sharing, performance canbe maintained on a different port even if the bulk of I/O is issued from oneside port.

The following shows a system configuration example of an in-house systemdivision providing the virtual private storage system for two divisions.Divisions A and B each use individual assigned ports and parity groups. Inthis example, they do not share a port.


The Security Administrator in the system division creates resource groups foreach division in the storage system and assigns them to the respectivedivisions. The Storage Administrator in Division A can manage the resourcegroups for Division A, but cannot access the resource groups for Division B.In the same manner, the Storage Administrator in Division B can manage theresource groups for Division B, but cannot access the resource groups forDivision A.

Configuration workflow for resource groups not sharing a port

1. The system division forms a plan about creating resource groups and theassigning resources to the groups.

2. The Security Administrator creates resource groups.See Creating a resource group on page 2-9 for more information.

3. The Security Administrator creates user groups.See the Hitachi Virtual Storage Platform G1000 Mainframe SystemAdministrator Guide for more information.

4. The Security Administrator assigns the resource groups to user groups.See the Hitachi Virtual Storage Platform G1000 Mainframe SystemAdministrator Guide for more information.

5. The Storage Administrator in the system division sets ports.


6. The Security Administrator assigns resources to the resource groups.See Adding resources to a resource group on page 2-10 for moreinformation.

7. The Security Administrator assigns each Storage Administrator to eachuser group.See the Hitachi Virtual Storage Platform G1000 Mainframe SystemAdministrator Guide for more information.

After the above procedures, the Storage Administrators in A and B divisionscan access the resource groups allocated to their own division.

Meta_resourceThe meta_resource is a resource group comprised of additional resources(other than external volumes) and the resources that exist on the storagesystem before the Resource Partition Manager is installed. By default, existingresources initially belong to the meta_resource group to ensure compatibilitywith older software when a system is upgraded to include Resource PartitionManager.

Resource lockWhile processing a task on a resource, all of the resource groups assigned tothe logged-on user are locked for exclusive access.

A secondary window (such as the Basic Information Display) or an operationfrom the service processor (SVP) locks all of the resource groups in thestorage system.

When a resource is locked, a status indicator appears on the status bar. Clickthe Resource Locked button to view information about the locked resource.

User groupsUser groups and associated built-in roles are defined in the SVP. A userbelongs to one or more user groups. Privileges allowed to a particular userare determined by the user group or groups to which the user belongs.

The Security Administrator assigns resource groups to user groups. A usergroup may already be configured, or a new user group may be required forcertain resources.

See the Hitachi Virtual Storage Platform G1000 Mainframe SystemAdministrator Guide for more information.


Resource group assignmentsAll resource groups are normally assigned to the Security Administrator andthe Audit Log Administrator.

Each resource group has a designated Storage Administrator who can accessonly their assigned resources and cannot access other resources.

All resource groups to which all resources in the storage system belong canbe assigned to a user group. Configure this in Hitachi Device Manager -Storage Navigator by setting All Resource Groups Assigned to Yes.

A user who has All Resource Groups Assigned set to Yes can access allresources in the storage system. For example, if a user is a SecurityAdministrator (with View & Modify privileges) and a Storage Administrator(with View and Modify privileges) and All Resource Groups Assigned isYes on that user account, the user can edit the storage for all the resources.

If allowing this access becomes a problem with security on the storagesystem, then register the following two user accounts and use these differentaccounts for different purposes.

• A user account for a Security Administrator where All Resource GroupsAssigned is set to Yes.

• A user account for a Storage Administrator who does not have allresource groups assigned and has only some of the resource groupsassigned.

Resource group license requirementsUse of Resource Partition Manager on the VSP G1000 storage system requiresthe following:

• A license key for Resource Partition Manager software.For details about the license key or product installation, see HitachiVirtual Storage Platform G1000 Mainframe System Administrator Guide.

Resource group rules, restrictions, and guidelines

Rules

• The maximum number of resource groups that can be created on astorage system is 1023.

• A Storage Administrator with the Security Administrator (View & Modify)role can create resource groups and assign resources to resource groups.

• Resources removed from a resource group are returned tometa_resource.

• Only a Security Administrator (View & Modify) can manage the resourcesin assigned resource groups.


Restrictions

• No new resources can be added to meta_resource.• Resources cannot be deleted from meta_resource.• LDEVs that has the same pool IDs or the journal IDs cannot be added to

multiple resource groups.In the case of adding LDEVs that are used as pool volumes or journalvolumes, add all the LDEVs that have the same pool IDs or journal IDs byusing a function such as sort.

Guidelines

• If you are providing a virtual private storage system to differentcompanies, you should not share parity groups, external volumes, orpools if you want to limit the capacity that can be used by each user.When parity groups, external volumes, or pools are shared betweenmultiple users, and if one user uses too much capacity of the sharedresource, the other users might not be able to create an LDEV.

Creating a resource groupWhen creating a resource group, observe the following:

• The maximum number of resource groups that can be created on astorage system is 1023.

• The name meta_resource cannot be set for a resource group name.• Duplicate occurrences of the same name are not allowed.• Resource group name can use alphanumeric characters, spaces, and the

following symbols: ! # $ % & ' ( ) + - . = @ [ ] ^ _ ` { } ~• Characters in a resource group name are case-sensitive.• You must have Security Administrator (View & Modify) role to perform

this task.

To create a resource group:

1. In the Hitachi Device Manager - Storage Navigator main window, in theStorage Systems tree, click Administration, then Resource Groups.

2. Click Create Resource Groups in the Resource Groups tab.3. Enter a resource group name in the Create Resource Groups window.

Parity groups, LDEVs, ports, or host groups can be specified as follows:

a. Click Select resource-name. For example, click Select ParityGroups.

b. Select resources from the Available resource-name table.c. Click Add resource-name table.

The added resources move to the Selected resource-name table.Click Remove to move resources from the Selected to the Availableresource-name table if necessary.


d. Click OK.The Create Resource Groups window

4. Click Add.The resource group is added to Selected Resource Groups table.If you select a row and click Detail, the Resource Group Propertieswindow appears.If you select a row and click Remove, a message appears that asks if youwant to remove the selected row. If you want to remove the row, clickOK.

5. Click Finish.6. In the Confirm window, confirm the settings, in Task Name type a

unique name for this task or accept the default, then click Apply.If you select a row and click Detail, the Resource Group Propertieswindow appears.If Go to tasks window for status is checked, the Tasks window opens.

Adding resources to a resource groupBefore adding resources to a resource group, consider the following:

• You must have Security Administrator (View & Modify) role to performthis task.

• No resource can be added to meta_resource.• Only resources allocated to meta_resource can be added to resource

groups.• LDEVs with the same pool IDs or journal IDs cannot be added to multiple

resource groups. For example, when two LDEVs belong to the same pool,you must allocate both to the same resource group. You cannot allocatethem separately. Use the sort function to sort the LDEVs by pool ID orjournal ID, then select them and add them all at once.

• If virtual storage machine attributes differ between meta_resource andthe resource group:

¢ LDEVs cannot be added to the resource group when virtual LDEV IDsare assigned to LDEVs in meta_resource.

¢ LDEVs and host groups cannot be added to the resource group whenLUN paths are assigned to LDEVs and host groups in meta_resource.

To add resources to a resource group:


2. Click a resource group to add in the Resource Groups tab.3. Click Add Resources.4. Select the type of resources to add in the resource group.5. Select one or more resources to add to the resource group, then click

Add.


6. Click OK, then click Finish.7. In the Confirm window, confirm the settings, in Task Name type a

unique name for this task or accept the default, then click Apply.If Go to tasks window for status is checked, the Tasks window opens.

Removing resources from a resource groupBefore removing remove resources from a resource group, consider thefollowing:

• The resources removed from a resource group are returned tometa_resource.

• Resources cannot be deleted from the meta_resource.• LDEVs that has the same pool IDs or journal IDs cannot be partially

removed. For example, if two LDEVs belong to the same pool, you cannotremove only LDEV1 from the resource group and leave only LDEV2. Usethe sort function to sort the LDEVs by pool ID or journal ID, then selectthem and remove them all at once.

• If virtual storage machine attributes differ between meta_resource andthe resource group:

¢ LDEVs cannot be removed from the resource group when virtual LDEVIDs are assigned to LDEVs in meta_resource.

¢ LDEVs and host groups cannot be removed from the resource groupwhen LUN paths are assigned to LDEVs and host groups inmeta_resource.

• You must have Security Administrator (View & Modify) role to performthis task.

To remove resources from a resource group:


2. Click a resource group to remove in theResource Groups tab.3. Select one or more resources to remove from the resource group, then

click Remove Resources.4. In the Confirm window, confirm the settings, in Task Name type a


Managing Resource Groups

Changing the name of a resource groupWhen changing the name of a resource group, observe the following:

• The name meta_resource cannot be changed.


• Duplicate occurrences of the same name are not allowed.• The name of meta_resource cannot be set for a resource group name.• Resource group names can use alphanumeric characters, spaces, and the

following symbols: ! # $ % & ' ( ) + - . = @ [ ] ^ _ ` { } ~• Characters in a resource group name are case-sensitive.• You must have Security Administrator (View & Modify) role to perform

this task.

To change a resource group name:


2. Click a resource group to change its name in the Resource Groups tab.3. Click Edit Resource Group.4. In the Edit Resource Group window, type a new resource group name,

then click Finish.5. In the Confirm window, confirm the settings, in Task Name type a

unique name for this task or accept the default, then click Apply.If you select a row and click Detail, the Resource Group Propertieswindow appears.If Go to tasks window for status is checked, the Tasks window opens.

Deleting a resource groupThe Security Administrator (View & Modify) role is required to perform thistask.

You cannot delete the following:

• The meta_resource.• A resource group that is assigned to a user group.• A resource group that has resources assigned to it.• Resource groups included in different resource groups cannot be removed

at the same time.

To delete a resource group:


2. Click one or more resource groups to delete in the Resource Groupstab.

3. Click Delete Resource Groups.4. In the Confirm window, confirm the settings, in Task Name type a



Using Resource Partition Manager and other VSP G1000products

To use Resource Partition Manager with other VSP G1000 products, theresources that are required for the operation must satisfy specific conditions.The following topics provide information about the specific resourceconditions that are required for using each VSP G1000 product.

• Compatible PAV on page 2-13• Dynamic Provisioning for Mainframe and Dynamic Tiering for Mainframe

on page 2-13• Encryption License Key on page 2-14• Performance Monitor on page 2-15• ShadowImage for Mainframe on page 2-15• TrueCopy for Mainframe on page 2-15• Universal Replicator for Mainframe on page 2-16• Universal Volume Manager on page 2-18• Virtual LVI on page 2-19• Virtual Partition Manager on page 2-20• Volume Shredder on page 2-20

Compatible PAVThe following table provides information about specific Compatible PAVconditions that must be observed when using Resource Partition Manager.

Operation name Condition

Assign aliases The specified base volumes and free volumes must beassigned to the Storage Administrator group permitted tomanage them.

Remove aliases The specified base volumes and alias volumes must beassigned to the Storage Administrator group permitted tomanage them.

Dynamic Provisioning for Mainframe and Dynamic Tiering forMainframe

The following table provides information about specific Dynamic Provisioningfor Mainframe and Dynamic Tiering for Mainframe conditions that must beobserved when using Resource Partition Manager.


Create LDEVs If DP-VOLs are created, the following must be assigned to theStorage Administrator group that is permitted to managethem.• LDEV ID



• Pool VOL of the pool

Delete LDEVs If DP-VOLs are deleted, the following must be assigned to theStorage Administrator group that is permitted to managethem.• LDEV ID• Pool-VOL of the pool

Create poolsExpand pools

Volumes to be specified as pool-VOLs must be assigned to theStorage Administrator group permitted to manage them.All the volumes that are specified when creating a pool mustbelong to the same resource group.

Edit poolsDelete pools

Pool-VOLs of the specified pool must be assigned to theStorage Administrator group permitted to manage them.

Expand V-VOLs You can expand only the DP-VOLs that are assigned to theStorage Administrator group permitted to manage them.

Reclaim zero pagesStop reclaiming zeropages

You can reclaim or stop reclaiming zero pages only for theDP-VOLs that are assigned to the Storage Administratorgroup permitted to manage them.

Compatible Software for IBM® FlashCopy® SE


Create LDEVs If TSE-VOLs are created, LDEV IDs must be assigned to theStorage Administrator group that is permitted to managethem.

Expand V-VOLs You can expand only TSE-VOLs that are assigned to theStorage Administrator group permitted to manage them.

Encryption License KeyThe following table provides information about specific Encryption License Keyconditions that must be observed when using Resource Partition Manager.


Edit encryption keys When you specify a parity group and open the Edit Encryptionwindow, the specified parity group and LDEVs belonging tothe parity group must be assigned to the StorageAdministrator group permitted to manage them.When you open the Edit Encryption window without specifyinga parity group, more than one parity group and LDEVsbelonging to the parity group must be assigned to theStorage Administrator group permitted to manage them.


Performance MonitorThe following table provides information about specific Performance Monitorconditions that must be observed when using Resource Partition Manager.


Add to ports The specified ports must be assigned to the StorageAdministrator group permitted to manage them.

Add new monitoredWWNs

The specified ports must be assigned to the StorageAdministrator group permitted to manage them.

Edit WWNs The specified ports must be assigned to the StorageAdministrator group permitted to manage them.

ShadowImage for MainframeThe following table provides information about specific ShadowImage forMainframe conditions that must be observed when using Resource PartitionManager.


Create pairs Both primary volumes and secondary volumes must beassigned to the Storage Administrator group permitted tomanage them.

Split pairs Primary volumes must be assigned to the StorageAdministrator group permitted to manage them.

Suspend pairs

Resynchronize pairs

Release pairs

TrueCopy for MainframeThe following table provides information about specific TrueCopy forMainframe conditions that must be observed when using Resource PartitionManager.


Edit Ports Specified ports must be assigned to the user.

Add Remote Connection Specified initiator ports must be assigned to the user.

Edit Remote ConnectionOptions

Operation can be performed with no conditions.

Create Pairs Primary volumes must be assigned to the user.Initiator ports of remote paths that are connected with theprimary volume in the remote storage must be assigned tothe user.

Split Pairs Specified primary volumes or secondary volumes must beassigned to the user.



Resync Pairs Primary volumes must be assigned to the user.

Delete Pairs Specified volumes must be assigned to the user.If primary volumes are specified, the initiator ports of remotepaths that are connected with the primary volume in theremote storage must be assigned to the user.

Edit Pair Options Primary volumes must be assigned to the user.

Add Remote Paths Specified initiator ports must be assigned to the user.

Remove Remote Paths Specified initiator ports must be assigned to the user.


Initiator ports of remote paths that are connected to aspecified remote storage must be assigned to the user.

Add SSIDs SSID Initiator ports of remote paths that are connected to aspecified remote storage must be assigned to the user.

Remove SSIDs Initiator ports of remote paths that are connected to aspecified remote storage must be assigned to the user.

Remove RemoteConnections


Force Delete Pairs Specified primary volumes or secondary volumes must beassigned to the user.

Universal Replicator for MainframeThe following table provides information about specific Universal Replicatorfor Mainframe conditions that must be observed when using ResourcePartition Manager.


Edit Ports Specified ports must be assigned to the user.

Add Remote Connection Specified initiator ports must be assigned to the user.

Add Remote Paths Specified initiator ports must be assigned to the user.

Create Journals All LDEVs that are specified when creating a journal mustbelong to the same resource group. Volumes to be assignedto a journal must be assigned to the user.

Assign Journal Volumes Volumes to be assigned to a journal must be assigned to theuser. All volumes to be assigned to a journal must belong to asame resource group to which the existing journal volumesbelong.

Assign MP Blade Journal volumes must be assigned to the user.


Operation can be performed with no conditions.

Create Pairs Journal volumes for pair volumes and primary volumes mustbe assigned to the user.



Initiator ports of remote paths that are connected with theprimary volume in the remote storage must be assigned tothe user.

Split Pairs Specified primary volumes or secondary volumes must beassigned to the user.

Split Mirrors All data volumes configured to a mirror must be assigned tothe user.

Resync Pairs Primary volumes must be assigned to the user.

Resync Mirrors All data volumes configured to a mirror must be assigned tothe user.

Delete Pairs Specified volumes or secondary volume must be assigned tothe user.Initiator ports of remote paths that are connected with theprimary volume in the remote storage must be assigned tothe user.

Delete Mirrors All data volumes configured to a mirror must be assigned tothe user.

Edit Pair Options Primary volumes must be assigned to the user.

Force Delete Pairs Specified volumes must be assigned to the user.

Edit Journal Options All data volumes consisting of the specified journal must beassigned to the user.Journal volumes must be assigned to the user.

Edit Mirror Options All data volumes configuring the specified journal must beassigned to the user.Journal volumes must be assigned to the user.

Remove Journals Journal volumes must be assigned to the user.



Remove Remote Paths Specified initiator ports must be assigned to the user.

Move LDEVs to otherresource groups

When you move LDEVs used for journal volumes to otherresource groups, you must specify all the journal volumes ofthe journal to which the LDEVs belong.

Assign Remote CommandDevices

Journal volumes must be assigned to the user.Specified remote command devices must be assigned to theuser.

Release RemoteCommand Devices

Journal volumes must be assigned to the user.Specified remote command devices must be assigned to theuser.


Universal Volume ManagerThe following table provides information about specific Universal VolumeManager conditions that must be observed when using Resource PartitionManager.


Add external volumes When creating an external volume, a volume is created in theresource group where the external port belongs.When you specify a path group and open the Add ExternalVolumes window, all the ports that compose the path groupmust be assigned to the Storage Administrator grouppermitted to manage them.

Delete external volumes The specified external volume and all the LDEVs allocated tothat external volume must be assigned to the StorageAdministrator group permitted to manage them.

Disconnect externalstorage systems

All the external volumes belonging to the specified externalstorage system and all the LDEVs allocated to that externalvolumes must be assigned to the Storage Administratorgroup permitted to manage them.

Reconnect externalstorage systems

All the external volumes belonging to the specified externalstorage system and all the LDEVs allocated to that externalvolumes must be assigned to the Storage Administratorgroup permitted to manage them.

Disconnect externalvolumes

The specified external volume and all the LDEVs allocated tothe external volumes must be assigned to the StorageAdministrator group permitted to manage them.

Reconnect externalvolumes

The specified external volume and all the LDEVs allocated tothe external volumes must be assigned to the StorageAdministrator group permitted to manage them.

Edit external volumes The specified external volume must be assigned to theStorage Administrator group permitted to manage them.

Assign MP Blade The specified external volumes and all the ports of theexternal paths connecting the external volumes must beassigned to the Storage Administrator group permitted tomanage them.

Disconnect externalpaths

Ports of the specified external paths and all the externalvolumes connecting with the external path must be assignedto the Storage Administrator group permitted to managethem.When you specify By Ports, all the external paths connectingwith the specified ports and all the external volumesconnecting with the external paths must be assigned to theStorage Administrator group permitted to manage them.When you specify By External WWNs, all the ports of theexternal paths connecting to the specified external WWN andall the external volumes connecting with those external pathsmust be assigned to the Storage Administrator grouppermitted to manage them.

Reconnect external paths Ports of the specified external paths and all the externalvolumes connecting with those external paths must be



assigned to the Storage Administrator group permitted tomanage them.When you specify By Ports, all the external paths connectingwith the specified ports and all the external volumesconnecting with the external paths must be assigned to theStorage Administrator group permitted to manage them.When you specify By External WWNs, all the ports of theexternal paths connecting to the specified external WWN andall the external volumes connecting with those external pathsmust be assigned to the Storage Administrator grouppermitted to manage them.

Edit external WWNs All the ports of the external paths connecting to the specifiedexternal WWN and all the external volumes connecting withthe external paths must be assigned to the StorageAdministrator group permitted to manage them.

Edit external pathconfiguration

Ports of all the external paths composing the specified pathgroup and all the external volumes that belong to the pathgroup must be assigned to the Storage Administrator grouppermitted to manage them.

Virtual LVIThe following table provides information about specific Virtual LVI conditionsthat must be observed when using Resource Partition Manager.


Create LDEVs When you specify a parity group and open the Create LDEVswindow, the parity group must be assigned to the StorageAdministrator group permitted to manage them.When you create an internal or external volumes paritygroups where the LDEV belongs and ID of the new LDEV mustbe assigned to the Storage Administrator group permitted tomanage them.

Delete LDEVs When deleting an internal or external volume, the deletedLDEV and parity groups where the LDEV belongs must beassigned to the Storage Administrator group permitted tomanage them.

Edit LDEVs The specified LDEV must be assigned to the StorageAdministrator group permitted to manage them.

Restore LDEVs When you specify LDEVs and open the Restore LDEVswindow, the specified LDEVs must be assigned to the StorageAdministrator group permitted to manage them.When you specify a parity group and open the Restore LDEVswindow, the specified parity group and all the LDEVs in theparity group must be assigned to the Storage Administratorgroup permitted to manage them.

Block LDEVs When you specify LDEVs and open the Block LDEVs window,the specified LDEVs must be assigned to the StorageAdministrator group permitted to manage them.



When you specify a parity group and open the Block LDEVswindow, the specified parity group and all the LDEVs in theparity group must be assigned to the Storage Administratorgroup permitted to manage them.

Format LDEVs When you specify LDEV and open the Format LDEVs window,the specified LDEV must be assigned to the StorageAdministrator group permitted to manage them.When you specify a parity group and open the Format LDEVswindow, the specified parity group and all the LDEVs in theparity group must be assigned to the Storage Administratorgroup permitted to manage them.

Virtual Partition ManagerThe following table provides information about specific Virtual PartitionManager conditions that must be observed when using Resource PartitionManager.


Migrate parity groups When you specify virtual volumes, the specified LDEV mustbe assigned to the Storage Administrator group permitted tomanage them.When you specify a parity group, the specified parity groupmust be assigned to the Storage Administrator grouppermitted to manage them.

Volume ShredderThe following table provides information about specific Volume Shredderconditions that must be observed when using Resource Partition Manager.


Shred LDEVs When you specify LDEVs and open the Shred LDEVs window,the specified LDEVs must be assigned to the StorageAdministrator group permitted to manage them.When you specify a parity group and open the Shred LDEVswindow, the specified parity group and all the LDEVs in theparity group must be assigned to the Storage Administratorgroup permitted to manage them.


3Configuring custom-sized provisioning

Configuring custom-sized provisioning involves creating and configuring acustomized volume (CV). A CV is a fixed-sized volume that is divided intoarbitrary sizes.

This provisioning strategy is suitable for use on both open and mainframesystems. Virtual LVI software is required to configure variable-sizedprovisioning on mainframe systems.

□ Virtual LVI functions

□ Virtual LVI requirements

□ Virtual LVI specifications

□ SSID requirements

□ Virtual LVI size calculations

□ Create LDEV function

□ Blocking LDEVs

□ Blocking LDEVs in a parity group

□ Restoring blocked LDEVs

□ Restoring blocked LDEVs in a parity group

□ Editing an LDEV name

□ Deleting an LDEV (converting to free space)

Configuring custom-sized provisioning 3-1Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

□ Formatting LDEVs

□ Making external mainframe system volumes usable

□ Assigning an MP blade

3-2 Configuring custom-sized provisioningHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Virtual LVI functionsVirtual LVI function is used to create, configure, or delete a customizedvolume (LDEV).

The Virtual LVI function is a mainframe function available in Virtual LVIsoftware.

A parity group usually consists of some fixed-sized volumes (FVs) and somefree space. The number of FVs is determined by the emulation type. A VirtualLVI volume usually consists of at least one FV, one or more customizedvolumes (CVs), and some free space.

Use the Virtual LVI function to configure variable-sized volumes thatefficiently exploit the capacity of a disk. Variable-sized volumes are logicalvolumes that are divided into smaller than normal fixed-size volumes. Thisconfiguration is desirable when frequently accessed files are distributedacross smaller multiple logical volumes. This generally improves the dataaccessing performance, though file access may be delayed in some instances.

The Virtual LVI function can also divide a logical volume into multiple smallervolumes to reduce unused capacity and provide a more efficient use of spacefor small volumes such as command devices. The Virtual LVI function canefficiently exploit the capacity of a disk by not wasting capacity using largervolumes when the extra capacity is not needed.

Virtual LVI requirementsUse of Virtual LVI on the VSP G1000 storage system to configure variable-sized volumes requires the following:

• A license key for Virtual LVI.

For details about the license key or product installation, see the HitachiVirtual Storage Platform G1000 Mainframe System Administrator Guide.

Virtual LVI specificationsVirtual LVI specifications for mainframe systems on page 3-3

CV capacity by emulation type for mainframe systems on page 3-4

Virtual LVI specifications for mainframe systems

Parameter Mainframe system

Track format 3390

Emulation type 3390-3, 3390-3A, 3390-3B, 3390-3C, 3390-9, 3390-9A,3390-9B, 3390-9C, 3390-L, 3390-LA, 3390-LB, 3390-LC, 3390-M, 3390-MA, 3390-MB, 3390-MC, 3390-A,3390-V


Parameter Mainframe system

Ability to intermix emulationtype

If track sizes of the volumes are the same, emulationtypes can be intermixed.

Maximum number of volumes(normal and Virtual LVI) perparity group

2,048 for RAID 5 (7D+1P), RAID 6 (6D+2P) or RAID 6(14D+2P).1,024 for other RAID levels.

Maximum number of volumes(normal and Virtual LVI perstorage system

65,280

Minimum size for one VirtualLVI volume

1 user cylinder

Maximum size for one VirtualLVI volume

See CV capacity by emulation type for mainframesystems on page 3-4

Size increment 1 cylinder (cyl) which is equal to 870 KB.

CV capacity by emulation type for mainframe systems

Emulation type Minimum CV capacity(cyl) Maximum CV capacity (cyl)

3390-1 1 1,113

3390-2 1 2,226

3390-3 1 3,339

3390-3A 1 3,339

3390-3B 1 3,339

3390-3C 1 3,339

3390-9 1 10,017

3390-9A 1 10,017

3390-9B 1 10,017

3390-9C 1 10,017

3390-A1,5 1 262,668

3390-L 1 32,760

3390-LA 1 32,760

3390-LB 1 32,760

3390-LC 1 32,760

3390-M 1 65,520

3390-MA 1 65,520

3390-MB 1 65,520

3390-MC 1 65,520


Emulation type Minimum CV capacity(cyl) Maximum CV capacity (cyl)

3390-V 2,3,4 44 For an internal volume:837,760For an external volume:1,117,760

Notes:1. For 3390-A, the incremental unit of the CV capacity within the first 65,520 cylinders

is 1 user-cylinder, and the incremented capacity between 65,521 and 262,668cylinders is the 1,113 user-cylinder. Therefore, if you specify a value that exceeds65,520 cylinders, the value is changed to multiples of 1,113 cylinders. For instance,if 65,521 is specified, the value is changed to 65,667, which is 59 times 1,113cylinders.

2. For 3390-A, for the Compatible Software for IBM® FlashCopy® SE volume, if youspecify a value between 1 and 40,068 cylinders, the free space whose size is thesum of the specified value and 252 cylinders is required. If you specify a value of40,069 cylinders or more, the free space calculated by the following formula isrequired.40,320 cylinders + the value rounded up after the decimal point of *A * 1,120cylinderswhere *A = (the specified value - 40,068) ÷ 1,113 cylinders

3. For 3390-V, the value specified in the Create LDEVs window is changed to a multipleof 44.8 cylinders (38,976 KB) and the resulting number of cylinders is truncatedafter the decimal point. For instance, if 10,000 is specified, 10,035 appears (224times 44.8 cylinders is 10,035.2).

4. When the CV of 3390-V is registered to the pool of Dynamic Provisioning forMainframe, 8 GB or more free space in the CV of 3390-V is necessary. When youcreate a CV of 3390-V, specify the capacity as more than 9,676 cylinders.

5. If you specify 1 cylinder to create the CV of 3390-A, actually, 1,120 cylinders areused. In 1,120 cylinders, 1,113 cylinders are defined as a user-cylinder, and 7cylinders are defined as a control cylinder. To effectively create the CV of 3390-A,we recommend that you specify multiples of 1,113 cylinders for the CV capacity.

SSID requirementsThe storage system is configured with one SSID (Storage System ID) foreach group of 64 or 256 devices, so there are one or four SSIDs per CUimage. Each SSID must be unique to each connected host system. SSIDs areuser-specified and are assigned during storage system installation inhexadecimal format, from 0004 to FEFF.

The following table shows the relationship between controller emulation typesand SSIDs.

Controller emulationtype SSID requirement Virtual LVI Support

I-2107 0004 to FEFF 3390-3, 3390-3A, 3390-3B, 3390-3C,3390-9, 3390-9A, 3390-9B, 3390-9C,3390-L, 3390-LA, 3390-LB, 3390-LC,


Controller emulationtype SSID requirement Virtual LVI Support

3390-M, 3390-MA, 3390-MB, 3390-MCvolumes

Virtual LVI size calculationsWhen creating a CV, you can specify the capacity of each CV. However,rounding will produce different values for the user-specified CV capacity andthe actual entire CV capacity. To estimate the actual capacity of a CV, use amathematical formula. The following topics explain how to calculate the userarea capacity and the entire capacity of a CV.

The capacity of a CV or an LDEV consists of two types of capacity. One type isthe user area capacity that stores the user data. The second type is thecapacities of all areas that are necessary for an LDEV implementationincluding control information. The sum of these two types of capacities iscalled the entire capacity.

Implemented LDEVs consume the entire capacity from the parity groupcapacity. Therefore, even if the sum of user areas of multiple CVs and theuser area of one CV are the same size, the remaining free space generatedwhen multiple CVs are created may be smaller than the free space in theparity group when one CV is created.

Calculating the size of a 3390-A volumeTo calculate the entire capacity of a CV, use the following formulas. For theuser-specified-CV-capacity, specify the capacity of the user area in a CV.

The resulting CV capacity is expressed in megabytes:( ceil (user-specified-CV-capacity / 1113) * 1120 * 15 * capacity-of-a-slot ) / 1024• The value enclosed in ceil( ) must be rounded up to the nearest whole

number.• The user-specified-CV-capacity is the capacity of the user area in a CV

expressed in cylinders.• The capacity-of-a-slot is expressed in kilobytes. The capacity-of-a-slot

value depends on volume emulation types (see Capacity of a slot on page3-9).

Tip:

• To calculate the capacity of the CV of 3390-A, apply the multiples of1,113 cylinders to user-specified CV capacity in the upper formula. Forinstance, if you want to apply 1 cylinder to user-specified CV capacity,apply 1,113 cylinders. If you want to apply 1,114 cylinders to user-specified CV capacity, apply 2,226 cylinders.


• In 3390-A, if a value is specified that exceeds 65,520 cylinders, the valueis corrected to multiples of 1,113 cylinders. For instance, if 65,521 isspecified, 65,667 which is 59 times 1,113 cylinders appears.

Calculating the size of a 3390-V volumeTo calculate the entire capacity of a CV, use the following formulas. For theuser-specified-CV-capacity, specify the capacity of the user area in a CV.

The resulting CV capacity is expressed in megabytes:( ceil ( (user-specified-CV-capacity * 15) / 672) * 672 * capacity-of-a-slot ) / 1024• The value enclosed in ceil( ) must be rounded up to the nearest whole


expressed in cylinders.• The capacity-of-a-slot is expressed in kilobytes. The capacity-of-a-slot


Tip:

• To calculate the capacity of the CV of 3390-V, apply the multiples of 44.8cylinders to user-specified CV capacity in the upper formula. For instance,if you want to apply 44 cylinder to user-specified CV capacity, apply 44.8cylinders. If you want to apply 45 cylinders to user-specified CV capacity,apply 89.6 cylinders.

• In 3390-V, the value specified in the Create LDEVs window is corrected tomultiples of 44.8 cylinders (38,976 KB) and rounded down to the nearestwhole number of cylinders.

Calculating the size of a 3390-X volume

Tip: 3390-X indicates 3390-1, 3390-2, 3390-3, 3390-9, 3390-L, and 3390-M.

To calculate the entire capacity of a CV, use the following formulas. For theuser-specified-CV-capacity, specify the capacity of the user area in a CV.

The resulting CV capacity is expressed in megabytes:( ceil( ceil( (user-specified-CV-capacity + management-area-capacity) / 1113)* 7 * 15 + (user-specified-CV-capacity + management-area-capacity)* 15) / 672 * capacity-of-a-slot) / 1024• The value enclosed in ceil( ) must be rounded up to the nearest whole


expressed in cylinders.


• The management-area-capacity is expressed in cylinders (seeManagement area capacity of a mainframe volume on page 3-8).

• The capacity-of-a-slot is expressed in kilobytes. The capacity-of-a-slotvalue depends on volume emulation types (see Capacity of a slot on page3-9).

Calculating the size of a 3390-XA, 3390-XB, 3390-XC volume

Tip:

• 3390-XA indicates 3390-3A, 3390-9A, 3390-LA, and 3390-MA.• 3390-XB indicates 3390-3B, 3390-9B, 3390-LB, and 3390-MB.• 3390-XC indicates 3390-3C, 3390-9C, 3390-LC, and 3390-MC.

To calculate the entire capacity of a CV, use the following formulas. For theuser-specified-CV-capacity, specify the capacity of the user area in a CV.

The resulting CV capacity is expressed in megabytes:( ceil( ( (user-specified-CV-capacity + management-area-capacity)* 15 * capacity-of-a-slot) / boundary-value) * boundary-value) / 1024• The value enclosed in ceil( ) must be rounded up to the nearest whole


expressed in cylinders.• The management-area-capacity is expressed in cylinders (see

Management area capacity of a mainframe volume on page 3-8).• The capacity-of-a-slot is expressed in kilobytes. The capacity-of-a-slot


• The boundary-value is expressed in kilobytes. The boundary-value valuedepends on volume emulation types and RAID levels (see Boundaryvalues for RAID levels on page 3-9).

Management area capacity of a mainframe volume

Emulation type Management areacapacity (cyl)

3390-A 7 cyl per 1,113 cyl

3390-3, 3390-3A, 3390-3B, 3390-3C 6

3390-V 0

3390-9, 3390-9A, 3390-9B, 3390-9C 25

3390-L, 3390-LA, 3390-LB, 3390-LC 23

3390-M, 3390-MA, 3390-MB, 3390-MC 53

3390-1 5

Notes:


Emulation type Management areacapacity (cyl)

• The management area capacity of a mainframe volume is expressed in cylinders(Cyl).

Boundary values for RAID levelsBoundary values of external volumes are always one slot, regardless of RAIDlevels.

Emulationtype

Boundary value (KB)

RAID 1 (2D+2D)

RAID 5 (3D+1P)

RAID 5 (7D+1P)

RAID 6 (6D+2P)

RAID 6(14D+2P)

3390-xx 928 1,392 3,248 2,784 6,496

Notes:• xx indicates one or more numbers or letters.• Boundary values are expressed in kilobytes.• Boundary values are of external volumes are always one kilobyte, regardless of

RAID levels.• Hyphen (-) indicates that the combination is not supported.

Capacity of a slot

Emulation type Capacity (KB) of a slot

3390-xx 58

Notes:• xx indicates one or more numbers or letters.• Slot capacity is expressed in kilobytes.

Configuring volumes in a parity groupFor RAID 5 (7D+1P), RAID 6 (6D+2P), or RAID 6 (14D+2P) a maximum of2,048 fixed-size volumes (FVs) and a certain amount of free space areavailable in one parity group. For other RAID levels, a maximum of 1,024 FVsand a certain amount of free space are available in one parity group. Eachparity group has the same configuration, and is assigned the same FVs of thesame size and RAID level.

The Virtual LVI functions of Delete LDEVs and Create LDEVs are performed oneach parity group. Parity groups are also separated from each other byboundary limitations. Therefore, you cannot define a volume across two ormore parity groups beyond these boundaries.


As the result of the Virtual LVI operations, a parity group contains FVs, CVs,and free spaces that are delimited in logical cylinders. Sequential free spacesare combined into a single free space.

The following depicts an example of configuring volumes in a parity group:

Create LDEV functionUse the Create LDEV function to create a customized variable-sized volume.Use Virtual LVI to create mainframe volumes.

The following depicts an example of creating customized volumes. First youdelete FVs to create free space. Then you can create one or more customizedvolumes of any size in that free space.

Creating an LDEVThe Storage Administrator (Provisioning) role is required to perform this task.

Use this procedure to create one or more internal or external logical volumes(LDEVs) in a selected storage system. You can create multiple LDEVs at once,for example, when you are setting up your storage system. After the storagesystem is set up, you can add LDEVs as needed.

Before creating an LDEV in a selected storage system, free space may needto be created. Before volumes are deleted to create free space, make surethat the selected mainframe volumes are disconnected from the host and donot contain data that may be required later.

You can create LDEVs using any of the following tabs in Hitachi DeviceManager - Storage Navigator:


• Parity Groups tab when selecting Parity Groups.You can create multiple LDEVs in the specified free space by setting thenecessary items collectively. If multiple free spaces are in one paritygroup, the number of free spaces appears in Total Selected Free Spacein the Parity Group Selection section on the Create LDEVs wizard.Confirm the number of free spaces, then create the LDEVs accordingly.For example, if you are creating LDEVs in parity group PG1-1 and itcontains two free spaces, 2 appears in Total Selected Free Space. Inthis case, if you specify 1 in Number of LDEVs per Free Space, andcontinue to create the LDEV, two LDEVs are created because one LDEV iscreated for each free space.

• LDEVs tab when selecting any parity group in Parity Groups.• LDEVs tab when selecting Logical Devices.

To create an LDEV:

1. In the Hitachi Device Manager - Storage Navigator main window, in theStorage Systems tree, select the resource to view in the tab, then clickCreate LDEVs.

2. In the Create LDEVs window, from the Provisioning Type list, select aprovisioning type for the LDEV to be created.

¢ If creating internal volumes, select Basic.¢ If creating external volumes, select External.

3. In System Type, select Mainframe to create mainframe volumes.4. From the Emulation Type list, select an emulation type for the selected

system type.5. If creating an internal volume, select the parity group, then do the

following:

a. From the Drive Type/RPM list in Parity Group Selection, selectthe drive type and RPM.

b. From the RAID level list in Parity Group Selection, select the RAIDlevel.

c. Click Select Free Spaces.d. In the Select Free Spaces window, in the Available Free Spaces

table, select the free spaces to be assigned to the volumes.Do the following, if necessary:- To specify the conditions and show the free space, click Filter,specify the conditions, then click Apply.- To specify the unit for capacity and the number of rows to view, clickOptions.

e. Click View Physical Location.f. In the View Physical Location window, confirm where the selected

free space is physically located, then click Close.g. In the Select Free Spaces window, if the selected free spaces have

no issues, click OK.


6. Otherwise, if creating an external volume, select the external volume,then do the following:

a. Click Select Free Spaces.b. In the Select Free Spaces window, in the Available Free Spaces

table, select the free space to be assigned to the volumes.Do the following, if necessary:- To specify the conditions and show the free space, click Filter,specify the conditions, then click Apply.- To specify the unit for capacity and the number of rows to view, clickOptions.

c. Click View Physical Location.d. In the View Physical Location window, confirm where the selected

free space is physically located, then click Close.e. In the Select Free Spaces window, if the selected free spaces have

no issues, click OK.7. In LDEV Capacity, type the amount of LDEV capacity to be created and

select a capacity unit from the list.Enter the capacity within the range of figures displayed below the textbox. The capacity unit is fixed to Cyl.

8. In Number of LDEVs, type the number of LDEVs to be created.

¢ If you create internal volume, Number of LDEVs per Free Spaceappears.

¢ If you create external volume, Number of LDEVs per ExternalVolume appears.

9. In LDEV Name, specify a name for this LDEV.

a. In Prefix, type the characters that will become the fixed charactersfor the beginning of the LDEV name. The characters are case-sensitive.

b. In Initial Number, type the initial number that will follow the prefixname.

10. In Format Type, select the format type for the LDEV from the list.

¢ For an internal volume, select Normal Format, Quick Format, orNo Format.If No Format is selected, format the volume after creating LDEVs.

¢ For an external volume, if you create the LDEV whose emulation typeis the mainframe system, select Write to Control Block, NormalFormat or No Format.If No Format is selected, format the volume after creating theLDEVs.

¢ If Quick Format is selected while quick formatting is in progress,host I/Os may be affected. For details, see Quick Format function onpage 3-20.

11. Click Options to show more options.


12. In Initial LDEV ID, make sure that an LDEV ID is set. To confirm theused number and unavailable number, click View LDEV IDs to open theView LDEV IDs window.

a. In Initial LDEV ID in the Create LDEVs window, click View LDEVIDs.In the View LDEV IDs window, the matrix vertical scale representsthe second-to-last digit of the LDEV number, and the horizontal scalerepresents the last digit of the LDEV number. The LDEV IDs tableshows the available, used, and disabled LDEV IDs.In the table, used LDEV numbers appear in blue, unavailable numbersappear in gray, and unused numbers appear in white. LDEV numbersthat are unavailable may be already in use, or already assigned toanother emulation group (group by 32 LDEV numbers).

Note: When a mainframe volume or multi-platform volume is created,corresponding LDEV numbers cannot be specified if these values arenot identical: - model/serial numbers of the virtual storage machineand the storage system - LDEV ID and the virtual LDEV ID

b. Click Close.13. In the Create LDEVs window, in SSID, type four digits, in hexadecimal

format (0004 to FEFF), for the SSID.14. To confirm the created SSID, click View SSIDs to open the View SSIDs

dialog box.

a. In the Create LDEVs window, in Initial SSID, click View SSIDs.In the SSIDs window, the SSIDs table shows the used SSIDs.

b. Click Close.15. In the Create LDEVs window, from the MP Blade list, select a MP blade

to be used by the LDEVs.

¢ If you assign a specific MP blade, select the ID of the MP blade.¢ If you can assign any MP blade, click Auto.

16. Click Add.The created LDEVs are added to the Selected LDEVs table.The Provisioning Type, System Type, Emulation Type, Parity GroupSelection, LDEV Capacity, and Number of LDEVs per Free Space orNumber of LDEVs per External Volume fields must be set. If theserequired items are not registered, you cannot click Add.

17. If necessary, change the following LDEV settings:

¢ Click Edit SSIDs to open the SSIDs window. If the new LDEV is to becreated in the CU, change SSID to be allocated to the LDEV. Fordetails about how to edit an SSID, see Editing an LDEV SSID on page3-14.

¢ Click Change LDEV Settings to open the Change LDEV Settingswindow. For details about how to change the LDEV settings, seeChanging LDEV settings on page 3-15.

18. If necessary, delete an LDEV from the Selected LDEVs table.


Select an LDEV to delete, then click Remove. For details about how toremove an LDEV, see Removing an LDEV to be registered on page 3-15.

19. Click Finish.The Confirm window opens.

20. In the Confirm window, confirm the settings, in Task Name type aunique name for this task or accept the default, then click Apply.If Go to tasks window for status is checked, the Tasks window opens.

Finding an LDEV IDWhen creating volumes, the LDEV ID (LDKC: CU: LDEV) must be specified.Use this procedure to determine the LDEV IDs in use in the storage system soyou can specify the correct LDEV.

1. In Initial LDEV ID in the Create LDEVs window, click View LDEV IDs.2. In the View LDEV IDs window, review the list to confirm the LDEV IDs.

The LDEV IDs table shows the available, used, and disabled LDEV IDs.The matrix vertical scale represents the second-to-last digit of the LDEVnumber, and the horizontal scale represents the last digit of the LDEVnumber.In the table, used LDEV numbers appear in blue, unavailable LDEVnumbers appear in gray, and unused LDEV IDs appear in white. LDEVnumbers that are unavailable may be already in use, or already assignedto another emulation group (group by 32 LDEV numbers).

3. Click Close.The Create LDEVs window opens.

Finding an LDEV SSID When creating volumes, the LDEV SSIDs must be specified. Use thisprocedure to determine the SSIDs in use in the storage system so you canspecify the correct SSID.

1. In the Create LDEVs window, beside Initial SSID, click View SSIDs.2. In the SSIDs window, review the list to confirm the LDEV SSIDs. The

SSIDs table shows the SSIDs in use in the system.3. Click Close. The Create LDEVs window opens.

Editing an LDEV SSIDThe Storage Administrator (Provisioning) role is required to perform this task.

Before registering an LDEV, you may need to edit the LDEV SSID. If a CU isspecified in which the first LDEV is created, the value of SSID can bechanged.

1. In the Create LDEVs window, in the Selected LDEVs table, click EditSSIDs.


2. In the Edit SSIDs window, review the SSIDs table showing the existingSSIDs and ones to be added.

3. If you change the SSID, select the appropriate LDEV, then click ChangeSSIDs.

4. In the Change SSIDs window, type the new SSID, then click OK.5. In the Edit SSIDs window, click OK.6. In the Create LDEVs window, click Finish.7. In the Confirm window, click Apply.

The new SSID is registered.If Go to tasks window for status is checked, the Tasks window opens.

Changing LDEV settingsThe Storage Administrator (Provisioning) role is required to perform this task.

Before registering an LDEV, you may need to change the LDEV settings.

1. In the Create LDEVs window, in the Selected LDEVs table, select anLDEV, then click Change LDEV Settings.

2. In the Change LDEV Settings window, change the setting of LDEVName, Initial LDEV ID, or MP Blade.

¢ If you change LDEV Name, specify the prefix characters and theinitial number for this LDEV.

¢ If you change Initial LDEV ID, specify the number of LDKC, CU,LDEV, and Interval. To confirm used LDEV IDs, click View LDEV IDsto confirm the used LDEV IDs in the View LDEV IDs window.

¢ If you change MP Blade, click the list and specify the MP blade ID. Ifthe specific MP blade is specified, select the MP blade ID. If any MPblade is specified, click Auto.

3. Click OK.4. In the Create LDEVs window, click Finish.5. In the Confirm window, verify the settings, then click Apply.

The settings are changed.If Go to tasks window for status is checked, the Tasks window opens.

Removing an LDEV to be registeredThe Storage Administrator (Provisioning) role is required to perform this task.

If you do not want to register an LDEV that is scheduled to be registered, youcan remove it from the registration task.

1. In the Selected LDEVs table in the Create LDEVs window, select anLDEV, then click Remove.A message appears asking whether you want to remove the selected rowor rows. If you want to remove the row, click OK.

2. Click Finish.


3. In the Confirm window, click Apply. The LDEV is removed from theregistering task.If Go to tasks window for status is checked, the Tasks window opens.

Blocking LDEVsThe Storage Administrator (Provisioning) role is required to perform this task.

Before you format or shred a registered LDEV, the LDEV must be blocked.Use this procedure to block internal and external volumes from any of thesetabs.

• LDEVs tab when you make a selection from Parity Groups.• LDEVs tab when you select Logical Devices.• Virtual Volumes tab when you select a Pool.

1. In the Storage Systems tree of the Hitachi Device Manager - StorageNavigator main window, select the resource of the tab you want to view.

2. If Blocked does not appear in the Status column, use the following stepsto block the LDEV.If Blocked does appear in the column, skip the remaining steps.

3. Select the LDEV.You can select multiple LDEVs that are listed together or separately.

4. Open the Block LDEVs window in one of two ways.

¢ Click More Actions > Block LDEVs.¢ From the Actions menu, select Logical Device > Block LDEVs.

5. Note the settings in the Confirm window and enter a unique Task Nameor accept the default and click Apply.If Go to tasks window for status is checked, the Tasks window opens.

Blocking LDEVs in a parity groupThe Storage Administrator (Provisioning) role is required to perform this task.

Use this procedure to block LDEVs in a parity group from one of these tabs.

• Parity Groups tab when you select Parity Groups from the StorageSystems tree of the Hitachi Device Manager - Storage Navigator mainwindow.

• Parity Groups tab when you select Internal or External from ParityGroups from the Storage Systems tree.

1. In the Storage Systems tree, select the resource of the tab you want toview.

2. If Blocked does not appear in the LDEV Status column, use thefollowing steps to block the LDEV.If Blocked does appear in the column, skip the remaining steps.


3. Select the parity group.You can select multiple parity groups that are listed together orseparately.

4. Open the Block LDEVs window in one of two ways.

¢ Click More Actions > Block LDEVs.¢ From the Actions menu, select Logical Device > Block LDEVs.


Restoring blocked LDEVsThe Storage Administrator (Provisioning) role is required to perform this task.

Use this procedure to restore LDEVs from any of these tabs.

• LDEVs tab when you make a selection from Parity Groups.• LDEVs tab when you select Logical Devices.• Virtual Volumes tab when you select a Pool.

1. In the Storage Systems tree of the Hitachi Device Manager - StorageNavigator main window, select the resource of the tab you want to view.

2. If Blocked appears in the Status column, use the following steps torestore the LDEV.If Blocked does not appear in the column, skip the remaining steps.

3. Select the LDEV.You can select multiple LDEVs that are listed together or separately.

4. Open the Restore LDEVs window in one of two ways.

¢ Click More Actions > Restore LDEVs.¢ From the Actions menu, select Logical Device > Restore LDEVs.


Restoring blocked LDEVs in a parity groupThe Storage Administrator (Provisioning) role is required to perform this task.

Use this procedure to restore LDEVs in a parity group from any of these tabs.

• Parity Groups tab when you select Parity Groups from the StorageSystems tree of the Hitachi Device Manager - Storage Navigator mainwindow.

• Parity Groups tab when you select a parity group from Parity Groupsin the Storage Systems tree.


1. In the Storage Systems tree, select the resource of the tab you want toview.

2. If Blocked appears in the LDEV Status column, use the following stepsto restore a blocked LDEV.If Blocked does not appear in the column, skip the remaining steps.

3. Select the parity group.You can select multiple parity groups that are listed together orseparately.

4. Open the Restore LDEVs window in one of two ways.

¢ Click More Actions > Restore LDEVs.¢ From the Actions menu, select Logical Device > Restore LDEVs.


Editing an LDEV nameThe Storage Administrator (Provisioning) role is required to perform this task.

Use this procedure to edit the name of a registered internal volume.

1. Select the LDEV to be edited.2. Click Edit LDEVs.3. In Edit LDEVs window, edit LDEV Name.4. Click Finish.5. In the Confirm window, confirm the settings, in Task Name type a


Deleting an LDEV (converting to free space)The Storage Administrator (Provisioning) role is required to perform this task.

You can convert one or more of the LDEVs on a selected parity group intofree space by deleting the LDEVs. That free space can be used to eithercreate one or more variable-sized volumes (CVs) using the Create LDEVsfunction, or left as free space for future use.

WARNING: Deleting LDEVs will erase your data. Back up your data beforedeleting LDEVs.

An LDEV cannot be deleted successfully if it is:

• In the defined path (including the pair volumes of TrueCopy forMainframe and Hitachi Universal Replicator for Mainframe).

• A pool-VOL.


• A journal volume.• An LDEV that has the Read/Write access attribute.

When you delete an LDEV, the alias information contained in the LDEV is alsodeleted. Therefore, if you delete an LDEV related to an alias device, youshould do one of the following:

• Allocate another LDEV to the alias device, then delete the LDEV.• Delete the LDEV first, then allocate another LDEV to the alias device.

For information about how to delete a registered external volume, see theHitachi Universal Volume Manager User Guide.

To delete an LDEV:

1. Select one or more LDEVs to be deleted.2. Click More Actions and select Delete LDEVs.3. In the Confirm window, confirm the settings, in Task Name type a

unique name for this task or accept the default, then click Apply.The LDEV is deleted. The alias information contained in the deleted LDEVis also deleted. If the alias information is set to the LDEV, move it toanother LDEV, or set it again after deleting the LDEV.If Go to tasks window for status is checked, the Tasks window opens.

Formatting LDEVsIf you initialize LDEVs that are being used, you will need to format the LDEVs.Read the following topics before formatting LDEVs:

• About formatting LDEVs on page 3-19• Storage system operation when LDEVs are formatted on page 3-20• Quick Format function on page 3-20• Write to Control Blocks function on page 3-22

Formatting LDEVs includes the following tasks:

• Formatting a specific LDEV on page 3-23• Formatting all LDEVs in a parity group on page 3-23

About formatting LDEVsThe LDEV Format function, which includes Normal Format, Quick Format andWrite to Control Blocks. These functions format volumes, including externalvolumes. Before formatting volumes, ensure that the volumes are in blockedstatus.

The following table lists which formatting functions can be used on whichLDEV types.


Formatting function Corresponding volume

Normal Format Internal volumeVirtual volumeExternal volume

Quick Format Internal volume

Write to Control Blocks External volume

Storage system operation when LDEVs are formattedThe storage system acts in one of two ways immediately after an LDEV isadded, depending on the default settings in the storage system.

• The storage system automatically formats the added LDEV. This is thedefault action.

• The storage system blocks the LDEV instead of automatically formattingit.

To confirm or change the default formatting settings on the storage system,contact the administrator. Users who have the Storage Administrator(Provisioning) role can change these default formatting settings.

Quick Format functionThe Quick Format function formats internal volumes in the background. WhileQuick Format is running in the background, you can configure your systembefore the formatting is completed.

Before using Quick Format to format internal volumes, ensure that theinternal volumes are in blocked status.

I/O operation from a host during Quick Format are allowed. Formatting in thebackground might affect performance.

Because shared resources such as MP blades or cache paths are used duringquick format operations, all host I/Os in a storage system may be affected.

Particularly, in the following cases of quick format operations, due to the loadconcentration on a specific component at the same time, the I/O performanceof the host may decrease while performing of the quick format.

• In a configuration that satisfies both of these conditions, many quickformats started at the same time.

¢ The number of modules is one or two.¢ Configuration of CPEX (Cache Path control adapter and PCI EXpress

path switch), DKA (DisK Adapter), and CHA (CHannel Adapter) areminimum in each module

• In a configuration that satisfies either one of these conditions, quickformats started.


¢ In the multiple modules configuration, the number of CPEXs, DKAs,and CHAs that are installed in each module, are extremely unbalancedbetween modules.For example, in the multiple modules configuration, one modulecontains many CPEX, DKA, and CHA, and other modules containsCPEX, DKA, and CHA of the least number.

¢ In a module, numbers of CPEXs, DKAs, and CHAs that connect toCPEX (Basic) or CPEX (Option) are extremely unbalanced betweenCPEX (Basic) and CPEX (Option).For example, inside of one module, CPEX (Basic) is connected bymany DKAs, CHAs, or other devices. However, CPEX (Option) isconnected by DKAs, CHAs, or other devices of the least number.

For configurations such as those described above, perform the quick formatoperation on one LDEV first to confirm that the I/O performance of the hostdoes not decrease. After that, it is strongly recommended that the number ofquick format operations you perform at the same time is increased one byone.

For configurations other than those described above, it is recommended thatno more than eight quick format operations are started at the same time.After eight or fewer quick formats, it is recommended that four quick formatoperations are started in each increment while I/O performance is monitoredon the host.

Quick Format specifications

Item Description

Preparation forexecuting the QuickFormat feature

The internal volume must be in blocked status.

The number of paritygroups that canundergo QuickFormat

Up to 72 parity groups can concurrently undergo Quick Format.There is no limit on the number of volumes that can undergoQuick Format.

Concurrent QuickFormat operations

While one Quick Format operation is in progress, another QuickFormat operation can be performed. A maximum of 72 paritygroups can concurrently undergo Quick Format.

Preliminaryprocessing

At the beginning of the Quick Format operation, preliminaryprocessing is performed to generate management information. Ifa volume is undergoing preliminary processing, the status of thevolume is Preparing Quick Format. While preliminaryprocessing is in progress, hosts cannot perform I/O access to thevolume.

Blocking andrestoring of volumes

If a volume undergoing Quick Format is blocked, the storagesystem recognizes that the volume is undergoing Quick Format.After the volume is restored, the status of the volume changes toNormal (Quick Format).If all volumes in one or more parity groups undergoing QuickFormat are blocked, the displayed number of parity groupsundergoing Quick Format decreases by the number of blocked


Item Description

parity groups. However, the number of parity groups that havenot undergone and can undergo Quick Format does not increase.To calculate the number of parity groups that have notundergone but can undergo Quick Format, use the followingformula:72 - X - YWhere:X indicates the number of parity groups on which Quick Format isbeing performed.Y indicates the number of parity groups where all volumes areblocked during the Quick Format.

Storage system ispowered off and backon

The Quick Format operation resumes when power is turned backon.

Restrictions • Quick Format cannot be executed on external volumes,virtual volumes, the journal volumes of Universal Replicatorfor Mainframe.

• The volume migration feature or the QuickRestore featurecannot be applied to volumes undergoing Quick Format.When you use Command Control Interface to execute thevolume migration operation or the QuickRestore operation onvolumes undergoing Quick Format, EX_CMDRJE will bereported to Command Control Interface. In this case, checkthe volume status.

• The prestaging feature of Cache Residency Manager forMainframe cannot be applied to volumes undergoing QuickFormat.

Write to Control Blocks functionThe Write to Control Blocks function writes the mainframe systemmanagement area to an external volume.

If the LDEV with the mainframe system emulation type is created on theformatted external volume, it is recommended that the Write to ControlBlocks is set to the format type. If the Write to Control Blocks is set to theformat type, in comparison with the case of the Normal Format setting, theformat time is shortened.

Before using this function, make sure that the external volumes have beenformatted by the external storage system.

Caution: When it is uncertain whether the external LDEV has been formattedby an external storage system, select Normal Format to perform the formatoperation. If an option other than Normal Format is selected, the host maynot have access to the formatted external LDEV.To format the following LDEVs, select Normal Format as the format type:

• LDEV which was accessed by hosts• LDEV on which the Write to Control Blocks function was performed


Formatting a specific LDEVThe Storage Administrator (Provisioning) role is required to perform this task.

This procedure performs Normal formatting on the volume.

1. Select and block the LDEV to be formatted.See Blocking LDEVs on page 3-16 for blocking an internal volume. Seethe Hitachi Universal Volume Manager User Guide for blocking an externalvolume.

2. Click Format LDEVs.When you select one of the following tabs, click More Actions and selectFormat LDEVs.

¢ LDEVs tab, which appears when Logical Devices is selected fromthe Storage System tree.

¢ Virtual Volumes tab, which appears when a pool from Pools in theStorage System tree is selected.

3. In the Format LDEVs window, select the format type from the FormatType list, then click Finish.

4. In the Confirm window, click Apply.If Go to tasks window for status is checked, the Tasks window opens.

Formatting all LDEVs in a parity groupThe Storage Administrator (Provisioning) role is required to perform this task.

Use this procedure to perform Normal formatting on the volume.

When formatting all LDEVs in a parity group, you will need to:

• Specify a parity group.• Format the LDEV.

Before formatting all LDEVs in a parity group, make sure that all LDEVs underthis parity group have been blocked.

See Blocking LDEVs on page 3-16 for blocking an internal volume. See theHitachi Universal Volume Manager User Guide for blocking an externalvolume.

1. To format all LDEVs in the parity group, select the parity group.2. Click Format LDEVs.

When you select one of the following tabs, click More Actions and selectFormat LDEVs.

¢ LDEVs tab, which appears when Logical Devices is selected fromthe Storage System tree.

¢ Virtual Volumes tab, which appears when a pool from Pools in theStorage System tree is selected.

3. In the Format LDEVs window, select the format type from the FormatType list, then click Finish.


In the Confirm window, click Next to go to the next operation.4. Click Apply.

If Go to tasks window for status is checked, the Tasks window opens.

Making external mainframe system volumes usableTo use external mainframe volumes with a storage system, usually you mustuse Universal Volume Manager to perform external volume mapping, thenuse the Format command of Virtual LVI to format the volumes. However,formatting the external mainframe system volumes in this way may take a lotof time.

If you want to make the external mainframe volumes usable more quickly,you can use an alternate method:

• Registering external volumes on page 3-24• Overwriting control blocks in specific external volumes on page 3-25

Registering external volumesThe Storage Administrator (Provisioning) role is required to perform this task.

Using this procedure, you can make the external mainframe system volumesusable more quickly.

When the external volume is disconnected, you cannot register the externalvolume.

1. Perform zero-formatting on the external mainframe system volumes.Zero-formatting writes 0's in the entire disk area, formatting the entiredisk area. For information about how to perform zero-formatting, see thedocumentation for your mainframe system or external storage system.

2. Map the zero-formatted external volumes using Universal VolumeManager to register the volume in the external volume group. For moreinformation, see the Hitachi Universal Volume Manager User Guide.Non-zero-formatted external volumes must not be registered in theexternal groups. If the external volumes are registered, performing thenext step (step 3) will block and disable the volumes to be read andwritten from the host. To make the non-zero-formatted external volumesusable with Virtual Storage Platform G1000, use the Format command ofVirtual LVI.

3. Specify the external volumes to overwrite the control blocks of theexternal volumes in the group (see Overwriting control blocks in specificexternal volumes on page 3-25). A control block, which is a kind ofvolume area, is used to store information other than the user's data. Onlythe storage administrator is authorized to overwrite the control blocks.After overwriting completes, the external volumes are available for use inthe storage system.


You can perform the following tasks while the LDEV is formatted, but onlywhen the storage system is, by default, set to making the increased volumesblocked instead of formatting them automatically. For information aboutdefault settings of the storage system, see Overwriting control blocks inspecific external volumes on page 3-25.

• Deleting LDEVs (converting LDEVs to the free space).• Creating LDEVs.

Overwriting control blocks in specific external volumesThe Storage Administrator (Provisioning) role is required to perform this task.

1. Perform zero-formatting on the mainframe system volumes to registerthem (see steps 1 and 2 in Registering external volumes on page 3-24).

2. In the Storage Systems tree, select External Storages.The External Storage Systems tab appears.

3. Click the value of Vendor / Model / Serial Number of the externalstorage.The External Path Groups tab appears.

4. Click the value of External Path Group ID.The Mapped Volumes tab appears.

5. Select the row of the parity group that contains the external volume to beblocked, click More Actions and select Disconnect External Volumes.For more details about using the Disconnect External Volumes button,see the Hitachi Universal Volume Manager User Guide.

6. In the Storage Systems tree, click Parity Groups and External. Thenselect the parity group that contains the blocked external volume.The LDEV tab appears. Confirm that Blocked displays in the Statuscolumn.

7. Select the target volumes from among the volumes with a status ofBlocked. Then click Format LDEVs.The Format LDEVs window appears.

8. From the Format Type list, select Write to Control blocks, then clickFinish.

9. In the Confirm window, click Apply.If Go to tasks window for status is checked, the Tasks window opens.

10. When the processing is complete, click OK.11. Select the external volumes. Then click More Actions and Reconnect

External Volumes to restore them.The Status column of the target volumes shows Normal.


Assigning an MP blade

Assigning an MP blade to a resourceThe Storage Administrator (System Resource Management) role is required toperform this task.

You can assign a MP blade to resources (logical devices, external volumes,and journal volumes).

1. In the Hitachi Device Manager - Storage Navigator main window, in theStorage Systems tree, select Components.

2. In Components, select the name of the DKC for which you want toassign a MP blade.MP blades can be viewed in the MP Blades tab.

3. Select a MP blade for which you want to change the settings, then clickEdit MP Blades.

4. In the Edit MP Blades window, disable or enable Auto Assignment.The default value depends on the value set for the selected MP blade.

¢ Select Enable if the MP blade can be automatically assigned.¢ Select Disable if the MP blade cannot be automatically assigned.



Changing the MP blade assigned to an LDEV

Caution:

• The MP blade assigned to the LDEV that is used as a utility volume forCompatible XRC can be changed only when the XRC session is suspendedand the number of the side files of the target session is zero.

• Changes to the MP blade ID of an LDEV should be made during off-peakhours when the I/O load is as low as possible. Before and after changesare made, it is recommended that the cache write-pending rate (%) forall CLPRs is lower than 50%. Do not change the MP blade ID when the I/Oload is high -- for example: during initial copy of ShadowImage forMainframe, TrueCopy for Mainframe, or Universal Replicator forMainframe).

• When you change the MP blade ID of an LDEV, you should usePerformance Monitor before and after the change to check the load statusof devices. Do not change several LDEV MP blade IDs during a shortperiod of time. As a guideline, you can change 10% or less of the totalnumber or the full workload of LDEV MP blade IDs assigned to the sameMP blade ID at the same time.

• After you change the MP blade for an LDEV, wait more than 30 minutesbefore you try to change the ID again for the same LDEV.


The Storage Administrator (System Resource Management) role is required toperform this task.

1. In the Hitachi Device Manager - Storage Navigator main window, in theStorage Systems tree, select Logical Devices.LDEVs are shown in the LDEVs tab.

2. Select the LDEV for which you want to change the MP blade.3. Click More Actions, then select Assign MP Blade.4. In the Assign MP Blade window, specify the MP blade in MP Blade.5. Click Finish.6. In the Confirm window, confirm the settings, in Task Name type a




4Configuring thin provisioning

Thin provisioning technology allows you to allocate virtual storage capacitybased on anticipated future capacity needs, using virtual volumes instead ofphysical disks.

Thin provisioning is an optional provisioning strategy for both open andmainframe systems. Thin provisioning is implemented by creating one ormore Dynamic Provisioning for Mainframe pools (DP pools) of physicalstorage space.

□ Dynamic Provisioning for Mainframe overview

□ Dynamic Tiering for Mainframe overview

□ Thin provisioning requirements

□ Using Dynamic Provisioning for Mainframe or Dynamic Tiering forMainframe with other VSP G1000 products

□ Dynamic Provisioning for Mainframe workflow

□ Dynamic Tiering for Mainframe

□ Changing a pool for Dynamic Tiering for Mainframe to a pool for DynamicProvisioning for Mainframe

□ Working with pools

□ Working with DP-VOLs

□ Monitoring capacity and performance

□ Thresholds

Configuring thin provisioning 4-1Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

□ Working with SIMs

□ Manually completing a SIM

□ Managing pools and DP-VOLs

□ Starting pool monitoring manually

□ Stopping pool monitoring manually

□ Starting tier relocation manually

□ Stopping tier relocation manually

4-2 Configuring thin provisioningHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Dynamic Provisioning for Mainframe overviewDynamic Provisioning for Mainframe is an advanced thin-provisioningsoftware product that allows you to save money on storage purchases andreduce storage management expenses.

You can operate Dynamic Provisioning for Mainframe using both HitachiDevice Manager - Storage Navigator software and the Command ControlInterface.

Dynamic Tiering for Mainframe overviewDynamic Tiering for Mainframe is a software product that helps you reducestorage costs and increase storage performance by supporting a volumeconfigured with different storage media of different cost and performancecapabilities. This support allows you to allocate data areas with heavy I/Oloads to higher-speed media and to allocate data areas with low I/O loads tolower-speed media. In this way, you can make the best use of the capabilitiesof installed storage media. Up to three storage tiers consisting of differenttypes of data drives are supported in a single pool of storage.

Thin provisioning requirements

License requirementsBefore you operate Dynamic Provisioning for Mainframe, the DynamicProvisioning and the Dynamic Provisioning for Mainframe program productsmust be installed on the storage system. For this, you will need to purchasethe Storage Virtualization Operating System (SVOS) license.

Before you operate Dynamic Tiering for Mainframe, the Dynamic Provisioning,Dynamic Provisioning for Mainframe, Dynamic Tiering, and Dynamic Tieringfor Mainframe program products must be installed on the storage system. Forthis, you will need to purchase the Storage Virtualization Operating System(SVOS) license. and the Dynamic Tiering for Mainframe licence.

You will need the Dynamic Tiering for Mainframe license for the total capacityof the pool for which the tier function is enabled.

If the DP-VOLs of Dynamic Provisioning for Mainframe or Dynamic Tiering forMainframe are used for the primary volumes and secondary volumes ofShadowImage for Mainframe, Compatible FlashCopy® V2, TrueCopy forMainframe, or Universal Replicator for Mainframe, you will need theShadowImage for Mainframe, TrueCopy for Mainframe, CompatibleFlashCopy® V2, Universal Replicator for Mainframe license for the total poolcapacity in use. In addition, if you assign a DP-VOL of Dynamic Provisioningfor Mainframe or Dynamic Tiering for Mainframe to the primary volume ofCompatible XRC, you will need the Compatible XRC license for the total poolcapacity in use by the related DP-VOL.


If you exceed the licensed capacity, you will be able to use the additionalunlicensed capacity for 30 days.

For more information about temporary license capacity, see the HitachiVirtual Storage Platform G1000 Mainframe System Administrator Guide.

Pool requirementsA pool is a set of volumes reserved for storing Dynamic Provisioning forMainframe write data.

Items Requirements

Pool capacity Calculate pool capacity using the following formula:The capacity of the pool (MB) = Total number of pages * 38 -3800.

3800 in the formula is the management area size of the pool-VOL withSystem Area.Total Number of pages = Σ(floor(floor(pool-VOL number ofblocks ÷ 116) ÷ 672)) for each pool-VOL.floor( ): Truncates the value calculated from the formula in parenthesesafter the decimal point.However, the upper limit of total capacity of all pools is 11.1 PB ifshared memory is installed.

Max number ofpool-VOLs

From 1 to 1,024 volumes (per pool).A volume can be registered as a pool-VOL to one pool only.

Maximumnumber ofpools

Up to a total of 128 pools per storage system. This is the total numberof pools, Dynamic Provisioning for Mainframe (including DynamicTiering for Mainframe) pools, Dynamic Tiering(Dynamic Tiering forMainframe) pools and Thin Image pools.Pool IDs (0 to 127) are assigned as pool identifiers.

Increasingcapacity

You can increase pool capacity dynamically. Increasing capacity by oneor more parity groups is recommended by adding pool-VOLs.

Reducingcapacity

You can reduce pool capacity by removing pool-VOLs.

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

Subscriptionlimit

From 0 to 65534 (%).If you do not specify a value, the subscription is set to unlimited.

Thresholds • Warning Threshold: You can set the value between 1% and 100%,in 1% increments. The default is 70%.

• Depletion Threshold: You can set the value between the warningthreshold and 100%, in 1% increments. The default is 80%.

Data allocationunit

38 MBThe 38-MB page corresponds to a 38-MB continuous area of the DP-VOL. Pages are allocated for the pool only when data has been writtento the area of the DP-VOL.

Tier Defined based on the media type. Maximum 3 tiers.


Items Requirements

(DynamicTiering forMainframe)

Maximumcapacity ofeach tier(DynamicTiering forMainframe)

927 TB (Total capacity of the tiers must be within 927 TB

Pool-VOL requirementsPool-VOLs make up a DP-pool.

Items Requirements

Volume type Logical volume (LDEV)While pool-VOLs can coexist with other volumes in the same paritygroup, for best performance:• pool-VOLs for a pool should not share a parity group with other

volumes.• pool-VOLs should not be located on concatenated parity groups.Pool-VOLs cannot be used for any other purpose. For instance, youcannot specify the following volumes as Dynamic Provisioning forMainframe and Dynamic Tiering for Mainframe pool-VOLs:• Volumes used by ShadowImage for Mainframe, TrueCopy for

Mainframe, or Universal Replicator for Mainframe• Volumes defined by Cache Residency Manager• Volumes already registered in Dynamic Provisioning for Mainframe

or Dynamic Tiering for Mainframe pools• Volumes whose LDEV status is other than Normal or Normal (Quick

Format)You cannot specify volumes in blocked status or volumes in copyingprocess.

• Command devicesThe following pool-VOLs cannot exist in the same pool:• Internal volumes with external volumes whose cache mode is

disabled.• External volumes whose cache mode is enabled and external

volumes whose cache mode is disabled.

Emulation type 3390-V

RAID level fora DynamicProvisioning forMainframe pool

All RAID levels of pool-VOLs can be added. Pool-VOLs of RAID 5, RAID6, RAID 1, and the external volume can coexist in the same pool. Forpool-VOLs in the same pool:• RAID 6 is the recommended RAID level for pool-VOLs, especially

for a pool where the recovery time of a pool failure due to a drivefailure is not acceptable.


Items Requirements

• Pool-VOLs of the same drive type with different RAID levels cancoexist in the same pool. Note that we recommend that you usethe following configuration:¢ Set one RAID level for pool-VOLs.

If you register pool-VOLs with multiple RAID levels, the I/Operformance depends on the RAID levels of pool-VOLs to beregistered. In that case, note the I/O performance of the disks.

• Pool-VOLs on external volumes cannot have a mix of cache modesset to enable and disable.

• For internal and external pool-VOLs to coexist, the cache mode ofthe external volume must be set to enable.

RAID level fora DynamicTiering forMainframe pool

All RAID levels of pool-VOLs can be added. Pool-VOLs of RAID 5, RAID6, RAID 1, and the external volume can coexist in the same pool.For pool-VOLs in a pool:• RAID 6 is the recommended RAID level for pool-VOLs, especially

for a pool where the recovery time of a pool failure due to a drivefailure is not acceptable.

• Pool-VOLs of the same drive type with different RAID levels cancoexist in the same pool. Note that we recommend that you usethe following configuration:¢ Set one RAID level for pool-VOLs.

If you register pool-VOLs with multiple RAID levels, the I/Operformance depends on the RAID levels of pool-VOLs to beregistered. In that case, note the I/O performance of the disks.

• If pool-VOLs are external volumes, set the cache mode to Enable.

Data drive typefor a DynamicProvisioning forMainframe pool

SSD*, SAS15K, SAS10K, SAS7.2K, and the external volume can beused as the data drive type. These data drive types can coexist in thesame pool.Cautions:• We recommend that drives with different types do not coexist in a

same pool. If multiple pool-VOLs with different drive types areregistered in the same pool, the I/O performance depends on thedrive type of the pool-VOL to which the page is assigned.Therefore, if different drive types are registered in the same pool,ensure that the required I/O performance is not degraded by usingless desirable drive types.

• If multiple data drives coexist in a same pool, we recommend notusing data drives that are same types and different capacity sizes.

Data drive typefor a DynamicTiering forMainframe pool

SAS15K, SAS10K, SAS7.2K, SSD*, and the external volume can beused as the data drive type. These data drive types can coexist in thesame pool.Cautions:• If multiple data drives coexist in a same pool, we recommend not

using data drives that are same types and different capacity sizes.

Volumecapacity

Internal volume: From 8 GB to 695 GB (from 9,676 cyl to 837,760 cyl).External volume: From 8 GB to 927 GB (from 9,676 cyl to 1,117,760cyl).


Items Requirements

A volume whose capacity is less than 8GB (9,676 cylinders) cannot be apool volume.

LDEV format The LDEV format operation can be performed on pool-VOLs if one ofthese conditions is satisfied:• The DP-VOL defined for the pool does not exist.• All DP-VOLs defined for the pool are blocked.

* Includes SLC/MLC for SSD, and FMD.

DP-VOL requirements

Items Requirements

Volume type DP-VOL (V-VOL)The LDEV number is handled in the same way as for normal volumes.

Emulation type 3390-A

Maximumnumber of DP-VOLs

Up to 63,232 per pool. Any number of available DP-VOLs can beassociated with a pool.Up to 63,232 volumes per system. If external volumes and V-VOLs areused, the total number of external volumes and V-VOLs must be 63,232or less.

Volumecapacity

For 3390-A, volume capacity from 1 cyl to 262,668 cyl per volume.11.1 PB per system.

LDEV format When you perform the format operation on a DP-VOL, the storagesystem releases the allocated page area in the DP-VOL. The quickformat cannot be performed.

Requirements for increasing DP-VOL capacityYou can increase DP-VOL capacity up to 262,668 cylinders.

The following requirements are important when increasing the DP-VOLcapacity:

• The emulation type is 3390-A.• The DP-VOL to be increased is not shared with the VSP G1000 product

that does not allow increasing the DP-VOL (See Increasing DP-VOLcapacity on page 4-108).

• The DP-VOL is not undergoing LDEV formatting.• The capacity to be added to the DP-VOL must be specified within the

range indicated below LDEV Capacity in the Expand V-VOLs window.• The pool related to DP-VOLs to be increased is in any one of the following

statuses:

¢ Normal¢ Exceeding the subscription limit threshold


¢ In progress of pool capacity shrinking• You cannot expand both the TSE-VOL and the DP-VOL in one operation.

Expand the same type volumes in a single operation.• You cannot expand both the TSE-VOL and DP-VOL in one operation. In

this case, you must expand volumes whose types are same.

Caution: When increasing DP-VOL capacity, do not perform the followingoperations. When you perform these operations, do not increase DP-VOLcapacity.

• Operations using Virtual LVI• Operations using Cache Residency Manager• Creating DP-VOLs• Restoring pools• Deleting DP-VOLs• Maintenance of your storage system

After increasing DP-VOL capacity, refresh the display, then confirm that theDP-VOL is increased. If the DP-VOL capacity is not increased, wait a while,refresh the display again, and confirm that the DP-VOL is increased. If youperform an operation without making sure that the DP-VOL is increased,operations may fail.

If you place the DP-VOL online with an operating system that does notsupport DVE (Dynamic Volume Expansion), for instance operating systemswhose versions are z/OS 1.9 and z/VM 5.4, the DP-VOL capacity cannot beincreased. If you add capacity to the DP-VOL, take the DP-VOL offline whenthe operating system that does not support DVE, then increase the capacityof the DP-VOL. DVE is a function for increasing volume capacity while thevolume is online to a host system.

After the DP-VOL capacity is increased, the host issues reserved I/Os to theDP-VOL to update the VTOC area. In this case, I/Os issued from other hoststo the DP-VOL are waiting for the reservation to be released. The reply fromthe DP-VOL may be delayed, or the I/Os from other hosts may time out. Ifthe system operation may be inhibited by an interruption of a delayed replyor a timeout, do not increase the capacity of the DP-VOL.

Using Dynamic Provisioning for Mainframe or DynamicTiering for Mainframe with other VSP G1000 products

Interoperability of DP-VOLs and pool-VOLsDP-VOLs and pool-VOLs can be used in conjunction with other VSP G1000products. The following table lists the operations that are permitted and notpermitted.


Product name (Guidename) Permitted Not permitted

Cache Residency Manager(Hitachi Virtual StoragePlatform G1000Performance Guide)

Not applicable Performing operations on DPpool-VOLs, TSE-VOLs, orDP-VOLs.

ShadowImage forMainframe (HitachiShadowImage® forMainframe User Guide)

Using a DP-VOL as aShadowImage for Mainframeprimary volume orsecondary volume.

• Using a pool-VOL as aShadowImage forMainframe primaryvolume or secondaryvolume.

• Using a TSE-VOL as aShadowImage forMainframe primaryvolume or secondaryvolume.

• Increasing the capacityof a DP-VOL used byShadowImage forMainframe.

TrueCopy for Mainframe(Hitachi TrueCopy® forMainframe User Guide)

Using a DP-VOL as aTrueCopy for Mainframeprimary volume orsecondary volume.

• Using a pool-VOL as aTrueCopy for Mainframeprimary volume orsecondary volume.

• Using a TSE-VOL as aTrueCopy for Mainframeprimary volume orsecondary volume.

• Increasing the capacityof DP-VOL used as aprimary or secondaryvolume of a TrueCopyfor Mainframe pair.

Universal Replicator forMainframe (HitachiUniversal Replicator forMainframe User Guide)

Using a DP-VOL as aUniversal Replicator forMainframe primary volumeor secondary volume.However, the journal volumemust be a DP-VOL that hasOPEN-V emulation type.

• Using a DP-VOL as ajournal volume that hasa mainframe emulationtype.

• Using a DP pool-VOL asa Universal Replicatorfor Mainframe journalvolume, secondaryvolume, or primaryvolume.

• Using a TSE-VOL as aprimary volume,secondary volume, orjournal volume ofUniversal Replicator forMainframe.

• Increasing the capacityof a DP-VOL used byUniversal Replicator forMainframe.



Universal Volume Manager(Hitachi Universal VolumeManager User Guide)

Enabling volumes created byUniversal Volume Managerto be used as pool-VOLs.

Increasing the capacity of aDP-VOL which is mapped tothe Universal VolumeManager. If you try toincrease the capacity of aDP-VOL with theconventional LDEVoperation, the capacity ofthe DP-VOL will not bechanged. In this case,remove the mappingbetween DP-VOL andUniversal Volume Manager,increase a capacity of theexternal volume used as apool-VOL, then perform themapping between DP-VOLand the Universal VolumeManager again.

Virtual LVI (Hitachi VirtualStorage Platform G1000Provisioning Guide forMainframe Systems)

Registering Virtual LVIvolumes in DynamicProvisioning for Mainframepools.

Performing Virtual LVIoperations on volumes thatare already registered in aDP pool.

Virtual Partition Manager(Hitachi Virtual StoragePlatform G1000Performance Guide)

Performing operations onDP-VOLs and pool-VOLs.

Not applicable

Volume Shredder (HitachiVolume Shredder UserGuide)

Use on DP-VOLs. • Using on pool-VOLs.• Using on TSE-VOLs.• Increasing the capacity

of DP-VOL used byVolume Shredder.

• Reclaiming zero pagesof V-VOL used byVolume Shredder.

Compatible PAV (HitachiCompatible PAV User Guide)

• Defining base devices toDP-VOLs

• Defining base devices toTSE-VOLs.

• Defining base devices topool-VOLs

• Defining alias devices topool-VOLs

• Defining alias devices toDP-VOLs

• Defining alias devices toTSE-VOLs

Compatible XRC (HitachiCompatible XRC User Guide)

Using a DP-VOL as aCompatible XRC primaryvolume or secondaryvolume.

• Using a DP pool-VOL asa Compatible XRCprimary volume orsecondary volume.

• Using a TSE-VOL as aCompatible XRC



primary volume orsecondary volume.

• Increasing the capacityof DP-VOL used byCompatible XRC.

Compatible FlashCopy® V2and Compatible Software forIBM® FlashCopy® SE(Hitachi CompatibleFlashCopy® User Guide )

Using a DP-VOL as a sourcevolume or target volume.Using a TSE-VOL as a targetvolume.

• Using a pool-VOL as asource volume or targetvolume.

• Using a TSE-VOL as asource volume.

• Increasing the capacityof a DP-VOL used byCompatible FlashCopy®V2 or CompatibleSoftware for IBM®FlashCopy® SE.

TrueCopy for MainframeYou can use Dynamic Provisioning for Mainframe or Dynamic Tiering forMainframe in combination with TrueCopy for Mainframe to replicate V-VOLs.The following figure illustrates the interaction when the TrueCopy forMainframe primary volume and secondary volume are also V-VOLs.

Figure 4-1 Dynamic Provisioning for Mainframe or Dynamic Tiering forMainframe and TrueCopy for Mainframe

TrueCopy P-VOL TrueCopy S-VOL Explanation

DP-VOLs DP-VOLs Supported.

DP-VOLs Normal (ordinary)volumes*

Supported.

Normal (ordinary)volumes*

DP-VOLs Supported.Note, however, that this combinationconsumes the same amount of pool capacityas the original normal volume (primaryvolume).


TrueCopy P-VOL TrueCopy S-VOL Explanation

*Normal volumes include the internal volumes and external volumes that are mapped tothe volumes of the external storage system using by Universal Volume Manager. Formore information on external volumes, see the Hitachi Universal Volume Manager UserGuide.

You cannot specify a Dynamic Provisioning for Mainframe or Dynamic Tieringfor Mainframe pool-VOL as a primary volume or secondary volume

For information on supported emulation types, see the Hitachi TrueCopy® forMainframe User Guide.

Universal Replicator for MainframeYou can use Dynamic Provisioning for Mainframe or Dynamic Tiering forMainframe in combination with Universal Replicator for Mainframe to replicateDP-VOLs.

Figure 4-2 Using Dynamic Provisioning for Mainframe or Dynamic Tieringfor Mainframe and Universal Replicator for Mainframe

The following table lists the supported Universal Replicator and DynamicProvisioning or Dynamic Tiering volume combinations.

UniversalReplicator for

Mainframe P-VOL

UniversalReplicator forMainframe S-

VOL


Mainframejournal volume

Explanation

DP-VOLs DP-VOLs DP-VOL that hasthe OPEN-Vemulation type2

Supported.

DP-VOLs Normal (ordinary)volumes1

DP-VOL that hasthe OPEN-Vemulation type2

Supported.

Normal (ordinary)volumes1

DP-VOLs DP-VOL that hasthe OPEN-Vemulation type2

Supported.Note, however, that thiscombination consumes thesame amount of poolcapacity as the original



Mainframe P-VOL

UniversalReplicator forMainframe S-

VOL


Mainframejournal volume

Explanation

normal volume (primaryvolume).

1Normal volumes include the internal volumes and external volumes that are mapped tothe volumes of the external storage system using by Universal Volume Manager. Formore information on external volumes, see the Hitachi Universal Volume Manager UserGuide.2DP-VOL that has a mainframe emulation type cannot be used.

You cannot specify a Dynamic Provisioning for Mainframe or Dynamic Tieringfor Mainframe pool-VOL as a primary volume, secondary volume, or journalvolume.

For information on supported emulation types, see the Hitachi UniversalReplicator for Mainframe User Guide.

ShadowImage for MainframeYou can use Dynamic Provisioning for Mainframe or Dynamic Tiering forMainframe in combination with ShadowImage for Mainframe to replicate DP-VOLs.

The following table lists the interaction when the ShadowImage for Mainframeprimary volume and secondary volume are also DP-VOLs.

Figure 4-3 Using Dynamic Provisioning for Mainframe or Dynamic Tieringfor Mainframe and ShadowImage for Mainframe

ShadowImage forMainframe primary

volume

ShadowImage forMainframe

secondary volumeExplanation

DP-VOLs DP-VOLs Supported.

DP-VOLs Normal (ordinary)volumes*

Supported.The Quick Restore function is unavailable.


ShadowImage forMainframe primary

volume

ShadowImage forMainframe

secondary volumeExplanation

Normal (ordinary)volumes*

DP-VOLs Supported.Note, however, that this combinationconsumes the same amount of pool capacityas the normal volume.The Quick Restore function is unavailable.

*Normal volumes include the internal volumes and external volumes that are mapped tothe volumes of the external storage system using by Universal Volume Manager. Formore information on external volumes, see the Hitachi Universal Volume Manager UserGuide.

You cannot specify a Dynamic Provisioning for Mainframe or Dynamic Tieringfor Mainframe pool-VOL as a primary volume or secondary volume. For moreinformation, see the "Pair volumes and supported emulation types" section ofthe Hitachi ShadowImage® for Mainframe User Guide.

Virtual Partition Manager CLPR settingDP-VOLs and the associated pool volumes should be assigned to the sameCLPR.

We recommend that pool volumes in each pool are assigned to the sameCLPR on a pool basis.

For detailed information about CLPRs, see the Hitachi Virtual Storage PlatformG1000 Performance Guide.

Volume MigrationFor more information, see the Hitachi Volume Migration User Guide.

Resource Partition ManagerSee Resource group rules, restrictions, and guidelines on page 2-8 for theconditions of resources that are necessary in the operation of other HitachiData Systems software and the precautions required when using ResourcePartition Manager.

Dynamic Provisioning for Mainframe workflowThe following diagram shows the steps for a Storage Administrator to followin setting up Dynamic Provisioning for Mainframe on a storage system.

Use Hitachi Device Manager - Storage Navigator or Command ControlInterface to create pools and DP-VOLs.


Caution: If you delete a pool, its pool-VOLs (LDEVs) will be blocked. Blockedvolumes must be formatted before use.

Caution: When data migration is done on a file-by-file basis, perform theoperation to reclaim zero pages if necessary. In the case of a volume copy orthe physical copy, the operation to reclaim zero pages is unnecessary.To restore the backup data:

1. Restore the V-VOL data.2. Perform the operation to reclaim zero pages.Perform the above procedure for each V-VOL.

Dynamic Tiering for Mainframe

About tiered storageIn a tiered storage environment, storage tiers can be configured toaccommodate different categories of data. A tier is a group of storage media(pool volumes) in a DP pool. Tiers are determined by a single storage mediatype. A storage tier can be one type of data drive, including SSD, SAS, orexternal volumes. Media of high-speed performance make up the upper tiers.Media of low-speed response become the lower tiers. Up to a maximum ofthree tiers can coexist in each Dynamic Tiering pool.


Categories of data may be based on levels of protection needed, performancerequirements, frequency of use, and other considerations. Using differenttypes of storage tiers helps reduce storage costs and improve performance.

Because assigning data to particular media may be an ongoing and complexactivity, Dynamic Tiering software automatically manages the process basedon user-defined policies.

As an example of the additional implementation of tiered storage, tier 1 data(such as mission-critical or recently accessed data) might be stored onexpensive and high-quality media such as double-parity RAIDs (redundantarrays of independent disks). Tier 2 data (such as financial or seldom-useddata) might be stored on less expensive storage media.

Tier monitoring and data relocationDynamic Tiering uses tiers to manage data storage. It classifies the specifieddrives in the pool into tiers (storage hierarchy). Up to three tiers can bedefined in a pool depending on the processing capacity of the data drives.Tiering allocates more frequently accessed data to the upper tier and lessfrequently accessed data, stored for a long period of time, to the lower tier.

Multi-tier poolWith Dynamic Tiering, you can enable the Multi-Tier pool option for anexisting pool. The default is to allow tier relocation for each DP-VOL. Only theDP-VOLs for which tier relocation is enabled are subject to calculation of thetier range value, and tier relocation will be performed on them. If tierrelocation is disabled for all DP-VOLs in a pool, tier relocation is notperformed.

Figure 4-4 Relationship between multi-tier pool and tier relocation

Example of adding a tier

If the added pool-VOLs is a different media type, then a new tier is created inthe pool. The tier is added to the appropriate position according to itsperformance. The following figure illustrates adding a tier.


Example of deleting a tier

If a tier no longer has any pool-VOLs when you delete them, the tier isdeleted from the pool. The following figure illustrates deleting a tier.

Tier monitoring and relocation cyclesPerformance monitoring and tier relocation can be set to execute in one oftwo execution modes: Auto and Manual. You can set up execution modes, orswitch between modes by using either Hitachi Device Manager - StorageNavigator or Command Control Interface.

In Auto execution mode, monitoring and relocation are continuous andautomatically scheduled. In Manual execution mode, the following operationsare initiated manually.

• Start monitoring• Stop monitoring and recalculate tier range values• Start relocation• Stop relocation

In both execution modes, relocation of data is automatically determinedbased on monitoring results. The settings for these execution modes can bechanged nondisruptively while the pool is in use.

Auto execution mode

Auto execution mode performs monitoring and tier relocation based oninformation collected by monitoring at a specified constant frequency: from0.5, 1, 2, 4, or 8 hours. All Auto execution mode cycle frequencies have astarting point at midnight (00:00). For example, if you select a 1 hourmonitoring period, the starting times would be 00:00, 01:00, 02:00, 03:00,and so on.

As shown in the following table, the 24-hour monitoring cycle allows you tospecify the times of day to start and stop performance monitoring. The 24-hour monitoring cycle does not have to start at midnight. Tier relocationbegins at the end of each cycle. For more information, see Edit Pools windowon page E-33.


Monitoring cycle(hours) Start Times Finish Times

0.5 0.5 hours from 00:00 AM. Forexample 00:00, 00:30, and01:00

0.5 hours after the start time

1 1 hour from 00:00 AM. Forexample 00:00, 01:00, and02:00

1 hour after the start time

2 2 hours from 00:00 AM. Forexample 00:00, 02:00, and04:00

2 hours after the start time





24 (monitoring timeperiod can bespecified)

Specified time Specified time

If the setting of the monitoring cycle is changed, performance monitoringbegins at the new start time. The collection of monitoring information and tierrelocation operations already in progress are not interrupted when the settingis changed.

Example 1: If the monitoring cycle is changed from 1 hour to 4 hours at01:30 AM, the collection of monitoring information and tier relocation inprogress at 01:30 AM continues. At 02:00 AM and 03:00 AM, however,monitoring information is not collected and tier relocation is not performed.From 04:00 AM, the collection of monitoring information and tier relocationoperations are started again. These operations are then performed at 4-hourintervals.

Example 2: If the monitoring cycle is changed from 4 hours to 1 hour at01:30 AM, the collection of monitoring information and tier relocation inprogress at 01:30 AM continues. From 04:00 AM, the collection of monitoringinformation and tier relocation operations are started again. These operationsare then performed at 1-hour intervals.


Figure 4-5 Collection of monitoring data to tier relocation workflow in autoexecution mode

In auto execution mode, the collection of monitoring data and tier relocationoperations are performed in parallel in the next cycle. Data from theseparallel processes are stored in two separate fields.

• Data while monitoring is in progress in the next cycle.• Fixed monitoring information used in the tier relocation.

Manual execution mode

You can start and stop performance monitoring and tier relocation at anytime. You should keep the duration of performance monitoring to less than 7days (168 hours). If performance monitoring exceeds 7 days, thenmonitoring stops automatically.

Manual execution mode starts and ends monitoring and relocation at the timethe command is issued. You can use scripts, which provide flexibility tocontrol monitoring and relocation tasks based on a schedule for each day ofthe week.

In manual execution mode, the next monitoring cycle can be started with thecollection of monitoring data and tier relocation operations performed inparallel. Data from these parallel processes are stored in two separate fields.

• Data while monitoring is in progress in the next cycle.• Fixed monitoring information used in the tier relocation.


Figure 4-6 Collection of monitoring data to tier relocation workflow inmanual execution mode

Case 1: If the second collection of the monitoring information is finishedduring the first tier relocation, the latest monitoring information is the secondcollection. In that case, the first collection of monitoring information isreferenced only after the first tier relocation has completed.


Figure 4-7 Second collection of monitoring information finishes before thefirst tier relocation is complete

Case 2: When tier relocation is performed with the first collection ofmonitoring information, the second collection of monitoring information canbe performed. However, the third collection cannot be started. Because onlytwo fields are used store collected monitoring information, the third collectioncannot be overwritten.

In that case, the third collection of the monitoring information is started afterthe first tier relocation is stopped or tier relocation has completed.

The collection of the monitoring information is not started under theseconditions as well:

• When the second tier relocation is performed, the fourth collection ofmonitoring information cannot be started.

• When the third tier relocation is performed, the fifth collection ofmonitoring information cannot be started.

If such conditions exist, two cycles of monitoring information cannot becollected continuously while tier relocation is performed.


Figure 4-8 Third collection of monitoring information while tier relocationis performed

Tier relocation flowThe following shows the flow of allocating new pages and migrating them tothe appropriate tier. The combination of determining the appropriate storagetier and migrating the pages to the appropriate tier is referred to as tierrelocation.


Explanation of the relocation flow:

1. Allocate pages and map them to DP-VOLsPages are allocated and mapped to DP-VOLs on an on-demand basis.Page allocation occurs when a write is performed to an area of any DP-VOL that does not already have a page mapped to that location.Normally, a free page is selected for allocation from an upper tier with afree page. If the capacity of the upper tier is insufficient for the allocation,the pages are allocated to the nearest lower tier. A DP-VOL set to a tierpolicy is assigned a new page that is based on the tier policy setting. Therelative tier for new page allocations can be specified during operations tocreate and edit LDEVs. If the capacity of all the tiers is insufficient, anerror message (SIM=622xxx) is sent to the host.

2. Gather I/O load information of each pagePerformance monitoring gathers monitoring information of each page in apool to determine the physical I/O load per page in a pool. I/Osassociated with page relocation, however, are not counted.

3. Create frequency distribution graphThe frequency distribution graph, which shows the relationship betweenI/O counts (I/O load) and capacity (total number of pages), is created.You can use the View Tier Properties window to view this graph. Thevertical scale of the graph indicates ranges of I/Os per hour and thehorizontal scale indicates a capacity that received the I/O level. Note thatthe horizontal scale is accumulative. For details about the View TierProperties window, see View Tier Properties window on page E-56.


Caution: When the number of I/Os is counted, the number of I/Ossatisfied by cache hits are not counted. Therefore, the number of I/Oscounted by Performance Monitoring is different from the number of I/Osfrom the host. The number of I/Os per hour is shown in the graph. If themonitoring time is less than an hour, the number of I/Os shown in thegraph might be higher than the actual number of I/Os.Monitoring mode settings (see Monitoring modes on page 4-36) ofPeriod or Continuous influences the values shown on the performancegraph. Period mode will report the most recent completed monitor cycleI/O data on the performance graph. Continuous mode will report aweighted average of I/O data that uses recent monitor cycle data, alongwith historical data on the performance graph.

4. Determine the tier range valuesThe page is allocated to the appropriate tier according to performancemonitoring information. The tier is determined as follows.

a. Determine the tier boundaryThe tier range value of a tier is calculated using the frequencydistribution graph. This acts as a boundary value that separates tiersThe pages of higher I/O load are allocated to the upper tier insequence. Tier range is defined as the lowest I/Os per hour (IOPH)value at which the total number of stored pages matches the capacityof the target tier (less some buffer percentage) or the IOPH value thatwill reach the maximum I/O load that the tier should process. Themaximum I/O load that should be targeted to a tier is the limitperformance value, and the rate of I/O to the limit performance valueof a tier is called the performance utilization percent. If theperformance utilization percent shows 100%, this indicates that thetarget I/O load to a tier is beyond the forecasted limit performancevalue.

Caution: The limit performance value is proportional to the capacityof the pool volumes used in the tier. The total capacity of the paritygroup should be used for a pool to further improve the limitperformance.

b. Determine the tier delta valuesThe tier range values are set as the lower limit boundary of each tier.The delta values are set above and below the tier boundaries (+10 to20%) to prevent pages from being migrated unnecessarily. If allpages subject to tier relocation can be contained in the upper tier,both the tier range value (lower limit) and the delta value will be zero.


c. Determine the target tier of a page for relocation.The IOPH recorded for the page is compared against the tier rangevalue to determine the tier to which the page moves.

5. Migrate the pagesThe pages move to the appropriate tier. After migration, the page usagerates are averaged out in all tiers. I/Os which occur in the page migrationare not monitored.

Tier relocation rules, restrictions, and guidelines

Rules

• Performance monitoring, using both Auto and Manual execution modes,observes the pages that were allocated to DP-VOLs prior to the start ofthe monitoring cycle and the new pages allocated during the monitoringcycle. Pages that are not allocated during performance monitoring are notcandidates for tier relocation.

• Tier relocation can be performed concurrently on up to eight pools. Ifmore than eight pools are specified, relocation of the ninth pool startsafter relocation of any of the first eight pools has completed.

• If Auto execution mode is specified, performance monitoring may stopabout one minute before to one minute after the beginning of the nextmonitor cycle start time.

• The amount of relocation varies per cycle. In some cases, the cycle mayend before all relocation can be handled. If tier relocation doesn't finishcompletely within the cycle, relocation to appropriate pages is executed inthe next cycle.

• Calculating the tier range values will be influenced by the capacityallocated to DP-VOLs with relocation disabled and the buffer reservepercentages.

• While a pool-VOL is being deleted, tier relocation is not performed. Afterthe pool-VOL deletion is completed, tier relocation starts.

• Frequency distribution is unavailable when there is no data provided byperformance monitoring.


• While the frequency distribution graph is being created or the tier rangevalues are being calculated, the frequency distribution graph is notavailable. The time required for determining the tier range values variesdepending on the number of DP-VOLs and total capacity. The maximumtime is about 20 minutes.

• To balance the usage levels of all parity groups, rebalancing may beperformed after several tier relocation operations. If rebalancing is inprogress, the next cycle of tier relocation might be delayed.For details on rebalancing, see Rebalancing the usage level among paritygroups on page 4-58.

Conditions for the discontinuance of performance monitoring or tierrelocation

The status of data collection, fixed monitoring, and tier relocation operationsare described in the following table. The latest fixed monitoring information isreferenced when tiers are relocated.

Monitoringinformation or

executionconditions

Status of datacollection in

progress

Status of fixedmonitoringinformationused in tierrelocation

Tierrelocationoperations

Solutions

Unallocatedpages.

Pages are notmonitored.

No monitoringinformation onpages.

Tiers of thepages are notrelocated.

Unnecessary.After the pagesare allocated,monitoring andrelocation areperformedautomatically.

Zero data isdiscarded duringdata monitoring.

Monitoring onpages is reset.

Only monitoringinformation onpages is invalid.

Tiers of thepages are notrelocated.

Unnecessary.After the pagesare allocated,monitoring andrelocation areperformedautomatically.

V-VOL settingsdo not allow tierrelocation.

Volume ismonitored.

Monitoringinformation onthe volume isvalid.

If the tierrelocationsetting isbeing disabledat theperformancemonitoringfinish time,tiers of thevolume arenot relocated.

N/A

When V-VOLsare deleted

Volume is notmonitored.

Only monitoringinformation onthe volume isinvalid.

Tier relocationof the volumeis suspended.

N/A



executionconditions


progress



Solutions

When executionmode ischanged toManual fromAuto or viceversa.

Suspended. Monitoringinformationcollected beforesuspension isvalid.

Suspended. Collect themonitoringinformation againif necessary.1

When the powerswitch is powerON or OFF.

Monitoring issuspended bypowering OFFand is notresumed evenafter poweringON.1

Monitoringinformationcollected duringthe previouscycle iscontinuouslyvalid.

Tier relocationis suspendedby poweringOFF and isresumed afterpowering ON.

Collect themonitoringinformation againif necessary.1

• WhenVolumeMigration isperformed.

• When QuickRestore ofShadowImage forMainframeisperformed.

The volume isnot monitored.2

Monitoringinformation isinvalid and thevolumes need tobe monitored.

Tier relocationto volumes issuspended.


S-VOL offollowingprogramproducts whenthe initial copyoperation isperformed:• TrueCopy

forMainframe

• UniversalReplicatorforMainframe

Monitoringinformation iscontinuouslycollectedcontinuously,but themonitoring ofthe volumes isreset.3

No effect on thefixed monitoringinformation. Themonitoringinformationcollected duringthe previouscycle continuesto be valid.

Tier relocationto volumes issuspended.


• When thenumber oftiersincreasesby addingpool-VOLs.3

• When thepool-VOLsof the tiers

Continued. Fixed monitoringinformation isinvalid and isdiscarded.5

Suspended. Relocate tiersagain.1



executionconditions


progress



Solutions

areswitched byaddingpool-VOLs.4

• When tierrank of theexternalLDEV ischanged.

When pool-VOLsare deleted.

Continued. Monitoringinformation isinvalidtemporarily.6

Deleting thepool-VOLstops the tierrelocation. Theprocessresumes afterthe pool-VOLis deleted.

N/A

When a cache isblocked.

Continued. No effect on thefixed monitoringinformation. Themonitoringinformationcollected duringthe previouscycle continuesto be valid.

Suspended. After recoveringthe faulty area,relocate tiersagain.1

When an LDEVis blocked.(Pool-VOL or V-VOL)


Suspended. After recoveringthe faulty area,relocate tiersagain.1

When thedepletionthreshold of thepool is nearlyexceeded duringrelocation.


Suspended. Add pool-VOLs,then collectmonitoringinformation andrelocate tiersagain.1

When executionmode is Autoand theexecution cycle

At the end timeof executioncycle, datamonitoringstops.

The monitoringinformationcollected beforemonitoring

Suspended. Unnecessary. Therelocation isperformedautomatically inthe next cycle.



executionconditions


progress



Solutions

ends during tierrelocation.

performancestops is valid.

When executionmode is Manualand 7 dayselapse aftermonitoringstarts.

Suspended. The monitoringinformationcollected beforesuspension isvalid.

Continued. Collect themonitoringinformation againif necessary.1

Notes:1. The execution mode is Auto or the script is written in manual execution mode,

information is monitored again and tiers are relocated automatically.2. The volume is monitored at the time of the next execution cycle.3. All pages of the S-VOLs are not allocated, and the monitoring information of the

volume is reset. After the page is allocated to the new page, the monitoringinformation is collected.

4. Example: Pool-VOLs of SAS15K are added to the following configuration 1¢ Configuration 1 (before change): Tier 1 is SSD, Tier 2 is SAS10K, and Tier 3 is

SAS7.2K.¢ Configuration 2 (after change): Tier 1 is SSD, Tier 2 is SAS15K, and Tier 3 is

SAS10K and SAS7.2K.5. The monitor information statuses are valid (VAL), invalid (INV), and calculating

(PND). See Execution modes when using Command Control Interface on page4-34. In this case, the monitor information is invalid (INV). If monitoring is incontinue mode, the information of the mode is discarded.

6. After completion of the pool-VOLs deletes, the monitor information status is changedfrom invalid (INV) to calculating (PND). After completion of calculating, the monitorinformation status is changed from calculating (PND) to valid (VAL).

Buffer area of a tierDynamic Tiering for Mainframe uses buffer percentages to reserve pages fornew page assignments and allow the tier relocation process. Areas necessaryfor processing these operations are distributed corresponding to settings usedby Dynamic Tiering for Mainframe. The following describes how processingtakes place to handle the buffer percentages.

Buffer space: The following table shows the default rates (rate to capacity ofa tier) of buffer space used for tier relocation and new page assignments,listed by drive type.

Drive type buffer area for tierrelocation

buffer area fornew page

assignmentTotal

SSD 2% 0% 2%


Drive type buffer area for tierrelocation

buffer area fornew page

assignmentTotal

Non-SSD 2% 8% 10%

New page assignment: New pages are assigned based on a number ofoptional settings. Pages are then assigned to the next lower tier, leaving abuffer area (2% per tier by default) for tier relocation. Once 98% of capacityof all tiers is assigned, the remaining 2% of the buffer space is assigned fromthe upper tier. The buffer space for tier relocation is 2% in all tiers. Thefollowing illustrates the workflow of new page assignment.

Figure 4-9 Workflow of a new page assignment

Setting external volumes for each tierIf you use external volumes as pool-VOLs, you can put the external volumesin tiers by setting the External LDEV Tier Rank for the external volumes.The External LDEV Tier Rank consists of the following three types: High,Middle, and Low. The following examples describe how tiers may beconfigured:

Example 1: When configuring tiers by using external volumes only

Tier 1: External volumes (High)

Tier 2: External volumes (Middle)

Tier 3: External volumes (Low)

Example 2: When configuring tiers by combining internal volumesand external volumes

Tier 1: Internal volumes (SSD)


Tier 2: External volumes (High)

Tier 3: External volumes (Low)

You can set the External LDEV Tier Rank when creating the pool, changingthe pool capacity, or setting the Edit External LDEV Tier Rank window. Thefollowing table explains the performance priority (from the top) of datadrives.

Priority Data drive type

1 SSD

2 SAS 15K rpm

3 SAS 10K rpm

4 SAS 7.2K rpm

5 External volume* (High)

6 External volume* (Middle)

7 External volume* (Low)

*Displays as External Storage in the Drive Type/RPM.

Reserved pages for relocation operation: A small percentage of pages,normally 2, are reserved per tier to allow relocation to operate. These are thebuffer spaces for tier relocation.

Tier relocation workflow: Tier relocation is performed taking advantage ofthe buffer space allocated for tier relocation, as mentioned above. Tierrelocation is also performed to secure the space reserved in each tier for newpage assignment. The area is called the buffer space for new pageassignments. When tier relocation is performed, Dynamic Tiering forMainframe reserves buffer spaces for relocation and new page assignment.

During relocation, a tier may temporarily be assigned over 98% of capacityas well, or well under the allowance for the buffer areas.

Execution modes for tier relocation

Execution modes when using Hitachi Device Manager - Storage Navigator

Dynamic Tiering for Mainframe performs tier relocations using one of twoexecution modes: Auto and Manual. You can switch between modes by usingHitachi Device Manager - Storage Navigator.

Auto execution mode

In Auto execution mode, the system automatically and periodically collectsmonitoring data and performs tier relocation. You can select an Autoexecution cycle of 0.5, 1, 2, 4, or 8 hours, or a specified time.

The following illustrates tier relocation processing in a 2-hour Auto executionmode:



In Manual execution mode, you can manually collect monitoring data andrelocate a tier. You can issue commands to manually:

1. Start monitoring.2. Stop monitoring.3. Perform tier relocation.

The following illustrates tier relocation processing in Manual execution mode:


Notes on performing monitoring

• You can collect the monitoring data even while performing the relocation.• After stopping the monitoring, the tier range is automatically calculated.• The latest available monitoring information, which is collected just before

the relocation is performed, is used for the relocation processing.• When the relocation is performed, the status of the monitor information

must be valid.

Viewing monitor and tier relocation information:

Information is displayed on the following items in the GUI windows:

• Monitoring Status on Pools window on page E-3, Pools: Volume tabson page E-9, and View Pool Management Status window on pageE-68.Displays the status of pool monitoring.

¢ In Progress: The monitoring is being performed.¢ During Computation: The calculating is being processed.Other than these cases, a hyphen (-) is displayed.

• Recent Monitor Data on Pools window on page E-3 and Pools:Volume tabs on page E-9.Displays the latest monitoring data.

¢ If the monitoring data exists, the monitoring period of time isdisplayed.Example: 2010/11/15 00:00 - 2010/11/15 23:59

¢ If the monitoring data is being obtained, only the starting time isdisplayed.Example: 2010/11/15 00:00 -

¢ If the latest monitoring data does not exist, a hyphen (-) is displayed.• Pool Management Task on Pools window on page E-3 and Pools:

Volume tabs on page E-9.Displays the pool management task being performed to the pool.

¢ Waiting for Relocation: The tier relocation process is being waited.¢ Relocating: The tier relocation process is being performed.For details about the relocation progress rate, check the tier relocationlog. For more information about the table item for the tier relocation logfile, see Tier relocation log file contents on page 4-38.

• Pool Management Task (Status/Progress) on View Pool ManagementStatus window on page E-68.Displays the status of the pool management task being performed, eachV-VOL progress ratio in the pool and its average.

¢ Waiting for Relocation: The tier relocation process is being waited.¢ Relocating: The tier relocation process is being performed.


For details about the relocation progress rate, check the tier relocationlog. For more information about the table item for the tier relocation logfile, see Tier relocation log file contents on page 4-38.

• Relocation Result on Pools window on page E-3, Pools: Volume tabson page E-9, and View Pool Management Status window on pageE-68.Displays the status of the tier relocation processing.

¢ In Progress: The status of Pool Management Task is Waiting forRelocation or Relocating.

¢ Completed: The tier relocation operation is not in progress, or the tierrelocation is complete.

¢ Uncompleted (n% relocated): The tier relocation is suspended at theindicated percentage progression.

¢ Hyphen (-): The pool is not a Dynamic Tiering or Dynamic Tiering forMainframe pool.

• Relocation Speed on Pools window on page E-3, View PoolManagement Status window on page E-68, Create Pools window on pageE-19, Edit Pools window on page E-33, Start Tier Relocation window onpage E-66, and Stop Tier Relocation window on page E-67.Displays the tier relocation speed settings: 1(Slowest), 2(Slower),3(Standard), 4(Faster), and 5(Fastest).

• Relocation Priority on Pools: Volume tabs on page E-9 and View PoolManagement Status window on page E-68.Displays the relocation priority.

¢ Prioritized: The priority is set to V-VOL.¢ Blank: The priority is not set to V-VOL.¢ Hyphen (-): V-VOL is not the Dynamic Tiering for Mainframe V-VOL or

the tier relocation function is disabled.• Performance Graph on View Tier Properties window on page E-56.

The performance graph for the available monitor information is displayedin the View Tier Properties window.

Execution modes when using Command Control Interface


In Manual execution mode, you can manually collect monitoring data andrelocate a tier. You can execute commands to do the following:

1. Start monitoring.2. Stop monitoring.3. Perform tier relocation.

The following illustrates tier relocation processing when in Manual executionmode:


Notes on performing monitoring

• You can collect the monitoring data even while performing the relocation.• After stopping the monitoring, the tier range is automatically calculated.• The latest available monitoring information, which is collected just before

the relocation is performed, is used for the relocation processing.• When the relocation is performed, the status of the monitor information

must be valid.

Viewing monitor and tier relocation information:

If the raidcom get dp_pool command is executed with the -key opt optionspecified, the monitoring information and tier relocation information aredisplayed. For details about the raidcom get dp_pool command, see theHitachi Command Control Interface Command Reference. Items are displayedas follows:

• STSThis item displays the operational status of the performance monitor andthe tier relocation.

¢ STP: The performance monitor and the tier relocation are stopped.¢ RLC: The performance monitor is stopped. The tier relocation is

operating.¢ MON: The performance monitor is operating. The tier relocation is

stopped.¢ RLM: The performance monitor and the tier relocation are operating.

• DAT


This item displays the status of the monitor information.

¢ VAL: Valid.¢ INV: Invalid.¢ PND: Being calculated.

• R(%)This item displays the progress percentage of tier relocation.0 to 99: Shows one of the following statuses.

¢ When the value of STS is RLC or RLM: Relocation is in progress.¢ When the value of STS is STP or MON: Relocation is suspended at the

indicated percentage progression.100: Shows if the relocation operation is not in progress, or the relocationis complete.

Relocation speedRelocation speed: The page relocation speed can be set to 1(Slowest),2(Slower), 3(Standard), 4(Faster), and 5(Fastest). The default is3(Standard). If you want to perform tier relocation at high speed, use the5(Fastest) setting. If you set a speed that is slower than 3(Standard), theload to data drives is low when tier relocation is performed.

Based on the number of the parity groups that constitute a pool, this functionadjusts the number of V-VOLs for which tier relocation can be performed atone time. Tier relocation can be performed on as many as 32 V-VOLs in astorage system at once.

After changing the setting, the relocation speed does not change and the datadrive load may not change in the following cases:

• The number of parity groups is very few.• The number of V-VOLs associated with the pool is very few.• Tier relocations are being performed on the multiple pools.

Monitoring modesWhen you create or edit a pool, specify the Dynamic Tiering for Mainframemonitoring mode. The monitoring mode is either the period mode or thecontinuous mode. If you change the mode from the one to the other whileperforming the monitoring, the changed setting becomes effective when thenext monitoring will starts.

Period mode

Period mode is the default setting. If Period mode is enabled, tier rangevalues and page relocations are determined based solely on the monitoringdata from the last complete cycle. Relocation is performed according to anychanges in I/O loads. However, if the I/O loads vary greatly, relocation maynot finish in one cycle.


Continuous mode

If Continuous Mode is enabled, by weighting the latest monitoring informationand the collected monitoring information in the past cycles, the weightedaverage efficiency is calculated. By performing the tier relocation based onthe weighted average efficiency, even if a temporary decrease or an increaseof the I/O load occurs, unnecessary relocation can be avoided.

Cautions when using monitoring modes

• If Continuous mode is used, best practice is to collect monitoringinformation using the following execution modes:

¢ Auto execution mode¢ Manual execution mode with collecting the periodic monitoring

information by defining a script using CCIIf the Manual execution mode is used without scripts, the Continuousmonitoring mode can be set. However, in this case, unexpected resultsmay be calculated because the weighted average efficiency is calculated


based on very different duration (short and long) periods informationobtained in the past cycles.

• When the monitoring mode is set to Continuous, the frequencydistributions are displayed for each pool and V-VOL calculated by usingthe monitor value on which the weighted calculation is done.These calculated values are the predictive values for the next cycle aftersuccessfully relocating all pages. Therefore, these values may differ froman actual monitoring result when they appear.In Performance Utilization of each tier, regardless of the type of themonitoring mode setting, the monitor values which were already collectedin the current cycle are displayed.If you switch the monitoring mode from Period to Continuous or fromContinuous to Period, the current cycle's monitoring data that is beingcollected is not discarded. However, the data calculated by using pastmonitor cycle information on which the weighted calculation is done willbe reset.

Downloading the tier relocation log fileThe Storage Administrator (Provisioning) role is required to perform this task.

You can download the log file that contains the results of past tier relocations.See Tier relocation log file contents on page 4-38 for information about thecontents of the log.

1. Use one of these methods to select Tier Relocation Log Export.

¢ Select Pool in the Storage Systems tree. In the Pool tab, clickMore Actions and select Tier Relocation Log Export.

¢ From the Actions menu, select Pool management > TierRelocation Log Export.

2. In the dialog box, specify a folder for the log file you download and clickSave.If you change the file name from the default, make sure the file name isappended with the .tsv extension before saving the file.

Tier relocation log file contents

In every cycle in which tier relocation is performed, information about eachpool and V-VOL is exported to the tier relocation log. The time required toincorporate the latest tier relocation results may be approximately 30minutes. The tier relocation log file is tab-delimited and contains the followinginformation.

ItemDoes each pooloutput the loginformation?

Does each V-VOL output

the loginformation?

Type ofinformation Description

Cycle ID Yes Yes Common ID of each cycle of a tierrelocation.




the loginformation?


A common ID is allocated to poollogs and V-VOL logs that arecollected in one cycle.

Log FormatVersion

Yes Yes Common Version number of the tierrelocation log format.

DKC SerialNumber

Yes Yes Common Serial number of the storagesystem.

Log Type Yes Yes Common Following log types are displayed.POOL: Log information of eachpool.V-VOL: Log information of eachV-VOL.

LDEV ID No Yes Common LDEV ID of a V-VOL exported toa log.

Pool ID Yes Yes Common Pool ID of a pool exported to alog.

Num of V-VOLs Yes No Common The number of V-VOLs to beprocessed when tier relocation isperformed.

Tiering Policy No Yes Tier relocationresult

Value of the tiering policy. Valuesfrom All(0) to Level31(31) can bedisplayed.

Tier1 Total Yes No Capacityinformation

Total pages of tier 1.





Tier1 Used Yes Yes Capacityinformation

Pages assigned to tier 1 at thestart of tier relocation.





Start RelocationDate

Yes Yes1 Common Starting date of the tierrelocation.

Start RelocationTime

Yes Yes1 Common Starting time of the tierrelocation.

End RelocationDate

Yes Yes1 Common Ending date of the tier relocation.




the loginformation?


End RelocationTime

Yes Yes1 Common Ending time of the tier relocation.

Result Status Yes Yes1 Tier relocationresult

Statuses of a tier relocation.Normal End: A tier relocationended normally.Suspend: A tier relocationsuspended.

Detail Status Yes Yes1 Tier relocationresult

If the Result Status is Suspend,one of following reasons isdisplayed.Monitor discarded: Suspendeddue to the discard of monitoringdata.2

End of cycle: Suspended due toincomplete tier relocation duringa monitoring cycle.End of cycle: Suspended due toincomplete tier relocation duringa monitoring cycle.Requested by user: Suspendeddue to request by a user.Threshold exceeded: Suspendedbecause the used capacity ofpools reaches a threshold due toa tier relocation. When the usedcapacity of a pool reaches thedepletion threshold, this reasonis logged.Cache blocked: Suspendedbecause a cache memory isblocked.Volume blocked: Suspendedbecause an LDEV which is pool-VOL or V-VOL is blocked.The tier management changed(Auto/Manual): Suspendedbecause the tier managementmode is changed from Auto toManual, or Manual to Auto.Other reasons: Suspended forreasons other than the above,such as:• A V-VOL was specified as the

secondary volume of theTrueCopy for Mainframe pairand an initial copy operationwas performed.




the loginformation?


• A V-VOL was specified as thesecondary volume of theUniversal Replicator forMainframe pair, and an initialcopy operation wasperformed.

Completed Rate(%)

Yes Yes Tier relocationresult

Progress percentage rate at thetime tier relocation ends or issuspended.

RemediationRate (%)

Yes Yes Tier relocationresult

IOPH (I/O per hour) remediationrate at the time tier relocationends or is suspended.The remediation rate = ((TotalIOPH of pages after thepromotion1) / (Total IOPH of allpages to be performed ofpromotion1)) * 1001: Promotion is the pagemigration from a lower to highertier.

Planned Tier1->Tier2

Yes Yes Tier relocation Number of pages that areplanned to move from the tier 1to tier 2.











Moved Tier1->Tier2

Yes Yes Tier relocation Number of pages that are movedfrom the tier 1 to tier 2.

Moved Tier1->Tier3


Moved Tier2->Tier1





the loginformation?


Moved Tier2->Tier3


Moved Tier3->Tier1


Moved Tier3->Tier2


IOPH Yes Yes Monitoringresult

IOPHs of all pools or V-VOLs.

IOPH Tier1 (%) Yes Yes Monitoringresult

Percentage of IOPH for tier 1.





PerformanceUtil Tier1 (%)

Yes No Monitoringresult

Performance utilization of tier 1.The performance utilization is thecurrent I/O percentage based onthe maximum performance of tier1.







Tier1 LowRange

No Yes Monitoringresult

Lower limit in a range for tier 1.

Tier2 HighRange


Higher limit in a range for tier 2.

Tier2 LowRange


Lower limit in a range for tier 2.

Tier3 HighRange


Higher limit in a range for tier 3.

Reclaim ZeroPage Num

Yes Yes Tier relocation Number of pages processed in anoperation to reclaim zero pages.

Non CompliantTiering PolicyNumber


Number of a tiering policy thatdoes not conform to the currenttier configuration. A non-




the loginformation?


compliant policy prevents tierrelocation.

Notes1. If the log file is lfv2 (Log Format Version 2) or later, the log file information of each V-VOL appears.

If the log file is lfv 1, a hyphen appears.2. When deleting pool-VOLs, ex-valid monitor information are discarded, so that the tier relocation is

interrupted. After completion of the pool-VOLs deleting, the tier determination calculation performsagain and completes. Processed by this way, the valid monitor information are re-created.

Tiering policyThe tiering policy function is used to assign a specific storage tier to a specificDP-VOL. A tiering policy specifies subset of tiers that is available to a givenset of DP-VOLs.

Tier relocation changes the location of previously stored data. It is performedin conformance to the tiering policy. If a DP-VOL is initially allocated to a low-speed tier and the tiering policy is changed to a high-speed tier, relocation isperformed in the next cycle.

For example, if you set the tiering policy level on a V-VOL(DP-VOL) to a tierwith a high I/O speed, the data is always stored on the high-speed tier whenrelocating tiers. When you use that V-VOL(DP-VOL), regardless of the actualsize of the I/O load, you can always get high-speed responses. See Tieringpolicy expansion on page 4-43.

When you create the DP-VOL, you can designate one of six existing tieringpolicies and define up to 26 new tiering policies. See Tiering policy expansionon page 4-43 and Setting tiering policy on a DP-VOL on page 4-45.

Use the Edit LDEVs window to change the tiering policy settings. When tierrelocation occurs, the related tiering policy set for the DP-VOL is used torelocate data to the desired tier or tiers.

The tiering policy does not own pool capacity. Rather, pool capacity is sharedamong tiers. Pages are allocated in order of priority from upper to lower tiersin a tiering policy. When you specify a new allocation tier, pages are allocatedstarting from the tier that you specify.

The tier range, frequency distribution, and used capacity are displayed pertiering policy: existing tier level All(0), Level1(1) through Level5(5) andLevel6(6) to Level31(31).

Tiering policy expansion

In the current release, the tiering policy concept has been expanded toprovide new options:


• Custom policies. You can define up to 26 new policies (Level6(6) -Level31(31)) in addition to the existing six (All(0), Level1(1), Level2(2),Level3(3), Level4(4), and Level5(5)). See Setting tiering policy on a DP-VOL on page 4-45.A custom policy can be set for a DP-VOL when it is created and changed,if necessary, after creation.

Note: Custom policies cannot be renamed.

• Dynamic Tiering for Mainframe performs relocation while calculating pageallocation based on the tiering policy setting of all DP-VOLs that have thesame tiering policy in each pool.

• Max(%) and Min(%) parameters. When a tiering policy is created, 4 typesof parameters can be set: Tier1 Max and Tier 1 Min, Tier 3 Max and Tier 3Min. Each parameter setting is a ratio that corresponds to the totalcapacity of the allocated area of DP-VOLs that have the same tieringpolicy set for a pool. See Tiering policy examples on page 4-44.Tier1 and Tier3 parameter settings can also limit the capacity for allvolumes in a configuration that contain multiple DP-VOLs that have thesame intended use. These settings can prevent conditions such as thefollowing from occurring.

¢ Excess allocation of SSD capacity for unimportant applications.¢ Degradation in average response time for high performance

operations.

Tiering policy examples

The following figure shows the parameter settings Tier1 Max=40%, Tier1Min=20%, Tier3 Max=40%, and Tier3 Min=20% for a DP-VOL with aLevel6(6) setting when the initial allocated capacity of is 100GB.


The following figure shows an example of data allocation when the defaulttiering policy level All(0) is specified. Pages in the DP-VOL are relocated toany tier.

The following figure shows an example of data allocation when setting thetiering policy to Level1(1) (see Level1(1) in Tiering policy levels on page4-46). In this case, pages in the DP-VOL are relocated to tier 1, and are notrelocated to other tiers.

Setting tiering policy on a DP-VOL

The setting of a tiering policy for a DP-VOL is optional. If one is not selected,the default is the All(0) tiering policy level. The available levels are listed inTiering policy levels on page 4-46). DP-VOLs of different tiering policies can


coexist in one pool. If you specify the level of the tiering policy, DP-VOLs withthe policy are grouped together.

• All(0) is the default policy. In this case, data is stored to all of the tiers.• When a tier is added to the pool after setting the tiering policy on a DP-

VOL, the DP-VOL is relocated according to the new tier lineup.For example, if you set the tiering policy to level 5, the data is alwaysallocated to the tier of the low I/O speed. If the pool has two tiers, data isstored in tier 2. If a new tier is added, the number of tiers becomes threeand if the new tier is the lowest tier, relocation will be performed to movedata into tier 3.

For more information about tiering policy and groups, see Tiering policy levelson page 4-46.

Tiering policy levels

Tiering policy 1 tierpool

2 tierpool

3 tierpool Note

All(0) SingleTier

Bothtiers

All 3tiers

Default Tiering Policy

Level1(1) Same asAll(0)

Tier 1 Tier 1 Data is located to the Top Tier. Anyoverflow moves to the next lower tier.


Same asAll(0)

Tier 1and Tier2Seenote

Data is located to the Top Tier afterLevel1(1) assignments are processed.Any overflow moves to the next lowertier.


Same asAll(0)

Tier 2Seenote

Data is located to the Middle Tier. Anyoverflow moves to the top tier.


Same asAll(0)

Tier 2and Tier3Seenote

Data is located to the Middle Tier afterLevel3(3) assignments are processed.Any overflow moves to the next lowertier.


Tier 2 Tier 3Seenote

Data is located to the bottom tier. Anyoverflow moves to the next higher tier.

From Level6(6)to Level31(31)

Same asAll(0)

Dependson usersetting

Dependson usersetting

For example:If additional capacity is added to the pool and the capacity defines a new Tier 1 or newTier 2, then the DP-VOLs with a Level 5(5) assignment will not physically move but Level5(5) will be associated with Tier 3.If additional capacity is added to the pool and the capacity defines a new Tier 3, the DP-VOLs with a Level 5(5) assignment will physically move to the new Tier 3 and Level 5(5)will be associated with Tier 3.


Viewing the tiering policy in the performance graph

You can view the frequency distribution graph of the pool by selecting eitherthe level of the tiering policy or the entire pool on the performance graph inthe View Tier Properties window.

The following table shows how tiering policy is shown in the performancegraph. How the graph appears depends on the number of tiers set in a pooland tiering policy level selected when viewing the performance graph.

Tiering policyselected withperformance

graph

V-VOL displayed in the performance graph

All(0) In the performance graph, you can display a frequency distribution ofa DP-VOL, set to all tiers.

Level 1(1) In the performance graph, you can display the frequency distributionof a DP-VOL set to level 1.





From Level6(6)to Level31(31)

In the performance graph, you can display the frequency distributionof a DP-VOL set to custom policy.


Reserving tier capacity when setting a tiering policy

If you set the tiering policy of a DP-VOL, the DP-VOL used capacity and theI/O performance limitation are reserved from the tier. The reserved limitperformance per page is calculated as follows:

The reserved limit performance per page = (The performance limit of the tier)÷ (The number of pages in the tier).

A DP-VOL without a tiering policy setting uses the unreserved area in thepool.


Example of reserving tier capacity

The reservation priority depends on the level of tiering policy. The followingfigure illustrates the reservation priority. Tiers are reserved in order ofpriority from (1) to (7) in the figure. If the pool-VOL capacity is deficientwhen you reserve a tier, the nearest tier of your specified tier is allocated. Ifyou specify two tiers like level 2 or level 4 of the tiering policy, first of all theupper tier is reserved. At this time, if the capacity of the pool-VOL assignedto the upper tier is deficient, the lower tier defined by the tiering policy isreserved automatically. For example, in case of level 2 in the diagram below,tier 1 is reserved first. If the capacity of tier 1 is deficient at this point, tier 2is reserved automatically. For details, see Notes on tiering policy settings onpage 4-51.


Tierreservation

priorityTiering policy Reserved tier

1 Level1(1) Tier 1

2 Level3(3) Tier 2

3 Level5(5) Tier 3

From 4 to 29 From Level6(6) toLevel31(31)

The custom policy whose number issmall is prioritized.Tier 1: From Level6(6) to Level31(31),each of the Tier1 Min values arereserved.Tier 2: From Level6(6) to Level31(31),each of values that deducted the totalvalue of Tier1 Max and Tier3 Max from100(%) are reserved.Tier 3: From Level6(6) to Level31(31),each of the Tier3 Min values arereserved.

30 All(0) All tiers

Level2(2) Tier 1 and Tier 2

Level4(4) Tier 2 and Tier 3

From Level6(6) toLevel31(31)

Tier 1: From Level6(6) to Level31(31),each of the Tier1 Max values arereserved.Tier 3: From Level6(6) to Level31(31),each of the Tier3 Max values arereserved.


Notes on tiering policy settings

• If Auto is set as the execution mode, tier relocation is performed based onthe monitoring cycle. Therefore, when the tiering policy setting ischanged, tier relocation will automatically implement the tiering policy atthe end of the current monitoring cycle. See Example 1 in Executionmode settings and tiering policy on page 4-52.

• If Manual is set as the execution mode, you must manually performmonitoring, issue a monitor stop, then start relocation (see Example 2,Case 1, in Execution mode settings and tiering policy on page 4-52). Ifyou change the tiering policy settings while obtaining monitoring data, themonitoring data is used for the next tier relocation (see Example 2, Case2, in Execution mode settings and tiering policy on page 4-52).Therefore, you do not need to perform new monitoring.

• If a capacity shortage exists in the tier being set, a message may appearin the View Tier Property window that the page allocation cannot becompleted according to the tiering policy specified for the V-VOL. Shouldthat occur, the page allocation in the entire pool -- including the tier thatdefines the tiering policy -- might not be optimized.

Note: The message that page allocation cannot be completed accordingto the tiering policy does not appear when these tiering policies are set:


• All(0)• In a 2-tier configuration, Level2(2), Level3(3), or Level4(4) which is

equivalent to All(0)When a capacity shortage exists in a tier, you can revise the setting ofthe tiering policy or the configuration of tiers. If the capacity of one tier isfully exhausted, the migrating pages are assigned to the next tieraccording to the tiering policy.

¢ Level1(1): When tier 1 is full, the remaining pages are allocated totier 2. If tier 2 is full, the remaining pages are allocated to tier 3.



¢ Level2(2), Level4(4), and from Level6(6) to Level31(31): When thespecified tier is full, the unallocated pages are kept in the prior tier orthey are allocated to the tier that has free space.

• If a performance shortage exists in the tier being set, pages may not beallocated in conformance to the tiering policy specified for the V-VOL. Inthat case, pages are allocated according to the performance ratio of eachtier.As shown in the following table, allocation capacity considerations arebased on the tiering policy.

Tiering Policy Allocation capacity considerations

All(0), Level2(2), orLevel4(4)

Tier range and I/O performance

Level1(1), Level3(3), orLevel5(5)

Tier range

From Level6(6) toLevel31(31)

First phase: Tier range.Allocation capacities in each tier.• Tier1: The setting value(%) in Tier1 Min.• Tier2: The value deducted Tier1 Max(%) and Tier3

Max(%) from 100(%).• Tier3: The setting value(%) in Tier3 Min.

Second phase: Tier range and I/O performance.Capacities deducted from the allocated capacities of thefirst phase from the total used capacity, are allocated toeach tier.

Execution mode settings and tiering policy

The follow depicts how tier relocation is performed after changing the tieringpolicy setting while Auto execution mode is used.


The following depicts two cases of how tier relocation is performed afterchanging the tiering policy setting while Manual execution mode is used.


New page assignment tier

If you set the new page assignment tier value, when a new page is needed bya DP-VOL the page is taken from the specified tier aligned with the new pageassignment tier value. You can set this function by using Hitachi DeviceManager - Storage Navigator. In addition, this function becomes effective justafter setting. The following table lists setting values:

Setting value Description

High The new page is assigned from the higher tier of tiers set inthe tiering policy.

Middle The new page is assigned from the middle tier of tiers set inthe tiering policy.

Low The new page is assigned from the lower tier of tiers set inthe tiering policy.

The following tables show the tiers to which new pages are preferentiallyassigned.

TieringPolicy

Whenspecifying

High

Whenspecifying

Middle

Whenspecifying

LowNote

All From tier 1 to 2 From tier 1 to2

From tier 2 to 1 If you set Low, tier 2is given a priorityover tier 1.

Level 1 From tier 1 to 2 From tier 1 to2

From tier 1 to 2 Assignmentsequences whenHigh, Middle, andLow are same.


From tier 2 to 1 Every assignmentsequence is thesame as when All isspecified as thetiering policy.






From tier 2 to 1 Assignmentsequences whenHigh, Middle, andLow are same.


Number Condition Order of new page allocation

1 T1 MIN = 100% Same as Level1(1)

2 T1 MAX = 0% Same as Level5(5)

3 T1 MAX > 0% Same as All(0)

Tieringpolicy

Whenspecifying

High

Whenspecifying

Middle

Whenspecifying

LowNote

All From tier 1, 2,to 3.

From tier 2, 3,to 1.


Specifying High,Middle or Low to theassignmentsequence iseffective.

Level 1 From tier 1, 2,to 3.



Assignmentsequences whenHigh, Middle, andLow are same.

Level 2 From tier 1, 2,to 3.



If you set Low, tier 2is given a priorityover tier 1.

Level 3 From tier 2, 3,to 1

From tier 2, 3,to 1

From the 2, 3,to 1



From tier 2, 3,to 1

From tier 3, 2,to 1

If you set Low, tier 3is given priority overtier 2.


From tier 3, 2,to 1

From tier 3, 2,to 1


Number Condition Order of new page allocation



3 T1 MAX > 0% and T3 MAX =0%

Same as Level2(2)

4 T1 MAX = 0% and T3 MAX =0%

Same as Level3(3)

5 T1 MAX = 0% and T3 MAX >0%

Same as Level4(4)

6 T1 MAX > 0% and T3 MAX >0%

Same as All(0)


Relocation priority

If you use the relocation priority function, you can set the selection priority ofa DP-VOL when performing relocation. With this setting, a prioritized DP-VOLcan be relocated earlier during a relocation cycle. You can set this function byusing Hitachi Device Manager - Storage Navigator. The function is activatedafter the monitoring data is collected.

• If no relocation priority is set for all DP-VOLs, the general order of DP-VOL selection is to select the next DP-VOL in LDEV number order after thelast DP-VOL that fully performed relocation. This selection order persistsacross relocation cycles.

• If one or more DP-VOLs is assigned a relocation priority, the prioritizedDP-VOLs are operated upon in the early portion of the relocation cycle,before others in the general order of DP-VOL selection.

• If V-VOL is not given priority for relocation:For example, if LDEVs of LDEV IDs with LDEV#1, LDEV#2, LDEV#3,LDEV#4, and LDEV#5 are not given priority for relocation, LDEVs arerelocated with the following sequences. In this example, three LDEVs arerelocated in each period, but the number of LDEVs to relocate maychange by the relocation cycle or the data size.

Relocatingcycle

Relocatingsequence

of LDEV#1in eachcycle

Relocatingsequence ofLDEV#2 ineach cycle


Relocatingsequence


Relocatingsequence


T1 1st 2nd 3rd Unperformed

Unperformed

T2 3rd Unperformed Unperformed 1st 2nd

T3 Unperformed

1st 2nd 3rd Unperformed

T4 2nd 3rd Unperformed Unperformed

1st

• If V-VOL is given priority for relocation:For example, if LDEVs of LDEV IDs with LDEV#3 and LDEV#4 are setpriority for relocation from LDEV#1 to LDEV#5, LDEVs are relocated withthe following sequences. In this example, three LDEVs are relocated ineach period, but the number of LDEVs to relocate may change by therelocation cycle or data size.

Relocatingcycle

Relocatingsequence




Relocatingsequence


Relocatingsequence


T1 3rd Unperformed 1st 2nd Unperformed


Relocatingcycle

Relocatingsequence




Relocatingsequence


Relocatingsequence


T2 Unperformed

3rd 1st 2nd Unperformed

T3 Unperformed

Unperformed 1st 2nd 3rd

T4 3rd Unperformed 1st 2nd Unperformed

Assignment tier when pool-VOLs are deleted

When you delete pool-VOLs, the pages allocated to the pool-VOLs are movedto other pool-VOLs. The following table shows the tier numbers to whichpages are allocated before and after pool-VOLs are deleted. This operationdoes not depend on the tiering policy or the settings of newly assigned tiers.Relocate tiers after deleting pool-VOLs.

The following table describes page allocation in a 3-tier configuration.

Tier of deleted pool-VOLs

Order in which pagesare allocated to tiers Description

Tier 1 Tier 1, Tier 2, and Tier 3 If there is free space in Tier 1,pages are allocated to Tier 1.If there is no free space in Tier 1,pages are allocated to Tier 2.If there is no free space in Tier 1and Tier 2, pages are allocated toTier 3.

Tier 2 Tier 2, Tier 1, and Tier 3 If there is free space in Tier 2, thepages are allocated to Tier 2.If there is no free space in Tier 2,pages are allocated to Tier 1.If there is no free space in Tier 1and Tier 2, pages are allocated toTier 3.

Tier 3 Tier 3, Tier 2, and Tier 1 If there is free space in Tier 3,pages are allocated to Tier 3.If there is no free space in Tier 3,pages are allocated to Tier 2.If there is no free space in Tier 2and Tier 3, pages are allocated toTier 1.

The following table describes page allocation in a 2-tier configuration.


Tier of deleted pool-VOLs

Order in which pagesare allocated to tiers Description

Tier 1 Tier 1 and Tier 2 If there is free space in Tier 1,pages are allocated to Tier 1.If there is no free space in Tier 1,pages are allocated to Tier 2.

Tier 2 Tier 2 and Tier 1 If there is free space in Tier 2,pages are allocated to Tier 2.If there is no free space in Tier 2,pages are allocated to Tier 1.

Formatted pool capacity

The formatted pool capacity is the capacity of initialized free space in thepool, not the capacity of all the free space in the pool. The free space of thepool is monitored by a storage system. Space is formatted automatically ifneeded. You can confirm the formatted pool capacity in the View PoolManagement Status window (see View Pool Management Status windowon page E-68). Dependent on the load of the storage system, the formatspeed of the free space of the pool is adjusted.

New pages are allocated, then initialized, during data write operations to theV-VOL. If a significant number of new pages are allocated, initialization mightbe delayed as a result of conflicts between data write and new pageinitialization processes. You can initialize the free space of a pool in advanceto prevent delays in data write operations.

If you want to change the method of performing the function to format thefree space of a pool, contact the Hitachi Data Systems Support Center.

Rebalancing the usage level among parity groups

If multiple parity groups that contain LDEVs used as pool-VOLs exist,rebalancing can improve biased usage rates in parity groups. Rebalancing isperformed as if each parity group were a single pool-VOL. After rebalancing,the usage rates of LDEVs in a parity group may not be balanced, but theusage rate in the entire pool is balanced.

The usage level among parity groups is automatically rebalanced when theseoperations are in progress:

• Expanding pool capacity• Shrinking pool capacity• Reclaiming zero pages• Reclaiming zero pages in a page release request issued by the host with

the Write Same command, for example.• Performing tier relocations several times


If you expand the pool capacity, Dynamic Provisioning for Mainframe movesdata to the added space on a per-page basis. When the data is moved, theusage rate among parity groups of the pool-VOLs is rebalanced.

Host I/O performance may decrease when data is moved. If you do not wantto have the usage level of parity groups automatically balanced, call theHitachi Data Systems Support Center.

You can see the rebalancing progress of the usage level among parity groupsin the View Pool Management Status window (see View Pool ManagementStatus window on page E-68). Dynamic Provisioning for Mainframeautomatically stops balancing the usage levels among parity groups if thecache memory is not redundant or the pool usage rate reaches up to thethreshold.

Changing the tiering policy level on a DP-VOL

The Storage Administrator (Provisioning) role is required to perform this task.

1. In the Hitachi Device Manager - Storage Navigator main window, in theStorage Systems tree, select Logical Devices.The following is another way to select LDEVs.

a. In the Hitachi Device Manager - Storage Navigator main window, inthe Storage Systems tree, select Pool.

b. Select the pool associated with the DP-VOL that has the tiering policylevel you want to change.

c. Click the Virtual Volumes tab.2. From the table, select the row with the DP-VOL that has the tiering policy

level you want to change.3. Click More Actions, then select Edit LDEVs.4. In the Edit LDEVs window, select Tiering Policy, and select the tiering

policy.5. Click Finish.6. In the Confirm window, confirm the settings, in Task Name type a


Changing new page assignment tier of a V-VOLThe Storage Administrator (Provisioning) role is required to perform this task.

1. In the Storage Systems tree on the left pane of the top window, selectLogical Devices.The following shows an example of the other operations to select LDEVs.

a. In the Storage Systems tree on the left pane of the top window,select Pool.The pool name appears below Pool.

b. Click the pool associated with the V-VOL that has new pageassignment tier you want to change.


c. Click the Virtual Volumes tab on the right pane.2. From the table, click the row that has the V-VOL with the new page

assignment tier that you want to change.3. Click More Actions to select Edit LDEVs.

The Edit LDEVs window appears.4. Click the New Page Assignment Tier checkbox and select the new page

assignment tier you want to use.5. Click Finish.

The Confirm window appears.6. In the Task Name text box, type a unique name for the task or accept

the default.You can enter up to 32 ASCII characters and symbols, with the exceptionof: \ / : , ; * ? " < > |. The value "date-window name" is entered bydefault.

7. Click Apply.If the Go to tasks window for status checkbox is selected, the Taskswindow appears.

Opening the Edit Tiering Policies windowThe Storage Administrator (View) role is required to perform this task.

1. In the Storage Systems tree, select Pool.The pool information is displayed on the right pane of the window.

2. Click the Edit Tiering Policies button.The Edit Tiering Policies window appears.

Changing a tiering policyYou must have the Storage Administrator (System Resource Management)role to perform this task.

To change the tiering policy

1. In the Storage Systems tree, select Pool.The pool information is displayed on the right pane of the window.

2. Click the Edit Tiering Policies button.The Edit Tiering Policies window appears.

3. Select the tiering policy that you want to change and click the Changebutton.The Change Tiering Policies window appears. The policies which havean ID numbered 0 to 5 cannot be changed.

4. Change the tiering policy, and click OK.5. Return to the Edit Tiering Policies window appears.

Each tiering policy value is needed in order to meet the conditionsdescribed in the following table.


6. In the Task Name text box, type a unique name for the task or acceptthe default.


8. Click Finish.9. In the Confirm window, verify your settings. In Task Name, type a

unique name for this task or accept the default, then click Apply.

Item Explanation

Tier1 Max Satisfy either one of following:Equal to Tier1 MinBigger than Tier1 Min

Tier1 Min* Satisfy either one of following:Equal to Tier1 MaxSmaller than Tier1 Max

Tier3 Max Satisfy either one of following:Equal to Tier3 MinBigger than Tier3 Min

Tier3 Min* Satisfy either one of following:Equal to Tier3 MaxSmaller than Tier3 Max

* The sum of Tier1 Min and Tier3 Min must be 100 (%) or less.

Changing relocation priority setting of a V-VOLThe Storage Administrator (System Resource Management) role is required toperform this task.

1. In the Storage Systems tree on the left pane of the top window, selectLogical Devices.The following is another way to select LDEVs.

a. In the Storage Systems tree on the left pane of the top window,select Pool.The pool name appears below Pool.

b. Click the pool associated with the V-VOL that has the relocationpriority you want to change.

c. Click the Virtual Volumes tab on the right pane.2. From the table, click the row that has the V-VOL with the relocation

priority you want to change.3. Click More Actions to select Edit LDEVs.

The Edit LDEVs window appears.


4. Select the Relocation Priority checkbox and click Default or Prioritize.If you choose Prioritize, LDEV is relocated preferentially.

5. Click Finish.The Confirm window appears.

6. In the Task Name text box, enter the task name.You can enter up to 32 ASCII characters and symbols, with the exceptionof: \ / : , ; * ? " < > |. The value "date-window name" is entered bydefault.


Dynamic Tiering for Mainframe workflowThe following diagram shows the flow of work for a Storage Administrator toset up Dynamic Tiering for Mainframe on the storage system.

As shown in the diagram,Hitachi Device Manager - Storage Navigator andCommand Control Interface have different workflows. The details about howto set up Dynamic Tiering using Hitachi Device Manager - Storage Navigatorare covered in subsequent topics. For details about how to set up DynamicTiering for Mainframe using Command Control Interface, see the HitachiCommand Control Interface Command Reference and Hitachi CommandControl Interface User and Reference Guide. Use Hitachi Device Manager -Storage Navigator to create pools and DP-VOLs.



• In Command Control Interface, when creating a pool, you cannot enableMulti-Tier Pool and cannot register multiple media as pool-VOLs. Beforemaking tiers, enable Multi-Tier Pool.

• Enabling Multi-Tier Pool from Command Control Interface automaticallysets Tier Management to Manual. To change Tier Management toAuto, you must do this in Hitachi Device Manager - Storage Navigator.

• If you delete a pool, its pool-VOLs (LDEVs) will be blocked. If they areblocked, format them before using them.

Dynamic Tiering for Mainframe tasks and parametersThe following topics list the Dynamic Tiering for Mainframe tasks andparameter settings and indicate whether the tasks can be performed or theparameters can be set in Hitachi Device Manager - Storage Navigator (GUI)or Command Control Interface, or both.

For functions that can be used by Hitachi Tiered Storage Manager forMainframe, see Hitachi Tiered Storage Manager for Mainframe User Guide.

• Task and parameter settings on page 4-64• Display items: Setting parameters on page 4-66• Display items: Capacity usage for each tier on page 4-67• Display items: Performance monitor statistics on page 4-67• Display items: Operation status of performance monitor/relocation on

page 4-67

Task and parameter settings

No. Item GUI

Command

ControlInterfa

ce

1 DP pool Create(Setting item)

Create Y Y

2 Pool Name Y Y

3 Threshold Y Y

4 Multi-Tier Pool: Enable/Disable Y N1

5 Tier Management: Auto mode Y N

6 Tier Management: Manualmode

Y N

7 Rate of space for new pageassignment

Y3 N

8 Buffer Space for Tier relocation Y N

9 Cycle Time Y N

10 Monitoring Period Y N


No. Item GUI

Command

ControlInterfa

ce

11 Monitoring Mode Y N

12 External LDEV Tier Rank Y N

13 Relocation speed Y N

14 Delete Y Y

15 Change Settings(Setting item)

Change Settings Y Y

16 Pool Name Y Y2

17 Threshold Y Y

18 Multi-Tier Pool: Enable/Disable Y Y

19 Tier Management: Auto toManual

Y Y

20 Tier Management: Manual toAuto

Y N

21 Buffer Space for New pageassignment

Y3 Y3

22 Buffer Space for Tier relocation Y Y

23 Cycle Time Y N

24 Monitoring Period Y N

25 Monitoring Mode Y Y



28 DP pool Add pool-VOLs Y Y

29 Delete pool-VOLs Y Y

30 Restore Pools Y Y

31 Monitoring start/end Y Y

32 Tier relocation start/stop Y Y

33 DP-VOL Create(Setting item)

Create Y Y

34 DP-VOL Name Y Y

35 Multi-Tier Pool relocation:Disable

N N

36 Tiering Policy Y N

37 New page assignment tier Y N

38 Relocation priority Y N

39 Expand Y Y


No. Item GUI

Command

ControlInterfa

ce

40 Reclaim zero pages Y Y

41 Delete Y Y

42 Change Settings(Setting item)

Change Settings Y Y

43 Tier relocation: Enable/Disable Y Y

44 Tiering Policy Y Y



47 Relocationlog

Download relocation log Y N

Notes:1. Set to Disable if the pool is created by Command Control Interface.2. You can rename a pool when adding pool-VOLs to it.3. We recommend that you specify 0% for SSD and 8% for other drives.

Display items: Setting parameters

No. Category Output information GUI CommandControl Interface

1 DP pool Multi-Tier Pool: Disable Y Y

2 Tier Management mode: Auto/Manual

Y Y

3 Rate of space for new pageassignment

Y Y

4 Cycle Time Y* N

5 Monitoring Period Y* N

6 Monitoring Mode Y Y



9 DP-VOL Tier relocation: Enable/Disable Y Y

10 Tiering Policy Y Y



*You can view this item only in the Auto execution mode.


Display items: Capacity usage for each tier


1 DP pool Capacity for each tier (Total) Y Y

2 Capacity for each tier (Usage) Y Y

3 DP-VOL Capacity for each tier (Usage) Y Y

Display items: Performance monitor statistics


1 DP pool Frequency distribution Y1 N

2 Tier range Y1 Y2

3 Performance utilization Y Y

4 Monitoring Period starting time Y N

5 Monitoring Period ending time Y N

6 DP-VOL Frequency distribution Y N

7 Tier range Y N

8 Monitoring Period starting time Y N

9 Monitoring Period ending time Y N

Notes:1. You can select either each level of the tiering policy or the entire pool. If you set

other than All(0), the tier range is not displayed when you select the entire pool.2. The tier range when the tiering policy All(0) is selected is displayed.

Display items: Operation status of performance monitor/relocation


1 DP pool Monitor operation status: Stopped/Operating

Y Y

2 Performance monitor information:Valid/Invalid/Calculating

Y Y

3 Relocation status: Relocating/Stopped

Y Y

4 Relocation progress: 0 to 100% Y Y


Managing Dynamic Tiering for Mainframe

Changing pool for Dynamic Provisioning for Mainframe to pool for DynamicTiering for Mainframe


To change a pool for Dynamic Provisioning for Mainframe to a poolfor Dynamic Tiering for Mainframe:

1. In the Storage Systems tree on the left pane of the top window, selectPool.

2. From the Pools table on right, click the row of a pool you want to changeto the Dynamic Tiering for Mainframe setting.

3. Click More Actions and select Edit Pools.The Edit Pools window appears.

4. Check Multi-Tier Pool.5. Select Enable from the Multi-Tier Pool field.

If TSE-VOL is assigned to the selected pool, you cannot select Enable.6. To configure Dynamic Tiering for Mainframe:

a. Select the Tier Management checkbox.b. From the Tier Management field, select Auto or Manual.

Normally Auto should be set.When you select Auto, monitoring and tier relocation canautomatically executed.When you select Manual, monitoring and tier relocation can beexecuted with the Command Control Interface commands or thePools window.When you change the setting of Auto to Manual while monitoringand tier relocation is executing, it is cancelled.

c. From the Cycle Time list, select the cycle of performance monitoringand tier relocation.

Note:

• When you change the Cycle Time while performance monitoringand tier relocation are being executed, the setting becomeseffective for the next cycle after the current cycle is complete.When you select 24 Hours (default):Monitoring and tier relocation is performed once a day. In theMonitoring Period field, specify the time of starting and endingof monitoring in 00:00 to 23:59 (default value).

• If you specify the starting time later than the ending time, themonitoring continues until the time when you specify as theending time on the next day. Anytime that is not in the specifiedrange of the monitor period is not monitored.


• You can view the information gathered by monitoring with HitachiDevice Manager - Storage Navigator and Command ControlInterface.

• When you change the time range of performance monitoring, thesetting becomes effective from the next cycle after the cycle thatis executing is complete.When you select any of 0.5 Hours, 1 Hour, 2 Hours, 4 Hours or8 Hours:Performance monitoring is performed every duration you selectedstarting at 00:00.You cannot specify the monitoring period.

d. Select the Monitoring Mode checkbox.e. From the Monitoring Mode option, select Period Mode or

Continuous Mode.If you want to perform tier relocation using the monitor results fromthe prior cycle, select Period Mode. If you want to perform tierrelocation weighted to the past period monitoring result, selectContinuous Mode.

f. Select the speed to use for page relocation in Relocation speed. Youcan set the speed to: 1(Slowest), 2(Slower), 3(Standard), 4(Faster),or 5(Fastest). The default is 3(Standard). If the speed specified isslower than 3(Standard), the data drive load is low when tierrelocation is performed.

g. Select the Buffer Space for New page assignment checkbox.h. In the Buffer Space for New page assignment text box, enter an

integer value from 0 to 50 as the percentage (%) to set for each tier.i. Select the Buffer Space for Tier relocation checkbox.j. In the Buffer Space for Tier relocation text box, enter an integer

value from 2 to 40 as the percentage (%) to set for each tier.7. Click Finish.

The Confirm window appears.8. In the Task Name text box, enter the task name.

You can enter up to 32 ASCII characters and symbols in all, except for\ / : , ; * ? " < > |. The value "date-window name" is entered by default.

9. In the Confirm window, click Apply to register the setting in the task.If the Go to tasks window for status checkbox is selected, the Taskswindow appears.

Changing monitoring and tier relocation settings


This topic describes how to change the following pool settings of DynamicTiering for Mainframe:

• Automatic or manual execution of monitoring and tier relocation• Cycle time of monitoring and tier relocation


• Time period of monitoring

To change monitoring and tier relocation settings:


2. From the Pools table on the right, click the row of the pool with theDynamic Tiering for Mainframe setting you want to change.


4. Check Tier Management.5. From the Tier Management field, select Auto or Manual.

Normally Auto should be set.When you select Auto, monitoring and tier relocation can automaticallyexecuted.When you select Manual, monitoring and tier relocation can be executedwith the Command Control Interface commands or the Pools window.When you change the setting of Auto to Manual while performancemonitoring and tier relocation is executing, it is cancelled and is notperformed since then.

6. If Auto is selected from the Cycle Time list, select the cycle ofperformance monitoring and tier relocation.


8. In the Task Name text box, enter the task name.You can enter up to 32 ASCII characters and symbols in all, except for\ / : , ; * ? " < > |. The value "date-window name" is entered by default.


Changing monitoring mode setting


To change monitoring mode setting:


2. From the Pools table on the right, click the row of the pool with theDynamic Tiering for Mainframe setting you want to change.


4. Check Monitoring Mode.5. From the Monitoring Mode option, select Period Mode or Continuous

Mode.


If you want to perform tier relocation using the monitor results from theprior cycle, select Period Mode. If you want to perform tier relocationweighted to the past period monitoring result, select Continuous Mode.




Changing relocation speed


To change relocation speed


2. From the Pools table on the right, click the row of a pool with theDynamic Tiering for Mainframe setting you want to change.


4. Set the Relocation Speed checkbox to ON.5. Use the Relocation Speed option to set the speed for page relocation to

1(Slowest), 2(Slower), 3(Standard), 4(Faster), and 5(Fastest).The default is 3(Standard). If you want to perform tier relocation at highspeed, set 5(Fastest). If the speed specified is slower than 3(Standard),the data drive load is low when tier relocation is performed.




Changing buffer space for new page assignment setting


To change buffer space for new page assignment setting:





4. Select the Buffer Space for New page assignment checkbox.5. In the Buffer Space for New page assignment text box, enter an

integer value from 0 to 50 as the percentage (%) to set for each tier.6. Click Finish.




Changing buffer space for tier relocation setting


To change buffer space for tier relocation setting:




4. Select the Buffer Space for Tier relocation checkbox.5. In the Buffer Space for Tier relocation text box, enter an integer value

from 2 to 40 as the percentage (%) to set for each tier.6. Click Finish.




Changing a pool for Dynamic Tiering for Mainframe to a poolfor Dynamic Provisioning for Mainframe



You can change a Dynamic Tiering for Mainframe pool to a DynamicProvisioning for Mainframe pool. However, you cannot change the pool statusof Dynamic Tiering for Mainframe to disable in the following cases:

• Tier relocation is being executed manually.• Pool-VOLs are being deleted.• Zero pages are being reclaimed.

1. In the Storage Systems tree on the left pane of the top window, selectPool.The pool name appears below Pool.

2. Select a pool that is changed from a pool for Dynamic Tiering forMainframe to a pool for Dynamic Provisioning for Mainframe.The pool information appears.

3. Click More Actions to select Edit Pool.The Edit Pool window appears.

4. Check Multi-Tier Pool and select Disable from the Multi-Tier Pooloption.Click OK in the warning message.




Working with pools

About poolsDynamic Provisioning for Mainframe requires the use of pools. A pool consistsof more than one pool-VOL.

A storage system supports up to 128 pools, each of which can contain up to1024 pool-VOLs and 63,232 DP-VOLs per pool. The pool for DynamicProvisioning for Mainframe cannot be used in conjunction with other pools.

A pool number must be assigned to a pool. Multiple DP-VOLs can be relatedto one pool.

• capacity of the pool (MB) = total number of pages * 38 - 38003800(MB) in the formula is the management area size of the pool-VOLwith System Area.

• total number of pages = Σ(floor(floor(pool-VOL number of blocks ÷ 116)÷ 672)) for each pool-VOL


• 1 cylinder means 1740 blocks• floor( ) means to truncate the part of the formula within the parentheses

after the decimal point.

About pool-VOLsPool-VOLs are grouped together to create a pool. When a new pool is created,the available pool-VOLs are selected in the Select Pool VOLs window andadded to the Selected Pool Volumes table. Every pool must have a pool-VOLwith System Area.

The pool-VOLs contained in a pool can be added or deleted. Removing a pool-VOL does not delete the pool or any related DP-VOLs. You must delete all DP-VOLs related to the pool before the pool can be deleted. When the pool isdeleted, all data in the pool is also deleted.

Creating poolsThe following procedure tells how to create a pool. This procedure is forsetting up Dynamic Provisioning for Mainframe.

Before creating a pool, you must install the proper amount of sharedmemory, and you must have a V-VOL management area in shared memory.When shared memory is added, the V-VOL management area is automaticallycreated. To add shared memory, contact your Hitachi Data Systemsrepresentative.

One pool-VOL with system area is defined for a pool. The priority of the pool-VOL with system area is assigned according to the data drive type. Theavailable capacity of the pool-VOL with system area is deducted from themanagement area capacity. The management area capacity stores themanagement information of software that uses the pool. If DynamicProvisioning for Mainframe, or Dynamic Tiering for Mainframe is used on amainframe system, 3.8 GB are used as the management area in the pool-VOLwith system area.

When the pool is created, a pool-VOL with system area is assigned thepriority shown in the following table.


1 SAS7.2K

2 SAS10K

3 SAS15K

4 SSD

5 External volume

If multiple pool-VOLs of the same data drive type exist, the priority of each isdetermined by the internal index of the storage system.


For Dynamic Provisioning for Mainframe when selecting pool-VOLsmanually


To create pools by selecting pool-VOLs manually:

1. In the Storage Systems tree on the left pane of the top window, selectPool.The Pool window appears.

2. Click Create Pools.The Create Pools windows appears.

3. From the Pool Type list, select Dynamic Provisioning.4. From the System Type list, select Mainframe.5. From the Multi-Tier Pool field, select Disable.6. From the Pool Volume Selection field, select Manual.7. Follow the steps below to select pool-VOLs.

a. From the Drive Type/RPM list, select data drive type and RPM.b. From the RAID Level list, select RAID level.

If you select External Storage from the Drive Type/RPM list, ahyphen (-) appears and you cannot select the RAID level.

c. Click Select Pool VOLs.The Select Pool VOLs window appears.

d. In the Available Pool Volumes table, select the pool-VOL row to beassociated with a pool. Then click Add.The selected pool-VOL is registered in the Selected Pool Volumestable. Up to 1,024 volumes can be added to a pool.

Note: When you add external volumes, note the following points.

• An external volume that has Cache Mode set to Enable cannotcoexist in the same pool with an external volume that has CacheMode set to Disable.

• An internal volume and an external volume that each have CacheMode set to Disable cannot coexist in the same pool.

• You can select a value other than Middle from External LDEVTier Rank and click Add to set another tier rank for an externalvolume.

Tip: Perform the following steps if necessary:

• Click Filter to open the menu, specify the filtering, then Apply.• Click Select All Pages to select all pool-VOLs in the table. To

cancel the selection, click Select All Pages again.• Click Options to specify the volumes or the number of rows to be

displayed.e. Click OK.


The information in the Selected Pool Volumes table is applied toTotal Selected Pool Volumes and Total Selected Capacity.

8. In the Pool Name text box, enter the prefix and initial number of thepool. The pool name may consist of up to 32 characters.Prefix: Case-sensitive, alphanumeric characters that begin the poolname.Initial Number: From 1 to 9 digits that follow the prefix.

9. Click Options.10. In the Initial Pool ID text box, type the number of the initial pool ID,

from 0 to 127.When you specify a pool ID that was previously registered, the smallestavailable ID is displayed by default instead of the value you entered. If apool ID unavailable, no number is displayed.

11. In the Subscription Limit text box, enter an integer value from 0 to65534 as the subscription rate (%) for the pool.If no number is entered, the subscription rate is set to unlimited.

12. In the Warning Threshold text box, enter an integer value from 1 to100 as the rate (%) for the pool. The default value is 70%.

13. In the Depletion Threshold text box, enter an integer value from 1 to100 as the rate (%) for the pool. The default value is 80%.Enter a value that is greater than the value of the Warning Threshold.

14. Click Add.The created pool is added to the Selected Pools table. If invalid valuesare set, an error message appears.The Pool Type, Pool Volume Selection, and Pool Name must be set.If the required items are not entered or selected, you cannot clickAdd.If you select a row and click Detail, the Pool Properties windowappears. If you select a row and click Remove, the message appearsasking whether you want to remove the selected row or rows. If you wantto remove the row, click OK.

15. Click Next.The Create LDEVs window appears. Go to Creating V-VOLs on page4-85 to create LDEVs.If Subscription Limit of the created pool is set to 0%, the CreateLDEVs window does not appear.Click Finish and the Confirm window appears.

16. In the Confirm window, click Apply to register the setting in the task.If you select a row and click Detail, the Pool Properties windowappears.If the Go to tasks window for status checkbox is selected, the Taskswindow appears.

For Dynamic Provisioning for Mainframe when selecting pool-VOLsautomatically

To create pools by selecting pool-VOLs automatically:




3. From the Pool Type list, select Dynamic Provisioning.4. From the System Type list, select Mainframe.5. From the Multi-Tier Pool field, select Disable.6. From the Pool Volume Selection field, select Auto.7. Follow the steps below to select pool-VOLs.

a. From the Resource Group list, select the resource group name ofthe pool-VOL.

b. From the Performance list, select the performance of the pool.c. In the Total Capacity list, specify the capacity of the pool

Values are displayed in Total Pool Volumes and Total Capacity.These values are greater than the specified value of the pool capacity.If you change the pool configuration, perform steps d, e, and f.

d. Click Change Pool Configuration.The Change Pool Configuration Pattern window appears. You canchange the pool configuration that is automatically selected.

e. From the Pool Configuration Patterns table, select the poolconfiguration row. Then click Select

Note:

• You can select the pool configuration on a parity group basis.• The priority of the pool configuration is determined by these

conditions:Priority 1: There is no free space in the parity group and one LDEVexists in the group.Priority 2: There is no free space in the parity group and multipleLDEVs exist in the group.Priority 3: There is free space in the parity group and multipleLDEVs exist in the group.

• The following items are not displayed in the Pool ConfigurationPatterns table:Parity groups with LDEVs that cannot be used as pool-VOLs.Pool configuration patterns that contain more than 1,024 LDEVs.

f. Click OK.The information in the Pool Configuration Patterns table is appliedto Total Pool Volumes and Total Capacity.

8. In the Pool Name text box, enter the prefix and initial number of thepool. The pool name may consist of up to 32 characters.Prefix: Case-sensitive, alphanumeric characters that begin the poolname.


Initial Number: From 1 to 9 digits that follow the prefix.9. Click Options.10. In the Initial Pool ID text box, type the number of the initial pool ID,





14. Click Add.The created pool is added to the Selected Pools table. If invalid valuesare set, an error message appears.If an item that must be set is not entered or selected, you cannot clickAdd.The Pool Type, Pool Volume Selection, and Pool Name must be set.If the required items are not entered or selected, you cannot click AddIf you select a row and click Detail, the Pool Properties windowappears. If you select a row and click Remove, the message appearsasking whether you want to remove the selected row or rows. If you wantto remove the row, click OK.



For Dynamic Tiering for Mainframe pool when selecting pool-VOLsmanually

To create pools by selecting pool-VOLs manually:




3. From the Pool Type list, select Dynamic Provisioning.4. From the System Type list, select Mainframe.5. From the Multi-Tier Pool field, select Enable.

Note: You cannot select Enable if the storage system has only externalvolumes with the Cache Mode set to Disable.

6. From the Pool Volume Selection field, select Manual.7. Follow the steps below to select pool-VOLs.

a. In the Drive Type/RPM list, make sure Mixable is selected.b. In the RAID Level list, make sure Mixable is selected.c. Click Select Pool VOLs.

The Select Pool VOLs window appears.d. In the Available Pool Volumes table, select the pool-VOL row to be

associated with a pool. Then click Add.The selected pool-VOL is registered in the Selected Pool Volumestable. Up to 1,024 volumes can be added to a pool.You can add volumes with the same Drive Type/RPM and differentRAID Levels. For example, you can add a volume that has anSAS/15K Drive Type/RPM and a 5(3D+1P) RAID Level to the samepool with a volume that has an SAS/15K Drive Type/RPM and a5(7D+1P) RAID Level.

Note: You can select a value other than Middle from External LDEVTier Rank and click Add to set another tier rank for an externalvolume.

Tip: Perform the following steps if necessary:

• Click Filter to open the menu, specify the filtering, then Apply.• Click Select All Pages to select all pool-VOLs in the table. To

cancel the selection, click Select All Pages again.• Click Options to specify the volumes or the number of rows to be

displayed.e. Click OK.

The information in the Selected Pool Volumes table is applied toTotal Selected Pool Volumes and Total Selected Capacity.

8. In the Pool Name text box, enter the prefix and initial number of thepool. The pool name may consist of up to 32 characters.Prefix: Case-sensitive, alphanumeric characters that begin the poolname.Initial Number: From 1 to 9 digits that follow the prefix.

9. Click Options.


10. In the Initial Pool ID text box, type the number of the initial pool ID,from 0 to 127.When you specify a pool ID that was previously registered, the smallestavailable ID is displayed by default instead of the value you entered. If apool ID unavailable, no number is displayed.




14. Configure Dynamic Tiering for Mainframe with the following steps.From the Tier Management option, select Auto or Manual.

a. The selection is usually Auto which allows performance monitoringand tier relocation to be performed automatically.If you select Manual, use the Command Control Interface or HitachiDevice Manager - Storage Navigator to manually perform performancemonitoring and tier relocation.

b. From the Cycle Time option, select the cycle for performancemonitoring and tier relocation.When you select 24 Hours (default value):Performance monitoring and tier relocation is performed once a dayIn the Monitoring Period field, set the time to start and endperformance monitoring. The default value is 00:00 to 23:59.Set one or more hours between the starting and ending times. If youspecify a starting time that is later than the ending time, theperformance monitoring continues until the ending time on the nextday.You can view the information gathered by performance monitoringwith Hitachi Device Manager - Storage Navigator or the CommandControl Interface.When you select 0.5 Hours, 1 Hour, 2 Hours, 4 Hours, 8 Hours:Performance monitoring is performed every hour that is selected,starting at 00:00.You cannot set a specific time to start performance monitoring.

Caution: When Auto is set, all the V-VOL pages may not be completelymigrated in one cycle. In the next cycle, migration starts by updatinginformation for the last processed V-VOL. At that point, the collection ofperformance monitoring information is switched to the current cycle.

15. From the Monitoring Mode option, select Period Mode or ContinuousMode.


If you perform tier relocation in a specified cycle, Period Mode isselected by default. If you perform tier relocation weighted to themonitoring result of the past period, select Continuous Mode

16. From the Relocation Speed option, select the page relocation speed touse when performing relocation.You can set the speed to: 1(Slowest), 2(Slower), 3(Standard),4(Faster), and 5(Fastest). The default is 3(Standard). If you want toperform tier relocation at high speed, use the 5(Fastest) setting. If thespeed specified is slower than 3(Standard), the data drive load is lowwhen tier relocation is performed.

17. In the Buffer Space for New page assignment text box, enter aninteger value from 0 to 50 as the percentage (%) for each tier.A default value depends on the data drive type of the pool-VOL in eachtier. The default value of SSD is 0%. The default value of a type otherthan SSD is 8%.

18. In the Buffer Space for Tier relocation text box, enter an integer valuefrom2 to 40 as the percentage (%) to set for each tier.The default value is 2%.

19. Click Add.The created pool is added to the Selected Pools table. If invalid valuesare set, an error message appears. If Detail is clicked when you select arow, the Pool Property window appearsThe Pool Type, Multi-Tier Pool,Pool Volume Selection, and PoolName must be set. If the required items are not registered, you cannotclick Add.If you select a row and click Detail, the Pool Properties windowappears. If you select a row and click Remove, the message appearsasking whether you want to remove the selected row or rows. If you wantto remove the row, click OK.



For Dynamic Tiering for Mainframe pool when selecting pool-VOLsautomatically

To create pools by selecting pool-VOLs automatically:



The Pool window appears.2. Click Create Pools.

The Create Pools windows appears.3. From the Pool Type list, select Dynamic Provisioning.4. From the System Type list, select Mainframe.5. From the Multi-Tier Pool field, select Enable.

Caution: You cannot select Enable if the storage system has onlyexternal volumes with the Cache Mode set to Disable.

6. From the Pool Volume Selection field, select Auto.7. Follow the steps below to select pool-VOLs.

a. From the Resource Group list, select the resource group name ofthe pool.

b. From the Performance list, select the performance of the pool.c. In the Total Capacity list, specify the capacity of the pool.

Values are displayed in Total Pool Volumes and Total Capacity.These values are greater than the specified value of the pool capacity.If you change the pool configuration, perform steps d, e, and f.

d. Click Change Pool Configuration.The Change Pool Configuration Pattern window appears. You canchange the pool configuration that is automatically selected.

e. From the Pool Configuration Patterns table, select the poolconfiguration row. Then click Select

Note:

• You can select the pool configuration on a parity group basis.• The priority of the pool configuration is determined by these

conditions:Priority 1: There is no free space in the parity group and one LDEVexists in the group.Priority 2: There is no free space in the parity group and multipleLDEVs exist in the group.Priority 3: There is free space in the parity group and multipleLDEVs exist in the group.

• The following items are not displayed in the Pool ConfigurationPatterns table:Parity groups with LDEVs that cannot be used as pool-VOLs.Pool configuration patterns that contain more than 1,024 LDEVs.

f. Click OK.The information in the Pool Configuration Patterns table is appliedto Total Pool Volumes and Total Capacity.

8. In the Pool Name text box, enter the prefix and initial number of thepool. The pool name may consist of up to 32 characters.


Prefix: Case-sensitive, alphanumeric characters that begin the poolname.Initial Number: From 1 to 9 digits that follow the prefix.

9. Click Options.10. In the Initial Pool ID text box, type the number of the initial pool ID,





14. Configure Dynamic Tiering for Mainframe with the following steps.From the Tier Management option, select Auto or Manual.

a. The selection is usually Auto which allows performance monitoringand tier relocation to be performed automatically.If you select Manual, use the Command Control Interface or HitachiDevice Manager - Storage Navigator to manually perform performancemonitoring and tier relocation.

b. From the Cycle Time option, select the cycle for performancemonitoring and tier relocation.When you select 24 Hours (default value):Performance monitoring and tier relocation is performed once a dayIn the Monitoring Period field, set the time to start and endperformance monitoring. The default value is 00:00 to 23:59.Set one or more hours between the starting and ending times. If youspecify a starting time that is later than the ending time, theperformance monitoring continues until the ending time on the nextday.You can view the information gathered by performance monitoringwith Hitachi Device Manager - Storage Navigator or the CommandControl Interface.When you select 0.5 Hours, 1 Hour, 2 Hours, 4 Hours, 8 Hours:Performance monitoring is performed every hour that is selected,starting at 00:00.You cannot set a specific time to start performance monitoring.

Caution: When Auto is set, all the V-VOL pages may not be completelymigrated in one cycle. In the next cycle, migration starts by updatinginformation for the last processed V-VOL. At that point, the collection ofperformance monitoring information is switched to the current cycle.


15. From the Monitoring Mode option, select Period Mode or ContinuousMode.If you perform tier relocation in a specified cycle or you do not need tospecify the Monitoring Mode option, select Period Mode. If youperform tier relocation weighted to the monitoring result of the pastperiod, select Continuous Mode

16. From the Relocation Speed option, select the page relocation speed touse when performing relocation.You can set the speed to: 1(Slowest), 2(Slower), 3(Standard),4(Faster), and 5(Fastest). The default is 3(Standard). If you want toperform tier relocation at high speed, use the 5(Fastest) setting. If thespeed specified is slower than 3(Standard), the data drive load is lowwhen tier relocation is performed.

17. In the Buffer Space for New page assignment text box, enter aninteger value from 0 to 50 as the percentage (%) for each tier.A default value depends on the data drive type of the pool-VOL in eachtier. The default value of SSD is 0%. The default value of a type otherthan SSD is 8%.

18. In the Buffer Space for Tier relocation text box, enter an integer valuefrom2 to 40 as the percentage (%) to set for each tier.The default value is 2%.

19. Click Add.The created pool is added to the Selected Pools table. If invalid valuesare set, an error message appears. If Detail is clicked when you select arow, the Pool Property window appearsThe Pool Type, Multi-Tier Pool,Pool Volume Selection, and PoolName must be set. If the required items are not registered, you cannotclick Add.If you select a row and click Detail, the Pool Properties windowappears. If you select a row and click Remove, the message appearsasking whether you want to remove the selected row or rows. If you wantto remove the row, click OK.




Working with DP-VOLs

About DP-VOLsDynamic Provisioning for Mainframe requires the use of DP-VOLs, which arevirtual volumes with no physical memory space. In Dynamic Provisioning forMainframe, multiple DP-VOLs can be created.

A DP-VOL is a volume in a thin provisioning storage system. It is the virtualvolume from a DP pool. Data in the DP pool is used via a DP-VOL. A DP-VOLis a virtual LU to some hosts.

On mainframe systems, 3390-A is the supported emulation type on a DP-VOL.

Relationship between a pool and DP-VOLsBefore you can use Dynamic Provisioning for Mainframe, a DP-VOL and a poolare required. Dynamic Provisioning for Mainframe uses the pool volumes in apool through the DP-VOLs.

Creating V-VOLsThe Storage Administrator (Provisioning) role is required to perform this task.

1. You can create LDEVs from the following tab windows:

¢ The LDEVs tab, which appears when Logical Devices is selected.¢ The Pools tab, which appears when Pools is selected.¢ The Virtual Volumes tab, which appears when a pool in Pools is

selected.2. Click Create LDEVs.

The Create LDEVs window appears.3. From the Provisioning Type list, confirm Dynamic Provisioning is

selected.If not, select Dynamic Provisioning from the list.

4. In the System Type option, select a system type.To create mainframe volumes, select Mainframe.

5. From the Emulation Type list, confirm 3390-A is selected.6. From the Multi-Tier Pool field, select Enable when you create the V-VOL

for Dynamic Tiering for Mainframe, and select Disable when you do notcreate one.If no pool is set to Enable in Dynamic Tiering for Mainframe, Disable isfixed.

7. If you create TSE-VOL, select Enable in the TSE Attribute option. If notcreated, select Disable.If you do not have the license of Compatible Software for IBM®FlashCopy® SE, you can select only Disable in TSE Attribute. In


addition, if there is no LDEV IDs that can be used as TSE-VOL, you canselect only Disable in TSE Attribute.

Note:

• You can specify the TSE Attribute function only when selectingMainframe in the System Type option.

• You can specify the TSE Attribute function only when selectingDisable in the Multi-Tier Pool field.

• For TSE-VOL, if the relating pool ID is the odd number, the oddnumber is automatically assigned as the CU number for the LDEV tocreate. If the relating pool ID is the even number, the even number isautomatically assigned as the CU number for the LDEV to create.

8. Select the pool according to the following steps.

a. From the Drive Type/RPM list in Pool Selection, select the datadrive type and RPM.

b. From the RAID level list, select the RAID level.c. Click Select Pool.

The Select Pool window appears.d. In the Available Pools table, select a pool.

Note: You can specify a pool when creating DP-VOLs if the pool has astatus of one of the following:

• Normal status• Exceeded Threshold status• In progress of pool capacity shrinkingYou can select only one pool. When Enable is selected in step 6, theDynamic Tiering for Mainframe-pools appear, and when Disable isselected, only the non-Dynamic Tiering for Mainframe-pools appear.Perform the following if necessary:

• Click Filter to open the menu, specify the filtering, then Apply.• Click Options to specify the units of pools or the number of rows

to be displayed.e. Click OK.

The Select Pool window closes. The selected pool name appears inSelected Pool Name (ID), and the total capacity of the selectedpool appears in Selected Pool Capacity.

9. In the LDEV Capacity text box, enter the DP-VOL capacity to be created.You can enter the capacity within the range of figures displayed below thetext box. The capacity unit is fixed to Cyl.

10. In the Number of LDEVs text box, enter the number of LDEVs to becreated.You can enter the number of LDEVs within a range of the figuresdisplayed below the text box.

11. In the LDEV Name text box, enter the DP-VOL name.


In the Prefix text box, enter the alphanumeric characters, which arefixed characters of the head of the DP-VOL name. The characters arecase-sensitive.In the Initial Number text box, type the initial number following theprefix name, which can be up to 9 digits.You can enter up to the 32 characters including the initial number.

12. Click Option.13. In the Initial LDEV ID field, make sure that LDEV ID is set.

To confirm the used number and unavailable number, click View LDEVIDs to display the View LDEV IDs window.In the table, used LDEV numbers appear in blue, unavailable numbersappear in gray, and unused numbers appear in white. LDEV numbers thatare unavailable may be already in use, or already assigned to anotheremulation group (group by 32 LDEV numbers).When a mainframe volume or multi-platform volume is created,corresponding LDEV numbers cannot be specified if these values are notidentical: - model/serial numbers of the virtual storage machine and thestorage system - LDEV ID and the virtual LDEV ID

Note: When you create TSE-VOL if you select the pool and display theView LDEV IDs window, the displaying when the selected pool ID is anodd number is different from the displaying when the selected pool ID isan even number. If the selected pool ID is an odd number, all the LDEVIDs belonging to the CU whose ID is an even number are displayed asdisabled (the cell color is gray). If the selected pool ID is an evennumber, all the LDEV IDs belonging to the CU whose ID is an odd numberare displayed as disabled (the cell color is gray).

14. In the Initial SSID text box, type the 4-digit SSID of a hexadecimalnumber (0004 to FFFE).To confirm the created SSID, click View SSID to display the View SSIDwindows.

15. From the Cache Partition list, select CLPR.16. From the MP Blade list, select a MP blade.

Select a MP blade to be used by the LDEVs. If you assign a specific MPblade, select the ID of the MP blade. If you can assign any MP blade, clickAuto.

17. From the Tiering Policy field, select the tiering policy to be used by theLDEVs. If you assign a specific tiering policy, select any policy. All(0) isselected by default. You can change a level from Level1(1) to Level5(5) orfrom Level6(6) to Level31(31). You can specify the function when theMulti-Tier Pool is enabled.

18. From the New Page Assignment Tier list, select a new pageassignment tier. You can select from levels High, Middle, and Low.You can specify the function when the Multi-Tier Pool is enabled.

19. In the Relocation Priority option, select a priority.


To relocate the LDEV preferentially, set Prioritize. You can selectDefault or Prioritize. You can specify this function when the Multi-TierPool is enabled.

20. If necessary, change the settings of the V-VOLs.You can change the following settings:

¢ Editing SSIDClick Edit SSIDs to open the Edit SSIDs window.

¢ Changing the LDEV settingsClick Change LDEV Settings to open the Change LDEV Settingswindow.

21. If necessary, delete a row from the Selected LDEVs table.Select a row to be deleted, then click Remove.

22. Click Add.The created V-VOLs are added to the right Selected LDEVs table. Ifinvalid values are set, an error message appears.The Provisioning Type, System Type, Emulation Type, PoolSelection, Drive Type/RPM, RAID Level, LDEV Capacity, andNumber of LDEVs field must be set. If these required items are notregistered, you cannot click Add.


24. In the Task Name in the text box, enter the task name.You can enter up to 32 ASCII characters and symbols in all, except for\ / : , ; * ? " < > |. "yymmdd-window name" is entered as a default.


Editing a DP-VOL's SSIDThe Storage Administrator (Provisioning) role is required to perform this task.

Before registering a DP-VOL, you may need to edit the DP-VOL's SSID. TheSSID is a hexadecimal value.

1. In the Selected LDEVs table in the Create LDEVs window, click EditSSIDs.The Edit SSIDs window opens. The SSIDs table shows the SSID existingand to be added.

2. If you want to change the SSID, select the appropriate LDEV, then clickChange SSIDs.

3. In the Change SSIDs window, type the new SSID in hexadecimalformat, then click OK

4. In the Edit SSIDs window, click OK.5. In the Create LDEVs window, click Finish.


6. In the Confirm window, confirm the settings, then click Apply.If Go to tasks window for status is checked, the Tasks window opens.

Changing DP-VOL settingsThe Storage Administrator (Provisioning) role is required to perform this task.

Before registering a DP-VOL, you may need to change the DP-VOL settings.

1. In the Selected LDEVs table in the Create LDEVs window, select anLDEV, then click Change LDEV Settings.

2. In the Change LDEV Settings window, you can change the setting ofLDEV Name, Initial LDEV ID, or MP Blade.

¢ If you change LDEV Name, specify the prefix characters and theinitial number for this LDEV.

¢ If you change Initial LDEV ID, specify the number of LDKC, CU,DEV, and Interval. To check used LDEVs, click View LDEV IDs toconfirm the used LDEVs. The View LDEV IDs window opens.

Caution: You cannot change the LDEV ID when you select a TSE-VOLin one of the following conditions:

• Selecting TSE-VOLs and other volumes at the same time.• Selecting together the TSE-VOL related to the pool whose ID is

the odd number and the TSE-VOL related to the pool whose ID isthe even number.

¢ If you change MP Blade, click the list and specify the MP blade ID. Ifthe specific MP blade is specified, select the MP blade ID. If any MPblade is specified, click Auto.

3. Change the settings, then click OK.4. In the Create LDEVs window, click Finish.5. In the Confirm window, click Apply.

The setting is changed.If Go to tasks window for status is checked, the Tasks window opens.

Removing the DP-VOL to be registeredThe Storage Administrator (Provisioning) role is required to perform this task.

If you do not want to register the DP-VOL, you can remove it from theregistering task.

1. In the Selected LDEVs table in the Create LDEVs window, select theLDEV, then click Remove.The message appears asking whether you want to remove the selectedrow or rows. Click OK.

2. Click Finish.3. In the Confirm window, click Apply.


The LDEV is removed.If Go to tasks window for status is checked, the Tasks window opens.

Monitoring capacity and performance

Monitoring pool capacityThe storage system monitors the pool's free capacity in accordance withthreshold values defined when you create pools. If the pool capacity reachesthe threshold values, warnings are issued as SIMs and as SNMP traps to theopen-systems host.

You can provision a larger virtual capacity beyond the pool capacity by usingDP-VOLs of Dynamic Provisioning for Mainframe. However, when the pool'sfree capacity is depleted, you can lose access to DP-VOLs that require morepool capacity. For example, if the pool usage rate is 100% due to increasedwrite operations, then I/O is not accepted and I/O will be stopped for a DP-VOL that failed to receive needed pool capacity. Therefore, you shouldcarefully monitor the pool usage or pool free capacity, as well as the level ofprovisioned virtual capacity.

Monitoring performanceYou can monitor system performance using Performance Monitor. For moreinformation, see the Hitachi Virtual Storage Platform G1000 PerformanceGuide.

You can monitor information on pools and DP-VOLs using Command ControlInterface (CCI). For more information, see the Hitachi Command ControlInterface User and Reference Guide.

The following activities help you to monitor and control performance of theDP-VOL. Collecting monitor information and subsequent tuning may increasethroughput and the operating rates.

• Collecting monitor information. Collecting the following monitorinformation helps you determine the pool load (including the accessfrequency, the trend of pool usage rates, and the access load upon datadrives) and DP-VOL load (including the access frequency and the trend ofpool allocation rates). You can then use this monitor information to tunethe appropriate allocation.

¢ Access frequency of DP-VOL, read hit rates, and write hit rates (usingPerformance Monitor)

¢ Usage rates of property groups of pools (using Performance Monitor)¢ Pool usage and elapsed time of pool usage (using Hitachi Device

Manager - Storage Navigator).¢ DP-VOL usage (stored data rates) and elapsed time of pool usage

(using Hitachi Device Manager - Storage Navigator).


¢ Dynamic Tiering for Mainframe performance monitoring of poolstorage

• Possible tuning actions (without Dynamic Tiering for Mainframe).The following techniques using ShadowImage for Mainframe or HitachiTiered Storage Manager will move a DP-VOL.

¢ The DP-VOL is copied using ShadowImage for Mainframe from a poolwith an I/O bottleneck. For more information, see the HitachiShadowImage® for Mainframe User Guide.

¢ When normal volumes exist in the same parity group as the pool-VOL,Hitachi Tiered Storage Manager can be used to move the normalvolume to another parity group that is not shared with a pool-VOL.For more information, see the Hitachi Command Suite Software UserGuide (MK-90HC172).

¢ ShadowImage for Mainframe copies a DP-VOL with a high I/O load toa pool with a lower access level to adjust the pool load.

Managing I/O usage rates example

The following figure illustrates an example of managing I/O usage rates.

Tuning with Dynamic Tiering for MainframeIf Dynamic Tiering for Mainframe is active on your storage system, you canmonitor access frequency and performance use, and while Dynamic Tiering


for Mainframe automatically relocates data to the most suitable data drive(tier). You can configure monitoring to be automatic or manual. In bothcases, relocation of the data is automatically determined based on monitoringresults.

For details, see Dynamic Tiering for Mainframe on page 4-15

Thresholds

Pool utilization thresholdsDynamic Provisioning for Mainframe monitors pool capacity using thresholds.A threshold is the proportion (%) of used capacity of the pool to the total poolcapacity. Each pool has its own pool threshold values.

• Warning Threshold: Set the value between 1% and 100%, in 1%increments. The default is 70%.

• Depletion Threshold: Set the value between 1% and 100%, in 1%increments. The default is 80%.

Pool usage over either threshold will cause a warning to be issued in the formof SIMs (Service Information Messages) to Hitachi Device Manager - StorageNavigator and SNMP (Simple Network Management Protocol) traps to theopen-systems host. For more information on SNMP traps and the SNMPManager, see the Hitachi SNMP Agent User Guide. See Working with SIMs onpage 4-95 for more information about SIMs.

The following figure illustrates a total pool capacity of 1 TB, WarningThreshold of 50%, and Depletion Threshold of 80%. If the used capacity ofthe 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 andexceeds the Depletion Threshold (80%), a SIM and an SNMP trap arereported again.

Note that in this scenario, if the actual pool usage percentage is 50.1%, only50% appears on the Hitachi Device Manager - Storage Navigator windowbecause the capacity amount is truncated after the decimal point. If thethreshold is set to 50%, a SIM and an SNMP trap are reported even thoughthe pool usage percentage appearing on the screen does not indicate anexceeded threshold.


Pool subscription limitThe value of using subscription limit is to manage the maximum amount ofover-provisioning that is acceptable for a pool. By managing the poolsubscription limit, you can control the potential demand for storing data thatmight exceed the pool capacity.

The subscription limit is the ratio (%) of the total DP-VOL capacity that hasbeen configured to the total capacity of the pool. When the subscription limitis set, you cannot configure another DP-VOL if the new DP-VOL capacitywould cause the subscription limit to be exceeded.

For example, if the pool capacity is 100 GB and the subscription limit is150%, you can configure up to a total of 150 GB of capacity to the DP-VOLsrelated to the pool.

The following figure depicts setting the subscription limit of pool capacity.

Monitoring total DP-VOL subscription for a pool

You can configure the Subscription Limit of total DP-VOL capacity to poolcapacity. This prevents a new DP-VOL capacity that exceeds the configuredsubscription limit from being allocated and is associated with the pool. If youspecify more than 100% as the Subscription Limit or the subscription limit isnot set, you must monitor the free capacity of the pool because it is possiblethat writes to the DP-VOLs may exceed pool capacity. For details about theSubscription Limit, see Create Pools window on page E-19.

The used value displayed on the cell for Current in the Subscription (%) istruncated after the decimal point of the calculated value. Therefore, theactual percentage of DP-VOL assigned to the pool may be larger than thevalue displayed on the window. If you create a new DP-VOL of the same sizeas the existing DP-VOL, the larger size of capacity which is displayed on theCurrent cell is necessary.

For example, if 262,668 Cyl V-VOL is assigned to a 41,574 cylinders pool, thecapacity (%) is calculated as follows:


(262668÷41574)x100=631.80....(%)In this case, 631 (%) is displayed on the cell for Current in theSubscription (%). If you create a new V-VOL of the same size as theexisting V-VOL, 632 (%) or more remaining capacity is necessary.

Changing pool thresholdsThe Storage Administrator (Provisioning) role is required to perform this task.

1. In the Hitachi Device Manager - Storage Navigator main window, in theStorage Systems tree, select Pool.The pool name appears below Pool.

2. From the Pools table, select the pool with the threshold you want tochange.

3. Click More Actions, then select Edit Pools.4. In the Edit Pools window, check Warning Threshold or Depletion

Threshold.5. Type the threshold values in the text box.

The threshold value can be within the range of values indicated below thetext box. The Depletion Threshold value can be equal to or greater thanthe Warning Threshold.



Changing the pool subscription limitThe Storage Administrator (Provisioning) role is required to perform this task.

1. In the Hitachi Device Manager - Storage Navigator main window, in theStorage Systems tree, select Pool.

2. From the Pools table, select the pool with the subscription limit you wantto change.

3. Click More Actions, then select Edit Pools.4. In the Edit Pools window, check Subscription Limit, then type the

subscription limit percentage.If the subscription limit is blank, then it is disabled, and any amount ofDP-VOLs can be created regardless of the pool free capacity.




Working with SIMs

About SIMsDynamic Provisioning for Mainframe provide Service Information Messages(SIMs) to report the status of the DP-VOLs and pools. The SIM level isModerate. If an event associated with a pool occurs, a SIM and an SNMP trapare reported.

An example of a SIM condition is if the actual pool usage rate is 50.2%, butonly 50% is displayed because the capacity amount is truncated after thedecimal point. If the threshold is set to 50%, a SIM and an SNMP trap arereported, even though the pool usage rate displayed on the GUI does notindicate the threshold is exceeded.

SIM reference codesThe following table provides information about SIM reference codesassociated with Dynamic Provisioning for Mainframe or Dynamic Tiering.

SIM Code(XXX =

hexadecimal pool

number)

Event Thresholds orValues

Types of reports

Is thereport

notifiedto thehost?

Does itneed

completionoperations

fromHitachiDevice

Manager -Storage

Navigator?

Does itneed

operationsby the

operator?

620XXX Pool usage levelexceeded theWarningThreshold

1% to 100% (in1% increments).Default: 70%

Yes Yes No

622XXX Pool is full 100% Yes Yes No

623XXX Error occurred inthe pool

Not applicable Yes No Yes

624000 No space in theshared memory

Not applicable Yes Yes Yes

625000 Pool usage levelcontinues toexceed thehighest poolthreshold. SOM734 must beenabled.

Highest poolthreshold

Yes Yes No

626XXX Pool usage levelexceeded the

1% to 100% (in1% increments).Default: 80%

Yes Yes No


SIM Code(XXX =

hexadecimal pool

number)

Event Thresholds orValues

Types of reports

Is thereport

notifiedto thehost?

Does itneed

completionoperations

fromHitachiDevice

Manager -Storage

Navigator?

Does itneed

operationsby the

operator?

DepletionThreshold

627XXX Pool-VOL isblocked

Not applicable Yes No Yes

Automatic completion of a SIM Some SIMs are completed automatically when you resolve the problem thatcaused the SIM. SOM 734 must be enabled for automatic completion of aSIM. Automatic completion of a SIM removes it from the system with noadditional manual intervention. After the SIM is automatically completed, thestatus of the SIM changes to completed.

The following SIMs are automatically completed when you resolve theproblem causing the SIM.

• SIMs 620XXX, 625000, and 626XXX are automatically completed if youincrease pool capacity by adding pool-VOLs because the condition thatcaused the SIM removed.

• SIMs are automatically completed in the following cases:

¢ SIM 620XXXIf the usage level of DP pool number XXX falls below the warningthreshold, SIM is automatically completed.

¢ SIM 625000If the usage level of each DP pool in all pools of the storage systemfalls below the depletion threshold, SIM is automatically completed.

¢ SIM 626XXXIf the usage level of DP pool number XXX falls below the depletionthreshold, SIM is automatically completed.

Manually completing a SIMThe Storage Administrator (System Resource Management) role is required toperform this task.

Some SIMs must be manually completed to clear them from the system.


After the trouble that caused the SIM is solved, you can manually completethe SIM. After manually completing a SIM, the status of the SIM changes tocompleted. If you complete the SIM before the underlying cause is solved,the SIM may reoccur.

1. Perform the troubleshooting associated with the issued SIM. For detailsabout troubleshooting, see Troubleshooting Dynamic Provisioning forMainframe on page 6-2.


3. Click More Actions, then select Complete SIMs.ORFrom Pool in the Actions menu, select Complete SIMs.The Complete SIMs window opens.

4. In the Confirm window, confirm the settings, in Task Name type aunique name for this task or accept the default, then click Apply.It takes time if many SIMs need to be completed.If Go to tasks window for status is checked, the Tasks window opens.

You can check whether a SIM completes successfully in the Hitachi DeviceManager - Storage Navigator main window.

Managing pools and DP-VOLs

Viewing pool informationThe Storage Administrator (Provisioning) role is required to perform this task.


2. View the pool information.


For details about the window for pool information, see Pools window onpage E-3 and Pools: Volume tabs on page E-9.

Viewing used pool capacityThe Storage Administrator (Provisioning) role is required to perform this task.

Viewing the used capacity for each pool


2. The used pool capacity of pools appears on the Used column in the Poolstab.


For details about the window for pool information, see Pools window onpage E-3 .

Viewing formatted pool capacityThe Storage Administrator (Provisioning) role is required to perform this task.


2. From the Pools table on the right, click the row of a pool you want toconfirm the free pool capacity.

3. Click More Actions to select View Pool Management Status.The View Pool Management Status window appears.

Following are cases that the free space of the pool is not formatted. In thosecases, the free space of the pool may not increase:

• Pools other than the selected pool are being formatted.• The pool usage level reaches up to the warning threshold or the depletion

threshold.• The selected pool is blocked.• I/O loads to the storage system are high.


• The cache memory is blocked.• Pool-VOLs in the selected pool are blocked.• Pool-VOLs which are external volumes in the selected pool are blocked.• Correction access executes to the pool-VOL in the selected pool.

Note: Following are cases that the formatted pool capacity may decrease:

• New pages are being allocated.• LDEV format is being performed on the pool-VOL.• Correction copy is being executed.

Viewing the progress of rebalancing the usage level among paritygroups



2. From the Pools table on the right, click the row of a pool you want toconfirm the progress of rebalancing the usage level among parity groups.

3. Click More Actions to select View Pool Management Status.The View Pool Management Status window appears.

Note: Following are cases that the progress ratio may not increase:

• The usage level is being rebalanced among the parity groups in poolsother than the selected pool.

• Tier relocation is performed.

Increasing pool capacityThe Storage Administrator (Provisioning) role is required to perform this task.

Adding the pool-VOL to the pool created for Dynamic Provisioning forMainframe or Dynamic Tiering for Mainframe increases the pool capacity. Theamount of pool capacity registered in the pool represents the pool capacity.You need to check the pool free capacity to determine if additional poolcapacity is required. You cannot increase the pool capacity while it is beingshrunk.

Notes on using Dynamic Provisioning for Mainframe

• The internal volume, and the external volume whose Cache Mode is setto Disable cannot coexist.

• The external volume whose Cache Mode is set to Enable, and theexternal volume whose Cache Mode is set to Disable cannot coexist.


Notes on using Dynamic Tiering for Mainframe

• When pool-VOLs with the available monitoring information are added in apool, tier relocation is performed. When pool-VOLs with no availablemonitoring information are added in a pool, the page usage rate isaveraged out in a tier.

• If the pool-VOL is the external volume, set Enable for Cache Mode.• If the pool-VOLs are added, the tier relocation being performed stops.

To increase pool capacity:


2. From the Pools table, select the pool for which you want to increase thecapacity. You cannot increase pool capacity for multiple pools.

3. Click Expand Pool.4. In the Expand Pool window, select the pool-VOL.

a. Click Select Pool VOLs.b. In the Select Pool VOLs window, from the Available Pool Volumes

table, select the pool-VOL you want to assign, then click Add.The selected pool-VOLs are registered in the Selected Pool Volumestable.Up to 1024 volumes can be added including the volumes already inthe pool.

Note: If necessary, perform the following steps:

• From Filter option, select ON to filter the rows.• Click Select All Pages to select pool-VOLs in the table. To cancel

the selection, click Select All Pages again.• Click Options to specify the unit of volumes or the number of

rows to be viewed.• To set the tier rank of an external volume to a value other than

Middle, select a tier rank from External LDEV Tier Rank, thenclick Add.

• For a pool, you can add volumes whose Drive Type/RPM settingsare the same and whose RAID Levels are different. For example,you can add the following volumes to the same pool:Volume whose Drive Type/RPM is SAS/15K and whose RAIDLevel is 5 (3D+1P)Volume whose Drive Type/RPM is SAS/15K and whose RAIDLevel is 5 (7D+1P)

c. Click OK.The Select Pool VOLs window closes. The number of the selectedpool volumes appears in Total Selected Pool Volumes, and thetotal capacity of the selected pool-VOL appears in Total SelectedCapacity.

5. Click Finish.



Changing a pool nameThe Storage Administrator (Provisioning) role is required to perform this task.


2. From the Pools table, select the pool with the name you want to change.3. Click More Actions, then select Edit Pools.4. In the Edit Pools window, in Pool Name, specify a name for this pool.

a. In Prefix, type the characters that will become the fixed charactersfor the beginning of the pool name. The characters are case-sensitive.




Recovering a blocked poolThe Storage Administrator (Provisioning) role is required to perform this task.

This procedure is for failure recovery of a blocked pool. Ordinarily, you shouldnot need to use this procedure. A recovered pool can be used, but the formerdata is lost.


2. From the Pool table, select the pool to be recovered.3. Click More Actions, then select Restore Pools.4. In the Confirm window, confirm the settings, in Task Name type a


The recovery time for pools varies depending on pool usage or DP-VOL usage.Allow roughly 20 minutes of recovery time for every 100 TB of pool or DP-VOL usage. Recovery time may vary depending on the workload of thestorage system at the time of recovery.


Decrease pool capacity

About decreasing pool capacity

You can decrease pool capacity by deleting pool-VOLs.

When a pool-VOL is removed from a pool, all the used pages in the pool-VOLare moved to other pool-VOLs.

When you delete a pool or decrease the pool capacity, the released pool-VOLs(LDEVs) will be blocked. If they are blocked, format them before using them.If the blocked pool-VOL is an external volume, use Normal Format whenformatting the volume.

You can decrease pool capacity for up to eight tasks at the same time. Do notexecute a Command Control Interface command to also decrease thecapacity of the pool whose capacity is already in the process of beingdecreased.

You cannot decrease pool capacity while doing any of the following to a pool.

• Creating the pool.• Deleting the pool.• Increasing the pool.• Decreasing the pool.• Recovering the pool.• Stopping decreasing the pool.• Changing the threshold.• Reclaiming zero pages.• Creating DP-VOLs.• Increasing DP-VOL capacity.

While the pool capacity is being decreased, if maintenance of cache memoryis performed, if the cache memory fails, or if the I/O load to the DP-VOLrelated to the pool is high, decreasing the pool capacity process might fail. Inthis case, check the Tasks window to determine whether processing hasabnormally ended.

If the processing has ended abnormally, restore the cache memory, then trydecreasing the pool capacity again.

Note: You cannot perform the following operations on a pool while the poolvolume capacity is in the process of shrinking. Wait until shrinking completesor stop the shrinking process.

• Expand Pool• Shrink Pools• Edit Pools• Restore Pools


If you delete the pool-VOL with the pool's system area, the used capacity andthe management area will move to other pool volumes. If you delete thepool-VOL with system area, a different system area pool-VOL will be assignedautomatically according to the priority shown in the following table. A poolmust include one or more pool-VOLs.


1 SAS7.2K

2 SAS10K

3 SAS15K

4 SSD

5 External volume

If multiple pool-VOLs of the same data drive type exist, the priority of each isdetermined by internal index of the storage system.

If pool capacity is decreased soon after creating a pool or adding a pool-VOL,processing may take a while to complete.

Notes on using Dynamic Provisioning for Mainframe

You cannot delete a pool-VOL under these conditions.

• If the pool-VOL is deleted, the used capacity of the pool-VOL exceeds thepool threshold.

• If the pool-VOL is deleted, the subscription rate of the total V-VOLcapacity exceeds the subscription limit.

• If the pool-VOL with system area is deleted, more than 3.8 GB of freespace is necessary in the pool.

Notes on using Dynamic Tiering for Mainframe

• You cannot delete a pool-VOL under these conditions.

¢ If the pool-VOL is deleted, the used capacity of the pool-VOL exceedsthe pool threshold.

¢ If the pool-VOL is deleted, the subscription rate of the total V-VOLcapacity including the control information exceeds the subscriptionlimit. For details about the formula used to calculate the requiredpages for one DP-VOL including the control information, see Poolsubscription limit on page 4-93.

¢ If the pool-VOL with system area is deleted, more than 3.8 GB of freespace is necessary in the pool.

• When the pool-VOL is deleted, the pages contained in the deleted pool-VOL transfer to another pool-VOL in the same tier. If the used capacity inthe tier exceeds Rate of Free Space Newly Allocated to, theoverflowing pages transfer to another tier.

• When pool-VOLs in the tier are empty, the appropriate tier is deleted.


• Deleting the pool-VOL stops the tier relocation. The process resumes afterthe pool-VOL is deleted.

Decreasing pool capacity



2. Select the pool that contains the pool-VOLs to be deleted.3. From the Pool volumes, select the pool-VOL to be deleted.

You cannot delete pool-VOLs unless Shrinkable is applied.4. Click Shrink Pool.

The Shrink Pool window opens.The details of Before Shrinking and After Shrinking, including the poolcapacity, the used pool capacity and the free pool capacity, appears inPrediction Result of Shrinking.


Stopping the decrease of pool capacity



2. From the Pools, select the pool for which you want to stop decreasingpool capacity.

3. Click Stop Shrinking Pools.The Stop Shrinking Pools window opens.


Deleting a tier in a poolThe Storage Administrator (Provisioning) role is required to perform this task.

To delete a tier in a pool, you must delete all the pool-VOLs in the tier to bedeleted. When pool-VOLs in the tier are empty, the appropriate tier isdeleted.

If you delete a pool, its pool-VOLs (LDEVs) will be blocked. If they areblocked, format them before using them.

You cannot delete the pool-VOL when:

• Creating the pool.


• Deleting the pool.• Increasing the pool capacity.• Decreasing the pool capacity.• Restoring the pool.• Stopping decreasing the pool capacity.• Changing the threshold.• Initializing the pool capacity.• Changing the external LDEV tier rank

Notes on deleting a tier in a pool

You cannot delete a pool-VOL under these conditions.

• If the pool-VOL is deleted, the used capacity of the pool-VOL exceeds thepool threshold.

• If the pool-VOL is deleted, the subscription rate of the total V-VOLcapacity exceeds the subscription limit.

• If the pool-VOL with system area has less than 3.8 GB of free space.There must be 3.8 GB of free space in the pool in order to delete thepool-VOL with system area.

Deleting the pool-VOL stops the tier relocation. The process resumes after thepool-VOL is deleted.

To delete a tier in a pool:


2. Select the pool that contains the pool-VOLs to be deleted.The pool information appears on the right.

3. Select the Pool volumes tab and select all the pool-VOLs contained inthe tier to be deleted.You cannot delete a pool-VOL unless Shrinkable has been applied.

4. Click Shrink Pool.5. In the Shrink Pool window, verify the changes.

The details of Before Shrinking and After Shrinking, including the poolcapacity, the used pool capacity and the free pool capacity, appears inPrediction Result of Shrinking.


Deleting a poolThe Storage Administrator (Provisioning) role is required to perform this task.


When you delete a pool, its pool-VOLs (LDEVs) are blocked. If the pool-VOLsare blocked, they must be formatted before they can be reused. If theblocked pool-VOL is an external volume, select Normal Format whenformatting the volume. You can delete a pool only when all of the DP-VOLshave been deleted.


2. From the Pools table on the right, select the pool to be deleted.3. Click More Actions, then select Delete Pools.

The Delete Pools window opens.You cannot delete a pool whose usage is not 0%, or a pool for which DP-VOLs are assigned.

4. Click Finish.The Confirm window opens.To continue with the shredding operation and delete volume data, clickNext. For details about the shredding operation, see the Hitachi VolumeShredder User Guide.If the pool is blocked, you might not be able to perform shreddingoperations.


Note: When the pool-VOLs of a pool are empty, the appropriate tier isdeleted.

Changing external LDEV tier rankThe Storage Administrator (Provisioning) role is required to perform this task.

1. In the Storage Systems tree on the left pane of the top window, selectPool.The pool name appears below Pool.

2. From the Pool volumes table in the right pane, select the pool-VOL thathas the external LDEV tier rank you want to change.You cannot change the external LDEV tier rank of a pool-VOL if ExternalVolume is not displayed in the Drive Type/RPM column.

3. Click More Actions and select Edit External LDEV Tier Rank.The Edit External LDEV Tier Rank window appears.

4. From the Selected Pool volumes table, select the pool-VOL with theexternal LDEV tier rank you want to change.

5. Click Change and select the tier rank.6. Click Finish.



You can enter up to 32 ASCII characters and symbols in all, except for\ / : , ; * ? " < > |. "date-window name" is entered by default.


Increasing DP-VOL capacityThe Storage Administrator (Provisioning) role is required to perform this task.


a. In the Hitachi Device Manager - Storage Navigator main window, inthe Storage Systems tree, select Pool.The pool name appears below Pool.

b. Select the pool associated with the DP-VOL that has the capacity thatyou want to increase.

c. Select the Virtual Volumes tab.2. From the table, select the DP-VOL with the capacity you want to increase.3. Click Expand V-VOLs.

The Expand V-VOLs window opens. If the DP-VOL is selected from theLDEV table in the Logical Devices window, click More Actions, then clickExpand V-VOLs.

4. Select Specify total capacity or Specify additional capacity5. In Capacity, type the capacity amount.

Enter the LDEV capacity to two decimal places within the range of valuesindicated below the text box.

6. Click Finish.The Confirm window opens.


Changing the name of a DP-VOLThe Storage Administrator (Provisioning) role is required to perform this task.



b. Select the pool associated with the DP-VOL you want to rename.


c. Select the Virtual Volumes tab.2. From the table, select the DP-VOL you want to rename.3. Click Edit LDEVs.

When you selected DP-VOLs from the Virtual Volumes table, click MoreActions, then Edit LDEVs.The Edit LDEVs window opens.

4. Check LDEV Name and change the LDEV name, if necessary.

a. In Prefix, type the characters that will become the fixed charactersfor the beginning of the LDEV name. The characters are case-sensitive.




About releasing pages in a DP-VOLYou can reclaim zero pages and release the appropriate pages if the status ofall data in the pages in the V-VOL reads no logical records (referred to aszero page). The free capacity of a pool increases after the pages arereleased. You can perform the operation to reclaim zero pages on each V-VOLand monitor progress. For details, see View Pool Management Status windowon page E-68. If you stop the operation to reclaim zero pages, the zeropages that have been reclaimed cannot be restored.

Logically, there is no difference between a page with just zero data and thearea of a DP-VOL without a page allotted. Both are effectively identical.However, the former uses pool capacity and the latter does not.

Zero pages can be reclaimed when all the following conditions are satisfied:

• The DP-VOL is not used in conjunction with another VSP G1000 productwhich does not support reclaiming zero pages.See Using Dynamic Provisioning for Mainframe or Dynamic Tiering forMainframe with other VSP G1000 products on page 4-8.

• LDEV formatting is not being performed on the DP-VOL.• The DP-VOL is not blocked.• The DP-VOL is associated with a pool.• The pool associated with the DP-VOL is not blocked, or is full and blocked.• The DP-VOL is not TSE-VOL.

Pages that include control cylinders are not processed when releasing pagesin a DP-VOL.

While releasing pages from a DP-VOL, performance of the host I/O to the DP-VOL may temporarily decrease due to scanning for non-zero data.


If you stop an operation to reclaim zero pages in mid-stream, the pages thathave been released will remain as free pool capacity.

After an operation to reclaim zero pages, Dynamic Provisioning for Mainframeautomatically balances usage levels among parity groups in the pool. Thisrebalancing is performed on parity groups related to the pool. If you do notwant automatic balancing of the usage levels of parity groups, call the HitachiData Systems Support Center to change your configuration.

Dynamic Provisioning for Mainframe does not automatically balance the usagelevels among parity groups if the cache memory is not redundant or if thepool usage reaches up to the threshold.

If all the tracks that belong to a page assigned to a DP-VOL have no recordswritten, you can reclaim the page and return it to the pool's availablecapacity.

Caution: In the following cases, an operation of the reclaim zero pages stopsand DP-VOL pages might be not released.

• The pool-VOL accessed by the target DP-VOL is blocked.• The pool associated with the target DP-VOL is blocked while the operation

to reclaim zero pages is in progress.• Cache memory failure occurs while the operation to reclaim zero pages is

in progress.• While the operation to reclaim zero pages is in progress, the initial copy

operation of the TrueCopy for Mainframe pair, or the Universal Replicatorfor Mainframe pair is performed on the DP-VOL.

Releasing pages in a DP-VOL


You can reclaim pages in a DP-VOL to free pool capacity. If a page assignedto a DP-VOL contains no logical records, you can reclaim the page. The usedcapacity of the pool can then be decreased. Before releasing pages in a DP-VOL, see About releasing pages in a DP-VOL on page 4-109).

To release pages in a DP-VOL:



b. Select the pool associated with the DP-VOL that has pages you wantto release.

c. Select the Virtual Volumes tab.2. From the table, select the DP-VOL that has pages you want to release.3. Click More Actions, then select Reclaim Zero Pages.


The Reclaim Zero Pages window opens.You cannot release pages in a DP-VOL when the DP-VOL is not in anormal status or the DP-VOL is in the process of reclaiming zero pages.

4. In Task Name type a unique name for this task or accept the default,then click Apply.If Go to tasks window for status is checked, the Tasks window opens.

After the operation to reclaim zero pages is complete, refresh the display toupdate the Page Status. If the Page Status is not immediately updated,wait a while, then refresh the display again.

Note: Completed is displayed as the Page Status even when no pages canbe reclaimed.

If you have started the reclaiming zero pages operation, and the storagesystem is powered off the reclaiming zero pages operation will notautomatically continue after the storage system restarts.

In any of the following cases, the reclaiming zero pages will stop, and DP-VOLpages will not be released:

• LDEV formatting was performed while reclaiming zero pages.• The pool-VOL that is being accessed by the target DP-VOL was blocked.• The pool associated with the target DP-VOL was blocked while reclaiming

zero pages.• Cache memory failure occurred while reclaiming zero pages.• The DP-VOL was deleted when zero pages were reclaimed.• The initial copy operation between the TrueCopy for Mainframe pair or the

Universal Replicator for Mainframe pair was performed on the DP-VOL inwhich zero pages were being reclaimed.

Stopping the release of pages in a DP-VOL




b. Select the pool associated with the DP-VOL that has pages you wantto release.

c. Select the Virtual Volumes tab.2. From the table, select the DP-VOL that you want to stop from releasing

pages.3. Click More Actions, then select Stop Reclaiming Zero Pages.

The Stop Reclaiming Zero Pages window opens.


You cannot stop releasing the pages in a DP-VOL where zero pages arenot being reclaimed.


Enabling/disabling tier relocation of a DP-VOLThe Storage Administrator (Provisioning) role is required to perform this task.

You can enable or disable tier relocation of individual DP-VOLs or on all DP-VOLs.

DP-VOLs on which tier relocation is disabled are excluded from the targets forthe tier range calculation, and are not reflected in the performanceinformation of pools. If tier relocation is disabled on all DP-VOLs in a pool,performance information of a pool is unavailable in the View Tier Propertieswindow.


a. In the Hitachi Device Manager - Storage Navigator main window, inthe Storage Systems tree, select Pool.

b. Select the pool associated with the DP-VOL for which tier relocation isto be enabled or disabled.

c. Click the Virtual Volumes tab.2. From the table, select the DP-VOL for which tier relocation is to be

enabled or disabled.3. Click More Actions, then select Edit LDEVs.4. In the Edit LDEVs window, check tier relocation and select Enable or

Disable.Enable allows tier relocation to be performed to the DP-VOL.Disable do not allow tier relocation to be performed on the DP-VOL in thecase of both automatic and manual tier relocation.



Deleting a DP-VOLThe Storage Administrator (Provisioning) role is required to perform this task.

You cannot delete a DP-VOL if the status is online.

1. In the Hitachi Device Manager - Storage Navigator main window, in theStorage Systems tree, select Logical Devices.


The following is another way to select LDEVs.

a. In the Hitachi Device Manager - Storage Navigator main window, inthe Storage Systems tree, select Pool. The pool name appearsbelow Pool.

b. Select the pool associated with the DP-VOLs to be deleted.c. Click the Virtual Volumes tab.

2. From the table, select the DP-VOL to be deleted.Do the following, if necessary.

¢ In the Filter option, select ON to filter the rows.¢ Click Select All Pages to select all DP-VOLs in the list.¢ Click Options to specify the unit of volumes or the number of rows to

view.3. Click More Actions, then select Delete LDEVs.

The Delete LDEVs window opens.4. In the Confirm window, confirm the settings, in Task Name type a


Starting pool monitoring manuallyThe Storage Administrator (Provisioning) role is required to perform this task.


2. From the Pools, click the row of a pool you want to start monitoring.3. Click More Actions to select Monitor Pools.

The Monitor Pools window appears.4. In the Task Name text box of the Monitor Pools window, enter the task

name.You can enter up to 32 ASCII characters and symbols in all, except for\ / : , ; * ? " < > |. "date-window name" is entered by default.

5. In the Monitor Pools window, click Apply to register the setting in thetask.If the Go to tasks window for status checkbox is selected, the Taskswindow appears.

Stopping pool monitoring manuallyThe Storage Administrator (Provisioning) role is required to perform this task.


2. From the Pools, click the row of a pool you want to stop monitoring.


3. Click More Actions to select Stop Monitoring Pools.The Stop Monitoring Pools window appears.

4. In the Task Name text box of the Stop Monitoring Pools window, enterthe task name.You can enter up to 32 ASCII characters and symbols in all, except for\ / : , ; * ? " < > |. "date-window name" is entered by default.

5. In the Stop Monitoring Pools window, click Apply to register thesetting in the task.If the Go to tasks window for status checkbox is selected, the Taskswindow appears.

Starting tier relocation manuallyThe Storage Administrator (Provisioning) role is required to perform this task.


2. From the Pools, click the row of a pool you want to start monitoring.3. Click More Actions to select Start Tier Relocation.

The Start Tier Relocation window appears.4. In the Task Name text box of the Start Tier Relocation window, enter

the task name.You can enter up to 32 ASCII characters and symbols in all, except for\ / : , ; * ? " < > |. "date-window name" is entered by default.

5. In the Start Tier Relocation window, click Apply to register the settingin the task.If the Go to tasks window for status checkbox is selected, the Taskswindow appears.

Stopping tier relocation manuallyThe Storage Administrator (Provisioning) role is required to perform this task.


2. From the Pools, click the row of a pool you want to start monitoring.3. Click More Actions to select Stop Tier Relocation.

The Stop Tier Relocation window appears.4. In the Task Name text box of the Stop Tier Relocation window, enter

the task name.You can enter up to 32 ASCII characters and symbols in all, except for\ / : , ; * ? " < > |. "date-window name" is entered by default.

5. In the Stop Tier Relocation window, click Apply to register the settingin the task.


If the Go to tasks window for status checkbox is selected, the Taskswindow appears.



5Configuring access attributes

Hitachi Volume Retention Manager is required to assign access attributes tovolumes.

□ Access attributes strategies

□ Volume Retention Manager requirements

□ Access attribute restrictions

□ Keywords

□ Assigning access attribute

□ Specifying the VTOC size

Configuring access attributes 5-1Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Access attributes strategiesBy default, all the volumes are subject to read and write operations by hosts.With Volume Retention Manager, you can assign access attributes to volumesthat restrict read and/or write operations as needed. By properly settingthese attributes, you can prevent unauthorized access to data and avoid thepossibility of data being damaged, lost, or leaked.

Volume Retention Manager requirementsThe Volume Retention Manager license key must be installed. The VolumeRetention Manager software contains license keys for Volume RetentionManager and Data Retention Utility software.

Access attribute restrictionsNotes on using Volume Retention Manager with other software follow.

Performance Monitor and Volume Migration

Some software may be set to start automatically at a certain time. Forexample, if an automatic start time is set in Performance Monitor or VolumeMigration, monitoring begins at the specified time. If another product hasbeen set to start automatically, you must take one of these actions.

• Perform Volume Retention Manager operations when the other program isnot running.

• Reset the specified start time of the other product.

TrueCopy for Mainframe and Universal Replicator for Mainframe

• Do not assign an access attribute to a volume that is in use by TrueCopyfor Mainframe or Universal Replicator for Mainframe. If you assign anaccess attribute to such a volume, the job may end abnormally. If youstill want to assign an access attribute to such a volume, you must assignthe same access attribute to both the primary volume (P-VOL) and thesecondary volume (S-VOL).

• When creating a TrueCopy for Mainframe or Universal Replicator forMainframe pair and using a read-only volume as the P-VOL, use an S-VOLon a storage system on which Volume Retention Manager is enabled.If the S-VOL must be on a storage system on which Volume RetentionManager is not installed, you must do either of the following:

¢ Change the access attribute of the P-VOL to Read/Write.¢ Uninstall Volume Retention Manager on the main site.

• If you use TrueCopy for Mainframe or Universal Replicator for Mainframeto create a pair, the P-VOL and the S-VOL will have the same accessattribute. Even if you suspend or delete the pair, access attribute forthese volumes will not change.

5-2 Configuring access attributesHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

• If a remote copy pair is suspended during a TrueCopy for Mainframe orUniversal Replicator for Mainframe copy operation and you want to enablethe S-VOL read option on the RCU (mode 20), you must ensure that theaccess attribute of the S-VOL is Read/Write before you enable the S-VOLread option. If the access attribute of the S-VOL is Read-Only, mode 20will be disabled. Also, operations such as REFORMAT and REFVTOC cannotbe performed for overwriting volume serial numbers.

• If a volume has the Protect attribute, the volume can neither be used asan P-VOL nor an S-VOL.

¢ If the Protect attribute is set to the volume which is being used byTrueCopy for Mainframe, the pair might be suspended.

¢ If the Protect attribute is set to the volume which is being used byUniversal Replicator for Mainframe, the remote copy processing mightnot be continued.

ShadowImage for Mainframe, Compatible FlashCopy(R) V2, andCompatible Software for IBM(R) FlashCopy(R) SE

If a volume has the Protect attribute, the volume cannot be used as aprimary volume (P-VOL) or as a secondary volume (S-VOL) for theShadowImage for Mainframe pair. If a volume has the Protect attribute, thevolume cannot be used as a source volume (S-VOL) or as a target volume (T-VOL) for the Compatible FlashCopy(R) V2 or for Compatible Software forIBM(R) FlashCopy(R) SE relationship.

KeywordsTo control the access to a volume, assign an access attribute to each volume.One of the following access attributes can be assigned to each logical volume:

Read/Write

If a logical volume has the Read/Write attribute, hosts can perform both readand write operations on the logical volume.

All volumes have the Read/Write attribute by default.

Read Only

If a logical volume has the Read Only attribute, hosts can perform readoperations but cannot perform write operations on the logical volume.

Protect

If a logical volume has the Protect attribute, hosts cannot access the logicalvolume. Hosts cannot perform either read nor write operations on the logicalvolume.


Assigning access attributeYou can assign access attributes to volumes by using Volume RetentionManager.

Caution: Do not perform Volume Retention Manager operations if any othersoftware is running.

Supported volume emulation typesVolume Retention Manager supports the following volume emulation types:

Table 5-1 Supported volume emulation types

Supported volume emulation types Description

3390-1, 3390-2, 3390-33390-9, 3390-A, 3390-L, 3390-M

These volumes can be used only bymainframe hosts.

3390-3A, 3390-3B, 3390-3C3390-9A, 3390-9B, 3390-9C3390-LA, 3390-LB, 3390-LC3390-MA, 3390-MB, 3390-MC

These volumes can be used by mainframehosts and open-systems hosts.Notes• You must ensure that the access

attribute of these volumes is Read/Write.

• Access attributes only take effectwhen mainframe hosts accessvolumes. Access attributes does nottake effect when open-system hostsaccess volumes.

Setting Access AttributesYou can prevent volumes from unauthorized read and/or write operations.

Caution:

• When jobs that manipulate data on a volume are in progress, do notassign an access attribute to the volume. The jobs in progress might beabnormally terminated.

• When the I/Os processing from hosts is being performed, do not changethe access attribute of volumes. The I/O processing being performedmight be abnormally terminated.

Hitachi Device Manager - Storage Navigator secondary windows must bedefined for use in advance. When you select Modify from the VolumeRetention secondary window to set access attributes, other users andprograms are prevented from changing storage system settings. When youclose the secondary window, Modify mode is released. For more informationon Hitachi Device Manager - Storage Navigator secondary windows andModify mode, see the Hitachi Virtual Storage Platform G1000 MainframeSystem Administrator Guide.


To set the access attributes of one or more volumes:

1. Click Action > Mainframe Connection > Volume Retention Managerto open the Volume Retention Manager window.

2.

Click to change to Modify mode.3. Select an LDKC number from the LDKC list and a group that a CU belongs

to from the CU Group list.The tree displays a list of CUs in the specified CU group.

4. Select a CU from the tree.The table displays a list of volumes in the specified CU.

5. From the table, select and right-click a volume whose access attribute youwant to change.A pop-up menu is displayed.

6. From the pop-up menu, select Attribute to display a submenu. Then,select the desired access attribute from the submenu.

Caution: Here, the settings in the window have not been applied to thestorage system.If you want to change access attribute of other volumes, repeat this step.

7. If you want to change access attributes of volumes in other CU images,repeat steps 2 to 5. If not, go to the next step.

8. Click Apply in the Volume Retention Manager window.The settings are applied to the storage system.


Specifying the VTOC sizeWhen a host accesses a volume, the volume table of contents (VTOC) in thevolume changes to include updated access logs.

Prerequisites

• Volume has Read Only attributes.• Volume is not for a VM minidisk.• Hitachi Device Manager - Storage Navigator secondary windows must be

defined for use in advance. When you select Modify from the VolumeRetention secondary window to set access attributes, other users andprograms are prevented from changing storage system settings. Whenyou close the secondary window, Modify mode is released. For moreinformation on Hitachi Device Manager - Storage Navigator secondarywindows and Modify mode, see the Hitachi Virtual Storage PlatformG1000 Mainframe System Administrator Guide.

To specify the VTOC size:

1. Click Action > Mainframe Connection > Volume Retention Managerto open the Volume Retention Manager window.

2.

Click to change to Modify mode.3. Select an LDKC number from the LDKC list and a group that a CU belongs

to from the CU Group list.The tree displays a list of CUs in the specified CU group.

4. Select a CU from the tree.The table displays a list of volumes in the specified CU.

5. From the table, select one or more volumes that have Read Onlyattributes and right-click the selection.A pop-up menu is displayed.

6. From the pop-up menu, select VTOC.The VTOC Area dialog box appears.

7. Use the End (CC:HH) text boxes to specify the ending position of theVTOC. The text box on the left enables you to enter the cylinder number.The text box on the right enables you to enter the head number. Thestarting position of the VTOC is always 0:1 to indicate the cylindernumber 0 and the head number 1. This number cannot be changed.

8. Click OK to close the VTOC Area dialog box.

Caution: At this point, the change to the VTOC size has not been appliedto the storage system.

9. Click Apply in the Volume Retention Manager window.The settings are now applied to the storage system.


6Troubleshooting

The information in this chapter can help you troubleshoot problems whenprovisioning a storage system.

□ Troubleshooting Virtual LVI

□ Troubleshooting Dynamic Provisioning for Mainframe

□ Troubleshooting provisioning while using Command Control Interface

□ Troubleshooting Volume Retention Manager

□ Calling the Hitachi Data Systems Support Center

Troubleshooting 6-1Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Troubleshooting Virtual LVIIf a failure occurs while you are operating, see the Hitachi Storage NavigatorMessages.

For the problems and solutions regarding the Hitachi Device Manager -Storage Navigator, see the Hitachi Virtual Storage Platform G1000 MainframeSystem Administrator Guide.

Troubleshooting Dynamic Provisioning for MainframeThe following table provides troubleshooting instructions for DynamicProvisioning for Mainframe.

Problems Causes and Solutions

Pool usage level exceeds thethreshold.

Causes:• Too many DP-VOLs are associated with a pool, or

too much data is stored in a pool.• 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 Increasing pool capacity on page4-100.

• Perform the operation to reclaim zero pages inorder to release pages in which zero data arestored. See About releasing pages in a DP-VOLon page 4-109.

• Set a larger value to the threshold of the pool.See Changing pool thresholds on page 4-94.

After correcting the causes of SIM 620XXX, or620XXX and 626XXX, you need to complete the SIMs(see Manually completing a SIM on page 4-96). Ifyou do not complete the SIMs, no new SIM will occureven if the usage level increases and again exceedsthe threshold (target SIM codes are 620XXX and626XXX).SIMs 620XXX, 625000, and 626XXX are automaticallycompleted if you increase pool capacity by addingpool-VOLs, because the condition that caused theSIM is removed.Caution: You need free volumes to add as pool-VOLs. If there are no free volumes, create newvolumes or ask the Hitachi Data Systems SupportCenter to add drives. Therefore, it may take time tosolve the problem.

Cannot create a DP-VOL. Causes:• Usage of the pool has reached to 100%.• Something in the storage system is blocked.

6-2 TroubleshootingHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems


• The available capacity of DP-VOL is restricteddue to the value of Subscription-Limit set for thepool.

Solutions:• Add some pool-VOLs to the pool. See Increasing

pool capacity on page 4-100.• Perform the operation to reclaim zero pages in

order to release pages in which zero data arestored. See About releasing pages in a DP-VOLon page 4-109.

• Adjust the value of Subscription Limit for thepool. See Changing the pool subscription limit onpage 4-94.

• Ask the Hitachi Data Systems Support Center tosolve the problem.

Cannot add a pool-VOL. Causes:• 1,024 pool-VOLs are already defined in the pool.• The pool-VOL does not fill the requirements for a

pool-VOL.• Something in the storage system is blocked.Solution:• Change the setting of the LDEV to satisfy the

requirement of the Pool-VOL. See Pool-VOLrequirements on page 4-5.

A pool-VOL is blocked. SIM code627XXX is reported.

Causes:• A failure occurred in data drives greater than the

parity group redundancy. The redundancy of theparity group depends on the number of theblocked PDEVs (data drives). For example:¢ When the parity group configuration is 3D

+1P and failures occur in two or more drives,the failures are considered to have occurredin data drives beyond the parity groupredundancy.

¢ When the parity group configuration is 6D+2P and failures occur in three or moredrives, the failures are considered to haveoccurred in data drives beyond the paritygroup redundancy.

Solutions:• Ask the Hitachi Data Systems Support Center to

solve the problem.

A pool is blocked. Solutions:• Ask the Hitachi Data Systems Support Center to

solve the problem.

A pool cannot be restored. Causes:• Processing takes time, because something in the

storage system is blocked.



• Usage of the pool has reached to 100%.Solutions:• After waiting for a while, refresh the display, and

check the pool status.• Add some pool-VOLs to the pool to increase the

capacity of the pool. See Increasing pool capacityon page 4-100).



A pool cannot be deleted. Causes:• The pool usage is not 0.• External volumes are removed from the pool

before you delete the pool.• DP-VOLs have not been deleted.Solutions:• Confirm that the pool usage is 0 after the DP-

VOLs are deleted, then you can delete the pool.• Ask the Hitachi Data Systems Support Center to

solve the problem.

A failure occurs to the applicationfor monitoring the volumesinstalled in a host.

Causes:• Free space of the pool is insufficient.• Some areas in the storage system are blocked.Solutions:• Check the free space of the pool and increase the

capacity of the pool. See Increasing pool capacityon page 4-100).



When the host computer tries toaccess the port, error occurs andthe host cannot access the port.

Causes:• Free space of the pool is insufficient.• Some areas in the storage system are blocked.Solutions:• Check the free space of the pool and increase the

capacity of the pool. See Increasing pool capacityon page 4-100.





When you are operating HitachiDevice Manager - StorageNavigator, a timeout occursfrequently.

Causes:• The load on the Hitachi Device Manager -

Storage Navigator computer is too heavy, so thatit cannot respond to the SVP.

• The period of time until when time-out occurs isset too short.

Solutions:• Wait for a while, then try the operation again.• Verify the setting of the environment parameter

of Hitachi Device Manager - Storage NavigatorRMI time-out period. For information about howto set the RMI time-out period, see the HitachiVirtual Storage Platform G1000 MainframeSystem Administrator Guide.

DP-VOL capacity cannot beincreased.

Solutions:• After refreshing the display, confirm whether the

processing for increasing DP-VOL capacity meetsconditions described in Requirements forincreasing DP-VOL capacity on page 4-7.

• Retry the operation after 10 minutes or so.• Ask the Hitachi Data Systems Support Center to

solve the problem.

Cannot reclaim zero pages in aDP-VOL.

Causes:• Zero pages in the DP-VOL cannot be reclaimed

because the DP-VOL does not meet conditions forreleasing pages in a DP-VOL.

Solutions:• Make sure that the DP-VOL meets the conditions

described in Releasing pages in a DP-VOL onpage 4-110.

The DP-VOL cannot be released ifthe process to reclaim zero pagesin the DP-VOL is interrupted.

Causes:• Pages of the DP-VOL are not released because

the process of reclaiming zero pages wasinterrupted.

Solutions:• Make sure that the DP-VOL meets the conditions

described in Releasing pages in a DP-VOL onpage 4-110.

SIM code such as 620XXX,622XXX, 625000 or 626XXX wasissued.

Causes:• Pool usage level exceeds the threshold.Solutions:• Add pool-VOLs to the pool to increase the free

space in the pool. See Increasing pool capacityon page 4-100.

• Perform the operation to reclaim zero pages inorder to release pages in which zero data are



stored. See About releasing pages in a DP-VOLon page 4-109.

SIM code 624000 was issued. Causes:• The pools and DP-VOLs configuration, of which

the size is more than the supported capacity, iscreated.

Solutions:• Remove pools that are not used.• Remove DP-VOLs that are not used.• Remove Thin Image pairs that are not used.• Shrink pools capacities.

Formatted pool capacitydisplayed in the View PoolManagement Status window doesnot increase.

Causes:• Another pool is being formatted.• The pool usage level reaches up to the threshold.• The pool is blocked.• I/O loads to the storage system are high.• The cache memory is blocked.• Pool-VOLs are blocked.• Pool-VOLs which are external volumes are

blocked.Solutions:• Confirm the display again after waiting for a

while.• Add pool-VOLs to the pool to increase the free

space in the pool. For more information, seeIncreasing pool capacity on page 4-100.


• Confirm the display again after decreasing I/Oloads of the storage system.

• Contact the Hitachi Data Systems Support Centerto restore the cache memory.

• Contact the Hitachi Data Systems Support Centerto restore the pool-VOL.

• If the blocked pool-VOL is an external volume,confirm following:¢ Path blockage¢ Status of the storage system

If you are unable to solve a problem using the above suggestions, or if youencounter a problem not listed, please contact the Hitachi Data SystemsSupport Center.


If an error occurs during the operations, the error code and error messageappear in the error message dialog box. For more information about errormessages, see the Hitachi Storage Navigator Messages.

Troubleshooting provisioning while using Command ControlInterface

If an error occurs while operating Data Retention Utility or DynamicProvisioning for Mainframe while using CCI, you might identify the cause ofthe error by referring to the log appearing on the CCI window or the CCIoperation log file.

The CCI operation log file is stored in the following directory./HORCM/log*/curlog/horcmlog_HOST/horcm.logwhere

• * is the instance number.• HOST is the host name.

The following is an example of a log entry in the CCI window.

Errors when operating CCI (Dynamic Provisioning for Mainframe,SSB1: 0x2e31/0xb96d)

Error Code(SSB2) Error Contents Solutions

0x9100 The command cannot be executedbecause user authentication is notperformed.

Perform user authentication.

0xb900/0xb901/0xaf28

Error occurred when increasing DP-VOL capacity operation.

Ask the Hitachi Data SystemsSupport Center to solve theproblem.

0xb902 The operation was rejectedbecause the configuration wasbeing changed by SVP or HitachiDevice Manager - StorageNavigator, or because the DP-VOLcapacity was going to be increasedby another instance of the CCI.

Increase the DP-VOL capacity afterfinishing operations on yourstorage system, such as the VirtualLVI operation or a maintenanceoperation. See Caution inRequirements for increasing DP-VOL capacity on page 4-7.

0xaf22 The operation was rejectedbecause the specified volume isplaced online with the OS whichdoes not support EAV (ExtendedAddress Volume).

Increase the DP-VOL capacity afterthe specified volume is placedonline with the OS which supportsEAV.


Error Code(SSB2) Error Contents Solutions

0xaf24 The operation was rejectedbecause the total DP-VOL capacityexceeded the pool reservation rateafter the capacity was increased.

Specify a capacity so that the poolreservation rate will not beexceeded.

0xaf25 The operation to increase capacitycannot be performed on thespecified DP-VOL.

Check the emulation type of thespecified DP-VOL.

0xaf26 The operation was rejectedbecause of lack of cachemanagement devices due toincreased capacity.

Specify a capacity so that themaximum number of cachemanagement devices will not beexceeded.

0xaf29 Because the specified volume wasnot a DP-VOL, the operation wasrejected.

Makes sure that the volume is aDP-VOL.

0xaf2a Because the specified capacitiesare invalid or exceeded the valueimmediately below LDEV Capacityin the Expand Virtual Volumeswindow, the operation wasrejected.

To increase capacity, specify thecorrect capacity that does notexceed the value immediatelybelow LDEV Capacity in the ExpandVirtual Volumes window. See theconditions for increasing DP-VOLcapacity in Requirements forincreasing DP-VOL capacity onpage 4-7.

0xaf2b Because the specified volumeoperation was not finished, theoperation was rejected.

Re-execute the operation after abrief interval.

0xaf2c Because the shared memorycapacity is not enough to increasethe specified capacity, theoperation was rejected.

Confirm the value immediatelybelow LDEV Capacity in the ExpandVirtual Volumes window.

0xaf2e Because the specified DP-VOL wasused by other software or wasbeing formatted, the operation wasrejected.

Wait until formatting of thespecified volume is finished, or seeUsing Dynamic Provisioning forMainframe or Dynamic Tiering forMainframe with other VSP G1000products on page 4-8 and confirmwhether the DP-VOL is used withsoftware in which that the DP-VOLcapacity cannot be increased.

0xaf2f Because the configuration ofjournal volumes is being changed,the specified DP-VOL capacitycannot be expanded.

Re-execute the operation after thejournal volume configuration ischanged.

0x0b2b Because the raidcom extend ldevcommand was executed withspecifying the -cylinder option tothe DP-VOL for the open system,the operation was rejected.

Re-execute the raidcom extendldev command without specifyingthe -cylinder option.


Troubleshooting Volume Retention ManagerIf an error occurs with Volume Retention Manager, the Error Detail Dialog Boxon page C-4 appears. The Error Detail dialog box displays error locationsand error messages.

The Error Detail dialog box does not display Hitachi Device Manager - StorageNavigator error messages. To find information about Hitachi Device Manager- Storage Navigator errors and solutions, see the Hitachi Virtual StoragePlatform G1000 Mainframe System Administrator Guide.

Caution: Read and/or write operations may fail under these conditions.

• If a host computer attempts to write data to a read-only volume, thewrite operation fails and the host receives a Write Inhibit report that thehost cannot write data because of the access attribute.

• If a host computer attempts to read data from or write data to a volumethat has the Protect attribute, the attempted access is rejected and anintervention request is reported to the host.

• If the DVE function of a host computer may attempt to change thecapacity of a volume with a Read-Only or Protect access attribute, releasethe access attribute in advance. If the capacity is changed withoutreleasing the access attribute, the modified volume will become unusableand a Write Inhibit or an intervention request will be reported to the host.

• When jobs that manipulate data on a volume are in progress, do notassign an access attribute to the volume. The jobs in progress might beabnormally terminated.

• When the I/Os processing from hosts is being performed, do not changethe access attribute of volumes. The I/O processing being performedmight be abnormally terminated.

Calling the Hitachi Data Systems Support CenterIf you need to call the Hitachi Data Systems Support Center, make sure youcan provide as much information about the problem as possible, including thefollowing:

• 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 Hitachi Device

Manager - Storage Navigator.• The Hitachi Device Manager - Storage Navigator configuration information

(use the Dump Tool).• The service information messages (SIMs), including reference codes and

severity levels, displayed by Hitachi Device Manager - Storage Navigator.

The Hitachi Data Systems customer support staff is available 24 hours a day,seven days a week. If you need technical support, log on to the Hitachi DataSystems Portal for contact information: https://portal.hds.com




ACCI command reference

This appendix provides information on Hitachi Device Manager - StorageNavigator tasks and corresponding Command Control Interface commandsused in provisioning.

□ Hitachi Device Manager - Storage Navigator tasks and CCI command list

CCI command reference A-1Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Hitachi Device Manager - Storage Navigator tasks and CCIcommand list

The following lists actions (tasks) that can be performed in the Hitachi DeviceManager - Storage Navigator GUI, and the corresponding commands that canbe issued in CCI.

Item Action name CCI command

Logical Device Create LDEVs raidcom add ldev

Delete LDEVs raidcom delete ldev

Edit LDEVs raidcom modify ldev

Format LDEVs raidcom initialize ldev

Block LDEVs raidcom modify ldev

Restore LDEVs raidcom modify ldev

Assign MP Blade raidcom modify ldev

Add LUN Paths raidcom add lun

Delete LUN Paths raidcom delete lun

Expand V-VOLs raidcom extend ldev

Reclaim Zero Pages raidcom modify ldev

Shredding raidcom initialize ldev

Port/Host Group Create Host Groups raidcom add host_grp

Delete Host Groups raidcom delete host_grp

Edit Host Groups raidcom modify host_grp

Add Hosts raidcom add hba_wwn

Add to Host Groups raidcom add hba_wwn

Remove Hosts raidcom delete hba_wwn

Edit Host raidcom add hba_wwn

Create Alternate LUN Paths raidcom add lun

Edit Ports raidcom modify port

Pool Create Pools raidcom add dp_pool

Expand Pool raidcom add dp_pool

Shrink pools raidcom delete pool

Delete Pools raidcom delete pool

Edit Pools raidcom modify pool

Monitor Pools raidcom monitor pool

Stop Monitoring Pools raidcom monitor pool

Start Tier Relocation raidcom reallocate pool

A-2 CCI command referenceHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Item Action name CCI command

Stop Tier Relocation raidcom reallocate pool

Restore Pools raidcom modify pool

View Tier Properties raidcom get dp_pool

External Storage Disconnect External Volumes raidcom disconnect external_grp

Reconnect External Volumes raidcom check_ext_storage

CCI command reference A-3Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

A-4 CCI command referenceHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

BResource Partition Manager GUI

reference

This appendix describes windows, wizards, and dialog boxes of ResourcePartition Manager used when configuring resource groups.

□ Resource Group window

□ Selected resource group window

□ Create Resource Groups wizard

□ Edit Resource Group wizard

□ Add Resources wizard

□ Remove Resources window

□ Delete Resource Groups window

□ Resource Group Properties window

Resource Partition Manager GUI reference B-1Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Resource Group windowUse this window to create or delete resource groups, and to view, edit, orexport information about resource groups. You must have correct userpermissions to perform tasks on resource groups.

• Summary and buttons on page B-2• Resource Groups tab on page B-3

Summary and buttons

Item Description

Number ofResource Groups

The number of resource groups configured in your storage system.The maximum allowed is 1024.

Create ResourceGroups

Opens the Create Resource Group window where you can createone or more new resource groups. The results will appear in thiswindow.

Edit ResourceGroup

Opens the Edit Resource Group window where you can edit thename of a selected resource group.

Delete ResourceGroups

Opens the Delete Resource Groups window where you can deleteone or more resource groups selected in this window.

Export Opens a window where you can export configuration informationlisted in the table to a file that can be used for multiple purposes,such as for backup or reporting.

B-2 Resource Partition Manager GUI referenceHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Resource Groups tab

Item Description

Resource GroupName

Name of a resource group.

Resource GroupID*

Identifier of a resource group.

Number of UserGroups

Number of user groups where the resource group is assigned.

Number of ParityGroups

Number of parity groups that are assigned to the resource group.

Number of LDEVs Number of LDEVs that are assigned to the resource group.

Number of Ports Number of ports that are assigned to the resource group.

Number of HostGroups

Number of host groups that are assigned to the resource group.

Virtual StorageMachine*

Model name and serial number of the virtual storage machineassigned to the resource group.

* This item does not appear in the window by default. To display this item, change theColumn Settings of the table option.

Selected resource group windowThis window opens when you select a resource group in the Resource Groupswindow. It provides information about parity groups, LDEVs, ports, and hostgroups in the selected resource group.

• Summary on page B-3• Parity Groups tab on page B-4• LDEVs tab on page B-5• Ports tab on page B-7• Host Groups tab on page B-8

Summary

Item Description







Virtual StorageMachine



Parity Groups tab

Item Description

Parity Group ID Identifiers of parity groups that are already defined.

Capacity Capacity of each parity group.

Number of LDEVs Number of LDEVs in each parity group.

Add Resources Opens the Add Resources window where you can add one or moreresources to the resource group.

Remove Resources Opens the Remove Resources window where you can remove one ormore resources from the resource group.

Export Opens a window where you can export configuration informationlisted in the table to a file that can be used for multiple purposes,such as backup or reporting.


LDEVs tab

Item Description

LDEV ID LDEV identifiers.Some undefined LDEV IDs may appear. A hyphen appearing in theLDEV name indicates the LDEV is undefined.

LDEV Name LDEV name.

Parity Group ID Parity group identifier in which the LDEV belongs.

Pool Name (ID) Pool name and identifier in which the LDEV belongs.

Capacity Capacity of each LDEV.

Provisioning Type Provisioning type of each volume.Basic: Internal volumeDP: V-VOLs of Dynamic Provisioning or Dynamic Provisioning forMainframeExternal: External volumeExternal MF: Migration volumeSnapshot: Thin Image volume

Attribute Attribute of the volume indicating how the LDEV is being used.Command Device: Command device.Remote Command Device.JNL VOL: Journal volume.


Item Description

Pool VOL: Pool volume. The number in parentheses is the poolidentifier.Quorum Disk: Quorum disk for global-active device.TSE: TSE-VOL.Hyphen (-): Volume in which the attribute is not defined.

Journal ID Journal identifier when the attribute is JNL VOL. A hyphen indicatesthe attribute is other than JNL VOL.

Virtual StorageMachine*

Information about the virtual storage machine.• LDEV ID*: Virtual LDEV ID. If a Virtual LDEV ID is not assigned

to LDEV, this column is blank. If the setting of the LDEVvirtualization management is aborted, Transient is displayed.Failed is displayed on the Status column in the Task window.Retry the same operation.

• Device Name*: Virtual device name, which is a combination ofthe virtual emulation type, virtual LUSE volume number, andthe virtual CVS attribute. Values of the virtual emulation type,virtual LUSE volume number, and virtual CVS attribute appearonly for items that have been set. This column is blank whenthe virtual emulation type, virtual LUSE volume number, andvirtual CVS attribute are not set. If the virtual CVS attribute isset, CVS is attached as the suffix to the device name.

• SSID*: Virtual SSID. If Virtual SSID is not set for LDEV, thiscolumn is blank.

• Attribute*: Virtual LDEV attribute. If the attribute is not set forLDEV, this column is blank.



Edit VirtualizationManagementSettings

Opens the Edit Virtualization Management Settings window whereyou can set the global storage virtualization function, and edit thevirtual LDEV ID or the virtual LDEV information. For details, seeHitachi Virtual Storage Platform G1000 Provisioning Guide for OpenSystems.

Assign GADReserves*

Opens the Assign GAD Reserves window where you can set theattribute of the global-active device secondary volume for theselected LDEV. For details, see Hitachi Virtual Storage PlatformG1000 Global-Active Device User Guide.

Release GADReserves*

Opens the Release GAD Reserves window where you can removethe attribute of the global-active device secondary volume from theselected LDEV. For details, see Hitachi Virtual Storage PlatformG1000 Global-Active Device User Guide.

Export* Opens a window where you can export configuration informationlisted in the table to a file that can be used for multiple purposes,such as backup or reporting.



Ports tab

Item Description

Port ID Identifiers of the ports that are already mounted.

Attribute Attribute of the port indicating I/O flow.Initiator: Issues I/O commands to a target port when I/O isexecuted between storage systems with TrueCopy, and so on.Target: Receives I/O commands from a host.RCU Target: Receives I/O commands from an initiator when I/O isexecuted between storage systems with TrueCopy, and so on.External: Issues I/O commands to a target port of an externalstorage system with Universal Volume Manager.





Host Groups tab

Item Description

Port ID Port identifiers.

Host Group Name Name and identifier of each host group that uses a port.Some undefined host groups may appear. If a host group is notdefined, the host name is blank.

Resource GroupID*

Identifier of a resource group.

Add Resources Opens the Add Resources window where you can add one or moreresources to a resource group.

Remove Resources Opens the Remove Resources window where you can remove one ormore resources from a resource group.




Create Resource Groups wizard

Create Resource Groups windowUse this window to designate the parity groups, LDEVs, ports, and hostgroups, if any, that will make up a resource group.


Setting fields

Item Description

Resource GroupName*

Type a unique name for this resource group. the following rulesapply:• meta_resource cannot be set as a resource group name.• Names must be unique, and multiple occurrences of the

same resource group name are not allowed in one storagesystem.

• Resource names are case-sensitive.• Usable characters are alphanumeric, spaces, and symbols (!

# $ % & ' ( ) + - . = @ [ ] ^ _ ` { } ~)

Select Parity Groups Opens the Select Parity Groups window where you select one ormore parity groups to be assigned to the resource group.

Select LDEVs Opens the Select LDEVs window where you select one or moreLDEVs to be assigned to the resource group.

Select Ports Opens the Select Ports window where you select one or moreports to be assigned to the resource group.

Select Host Groups Opens the Select Host Groups window where you select one ormore host groups to be assigned to the resource group.

Add Adds your settings to the Selected Resource Groups table.

* Item requires configuration


Selected Resource Groups table

Item Description

Resource GroupName (ID)

Name and identifier of each resource group.A hyphen indicates the ID number is not assigned before settinga resource group.


Number of parity groups to be assigned to the resource group.

Number of LDEVs Number of LDEVs to be assigned to the resource group.

Number of Ports Number of ports to be assigned to the resource group.


Number of host groups to be assigned to the resource group.

Detail Opens the Resource Group Property window where you can viewdetails of the selected resource group.

Remove Removes a selected resource group.


Select Parity Groups window

Available Parity Groups table

Item Description

Parity Group ID Parity group identifiers.




Item Description

Add Adds one or more parity groups selected in the Available ParityGroups table to the Selected Parity Groups table.

Remove Removes one or more selected parity groups from the SelectedParity Groups table and relocates the parity groups to theAvailable Parity Groups table.

Selected Parity Groups table

Item Description

Parity Group ID Parity group identifiers.




Select LDEVs window

Available LDEVs table

Item Description

LDEV ID LDEV identifiers.LDEV IDs may be appear for undefined LDEVs. A hyphenappearing in columns to the right of the LDEV ID and LDEV name(for example, Parity Group ID, Pool Name ID, Capacity, and soon) indicates the LDEV is undefined.

LDEV Name LDEV names.

Parity Group ID Parity group identifier where the LDEV belongs.


Item Description

Pool Name (ID) Pool name and identifier where the LDEV belongs.



Attribute Attribute of the volume indicating how the LDEV is used.Command Device: Command deviceRemote Command Device: Remote command deviceJNL VOL: Journal volumePool VOL: Pool volume. The number in parentheses shows thepool ID.Quorum Disk: Quorum disk for global-active device.TSE: TSE-VOLHyphen (-): Volume in which the attribute is not defined

Journal ID Journal identifier when the attribute is JNL VOL. A hyphenindicates the attribute is other than JNL VOL.

Add Adds one or more LDEVs selected in the Available LDEVs table tothe Selected LDEVs table.

Remove Removes one or more selected LDEVs from the Selected LDEVstable and relocates the LDEVs to the Available LDEVs table.

Selected LDEVs table


Item Description

LDEV ID LDEV identifiers.Some undefined LDEV IDs may appear. A hyphen in the LDEVname indicates the LDEV is undefined.




Capacity Capacity of the LDEV.

Provisioning Type Displays the type of each volume.Basic: Internal volumeDP: V-VOLs of Dynamic Provisioning or Dynamic Provisioning forMainframeExternal: External volumeExternal MF: Migration volumeSnapshot: Thin Image volume

Attribute Attribute of the volume indicating how the LDEV is being used.Command Device: Command device.Remote Command Device.JNL VOL: Journal volume.Pool VOL: Pool volume. The number in parentheses is the poolidentifier.Quorum Disk: Quorum disk for global-active device.TSE: TSE-VOL.Hyphen (-): Volume in which the attribute is not defined.

Journal ID Journal identifier when the attribute is JNL VOL. A hyphenindicates the attribute is other than JNL VOL.


Select Ports window

Available Ports table

Item Description

Port ID Port identifier.

Attribute Attribute of the port indicating I/O flow.


Item Description

Initiator: Issues I/O commands to a target port when I/O isexecuted between storage systems with TrueCopy, and so on.Target: Receives I/O commands from a host.RCU Target: Receives I/O commands from an initiator when I/Ois executed between storage systems with TrueCopy, and so on.External: Issues I/O commands to a target port of an externalstorage system with Universal Volume Manager.HTP: Use this port when the external volume is mapped to thelocal storage system. Specify this port to the external storagesystem.FNP: Use this port when the external volume is mapped to thelocal storage system. Specify this port to the local storagesystem.

Add Adds one or more ports selected in the Available Ports table tothe Selected Ports table.

Remove Removes one or more selected ports from the Selected Portstable and relocates the ports to the Available Ports table.

Selected Ports table

Item Description

Port ID Port identifier.

Attribute Attribute of the port indicating I/O flow.Initiator: Issues I/O commands to a target port when I/O isexecuted between storage systems with TrueCopy, and so on.Target: Receives I/O commands from a host.RCU Target: Receives I/O commands from an initiator when I/Ois executed between storage systems with TrueCopy, and so on.


Item Description

External: Issues I/O commands to a target port of an externalstorage system with Universal Volume Manager.HTP: Use this port when the external volume is mapped to thelocal storage system. Specify this port to the external storagesystem.FNP: Use this port when the external volume is mapped to thelocal storage system. Specify this port to the local storagesystem.

Select Host Groups window


Available Host Groups table

Item Description



Add Adds one or more host groups selected in the Available HostGroups table to the Selected Host Groups table.

Remove Removes one or more selected host groups from the SelectedHost Groups table and relocates the host groups to the AvailableHost Groups table.


Selected Host Groups table

Item Description



Create Resource Groups Confirm windowConfirm proposed settings, name the task, then click Apply. The task will beadded to the execution queue.


Item Description


Name and identifier of each resource group.


Number of parity groups to be assigned to the resource group.

Number of LDEVs Number of LDEVs to be assigned to the resource group.

Number of Ports Number of ports to be assigned to the resource group.


Number of host groups to be assigned to the resource group.

Detail Opens the Resource Group Property window where you can viewthe details of the selected resource group.


Edit Resource Group wizard

Edit Resource Group window

Item Description

Resource GroupName

Type the name of the resource group after editing.• meta_resource cannot be set as a name.• Duplicate occurrences of the same resource group name are

not allowed in one storage system.• Names are case-sensitive.• Usable characters are alphanumeric, spaces, and symbols (!

# $ % & ' ( ) + - . = @ [ ] ^ _ ` { } ~)

Edit Resource Group Confirm windowConfirm proposed settings, name the task, then click Apply. The task will beadded to the execution queue.


Selected Resource Group tab

Item Description


Name and identifier of the edited resource group.







Detail Opens the Resource Group Property window where you can viewthe details of the selected resource group.


Add Resources wizard

Add Resources window

Item Description

Select Parity Groups Opens the Select Parity Group window where you can select oneor more parity groups to be added to the resource group.

Select LDEVs Opens the Select LDEVs window where you can select one ormore LDEVs to be added to the resource group.

Select Ports Opens the Select Ports window where you can select one or moreports to be added to the resource group.

Select Host Groups Opens the Select Host group window where you can select one ormore host groups to be added to the resource group.

Add Resources Confirm windowConfirm proposed settings, name the task, then click Apply. The task will beadded to the execution queue.


Selected Resource Group table

Item Description


Name and identifier of the resource group to be added to thestorage system.

Selected Parity Groups table

Item Description

Parity Group ID One or more parity group identifiers to be added to the resourcegroup.



Total Total number of selected parity groups.


Item Description

LDEV ID The identifiers of the LDEVs to be added to a resource group.


Item Description

Some undefined LDEV IDs may appear. A hyphen in the LDEVname indicates the LDEV is undefined.





Provisioning Type Provisioning type of the volume.Basic: Internal volumeDP: V-VOLs of Dynamic Provisioning or Dynamic Provisioning forMainframeExternal: External volumeExternal MF: Migration volumeSnapshot: Thin Image volume


Journal ID Journal identifier appears when the attribute is JNL VOL. Ahyphen indicates the attribute is other than JNL VOL.

Total Total number of selected LDEVs.

Selected Ports table

Item Description

Port ID Port identifiers to be added to a resource group.

Attribute Attribute of the port indicating I/O flow.Initiator: Issues I/O commands to a target port when I/O isexecuted between storage systems with TrueCopy, and so on.Target: Receives I/O commands from a host.RCU Target: Receives I/O commands from an initiator when I/Ois executed between storage systems with TrueCopy, and so on.External: Issues I/O commands to a target port of an externalstorage system with Universal Volume Manager.

Total Total number of selected ports.


Selected Host Groups table

Item Description

Port ID Port identifiers that are used by the host group.

Host Group Name Name and identifier of each host group to be added to a resourcegroup.Some undefined host groups may appear. If a group is notdefined, the host name is blank.

Total Total number of selected host groups.

Remove Resources window

Selected Resource Group table

Item Description


Name and identifier of each resource group whose resources aredeleted.

Selected Parity Groups table (when deleting parity groups)

Item Description

Parity Group ID Identifier of each parity group to be deleted from the resourcegroup.


Number of LDEVs Number of LDEVs in the parity group.

Total Total number of parity groups.


Selected LDEVs table (when deleting LDEVs)

Item Description

LDEV ID LDEV identifiers to be deleted from a resource group.Some undefined LDEV IDs may appear. A hyphen in the LDEVname indicates the LDEV is undefined.

LDEV Name LDEV names to be deleted from the resource group.

Parity Group ID Parity group ID where the LDEV belongs.

Pool Name (ID) Pool name where the LDEV belongs.




Journal ID Journal ID when the attribute is JNL VOL. A hyphen indicates theattribute is other than JNL VOL.

Total Total number of selected LDEVs.

Selected Ports table (when deleting ports)

Item Description

Port ID Port IDs that to be deleted from the resource group.

Attribute Attribute of the port indicating I/O flow.Initiator: Issues I/O commands to a target port when I/O isexecuted between storage systems with TrueCopy, and so on.Target: Receives I/O commands from a host.RCU Target: Receives I/O commands from an initiator when I/Ois executed between storage systems with TrueCopy, and so on.External: Issues I/O commands to a target port of an externalstorage system with Universal Volume Manager.


Item Description

HTP: Use this port when the external volume is mapped to thelocal storage system. Specify this port to the external storagesystem.FNP: Use this port when the external volume is mapped to thelocal storage system. Specify this port to the local storagesystem.


Selected Host Groups table (when deleting Host Groups)

Item Description

Port ID Port IDs that are used by the host group.

Host Group Name Name and ID of each host group name to be deleted from theresource group.Some undefined host group names may appear. If a host groupis not defined, the host name is blank.


Delete Resource Groups window

Selected Resource Groups table

Item Description


Name and ID of each resource group name to be deleted.


Resource Group Properties window

Resource Group Properties table

Item Description


Name and ID of a resource group name.






Item Description





Parity Groups table

Item Description

Parity Group ID Parity group IDs.



Attribute Displays the attribute of the parity group.Hyphen (-): Parity group in which the attribute is not defined.

Total Total number of selected parity groups.

LDEVs table

Item Description

LDEV ID LDEV IDs.Some undefined LDEV IDs may appear. A hyphen in the LDEVname indicates the LDEV is undefined.


Parity Group ID Parity group ID where the LDEV belongs.

Pool Name (ID) Pool name and ID where the LDEV belongs.


Provisioning Type Provisioning type of a volume.Basic: Internal volumeDP: V-VOLs of Dynamic Provisioning or Dynamic Provisioning forMainframeExternal: External volumeExternal MF: Migration volumeSnapshot: Thin Image volume

Attribute Attribute of the volume indicating how the LDEV is being used.Command Device: Command device.Remote Command Device.JNL VOL: Journal volume.Pool VOL: Pool volume. The number in parentheses is the poolidentifier.Quorum Disk: Quorum disk for global-active device.


Item Description

TSE: TSE-VOL.Hyphen (-): Volume in which the attribute is not defined.

Journal ID Journal ID when the attribute is JNL VOL. A hyphen indicates theattribute is other than JNL VOL.


Information about the virtual storage machine.• LDEV ID: Virtual LDEV ID. If a Virtual LDEV ID is not

assigned to LDEV, this column is blank.• Device Name: Virtual device name, which is a combination of

the virtual emulation type, virtual LUSE volume number, andthe virtual CVS attribute. Values of the virtual emulationtype, virtual LUSE volume number, and virtual CVS attributeappear only for items that have been set. This column isblank when the virtual emulation type, virtual LUSE volumenumber, and virtual CVS attribute are not set. If the virtualCVS attribute is set, CVS is attached as the suffix to thedevice name.

• SSID: Virtual SSID. If Virtual SSID is not set for LDEV, thiscolumn is blank.

• Attribute: Virtual LDEV attribute. If the attribute is not setfor LDEV, this column is blank.

Total Total number of selected volumes.

Ports table

Item Description

Port Name Port IDs.

Attribute Displays the attribute of each port. Initiator, Target, RCU Target,External, HTP, or FNP is displayed.


Host Groups table

Item Description

Port ID Port IDs that are used by the host group.

Host Group Name Name and ID of each host group.Some undefined host group names may appear. If a host groupis not defined, the host group is blank.




CVolume Retention Manager GUI

reference

Sections in this appendix describe the windows, wizards, and dialog boxes ofthe Volume Retention Manager.

□ Volume Retention Manager window

□ VTOC Area dialog box

□ Error Detail Dialog Box

Volume Retention Manager GUI reference C-1Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Volume Retention Manager window

Use Volume Retention Manager to change attributes of volumes.

Item Description

LDKC Select a LDKC to be displayed in the tree.

CU Group Select the CU group to be displayed in the tree.

Tree Displays a CUs of the CU group that is selected from CUGroup. When you click a CU, the table on the right displaysdetails of the volumes that belong to the CU.

Table Lists volumes and provides detailed information, such asaccess attributes, on each volume. For details, see the tablebelow.At the bottom of the table, the number of volumes on eachaccess attributes in the table is displayed.

Read/Write: Number of volumes in the selected CU thathave the Read/Write access attribute.

Read Only: Number of volumes in the selected CU thathave the Read Only attribute.

Protect: Number of volumes in the selected CU that havethe Protect attribute.

Apply Applies the requested Volume Retention Manager settingsto the storage system.

Cancel Discards the requested Volume Retention Manager settingswithout applying them to the storage system.

C-2 Volume Retention Manager GUI referenceHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

The table of Volume Retention Manager displays following items.

Item Description

LDEV Displays an LDEV ID. If an LDEV ID is displayed with anumber sign (#), the volume is an external volume.The descriptions of icons follow:

Indicates a volume that has the Read/Write attribute.

Indicates a volume that has the Read Only attribute.

Indicates a volume that has the Protect attribute.

Attribute Displays an access attribute of the volume.

Emulation Displays the device emulation type of the volume.

Capacity Displays the capacity (in cylinders) of the volume.

VTOC (CC:HH) Displays the range of the VTOC area (CC:HH – CC:HH) andthe number of tracks in the VTOC area. CC indicates acylinder number. HH indicates a head number.For example, 0:1-0:14(14Trk) indicates the following:• The range of the VTOC area is from cylinder 0 head 1

to cylinder 0 head 14.• The number of tracks in the VTOC area is 14.

VTOC Area dialog box

When a host accesses a volume, the volume table of contents (VTOC) in thevolume is updated to include updated access logs. Use VTOC Area dialog boxto specify the size of VTOC area.

Item Description

Start (CC:HH) Displays starting location (CC:HH) of the VTOC. CCindicates a cylinder number. HH indicates a head number.You cannot change the starting location.

End (CC:HH) Specifies ending location of the VTOC. You van specify acylinder number in the textbooks on the left and a headnumber in the text box on the right.

OK Saves the requested VTOC change, and closes the VTOCArea dialog box. The requested change is displayed on theVolume Retention Manager window.Note: When you click OK, the change to the VTOC size hasnot been applied to the storage system. To apply therequested change to the storage system, you must clickApply in the Volume Retention Manager window.

Volume Retention Manager GUI reference C-3Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Item Description

Cancel Closes the VTOC Area dialog box without saving therequested VTOC change.

Error Detail Dialog BoxIf an error occurs with Volume Retention Manager, the Error Detail dialog boxappears. The Error Detail dialog box displays error locations and errormessages. For troubleshooting information related to the Volume RetentionManager, see Troubleshooting Volume Retention Manager on page 6-9.

The items and descriptions of the Error Detail dialog box follow.

Item Description

Location Indicates where error occurred. If an error occurs with avolume, this column displays the LDKC number, the CUnumber and the LDEV number.

Error Message Displays error messages. For information on removingerrors, see the Hitachi Virtual Storage Platform G1000Mainframe System Administrator Guide.

Close Closes the Error Detail dialog box.

C-4 Volume Retention Manager GUI referenceHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

DLDEV GUI reference

This appendix describes windows, wizards, and dialog boxes used whencreating LDEVs.

□ Parity Groups window

□ Parity Groups tab: Internal or external volume

□ LDEVs tab: Internal or external volumes

□ Logical Devices window

□ Create LDEVs wizard

□ Edit LDEVs wizard

□ Change LDEV Settings window

□ View SSIDs window

□ Select Free Spaces window

□ Select Pool window

□ View LDEV IDs window

□ View Physical Location window

□ Edit SSIDs window

□ Change SSIDs window

LDEV GUI reference D-1Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

□ Format LDEVs wizard

□ Restore LDEVs window

□ Block LDEVs window

□ Delete LDEVs window

□ LDEV Properties window

□ Components window

□ DKC: MP Blades tab

□ Edit MP Blades wizard

□ Assign MP Blade wizard

□ View Management Resource Usage window

D-2 LDEV GUI referenceHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Parity Groups windowUse this window to view information about parity groups. Only the paritygroups assigned to the logged-on user are available.

• Summary on page D-3• Parity Groups tab on page D-4

Summary

Item Description

Capacity • Internal: Capacity of all of the parity groups in theinternal volume.¢ Free1: Free space capacity of the internal volume.¢ Total2: Total capacity of the internal volume.

• External: Capacity of all of the parity groups in theexternal volume.¢ Free1: Free space capacity of the external volume.¢ Total2: Total capacity of the external volume.

Notes:1. The control information used by the storage system, such as control cylinders, is not

included in the Free capacity.2. The total capacity of the LDEVs and the Free capacity is displayed in the Total.


Parity Groups tab

Item Description

Parity Group ID Parity group identifier of the parity group in the storagesystem.

LDEV Status Status of each LDEV in the parity group.

Normal: Normal status.

Blocked: Host cannot access a blocked volume.

Warning: Problem occurs in the volume.

Formatting: Volume is being formatted.

Preparing Quick Format: Volume is being prepared forquick formatting.

Quick Formatting: Volume is being quick-formatted.

Correction Access: Access attribute is being corrected.

Copying: Data in the volume is being copied.

Read Only: Data cannot be written on a read-onlyvolume.

Shredding: Volume is being shredded.

Hyphen (-): Any status other than the above.

RAID Level RAID level. An asterisk "*" indicates that the parity group towhich the LDEV belongs is interleaved (concatenated).Either RAID level of the parity group appears.

Base Emulation Type Emulation type of each parity group.

Capacity • Free: Capacity of the free space of each parity group.The control information used by the storage system,such as control cylinders, is not included in the Freecapacity.

• Total: The total capacity of the LDEVs and Free capacityis displayed in the Total.

Number of LDEVs • Unallocated: Number of unallocated LDEVs in eachparity group.

• Total: Total number of LDEVs in each parity group.

Drive Type/RPM Drive type and rpm in use on this LDEV.

Encryption Encryption information.Enable: encrypted parity groupDisable: non-encrypted parity groupIf the parity group in which the encryption setting is notdefined, a hyphen (-) is displayed.


Item Description

Attribute Displays the attribute of the parity group.Hyphen (-): The parity group in which the attribute is notdefined.

Resource Group Name (ID) Resource group name and ID of which this parity group is amember.

Virtual Storage Machine* Model name and serial number of the virtual storagemachine that has the parity group.

Create LDEVs Opens the Create LDEVs window.

Format LDEVs Opens the Format LDEVs window.

Edit Encryption Opens the Edit Encryption window.

Shred LDEVs* Opens the Shred LDEVs window.

Block LDEVs* Opens the Block LDEVs window.

Restore LDEVs* Opens the Restore LDEVs window.

Export Opens a window where you can export configurationinformation listed in the table to a file that can be used formultiple purposes, such as backup or reporting.

* Available when you click More Actions.

Parity Groups tab: Internal or external volumeUse this window to view information about the parity groups in the internal(or external) volume. Only the parity groups assigned to the logged-on userare available.

• Summary on page D-6• Parity Groups tab on page D-6


Summary

Item Description

Capacity • Free: The free space capacity of the internal or externalvolume. The control information used by the storagesystem, such as control cylinders, is not included in theFree capacity.

• Total: The total capacity of the LDEVs and Free capacityis displayed in the Total.

Parity Groups tab

Item Description

Parity Group ID The parity group identifiers of the parity groups in thestorage system.

LDEV Status The icons indicate the LDEV status.






Item Description








RAID Level RAID level. An asterisk "*" indicates that the parity group towhich the LDEV belongs is interleaved (concatenated).Either RAID level of the parity group appears.

Base Emulation Type Emulation type.

Capacity • Free: Capacity of the free space. The controlinformation used by the storage system such as controlcylinders is not included in the displayed capacity.

• Total: The total capacity of the LDEVs and the"Capacity - Free" capacity is displayed.

Number of LDEVs • Unallocated: Number of unallocated LDEVs.• Total: Total number of LDEVs.


Encryption Encryption information.Enable: encrypted parity groupDisable: non-encrypted parity groupIf the parity group in which the encryption setting is notdefined, a hyphen (-) is displayed.

Attribute Displays the attribute of the parity group.Hyphen (-): The parity group in which the attribute is notdefined.


Virtual Storage Machine* Model name and serial number of the virtual storagemachine having the parity group.



Edit Encryption Opens the Edit Encryption window.

Shred LDEVs* Opens the Shred LDEVs window.


Item Description

Block LDEVs* Opens the Block LDEVs window.

Restore LDEVs* Opens the Restore LDEVs window.


*Available when you click More Actions.

LDEVs tab: Internal or external volumesUse this window to view information about the LDEVs assigned to paritygroups in an internal or external volume. Only the parity groups assigned tothe logged-on user are available.

• Summary on page D-8• LDEVs tab on page D-9

Summary

Item Description

LDEV Status Current status of the LDEV.


Item Description












RAID Level RAID level. An asterisk "*" indicates that the parity group towhich the LDEV belongs is interleaved (concatenated).

Capacity • Free: Capacity of the free space. The controlinformation used by the storage system, such ascontrol cylinders, is not included in the Free capacity.

• Total: The total capacity of the LDEVs and the"Capacity - Free" capacity is displayed in the Total.


Interleaved Parity Groups Interleaved (concatenated) parity groups.

Number of LDEVs • Unallocated: Number of unallocated LDEVs.• Total: Total number of LDEVs.

LDEVs tab

Item Description

LDEV ID LDEV identifier, which is the combination of LDKC, CU, and LDEV.


Status LDEV status.




Item Description



Preparing Quick Format: Volume is being prepared for quickformatting.




Read Only: Data cannot be written on a read-only volume.



Emulation Type Emulation type.

Capacity Capacity of the selected LDEV.

Attribute Attribute of the volume indicating how the LDEV is being used.Command Device: The volume is a command device.Remote Command Device: The volume is a remote command device.JNL VOL: The volume is a journal volume.Pool VOL: The volume is a pool volume. The number in theparenthesis indicates the pool identifier.Quorum Disk: Quorum disk for global-active device.TSE: TSE-VOLHyphen (-): Volume in which the attribute is not defined


Resource group name and identifier of the LDEV.

Virtual StorageMachine1

Information about the virtual storage machine.• Model / Serial Number1: Model name and serial number of the

virtual storage machine that has LDEV.• LDEV ID1: Virtual LDEV ID. If a Virtual LDEV ID is not assigned

to LDEV, this column is blank.• Device Name1: Virtual device name, which is a combination of

the virtual emulation type, virtual LUSE volume number, and thevirtual CVS attribute. Values of the virtual emulation type,virtual LUSE volume number, and virtual CVS attribute appearonly for items that have been set. This column is blank when thevirtual emulation type, virtual LUSE volume number, and virtualCVS attribute are not set. If the virtual CVS attribute is set, CVSis attached as the suffix to the device name.

• SSID1: Virtual SSID. If Virtual SSID is not set for LDEV, thiscolumn is blank.


Item Description


Edit LDEVs Opens the Edit LDEVs window.


Delete LDEVs2 Opens the Delete LDEVs window.

Shred LDEVs2 Opens the Shred LDEVs window.

Block LDEVs2 Opens the Block LDEVs window.

Restore LDEVs2 Opens the Restore LDEVs window.


1Does not appear by default. To display this item, change the Column Settings of thetable option.2Available when you click More Actions.

Logical Devices windowUse this window to view information about logical devices. Only the LDEVSassigned to the logged-on user are available.

• Summary on page D-12• LDEVs tab on page D-13


Summary

Item Description

Number of LDEVs • Open Allocated: Number of allocated LDEVs for opensystem.

• Open Unallocated: Number of unallocated LDEVs foropen system.

• Open Reserved: Number of reserved LDEVs for theopen system.

• Open V-VOLs: Number of allocated V-VOLs for the opensystem.

• Mainframe Allocated: Number of allocated LDEVs forthe mainframe system.

• Mainframe Reserved: Number of reserved LDEVs forthe mainframe system.

• Mainframe V-VOLs: Number of allocated V-VOLs for themainframe system.

Total Number of LDEVs Total number of LDEVs.

Format/Shredding TaskStatus

Formatting n %: Displays the percentage of the progress offormatting processing.Preparing Quick Format n %: Displays the percentage ofthe progress of the preparing quick format processing.Shredding n %: Displays the percentage of the progress ofthe shredding processing.


Item Description

Blank: Displays a blank when formatting or shredding doesnot perform. If the information cannot be obtained, forexample being changed of the storage systemconfiguration, a blank is displayed.

View Migration Plans* Open the View Migration Plans window. For details, seethe Hitachi Volume Migration User Guide.

View Histories* Open the View Histories window. For details, see theHitachi Volume Migration User Guide.

*Available when you select Volume Migration.

LDEVs tab

Item Description

LDEV ID LDEV identifier, which is the combination of LDKC, CU, and LDEV.


Status LDEV status.





Preparing Quick Format: Volume is being prepared for quickformatting.




Read Only: Data cannot be written on a read-only volume.



V-VOLManagementTask1

Displays the V-VOL management task being performed on a DynamicProvisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering,or a Dynamic Tiering for Mainframe V-VOL.• Reclaiming Zero Pages: The process is in progress.• Waiting for Zero Page Reclaiming: The process has been waited.• Blank: The V-VOL management task can be performed on the

volume, but the task is not currently in process.


Item Description

• Hyphen(-): The V-VOL management task cannot be performedon the volume.

Capacity LDEV capacity.

Number of paths Number of paths set for the LDEV.


Provisioning Type Provisioning type to be assigned to the LDEV.Basic: Internal volume.External: External volume.External MF: Migration volume.Snapshot: Thin Image volume.

Attribute Attribute of the volume indicating how the LDEV is being used.Command Device: Volume is a command device.Remote Command Device: Volume is a remote command device.JNL VOL: Volume is a journal volume.Pool VOL: Volume is a pool volume. The number in parenthesesshows the pool identifier.Quorum Disk: Quorum disk for global-active device.TSE: TSE-VOLHyphen (-): Volume other than the above.

Access Attribute1 Displays the access attribute of the LDEV.

Pool Name (ID) Pool name (pool identifier).

Parity Group ID Parity group identifier.

RAID Level RAID level. An asterisk (*) indicates that the parity group that theLDEV belong to is interleaved (concatenated).

MP Blade ID1 MP blade identifier.

Encryption1 Encryption information.Enable: encrypted parity groupDisable: non-encrypted parity groupIf the parity group in which the encryption setting is not defined, ahyphen (-) is displayed.

Resource GroupName (ID)1

Resource group name and ID of which this LDEV is a member.

Virtual StorageMachine1

Information about the virtual storage machine.• Model / Serial Number1: Model name and serial number of the

virtual storage machine that has LDEV.• LDEV ID1: Virtual LDEV ID. If a Virtual LDEV ID is not assigned

to LDEV, this column is blank.• Device Name1: Virtual device name, which is a combination of

the virtual emulation type, virtual LUSE volume number, and thevirtual CVS attribute. Values of the virtual emulation type,


Item Description

virtual LUSE volume number, and virtual CVS attribute appearonly for items that have been set. This column is blank when thevirtual emulation type, virtual LUSE volume number, and virtualCVS attribute are not set. If the virtual CVS attribute is set, CVSis attached as the suffix to the device name.

• SSID1: Virtual SSID. If Virtual SSID is not set for LDEV, thiscolumn is blank.

• Attribute1: Virtual LDEV attribute. If the attribute is not set forLDEV, this column is blank.


Add LUN Paths Opens the LUN Paths window.

Edit LDEVs Opens the Edit LDEVs window.

Format LDEVs2 Opens the Format LDEVs window.

Delete LDEVs2 Opens the Delete LDEVs window.

Shred LDEVs2 Opens the Shred LDEVs window.

Delete LUN Paths2 Opens the Delete LUN Paths window.

Edit CommandDevice2

Opens the Edit Command Devices window

Block LDEVs2 Opens the Block LDEVs window.

Restore LDEVs2 Opens the Restore LDEVs window.

Assign MP Blade2 Opens the Assign MP Blade window.

Delete UUIDs2 Opens the Delete UUIDs window.

Reclaim ZeroPages2

Opens the Reclaim Zero Pages window.

Stop ReclaimingZero Pages2

Opens the Stop Reclaiming Zero Pages window.

Expand V-VOLs2 Opens the Expand V-VOLs window.

Migrate Volumes2 Opens the Migrate Volumes window. For details, see Hitachi VolumeMigration User Guide.

Force Delete Pairs(TC Pairs)2

Opens the Force Delete Pairs (TC Pairs) window. For details seeHitachi TrueCopy® User Guide or Hitachi TrueCopy® for MainframeUser Guide.

Force Delete Pairs(UR Pairs)2

Opens the Force Delete Pairs (UR Pairs) window. For details seeHitachi Universal Replicator User Guide or Hitachi UniversalReplicator for Mainframe User Guide.

Force Delete Pairs(GAD Pairs)2

Opens the Force Delete Pairs (GAD Pairs) window. For details seeHitachi Virtual Storage Platform G1000 Global-Active Device UserGuide.

Export2 Opens a window where you can export configuration informationlisted in the table to a file that can be used for multiple purposes,such as backup or reporting.


Item Description

1Does not appear by default. To display this item, change the Column Settings of thetable option.2 Available when you click More Actions.

Create LDEVs wizardUse this window to create and provision LDEVs. You can create multipleLDEVs at once when setting up your storage system.

Create LDEVs window• Setting fields on page D-17• Selected LDEVs table on page D-21


Setting fields

Item Description

Provisioning Type Select the type of LDEV.Basic: Internal volume.Dynamic Provisioning: DP-VOL.External: External volume.Snapshot: Thin Image volume.

System Type Select the system of LDEV.Open: Volume for open system.Mainframe: Volume of mainframe system.

Emulation Type Select the LDEV emulation.For open system, OPEN-V is default.For mainframe system, 3390 is default.Note: The emulation type might differ depending onthe configuration.

Multi-Tier Pool Select Enable or Disable of using Dynamic Tiering orDynamic Tiering for Mainframe.Enable: The pool for Dynamic Tiering or DynamicTiering for Mainframe is displayed in the Select Poolwindow.Disable: The pool for Dynamic Provisioning or DynamicProvisioning for Mainframe is displayed in the SelectPool window.

TSE Attribute Select whether to create TSE-VOL or not.


Item Description

Enable: TSE-VOL is created.Disable: TSE-VOL is not created.If all the following conditions are satisfied, you canspecify this item:• Selected Mainframe in the System Type• Selected Disable in the Multi-Tier Pool field

Parity Group Selection, PoolSelection, or External VolumeSelection

Select the parity group to which the LDEV is assigned.Parity Group Selection: Displayed when you createinternal volumes.Pool Selection: Displayed when you create DP-VOLs.External Volume Selection: Displayed when you createexternal volumes.

Drive Type/RPM Select the data drive type and RPM.Any: All types of disk drives and RPMs that can becontained in the system.SSD: Containing SSD (SLC, MLC) and FMD.SAS/RPM: SAS drive and RPM.External Storage: External storage system.Mixed: Mixes the data drive type.

RAID Level Select the RAID level. External Storage is selected fromthe Drive Type/RPM field, a hyphen (-) appears.

Select Free Spaces Displays the Select Free Spaces window.

Select Pool Displays the Select Pool window.

Total Selected Free Spaces Displays the number of the selected free spaces.

Total Selected Free SpaceCapacity

Displays the total capacity of the free spaces.

Selected Pool Name (ID) Displays the selected pool name and ID.

Selected Pool Capacity Displays the selected pool capacity.

LDEV Capacity • Offset boundary:¢ If you want to offset the specified LDEV

capacity by boundary, set the Offset boundaryto ON.

¢ If the emulation type is OPEN-V, Offsetboundary is set to OFF by default.

¢ If the emulation type is other than OPEN-V,Offset boundary is set to ON by default.

• Input area: Specify the LDEV capacity to create ina free space, a pool, or an external volume.

Detailed calculation of the LDEV capacity differsdepending on the specification of the unit. For details,see Virtual LVI size calculations on page 3-6.

Number of LDEVs per FreeSpace, Number of LDEVs, or

Specify the number of LDEVs to create in a free space,pool, or the external volume.


Item Description

Number of LDEVs per ExternalVolume

LDEV Name LDEV name. Specify the prefix characters and the initialnumber.• Prefix: A fixed character string.• Initial Number: The initial number of the LDEV

name.Specify the initial number according to theexamples below. You can specify up to 32characters total.Example:¢ 1: Up to 9 numbers are added (1, 2, 3... 9).¢ 08: Up to 92 numbers are added (08, 09, 10...

99).¢ 23: Up to 77 numbers are added (23, 24, 25...

99).¢ 098: Up to 902 numbers are added (098, 099,

100... 999).

Format Type Specify the format type. This appears when an internalor external volume is used.Quick Format: Quick formatting is the default formattype. You cannot select this when the provisioning typeis something other than the internal volume.Write to Control Blocks: You can select this optionwhen the external mainframe volume is created. This isdefault when selecting the external volume of themainframe system.Normal Format: Normal formatting.No Format: Volumes are not formatted.

Initial LDEV ID Specify the LDEV ID. LDKC is fixed to 00. Default of CUand DEV is 00:00.For creating multiple LDEVs, select the interval of theassigned LDEV ID from the Interval list.

View LDEV IDs Displays the View LDEV IDs windows.

Initial SSID Specify the SSID. The default is 0004.When creating multiple LDEVs, specify the beginningnumber setting to the LDEV.

View SSIDs Displays the View SSIDs window.

CLPR Cache logical partition number, displayed as ID:CLPR.

MP Blade Specify the MP blade you want to assign to the LDEV.You can select an ID from MPB0 to MPB7. If automaticassignment is enabled for one or more MPs, you canalso select Auto.If Auto is enabled, the default is Auto. If Auto isdisabled, the default is the lowest number of the MPblade.


Item Description

Tiering Policy Tiering Policy: All(0) is selected by default. You canchange a level from Level1(1) to Level5(5) or fromLevel6(6) to Level31(31). See Notes on tiering policysettings on page 4-51.You can specify this function when the Multi-Tier Pool isenabled.

New Page Assignment Tier Specify the new page assignment tier you want toassign to the LDEV. Middle is selected by default. Youcan select from the levels of High, Middle, and Low.See New New page assignment tier on page 4-54. Youcan specify this function when the Multi-Tier Pool isenabled.

Relocation Priority Specify this option if the LDEV is to be relocatedpreferentially. You can select Default or Prioritize.You can specify this function when the Multi-Tier Pool isenabled.

Add Adds the LDEVs that have settings specified in thesetting field is added to the Selected LDEVs table.

The items that can be set in this window depend on the type of volume youare creating. The following table lists the items that can be set according tovolume type.

Item Internalvolume

V-VOL foropen

system

V-VOL formainframe system

Externalvolume

Snapshotvolume

Provisioning Type Required Required Required Required Required

System Type Required Required Required Required Required

Emulation Type Required Required Required Required Required

Multi-Tier Pool N/A Required Required N/A N/A

TSE Attribute N/A Disabled Required N/A N/A

Drive Type/RPM Required Required Required Disabled N/A

RAID Level Required Required Required Disabled N/A

Select Free Spaces Required N/A N/A Required N/A

Select Pool N/A Required Required N/A N/A

Offset boundary Optional Optional N/A Optional Optional

LDEV Capacity Required Required Required Required Required

Number of LDEVs perFree Space

Required N/A N/A N/A N/A

Number of LDEVs N/A Required Required N/A Required

Number of LDEVs perExternal Volume

N/A N/A N/A Required N/A


Item Internalvolume

V-VOL foropen

system

V-VOL formainframe system

Externalvolume

Snapshotvolume

LDEV Name Optional Optional Optional Optional Optional

Format Type Required N/A N/A Required N/A

Initial LDEV ID Optional Optional Optional Optional Optional

View LDEV IDs Optional Optional Optional Optional Optional

Initial SSID Optional Optional Optional Optional Optional

View SSIDs Optional Optional Optional Optional Optional

CLPR N/A Optional Optional N/A Optional

MP Blade Optional Optional Optional Optional Optional

Tiering Policy N/A Optional Optional N/A N/A

New Page AssignmentTier

N/A Optional Optional N/A N/A

Relocation Priority N/A Optional Optional N/A N/A


Item Description

LDEV ID LDEV identifier, which is the combination of LDKC, CU,and LDEV.


Item Description

LDEV Name LDEV name, including the combination of prefixcharacters and the initial number.


Pool Name (ID) Pool name and pool identifier.


RAID Level RAID level. An asterisk "*" indicates that the paritygroup to which the LDEV belongs is interleaved(concatenated).



Format Type Format type.

SSID Storage system identifier in hexadecimal format.

CLPR Cache logical partition number, displayed as ID:CLPR.For detailed information about CLPRs, see the HitachiVirtual Storage Platform G1000 Performance Guide.

MP Blade ID MP blade identifier. If Auto is selected, the ID isautomatically assigned.

Multi-Tier Pool Indicates whether Dynamic Tiering or Dynamic Tieringfor Mainframe is enabled or disabled.Enabled: The LDEV is for Dynamic Tiering or DynamicTiering for Mainframe.Disabled: The LDEV is not for Dynamic Tiering orDynamic Tiering for Mainframe.

Tiering Policy The tiering policy name and ID for the LDEV.

New Page Assignment Tier Displays the new page assignment tier for the LDEV.

Relocation Priority Displays the relocation priority assigned to the LDEV.

Attribute Displays the attribute of the LDEV.TSE: TSE-VOLHyphen (-): Volume in which the attribute is notdefined.

Encryption Encryption information.Enable: encrypted parity groupDisable: non-encrypted parity groupIf the parity group in which the encryption setting isnot defined, a hyphen (-) is displayed.

Resource Group Name (ID) Resource group name and ID of which this LDEV is amember.

Virtual Storage Machine Displays the information about the virtual storagemachine.


Item Description

• Model / Serial Number: The model name and serialnumber of the virtual storage machine having theLDEV.

• Attribute: Virtual LDEV attribute. If the attribute isnot set for LDEV, this column is blank.

Edit SSIDs Opens the Edit SSIDs window.

Change LDEV Settings Opens the Change LDEV Settings window.

Remove Removes the added LDEV.

Create LDEVs Confirm window

Note: If multiple tasks that are connected in one wizard are executed, thiswindow shows all configured items of tasks. To show information ofconfigured items other than this topic, click Back to display related settingwindows, then click Help.


Item Description






Item Description

Pool Name (ID) Pool name (pool identifier).

RAID Level RAID level. An asterisk "*" indicates that the paritygroup to which the LDEV belongs is interleaved(concatenated).



Provisioning Type Type of LDEV.Basic: Internal volume.DP: DP-VOL.External: External volume.Snapshot: Thin Image volume.

Format Type Format type.


CLPR Cache logical partition number, in ID:CLPR format.For detailed information about CLPRs, see the HitachiVirtual Storage Platform G1000 Performance Guide.

MP Blade ID MP blade identifier. If Auto is selected, the ID isautomatically assigned.

Multi-Tier Pool Displays whether Dynamic Tiering or Dynamic Tieringfor Mainframe is enabled or disabled.Enable: The LDEV for Dynamic Tiering or DynamicTiering for Mainframe is displayed.Disable: The LDEV for Dynamic Provisioning orDynamic Provisioning for Mainframe is displayed.

Tiering Policy Displaying the tiering policy name and ID for the LDEV.

New Page Assignment Tier Displays the new page assignment tier for the LDEV.

Relocation Priority Relocation priority assigned to the LDEV.

Attribute Displays the attribute of the LDEV.TSE: TSE-VOL.Hyphen (-): Volume in which attribute is not defined.

Encryption Encryption information.Enable: encrypted parity groupDisable: non-encrypted parity groupIf the parity group in which the encryption setting isnot defined, a hyphen (-) is displayed.

Resource Group Name (ID) Resource group name and ID of which this LDEV is amember.

Virtual Storage Machine Displays the information about the virtual storagemachine.


Item Description

• Model / Serial Number: The model name and serialnumber of the virtual storage machine having theLDEV.

• Attribute: Virtual LDEV attribute. If the attribute isnot set for LDEV, this column is blank.

Edit LDEVs wizardUse this window to change the LDEV name.

Edit LDEVs windowUse this window to edit LDEV properties.

Item Description

LDEV Name Specify the LDEV name, using up to 32 characters.• Prefix: Fixed character string.• Initial Number: Initial number.

Specify the initial number according to these examples.Example:¢ 1: Up to 9 numbers are added (1, 2, 3 ... 9)


Item Description¢ 08: Up to 92 numbers are added (08, 09, 10 ...

99)¢ 23: Up to 77 numbers are added (23, 24, 25 ...

99)¢ 098: Up to 902 numbers are added (098, 099,

100 ... 999)

Tiering Policy Specify the tiering policy for the LDEV. For details about thesetting. You can specify this function only when the V-VOLsusing Dynamic Tiering or Dynamic Tiering for Mainframe areavailable. See Notes on tiering policy settings on page 4-51

New Page Assignment Tier Specify the new page assignment tier you want to assign tothe LDEV. Middle is set by default. You can select fromHigh, Middle, or Low. See New page assignment tier onpage 4-54.You can specify this function only when the V-VOLs that useDynamic Tiering or Dynamic Tiering for Mainframe areavailable.

Tier Relocation Specify Enable or Disable for the performing of the tierrelocation. You can specify this function only when the V-VOLs using Dynamic Tiering or Dynamic Tiering forMainframe are available.

Relocation Priority Specify the relocation priority assigned to the LDEV. Youcan set this function under the following conditions:• When there are V-VOLs where Dynamic Tiering or

Dynamic Tiering for Mainframe is enabled.• When the tier relocation is enabled.

Edit LDEVs Confirm windowConfirm proposed settings, name the task, then click Apply. The task will beadded to the execution queue.


Item Description







Provisioning Type Type of LDEV.Basic: Internal volume.DP: DP-VOL.External: External volume.Snapshot: Thin Image volume.

Tiering Policy Tiering policy. A hyphen is displayed for volumes otherthan Dynamic Tiering or Dynamic Tiering for Mainframevolumes.

New Page Assignment Tier Displays the new page assignment tier for the LDEV. Ahyphen (-) is displayed for volumes other thanDynamic Tiering or Dynamic Tiering for Mainframevolumes.

Tier Relocation Displays whether tier relocation is enabled or disabled.A hyphen (-) is displayed for volumes other thanDynamic Tiering or Dynamic Tiering for Mainframevolumes.

Relocation Priority Displays the relocation priority assigned to the LDEV. Ahyphen is displayed if the LDEV is the one of following:• LDEV other than Dynamic Tiering.


Item Description

• LDEV other than Dynamic Tiering for Mainframe.• The tier relocation of LDEV is set to disabled.

Change LDEV Settings windowUse this window to edit one or more LDEV properties.

Item Description

LDEV Name Specify the LDEV name, using up to 32 characters.• Prefix: Fixed character string.• Initial Number: Initial number.

Specify the initial number according to these examples.Examples:¢ 1: Up to 9 numbers are added (1, 2, 3 ... 9)¢ 08: Up to 92 numbers are added (08, 09, 10 ...

99)¢ 23: Up to 77 numbers are added (23, 24, 25 ...

99)¢ 098: Up to 902 numbers are added (098, 099,

100 ... 999)


Item Description

Initial LDEV ID Specify the LDEV identifier, which is the combination ofLDKC, CU, and LDEV. Assigns the ID at a certain intervalstarting with the ID you specify.• LDKC: Specify the LDKC number. It is fixed to 00.• CU: Specify the CU number.• DEV: Specify the LDEV number.• Interval: Specify the interval of the assigned LDEV ID.• View LDEV IDs: Opens the View LDEV IDs window.

MP Blade Select the MP blade you want to assign to the LDEV.Select any ID or Auto.Select an ID from MPB0 to MPB7. If automatic assignmentis enabled for one or more MPs, you can also select Auto.

View SSIDs windowUse this window to view storage system identifier information.

Item Description

LDKC LDKC number.

CU Control unit number.


Item Description

LDEV Boundary The range of LDEVs that can be allocated to the SSID. EachLDEV group (divided by LDEV boundary) has a unique SSID.


Select Free Spaces windowUse this window to view information about available free space slots in theparity group. Only the free spaces in the parity groups assigned to thelogged-on user are available.

Item Description


Free Space No. Sequence number for identifying free space in the parity group.

RAID Level RAID level. An asterisk "*" indicates that the parity group to whichthe LDEV belongs is interleaved (concatenated).

Capacity Capacity of free space.

Base EmulationType

Emulation type of the parity group.

Drive Type/ RPM Drive type and rpm in use on this LDEV.

Encryption Encryption information.Enable: encrypted parity groupDisable: non-encrypted parity groupIf the parity group in which the encryption setting is not defined, ahyphen (-) is displayed.

View PhysicalLocation

Opens the View Physical Location window.


Select Pool window

Available Pools table

Item Description

Pool Name (ID) Displays the pool name and pool ID.

RAID Level Displays the RAID level.

Capacity Displays information about the pool capacity.• Total: Total capacity of pool.• Used: Used pool capacity.• Used (%): Pool usage rates for pool capacity. Used (%)

displays the value which is truncated after the decimalpoint of the actual value.

Drive Type/RPM Displays the data drive type and RPM. When the volume isthe external volume, Drive Type displays ExternalStorage and the value of the external LDEV tier rank.

User-Defined Threshold(%)

Displays the pool threshold.• Warning: Warning threshold is displayed.• Depletion: Depletion threshold is displayed.

Tier Management Displays Auto or Manual according to the Tier Managementsetting when Dynamic Tiering or Dynamic Tiering forMainframe is enabled. Displays Manual for pools other thanDynamic Tiering or Dynamic Tiering for Mainframe whichare available for monitoring. For other pools, a hyphen (-) isdisplayed.

Subscription (%) Displays information about subscription of the pool.


Item Description

• Current: Percentage of the total V-VOL capacityassigned to the pool and the V-VOL capacity to becreated.

• Limit: Percentage of the subscription limit of the pool.

Detail Displays the Pool Properties window when selecting a rowand clicking this button

View LDEV IDs windowUse this window to view available, used, and disabled LDEV IDs in matrixformat. The vertical scale in the matrix represents the second-to-last digit ofthe LDEV number, and the horizontal scale represents the last digit of theLDEV number.

In the matrix, cells of used LDEV numbers display in blue, unselectable ingray, and unused in white. The LDEV numbers corresponding to any one ofthe following conditions cannot be specified:

• LDEV is already in use.• LDEV is already assigned to another emulation group (grouped every 32

LDEVs).• LDEV is not assigned to the user.• If the following values are not identical when a mainframe volume or

multi-platform volume is created: - LDEV ID and the virtual LDEV ID -model/serial numbers of the virtual storage machine and the storagesystem.


Item Description

Usage of selectedemulation type

Emulation type selected in the Create LDEVs window. SeeEmulation groups and types on page D-33 for a list.

LDEV IDs LDEV identifier, which is the combination of LDKC, CU, andLDEV.LDKC: Indicates the LDKC number.CU: Indicates the CU number.

Emulation groups and typesThe following table shows the emulation groups and emulation types formainframe systems.

Emulation group D-type (Overseas PCM) emulation type

Group 1 3390-3, 3390-A, 3390-3A, 3390-3B, 3390-3C, 3390-9,3390-9A, 3390-9B, 3390-9C, 3390-L, 3390-LA, 3390-LB,3390-LC, 3390-M, 3390-MA, 3390-MB, 3390-MC, 3390-V

The following table shows the emulation groups and emulation types for opensystems.


Group 4 OPEN-3, OPEN-8, OPEN-9, OPEN-E



Group 5 None

Group 6 OPEN-V

View Physical Location windowUse this window to view information about the physical location of where freespaces and LDEVS are assigned in a parity group.

Parity Group Property table

Item Description

Parity Group ID Parity group identifier. For an interleaved parity group, allparity groups that are contained in the interleaved paritygroup are shown.

RAID Level RAID level. An asterisk "*" indicates that the parity group towhich the LDEV belongs is interleaved (concatenated).

Capacity (Free/Total) Free capacity and total capacity of the parity group. Thecontrol information used by the storage system, such ascontrol cylinders, is not included in the Free capacity. Thetotal capacity of the LDEVs and Free capacity is displayed inthe Total.

Drive Type/ RPM Drive type and rpm in use on this LDEV.

Vendor/Model/SerialNumber

For external volumes, vendor name, model name, andserial number appear. For internal volumes, -/-/- appears.


Item Description


Physical Location table

Item Description

Physical Location No. Location where the free spaces and LDEVs are assigned.

Free Space No. Free space number. The hyphenation appears for volumesother than free spaces.

LDEV ID LDEV identifier. A hyphen (-) appears for other than LDEVIDs.

LDEV Name LDEV name. A hyphen (-) appears for volumes other thanLDEVs.

Emulation Type Emulation type. A hyphen (-) appears for volumes otherthan LDEVs.


Number of Paths Number of paths set for the LDEV. A hyphen (-) appears forvolumes other than LDEVs.

Edit SSIDs windowUse this window to select a storage system identifier whose properties can bechanged.


Item Description

LDKC LDKC number.

CU Control unit number.

LDEV Boundary The range of LDEVs that can be allocated to the SSID. EachLDEV group (divided by LDEV boundary) has a unique SSID.


SSID Changeable Indicates whether the storage system identifier is can bechanged.Yes: The SSID can be changed. The SSID was assignedwhen creating LDEVs but has not yet been registered(unused).No: The SSID can not be changed. The SSID has beenregistered (used) and cannot be changed.Hyphen (-): The SSID is not assigned.

Change SSIDs Select a row and click to open the Change SSID window.

Change SSIDs windowUse this window to change the SSID.


Item Description

Initial SSID Specify the initial storage system identifier in hexadecimalformat. The default is 0004 if none is specified.

Format LDEVs wizardUse this window to format LDEVs. LDEVs must be formatted before you canuse the storage space.


Format LDEVs window

Item Description

Format Type Select the type of formatting to be used on this LDEV.Quick Format (default): Select this to perform quick-formatting. This option is available only for formatting aninternal volume.Write to Control Blocks: Select this when the provisioningtype is for a mainframe external volume. The managementarea of external volumes for mainframe systems will beoverwritten. This is the default option for an externalvolume.Normal Format: Select this to perform normal-formatting.This option is available for formatting an internal volume, oran external volume whose emulation type is OPEN.

Number of Selected ParityGroups

Number of selected parity groups.

Format LDEVs Confirm windowConfirm proposed settings, name the task, then click Apply. The task will beadded to the execution queue.


Item Description







Provisioning Type Provisioning type to be assigned to the LDEV.Basic: Internal volume.DP: DP-VOL.External: External volume.Snapshot: Thin Image volume.

Attribute Displays the attribute of the LDEV.Command Device: Command device.TSE: TSE-VOL.Hyphen (-): Volume in which the attribute is notdefined.

Format Type How the LDEV will be formatted.• Quick Format: Quick-formatting is performed.• Normal Format: Normal formatting is performed.• Write to Control Blocks: The management area of

external volumes for mainframe systems isoverwritten.


Restore LDEVs windowUse this window to recover blocked LDEVs.

Item Description







Provisioning Type Provisioning type assigned to the LDEV.Basic: Internal volume.DP: DP-VOL.External: External volume.Snapshot: Thin Image volume.

Attribute Displays the attribute of the LDEV.Command Device: Command device.Remote Command Device: Remote command device.JNL VOL: Journal volume.Quorum Disk: Quorum disk for global-active device.TSE: TSE-VOL.Hyphen (-): Volume in which the attribute is notdefined.


Block LDEVs windowUse this window to block specific LDEVs. The data on the LDEV cannot beaccessed when the LDEV is blocked.

Item Description








Attribute Displays the attribute of the LDEV.Command Device: Command device.Remote Command Device: Remote command device.TSE: TSE-VOL.Hyphen (-): Volume in which the attribute is notdefined.

Delete LDEVs windowUse the window to delete an LDEV from a parity group.


Item Description








Attribute Displays the attribute of the LDEV.Command Device: Command device.TSE: TSE-VOL.Hyphen (-): Volume in which the attribute is notdefined.

LDEV Properties windowUse this window to view properties assigned to a selected LDEV.

• LDEV Properties table on page D-43• Basic tab on page D-44• Replication Tab on page D-46


LDEV Properties table

Item Description


LDEV Name Displays the LDEV name.

Emulation Type Displays the emulation type.

Capacity Displays the LDEV capacity.

Virtual Storage Machine Information about the virtual storage machine.• Model / Serial Number: Model name and serial

number of the virtual storage machine that hasLDEV.

• LDEV ID: Virtual LDEV ID. If a Virtual LDEV ID isnot assigned to LDEV, this column is blank.

• Device Name: Virtual device name, which is acombination of the virtual emulation type, virtualLUSE volume number, and the virtual CVS


Item Description

attribute. Values of the virtual emulation type,virtual LUSE volume number, and virtual CVSattribute appear only for items that have been set.This column is blank when the virtual emulationtype, virtual LUSE volume number, and virtual CVSattribute are not set. If the virtual CVS attribute isset, CVS is attached as the suffix to the devicename.

• SSID: Virtual SSID. If Virtual SSID is not set forLDEV, this column is blank.

Basic tab

LDEV basic information is displayed in the Basic Properties, LUNs, and Hoststables.

Basic Properties table

Item Description

Parity Group • ID: Displays the parity group ID.• Interleaved Parity Groups: Displays the interleaved

parity groups.• RAID Level: Displays the RAID level of parity

group. The asterisk (*) indicates the parity groupis the interleaved parity group.

• Drive Type/RPM: Displays the data drive type andRPM.

• Encryption: Displays the encryption setting (enableor disable). If the parity group in which theencryption setting is not defined, a hyphen (-) isdisplayed.

Pool • Name (ID): Displays the pool name and ID.• RAID Level: Displays the RAID level of pool.• Type: Displays the data drive type of pool.

Provisioning Type Display the type of LDEV.Basic: Internal volume.DP: DP-VOL.External: External volume.External MF: Migration volume.Snapshot: Thin Image volume.

Status Displays the LDEV status.Normal: Normal status.Blocked: Host cannot access blocked volumes.Warning: Problem occurs in the volumes.Formatting: Volumes are being formatted.


Item Description

Preparing Quick Format: Volumes are being preparedfor quick formatting.Quick Formatting: Volumes are being quick-formatted.Correction Access: Access attribute is being corrected.Copying: Data in the volumes are being copied.Read Only: Data cannot be written on the Read Onlyvolumes.Shredding: Volumes are being shredded.

Attribute Displays the attribute of the LDEV.Command Device: Command device.Remote Command Device: Remote command device.JNL VOL: Journal volume.Pool VOL: Pool volume. The number in parenthesesshows the pool ID.Quorum Disk: Quorum disk for global-active device.TSE: TSE-VOL.Hyphen (-): Volume in which the attribute is notdefined.

Command Device Attribute • Security: Displays the setting (Enable or Disable)of Command Device Security.

• User Authentication: Displays the setting (Enableor Disable) of user authentication.

• Device Group Definition: Displays the setting(Enable or Disable) of Device Group Definition.

Number of Paths Displays the number of paths of the selected LDEV.

UUID Displays the UUID.

CLPR Displays the ID and name of the CLPR in ID:CLPRformat.

Access Attribute Displays the access attribute of the LDEV.

SSID Displays the SSID.

Cache Mode Displays the cache mode.

V-VOL Management Task Displays the V-VOL management task being performedon a Dynamic Provisioning, Dynamic Provisioning forMainframe, Dynamic Tiering, or a Dynamic Tiering forMainframe V-VOL.

Current MP Blade ID Displays the current MP blade ID.

Current MP Blade Name Displays the current MP blade name.

Assigned MP Blade ID Displays the assigned MP blade ID.

Assigned MP Blade Name Displays the assigned MP blade name.

Resource Group Name (ID) Displays the resource group name and ID of the LDEV.The ID is provided in parentheses.

Tiering Policy Displays the tiering policy name and ID.


Item Description

New page Assignment Tier Displays the new page assignment tier.

Tier Relocation Displays the tier relocation setting.

Relocation Priority Displays the relocation priority setting.

Virtual Attribute Displays the virtual LDEV attribute. If the attribute isnot set for LDEV, this column is blank.

LUNs table

This table is not displayed if the path is not set.

Item Description

Port ID Port name.

Host Group Name Host group name.

LUN ID Identifier of the logical unit.

Hosts table

This table provides information about the host that can view LDEVs. Thistable is not available if the WWN is not registered in the host to which thepath is set.

Item Description

HBA WWN WWN of the host that can view LDEVs.

Host Name Host name.

Replication Tab

Information about the volume of the local replication pair is displayed in theReplication Properties, SI Pairs, TI Pairs, TC Pairs, UR Pairs, and GAD Pairstables.

For details about each item, see following:

• Hitachi ShadowImage® User Guide• Hitachi ShadowImage® for Mainframe User Guide• Hitachi Thin Image User Guide• Hitachi Compatible FlashCopy® User Guide• Hitachi TrueCopy® User Guide• Hitachi TrueCopy® for Mainframe User Guide• Hitachi Universal Replicator User Guide• Hitachi Universal Replicator for Mainframe User Guide• Hitachi Virtual Storage Platform G1000 Global-Active Device User Guide


Replication table

Item Description

Local Replication • ShadowImage L1: Displays the status of theShadowImage L1 pair.

• ShadowImage L2: Displays the status of theShadowImage L2 pair.

• Thin Image: Displays the status of the Thin Imagepair.

• ShadowImage for Mainframe: Displays the statusof the ShadowImage for Mainframe pair.

• Compatible FlashCopy® V2: Displays the status ofthe Compatible FlashCopy® V2 relationship.

• Compatible Software for IBM® FlashCopy® SE:Displays the status of the Compatible Software forIBM® FlashCopy® SE relationship.

Remote Replication • TrueCopy: Displays the status of the TrueCopypair.

• Universal Replicator: Displays the status of theUniversal Replicator pair.

• TrueCopy for Mainframe: Displays the status of theTrueCopy for Mainframe pair.

• Universal Replicator for Mainframe: Displays thestatus of the Universal Replicator for Mainframepair.

• Global-Active Device: Displays the status of theglobal-active device pair.

SI Pairs table

Item Description

Primary Volume • LDEV ID: Displays LDEV ID of the primary volume.• LDEV Name: Displays LDEV name of the primary

volume.• Emulation Type: Displays emulation type of the

primary volume.• Capacity: Displays capacity of the primary volume.• CLPR: Displays CLPR ID of the primary volume.

Copy Type Displays copy type of the pair.

Status Displays the pair status.

Secondary Volume • LDEV ID: Displays LDEV ID of the secondaryvolume.

• LDEV Name: Displays LDEV name of the secondaryvolume.

• Emulation Type: Displays emulation type of thesecondary volume.

• Capacity: Displays capacity of the secondaryvolume.


Item Description

• CLPR: Displays CLPR ID of the secondary volume.

Copy Pace Displays the pace of copying of the pair.

CTG ID Displays the consistency group number of the pair.

Mirror Unit Displays the mirror unit number of the pair.

Detail Displays the View Pair Properties window.

TI Pairs table

Item Description

Primary Volume • LDEV ID: Displays LDEV ID of the primary volume.• LDEV Name: Displays LDEV name of the primary

volume.• Emulation Type: Displays emulation type of the

primary volume.• Capacity: Displays capacity of the primary volume.• CLPR: Displays CLPR ID of the primary volume.

Snapshot Group Displays the snapshot group name.Information is shown for this item only if you haveconfigured a snapshot group for the HTI pair.


Snapshot Date Displays the date and time when you created the pairto store snapshot.

Secondary Volume • LDEV ID: Displays LDEV ID of the secondaryvolume.

• LDEV Name: Displays LDEV name of the secondaryvolume.

• Capacity: Displays capacity of the secondaryvolume.

• CLPR: Displays CLPR ID of the secondary volume.

Pool Name (ID) Displays pool name and identification number.

CTG ID Displays the consistency group identification number.

Mirror Unit Displays the mirror unit number of the pair.


TC Pairs table

Item Description

Copy Type Displays the copy type of the pair• TC: TrueCopy pair• TCMF: TrueCopy for Mainframe pair


Item Description

Pair Position Displays whether the volume is a primary or secondaryvolume.


Remote Storage System • Model / Serial Number: Displays the model andserial number of the remote storage system.

• SSID: Displays the SSID of the remote storagesystem.

• LDEV ID: Displays LDEV ID of the remote storagesystem.

• Port ID, Host Group ID, LUN ID: Displays Port ID,Host Group ID, and LUN ID of the remote storagesystem.

Path Group ID Displays the path group ID.

Update Type Displays the update type.

CTG ID Displays the consistency group ID.

CTG Utilization Displays whether the consistency group is shared bymultiple local and remote storage systems.

Preserve Mirror Status Displays the preserve mirror status.

Fence Level Displays the fence level.

Host I/O Time Stamp Transfer Displays whether the host I/O time stamp istransferred from P-VOL to S-VOL.


UR Pairs table

Item Description

Copy Type Displays the copy type of the pair• UR: Universal Replicator pair• URMF: Universal Replicator for Mainframe pair

Journal ID Displays the journal ID.

Pair 1 Displays the pair 1 information.• Pair Position: Displays whether the volume is a

primary or secondary volume.• Mirror ID: Displays the mirror ID.• Status: Displays the pair status.• Remote Storage System: Displays the information

about the remote storage system.¢ Model / Serial Number: Displays the model

and serial number of the remote storagesystem.

¢ LDEV ID: Displays LDEV ID of the remotestorage system.


Item Description¢ Port ID, Host Group ID, LUN ID: Displays Port

ID, Host Group ID, and LUN ID of the remotestorage system.

¢ Journal ID: Displays journal ID of the remotestorage system.

• Path Group ID: Displays the path group ID.• CTG ID: Displays the consistency group ID.• Error Level: Displays the error level.

Pair 2 Displays the pair 2 information.• Pair Position: Displays whether the volume is a

primary or secondary volume.• Mirror ID: Displays the mirror ID.• Status: Displays the pair status.• Remote Storage System: Displays the information

about the remote storage system.¢ Model / Serial Number: Displays the model

and serial number of the remote storagesystem.

¢ LDEV ID: Displays LDEV ID of the remotestorage system.

¢ Port ID, Host Group ID, LUN ID: Displays PortID, Host Group ID, and LUN ID of the remotestorage system.

¢ Journal ID: Displays journal ID of the remotestorage system.

• Path Group ID: Displays the path group ID.• CTG ID: Displays the consistency group ID.• Error Level: Displays the error level.


GAD Pairs table

Item Description

Pair Position Displays whether the volume is a primary or secondaryvolume.


Remote Storage System • Model / Serial Number: Displays the model andserial number of the remote storage system.

• LDEV ID: Displays LDEV ID of the remote storagesystem.

• Port ID, Host Group ID, LUN ID: Displays Port ID,Host Group ID, and LUN ID of the remote storagesystem.

Path Group ID Displays the path group ID.


Item Description

CTG ID Displays the consistency group ID.

Quorum Disk ID Displays the quorum disk ID.


Components windowUse this window to view information about the controller chassis componentsin the storage system.

• Summary on page D-52• Components tab on page D-52


Summary

Item Description

Number of ControllerChassis

Number of controller chassis.

High Temperature Mode High Temperature Mode.• Enabled (16-40 degrees C ) : High Temperature mode

is enable.• Disabled (16-32 degrees C ) : High Temperature mode

is disable.

Power Consumption Power Consumption.

Edit High TemperatureMode

Opens the Edit Temperature Mode window.

Components tab

Item Description

Chassis ID Chassis identifier of the storage system.

Chassis Type Chassis type.

Temperature Mode( degrees C )

Temperature of the cluster.• Cluster 1 : Temperature of the cluster 1.• Cluster 2 : Temperature of the cluster 2.


DKC: MP Blades tabUse this window to view information about MP blades in the storage system.


• Summary on page D-53• MP Blades tab on page D-53

Summary

Item Description

Number of MP Blades Number of MP blades assigned to this component.

MP Blades tab

Item Description

MP Blade ID Identifier of the MP blade.

MP Blade Name Name of the MP blade.

Status Status of the MP blade.

Normal: Available.

Warning: The MP blade is partially blocked.

Blocked: The MP blade is blocked.


Item Description

Failed: The MP blade is in abnormal status.

Cluster Cluster number of the MP blade.

Auto Assignment Indicates whether the MP blade is automatically assigned toresources.Enabled: The MP blade is automatically assigned toresources (logical devices, external volumes, and journalvolumes).Disabled: The MP blade is not automatically assigned toresources.

Edit MP Blades Opens the Edit MP Blades window.


Edit MP Blades wizardUse this wizard to enable or disable the storage system to automaticallyassign the load of resources controlled by the selected MP blades.

Edit MP Blades window

Item Description

Auto Assignment Specify whether to automatically assign an MP blade toresources (logical devices, external volumes, and journalvolumes).• Enable: Resources will be automatically assigned to the

specified MP blade.


Item Description

• Disable: Resources will not be automatically assignedto the specified MP blade.

Edit MP Blades Confirm windowConfirm proposed settings, name the task, then click Apply. The task will beadded to the execution queue.

Item Description

MP Blade ID MP blade identifier.

Cluster Cluster number of the MP blade.

Auto Assignment Indicates whether automatic assignment of MP bladesis in use.• Enabled: An MP blade is automatically assigned to

resources (logical devices, external volumes, andjournal volumes).

• Disabled: An MP blade is not automaticallyassigned to resources.

Assign MP Blade wizardUse this wizard to assign a MP blade that will control selected resources.

Assign MP Blade windowUse this window to select a MP blade to assign to an LDEV.


Item Description

MP Blade Change the MP blade assigned to the LDEV.MP blade ID: The selected MP blade is assigned to theLDEV.

Assign MP Blade Confirm windowConfirm proposed settings, name the task, then click Apply. The task will beadded to the execution queue.



Item Description







Provisioning Type Provisioning type to be assigned to the LDEV.Basic: Internal volume.DP: DP-VOL.External: External volume.External MF: Migration volume.Snapshot: Thin Image volume.

Attribute Displays the attribute of the LDEV.Command Device: Command device.Remote Command Device: Remote command device.JNL VOL: Journal volume.Pool VOL: Pool volume. The number in parenthesesshows the pool ID.Quorum Disk: Quorum disk for global-active device.TSE: TSE-VOL.Hyphen (-): Volume in which the attribute is notdefined.

MP Blade ID MP blade identifier to be set.

View Management Resource Usage window


Management Resource Usage table

Item Description

Number of Cache ManagementDevices

The current number and maximum allowed number ofcache management devices in the storage system aredisplayed.


EDynamic Provisioning for Mainframe

and Dynamic Tiering for Mainframe GUIreference

The Dynamic Provisioning for Mainframe and Dynamic Tiering for Mainframewindows, wizards, and dialog boxes are described in the following topics.

□ Pools window

□ Pools: Volume tabs

□ Create Pools wizard

□ Expand Pool wizard

□ Edit Pools wizard

□ Delete Pools wizard

□ Expand V-VOLs wizard

□ Restore Pools window

□ Shrink Pool window

□ Stop Shrinking Pools window

□ Complete SIMs window

□ Select Pool VOLs window

Dynamic Provisioning for Mainframe and Dynamic Tiering for Mainframe GUI reference E-1Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

□ Reclaim Zero Pages window

□ Stop Reclaiming Zero Pages window

□ Pool Property window

□ View Tier Properties window

□ Monitor Pools window

□ Stop Monitoring Pools window

□ Start Tier Relocation window

□ Stop Tier Relocation window

□ View Pool Management Status window

□ Edit External LDEV Tier Rank wizard

□ Edit Tiering Policies wizard

□ Change Tiering Policy Window

□ Change Pool Configuration Pattern Window

E-2 Dynamic Provisioning for Mainframe and Dynamic Tiering for Mainframe GUI referenceHitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Pools window

• Summary on page E-3• Pools tab on page E-5

Summary

Item Description

Pool Capacity1 Displays information about the pool capacity.• Used/Total

DP: Displays the pool capacity (used/total) of DynamicProvisioning and Dynamic Tiering.Mainframe DP: Displays the pool capacity (used/total) ofDynamic Provisioning for Mainframe and Dynamic Tiering forMainframe.TI: Displays the pool capacity (used/total) of Thin Image.For each value, if the Estimated Configurable capacity is

zero, is displayed in the cell.• Estimated Configurable2


Item Description

DP: Displays the estimated pool capacity of DynamicProvisioning and Dynamic Tiering.Mainframe DP: Displays the estimated pool capacity ofDynamic Provisioning for Mainframe and Dynamic Tiering forMainframe.TI: Displays the remaining physical pool capacity that isconfigurable for Thin Image.

V-VOL Capacity1 Displays information about the DP-VOL capacity.• Allocated/Total

DP: In the Allocated field, total capacity of the DynamicProvisioning and Dynamic Tiering DP-VOLs to which LU pathsare allocated is displayed. In the Total field, total capacity ofthe Dynamic Provisioning and Dynamic Tiering DP-VOLs isdisplayed.Mainframe DP: In each of the Allocated and Total fields,total capacity of the Dynamic Provisioning for Mainframe andDynamic Tiering for Mainframe DP-VOLs is displayed.For each value, if the Estimated Configurable capacity is

zero, is displayed in the cell.• Estimated Configurable2

DP: Displays the DP-VOL estimated configurable capacity ofDynamic Provisioning and Dynamic Tiering.Mainframe DP: Displays the DP-VOL estimated configurablecapacity of Dynamic Provisioning for Mainframe and DynamicTiering for Mainframe.

Licensed Capacity(Used / Licensed)

DP: Displays the licensed capacity of Dynamic Provisioning.Used displays the total capacity of pools for DynamicProvisioning and Dynamic Tiering,Mainframe DP: Displays the licensed capacity of DynamicProvisioning for Mainframe. Used displays the total capacity ofpools for Dynamic Provisioning for Mainframe and DynamicTiering for Mainframe.TI: Displays the licensed capacity of the Thin Image.Caution: In the Licensed Capacity(Used/Licensed) field, thetotal capacity of the system is displayed. The total capacity of thesystem includes capacities of LDEVs assigned to each user andresources other than LDEVs. Therefore, the value displayed asthe "Used" Licensed Capacity (Used/ Licensed) might differfrom the value of the "Total" Pool Capacity.

Number of Pools Displays the total number of pools for Dynamic Provisioning,Dynamic Tiering, Thin Image, and Dynamic Tiering forMainframe.

Edit Tiering Policies Displays the Edit Tiering Policies window.

Notes:1. The total value of the Total cells under Capacity of each pool type in the Pools tab

window and the total Used capacity of the Pool Capacity in the Summary tableare almost same, but small differences might occur.


Item Description

The capacity used by the Mainframe DP volume is different from the capacity usedby the DP volume. If the pool-VOL or DP-VOL for Dynamic Provisioning or DynamicProvisioning for Mainframe is created, the estimated configurable pool capacity andestimated configurable V-VOL capacity for both DP and Mainframe DP change. Theestimated capacity is calculated based on the configuration of current pools and DP-VOL, and remaining capacity of the shared memory.

2. The estimated configurable capacity of Dynamic Provisioning or DynamicProvisioning for Mainframe is the estimate of the DP-VOL capacity or the poolcapacity that can be created by using the remaining capacity of the shared memoryafter deduction of the capacity of the shared memory used by the current pool andDP-VOL. The values of the Estimated Configurable Pool Capacity and theEstimated Configurable V-VOL Capacity can be used only as a guide, but are notguaranteed to create pools and DP-VOLs having the estimated configurable capacity.If the pool-VOL or DP-VOL for Dynamic Provisioning or Dynamic Provisioning forMainframe is created or deleted, the estimated configurable pool capacity andestimated configurable V-VOL capacity for both Dynamic Provisioning and DynamicProvisioning for Mainframe change.

Pools tab

Item Description

Pool Name Displays the pool name. Clicking the pool name takes youto the pool information window in the lower hierarchy.

Pool ID1 Displays pool ID.

Status Displays information about the pool status.

Normal: Pool is in a normal status.

Warning: Pool-VOL in the pool is blocked, or the pool isbeing shrunk.

Exceeded Threshold: Used capacity of the pool exceedsthe pool threshold.

Shrinking: Pool-VOL is being reduced.

Blocked: Pool is full, or an error occurred in the pool,indicating that the pool is blocked. If the pool is in bothWarning and Blocked status, only Blocked is displayed.

Number of Pool VOLs Displays the number of pool-VOLs associated with the pool.

Number of V-VOLs Displays the number of V-VOLs associated with the pool.For a Thin Image pool, a hyphen (-) is displayed.

Number of Primary VOLs Displays the number of primary volumes of the Thin Imagepairs. If a pool is other than the Thin Image pool, a hyphen(-) is displayed.

RAID level Displays RAID level. If multiple RAID levels exist in a pool,this field indicates that RAID levels are mixed. If all pool-VOLs are external volumes, a hyphen (-) is displayed.


Item Description

Capacity Displays information about the pool capacity.• Total: Total capacity of pool.

Using Option, you can select unit of capacity.- One block means 512 bytes and one page means 42megabytes in a pool capacity of Dynamic Provisioning,Dynamic Tiering, or Thin Image,- One slot means 58 kilobytes and one page means 38megabytes in a pool capacity of Dynamic Provisioningfor Mainframe or Dynamic Tiering for Mainframe.

• Used: Used pool capacity.• Used (%): Pool usage rates to pool capacity.

Used (%) displays the value which is truncated afterthe decimal point of the actual value.

For the pool of Dynamic Provisioning, Dynamic Tiering, andThin Image, a hyphen (-) is displayed if the unit of capacityis changed into Cylinder.


Displays information about the threshold of a pool.• Warning: Warning threshold.• Depletion: Depletion threshold.For a Thin Image pool, a hyphen (-) is displayed forDepletion.

Subscription (%) Displays information about subscription of the pool.• Current: Percentage of the total V-VOL capacity

assigned to the pool.• Limit: Percentage of the subscription limit of the pool.For a Thin Image pool, a hyphen (-) is displayed for Currentand Limit.

Pool Type Displays the pool type.For a Dynamic Provisioning pool, DP is displayed.For a Dynamic Tiering pool, DT is displayed.For a Dynamic Provisioning for Mainframe pool, MainframeDP is displayed.For a Dynamic Tiering for Mainframe pool, Mainframe DT isdisplayed.For a Thin Image pool, TI is displayed.

Drive Type/RPM Displays the data drive type and RPM of the pool. If multipledrive types or RPMs exist in a pool, this field indicates thatdrive types or RPMs are mixed. When the volume is theexternal volume, Drive Type displays External Storageand the value of the external LDEV tier rank.

Tier Management Displays whether Dynamic Tiering or Dynamic Tiering forMainframe is enabled or disabled. If it is enabled Auto orManual is displayed. If it is disabled, a hyphen (-) isdisplayed.For a Thin Image pool, a hyphen (-) is displayed.


Item Description

Shrinkable Displays whether the pool-VOL can be removed. While thepool is being shrunk, a hyphen (-) is displayed.

Monitoring Mode Displays the monitoring mode that is set for the pool. If thecontinuous mode is enabled, Continuous Mode is displayed.If the period mode is enabled, Period Mode is displayed. IfDynamic Tiering or Dynamic Tiering for Mainframe isdisabled, a hyphen (-) is displayed.

Monitoring Status Displays the status of pool monitoring.• In Progress: The monitoring is being performed.• During Computation: The calculating is being

processed.Other than these cases, a hyphen (-) is displayed.

Recent Monitor Data Displays the latest monitoring data.• If the monitoring data exists, the monitoring period of

time is displayed.Example: 2010/11/15 00:00 - 2010/11/15 23:59

• If the monitoring data is being obtained, only thestarting time is displayed.Example: 2010/11/15 00:00 -

• If the latest monitoring data does not exist, a hyphen(-) is displayed.

Pool Management Task Displays the pool management task being performed to thepool.• Waiting for Rebalance: The rebalance process is being

waited.• Rebalancing: The rebalance process is being performed.• Waiting for Relocation: The tier relocation process is

being waited.• Relocating: The tier relocation process is being

performed.• Waiting for Shrink: The pool shrinking process is being

waited.• Shrinking: The pool shrinking process is being

performed.• Blank: The pool management task is not being

performed to the pool.For details about the tier relocation, see the tier relocationlog file. For details about the table items of the tierrelocation log file, see Tier relocation log file contents onpage 4-38.

Relocation Result Displays the status of the tier relocation processing.In Progress: The status of Pool Management Task isWaiting for Relocation or Relocating.Completed: The tier relocation operation is not in progress,or the tier relocation is complete.Uncompleted (n% relocated): The tier relocation issuspended at the indicated percentage progression.


Item Description

Hyphen (-): The pool is not a Dynamic Tiering or DynamicTiering for Mainframe pool.

Relocation Speed Displays the tier relocation speed: 1(Slowest), 2(Slower),3(Standard), 4(Faster), or 5(Fastest).

Protect V-VOLs when I/Ofails to Blocked Pool VOL

Displays whether the protect function for DP-VOL is beingenabled or disabled. If the setting is enabled, when thepool-VOL is blocked, DP-VOL is protected from reading andwriting requests. And at the same instant, the accessattribute of the DP-VOL is changed to the Protect attribute.A hyphen appears if the pool corresponds with one offollowing:• Data Retention Utility is not installed.• Pool type is the type other than DP and DT.

Protect V-VOLs when I/Ofails to Full Pool

Displays whether the protect function for DP-VOL is beingenabled or disabled. If the setting is enabled, when the poolusage reaches the full size, DP-VOL is protected fromreading and writing requests. And at the same instant, theaccess attribute of the DP-VOL is changed to the Protectattribute.A hyphen appears if the pool corresponds with one offollowing:• Data Retention Utility is not installed.• Pool type is the type other than DP and DT.

Create Pools Displays the Create Pools window.

Create LDEVs Displays the Create LDEVs window.

Expand Pool Displays the Expand Pool window.

Delete Pools2 Displays the Delete Pools window.

Restore Pools2 Displays the Restore Pools window.

Edit Pools2 Displays the Edit Pools window.

Monitor Pools2 Displays the Monitor Pools window.

Stop Monitoring Pools2 Displays the Stop Monitoring Pools window.

Start Tier Relocation2 Displays the Start Tier Relocation window.

Stop Tier Relocation2 Displays the Stop Tier Relocation window.

Complete SIMs2 Displays the Complete SIMs window.

View Tier Properties2 Displays the View Tier Properties window. This window canbe viewed only for the pools for which Dynamic Tiering orDynamic Tiering for Mainframe is enabled.

View Pool ManagementStatus2

Displays the View Pool Management Status window.

Export Tier Relocation Log2 Displays the window to download the result of the tierrelocation. For more information about the table item of the


Item Description

tier relocation file, see Tier relocation log file contents onpage 4-38.

Export2 Displays the window for outputting table information.

Notes:1Does not appear by default. To display this item, change the Column Settings of thetable option.2Appears when you click More Actions.

Pools: Volume tabs

• Summary on page E-10• Pool Volumes tab on page E-13• Virtual Volumes tab on page E-14


Summary

Item Description

Status Displays information about the pool status.

Normal: Pool is in a normal status.

Warning: Pool-VOL in the pool is blocked, or the pool isbeing shrunk.

Exceeded Threshold: Used capacity of the pool exceedsthe pool threshold.


Blocked: The pool is full, or an error occurred in thepool, indicating that the pool is blocked. If the pool is inboth Warning and Blocked status, only Blocked isdisplayed.


Pool VOL with System Area(Name)

Displays the LDEV ID and LDEV name of the pool-VOLwhich includes the pool management area.


RAID Level Displays RAID level. If multiple RAID levels exist in a pool,this field indicates that RAID levels are mixed. If all pool-VOLs are external volumes, a hyphen (-) is displayed.

Drive Type/RPM Displays the data drive type and RPM of the pool. Ifmultiple drive types or RPMs exist in a pool, this fieldindicates that drive types or RPMs are mixed. When thevolume is the external volume, Drive Type displaysExternal Storage and the value of the external LDEV tierrank.

Cache Mode Displays whether the cache mode is enabled or disabled.For a configuration other than external volumeconfiguration, a hyphen (-) is displayed.


Displays whether the protect function for DP-VOL is beingenabled or disabled. If the setting is enabled, when thepool-VOL is blocked, DP-VOL is protected from reading andwriting requests. And at the same instant, the accessattribute of the DP-VOL is changed to the Protect attribute.A hyphen appears if the pool corresponds with one offollowing:• Data Retention Utility is not installed.


Item Description

• Pool type is the type other than DP and DT.


Displays whether the protect function for DP-VOL is beingenabled or disabled. If the setting is enabled, when thepool usage reaches the full size, DP-VOL is protected fromreading and writing requests. And at the same instant, theaccess attribute of the DP-VOL is changed to the Protectattribute.A hyphen appears if the pool corresponds with one offollowing:• Data Retention Utility is not installed.• Pool type is the type other than DP and DT.

Number of Pool VOLs Displays the number of pool-VOLs set for the pool, and themaximum number of pool-VOLs that can be set for thepool.

Number of V-VOLs Displays the number of V-VOLs associated with the pool,and the maximum number of V-VOLs that can beassociated with the pool.For a Thin Image, a hyphen (-) is displayed.

Number of Primary VOLs Displays the number of primary volumes of the Thin Imagepairs. When the applicable volume does not exist, ahyphen (-) is displayed.

Pool Capacity (Used/Total) Displays the used and total pool capacity. If the poolconsists of multiple pool-VOLs, the sum of its capacities isdisplayed in the Total field.

V-VOL Capacity (Used/Total)

Displays the used and total V-VOL capacity. For a ThinImage pool, a hyphen (-) is displayed along with the usedand total V-VOL capacity.

Subscription (Current/Limit) Displays the subscription (Rate of total V-VOL capacityassociated with a pool to the pool capacity/Subscriptionthat is set).For a Thin Image, a hyphen (-) is displayed for Current orLimit.

User-Defined Threshold(Warning/Depletion)

Displays the user-defined threshold (Warning/Depletion).For a Thin Image, a hyphen (-) is displayed for Depletion.

Tier Management If Dynamic Tiering or Dynamic Tiering for Mainframe isenabled, Auto or Manual is displayed. If Dynamic Tiering orDynamic Tiering for Mainframe is disabled, a hyphen (-) isdisplayed.For a Thin Image, a hyphen (-) is displayed.

Cycle Time Displays the cycle of performance monitoring and tierrelocation. If Dynamic Tiering or Dynamic Tiering forMainframe is disabled, a hyphen (-) is displayed.

Monitoring Period Displays the time of starting and ending of performancemonitoring. If Dynamic Tiering or Dynamic Tiering forMainframe is disabled, a hyphen (-) is displayed.

Monitoring Mode Displays the monitoring mode that is set for the pool. Ifthe continuous mode is enabled, Continuous Mode is


Item Description

displayed. If the period mode is enabled, Period Mode isdisplayed. If Dynamic Tiering or Dynamic Tiering forMainframe is disabled, a hyphen (-) is displayed.

Monitoring Status Displays the status of pool monitoring.If the monitoring is being performed, In Progress isdisplayed. A hyphen (-) is displayed other than this case.

Recent Monitor Data Displays the latest monitoring data.• If the monitoring data exists, the monitoring period of

time is displayed.Example: 2010/11/15 00:00 - 2010/11/15 23:59

• If the monitoring data is being obtained, only thestarting time is displayed.Example: 2010/11/15 00:00 -

• If the latest monitoring data does not exist, a hyphen(-) is displayed.

Pool Management Task Displays the pool management task being performed tothe pool.• Waiting for Rebalance: The rebalance process is being

waited.• Rebalancing: The rebalance process is being

performed.• Waiting for Relocation: The tier relocation process is

being waited.• Relocating: The tier relocation process is being

performed.• Waiting for Shrink: The pool shrinking process is being

waited.• Shrinking: The pool shrinking process is being

performed.• Blank:The pool management task is not being

performed to the pool.For details about the tier relocation, see the tier relocationlog file. For details about the table items of the tierrelocation log file, see Tier relocation log file contents onpage 4-38.

Relocation Result Displays the status of the tier relocation processing.In Progress: The status of Pool Management Task isWaiting for Relocation or Relocating.Completed: The tier relocation operation is not in progress,or the tier relocation is complete.Uncompleted (n% relocated): The tier relocation issuspended at the indicated percentage progression.Hyphen (-): The pool is not a Dynamic Tiering or DynamicTiering for Mainframe pool.

Relocation Speed Displays the tier relocation speed: 1(Slowest), 2(Slower),3(Standard), 4(Faster), or 5(Fastest).


Pool Volumes tab

Only the LDEVs assigned to the logged-on user are available.

Item Description

LDEV ID LDEV identifier, which is the combination of LDKC, CU, andLDEV.


Status Displays the following information about the pool-VOLstatus.

Normal: Pool-VOL is in the normal status.


Blocked: Pool-VOL is blocked.

Parity Group ID Displays the parity group ID.

Usable Capacity Displays available capacity of page boundaries in a pool-VOL by the specified unit. For the pool-VOL with systemarea, the displayed capacity does not include the capacity ofthe management area.


Item Description

For the pool of Dynamic Provisioning, Dynamic Tiering, andThin Image, a hyphen (-) is displayed if the unit of capacityis changed to Cylinder.

RAID Level Displays the RAID level.



Tier ID Displays the tier ID. For a Dynamic Provisioning, DynamicProvisioning for Mainframe, or a Thin Image pool, a hyphen(-) is displayed.

Provisioning Type Displays the type of the LDEV.Basic: Internal volume.External: External volume.

Shrinkable Displays whether the pool-VOL can be removed while thepool is being shrunk, a hyphen (-) is displayed.

Encryption1 Displays the information about parity group encryption.Enabled: The encryption of the parity group which containsLDEV is enabled.Disabled: The encryption of the parity group which containsLDEV is disabled.If LDEV is a V-VOL for Dynamic Provisioning, externalvolume, or migration volume, a hyphen (-) is displayed.

Resource Group Name (ID) Displays the resource group names and IDs of the LDEV.The ID is provided in parentheses.

Expand Pool Displays the Expand Pool window.

Shrink Pool Displays the Shrink Pool window.

Stop Shrinking Pools Displays the Stop Shrinking Pools window.

Edit External LDEV TierRank2

Displays the Edit External LDEV Tier Rank window. Youcannot operate the pool other than the pool of DynamicProvisioning, Dynamic Provisioning for Mainframe, DynamicTiering, Dynamic Tiering for Mainframe.


1 This item does not appear in the window by default. To display this item, change theColumn Settings of the table option.2Appears when you click More Actions.

Virtual Volumes tab

This tab is displayed unless you select a Thin Image pool.


Item Description



Status Normal: Normal status.









Item Description

Read Only: Data cannot be written to a read-onlyvolume.




Capacity Displays information about the V-VOL capacity.• Total: Displays the V-VOL capacity.• Used: Displays the V-VOL used capacity.

The displayed value on Total might be larger than thedisplayed value on Used due to following reasons:¢ Used displays the used V-VOL capacity which is

rounded up on each page.¢ If the emulation type is 3390-A, the used capacity

of V-VOL includes the capacity of control cylinders(7 Cyl is required per 1,113 Cyl).

• Used(%): Displays the V-VOL usage level.

Used Capacity Displays information about the used capacity of V-VOL• Tier1: Displays the used capacity of tier 1.

A hyphen (-) is displayed if the logical volume is a not aV-VOL of Dynamic Tiering or Dynamic Tiering forMainframe.

• Tier2: Displays the used capacity of tier 2.A hyphen (-) is displayed if tier 2 does not exist or ifthe logical volume is a not a V-VOL of Dynamic Tieringor Dynamic Tiering for Mainframe.

• Tier3: Displays the used capacity of tier 3.A hyphen (-) is displayed if tier 3 does not exist or ifthe logical volume is a not a V-VOL of Dynamic Tieringor Dynamic Tiering for Mainframe.

Number of Paths Displays the number of alternate paths. A hyphen(-) isdisplayed for the Dynamic Provisioning for Mainframe orDynamic Tiering for Mainframe V-VOL.

CLPR Displays the CLPR ID.

Tiering Policy Displays the tiering policy name and ID.All(0): The policy of which all tiers in the pool are used.Level1(1) - Level5(5): One of the policy from Level1 toLevel5 is set to V-VOL.Level6(6) - Level31(31): The tiering policy of the userdefinition is set to V-VOLHyphen (-): V-VOL is not the Dynamic Tiering or DynamicTiering for Mainframe V-VOL.

New Page Assignment Tier Displays the new page assignment tier.High: High is set to V-VOL.


Item Description

Middle: Middle is set to V-VOL.Low: Low is set to V-VOL.Hyphen (-): V-VOL is not the Dynamic Tiering or DynamicTiering for Mainframe V-VOL.

Tier Relocation Displays whether tier relocation is set to enabled ordisabled. If the Dynamic Tiering or Dynamic Tiering forMainframe V-VOL is not used, a hyphen (-) is displayed.

Relocation Priority Displays the relocation priority.Prioritized: The priority is set to V-VOL.Blank: The priority is not set to V-VOL.Hyphen (-): V-VOL is not the Dynamic Tiering or DynamicTiering for Mainframe V-VOL or the tier relocation functionis disabled.

Pool Management Task Displays the pool management task being performed to thepool.Waiting for Rebalance: The rebalance process is beingwaited.Rebalancing: The rebalance process is being performed.Waiting for Relocation: The tier relocation process is beingwaited.Relocating: The tier relocation process is being performed.Waiting for Shrink: The pool shrinking process is beingwaited.Shrinking: The pool shrinking process is being performed.Blank:The pool management task is not being performed tothe pool.

V-VOL Management Task Displays the V-VOL management task being performed toV-VOL.Reclaiming Zero Pages: The zero page reclaimingprocessing is being performed.Waiting for Zero Page Reclaiming: The zero page reclaimingprocessing is being waited.Blank:The V-VOL management task is not being performedto V-VOL.

Attribute Displays the attribute of the LDEV.TSE: TSE-VOL.Hyphen (-): Volume in which the attribute is not defined.

Access Attribute1 Displays the access attribute of the LDEV.


Virtual Storage Machine1 Information about the virtual storage machine.• Model / Serial Number1: Model name and serial number

of the virtual storage machine that has LDEV.• LDEV ID1: Virtual LDEV ID. If a Virtual LDEV ID is not

assigned to LDEV, this column is blank.


Item Description

• Device Name1: Virtual device name, which is acombination of the virtual emulation type, virtual LUSEvolume number, and the virtual CVS attribute. Valuesof the virtual emulation type, virtual LUSE volumenumber, and virtual CVS attribute appear only for itemsthat have been set. This column is blank when thevirtual emulation type, virtual LUSE volume number,and virtual CVS attribute are not set. If the virtual CVSattribute is set, CVS is attached as the suffix to thedevice name.

• SSID1: Virtual SSID. If Virtual SSID is not set for LDEV,this column is blank.

• Attribute1: Virtual LDEV attribute. If the attribute is notset for LDEV, this column is blank.

Create LDEVs Displays the Create LDEV window.

Add LUN Paths Displays the Add LUN Paths window. If Mainframe DP or DTis displayed in the Pool Type, you cannot select this item.

Expand V-VOLs Displays the Expand V-VOLs window.

Format LDEVs2 Displays the Format LDEVs window.

Delete LDEVs2 Displays the Delete LDEVs window.

Shred LDEVs2 Displays the Shred LDEVs window.

Delete LUN Paths2 Displays the Delete LUN Paths window.

Block LDEVs2 Displays the Block LDEVs window.

Restore LDEVs2 Displays the Restore LDEVs window.

Edit LDEVs2 Displays the Edit LDEVs window.

Reclaim Zero Pages2 Displays the Reclaim Zero Pages window.

Stop Reclaiming ZeroPages2

Displays the Stop Reclaiming Zero Pages window.

View Tier Properties2 Displays the View Tier Properties window. This window canopen only for a pool for which Dynamic Tiering or DynamicTiering for Mainframe is enabled.


1Does not appear by default. To display this item, change the Column Settings of thetable option.2Appears when you click More Actions.


Create Pools wizard

Create Pools windowUse this window to create new pools for Dynamic Provisioning for Mainframe,Thin Image.

Caution: When you create the Dynamic Provisioning or Dynamic Provisioningfor Mainframe pool, if you specify Any for RAID level to display the SelectPool VOLs window, external volumes with the cache mode set to disabledare not displayed in the Available Pool Volumes table because they cannotcoexist with volumes of the other RAID levels:When you select these volumes in the Select Pool VOLs window, specify ahyphen (-) for RAID level.

When selecting pool-VOL manually


When selecting pool-VOL automatically

Setting fields


Item Description

*Pool Type Select the pool type.For Thin Image, select Thin Image.For following software, select Dynamic Provisioning.• Dynamic Provisioning• Dynamic Tiering• Dynamic Provisioning for Mainframe• Dynamic Tiering for Mainframe

*System Type Select the system type.If you select Thin Image, only Open is displayed.

*Multi-Tier Pool If Dynamic Tiering or Dynamic Tiering for Mainframe isenabled, Auto or Manual for performance monitoring andtier relocation is displayed. If Dynamic Tiering or DynamicTiering for Mainframe is disabled, a hyphen (-) is displayed.

*Pool Volume Selection Select the mode of the pool-VOL setting from Auto orManual.

*Drive Type/RPM Select the data drive type and RPM of the pool-VOL.Mixable appears. When the volume is the external volume,Drive Type displays External Storage. This item isdisplayed when you select Manual as your Pool VolumeSelection.

*RAID Level Select the RAID level of the pool-VOL. This item is displayedwhen you select Manual as your Pool Volume Selection.Mixable appears in the case of Dynamic Provisioning orDynamic Tiering. A hyphen (-) appears when ExternalStorage is selected in the Drive Type/RPM list.

*Select Pool VOLs Opens the Select Pool VOLs window. Selecting a pool-VOL ismandatory. This item is displayed when you select Manualas your Pool Volume Selection.

Total Selected PoolVolumes

Displays the total number of the selected pool-VOLs. Thisitem is displayed when you select Manual as your PoolVolume Selection.

Total Selected Capacity Displays the total capacity of the selected pool-VOLs. Thisitem is displayed when you select Manual as your PoolVolume Selection.

Resource Group This item is displayed when you select Auto as your PoolVolume Selection.Select the resource group name of the pool.

Performance This item is displayed when you select Auto as your PoolVolume Selection.Select the performance of the pool.

Total Capacity This item is displayed when you select Auto as your PoolVolume Selection.Specify the total capacity of the pool.

Change Pool Configuration This item is displayed when you select Auto as your PoolVolume Selection.


Item Description

Opens the Change Pool Configuration Pattern window. Youcan change the pool configuration that is automaticallyselected. For details, see Change Pool Configuration PatternWindow on page E-78.

Total Pool Volumes This item is displayed when you select Auto as your PoolVolume Selection.Displays the total number of pool-VOLs.

Total Capacity This item is displayed when you select Auto as your PoolVolume Selection.Displays the capacity of the pool created by the selectedpool configuration.

*Pool Name Set the pool name.• Prefix: Enter the alphanumeric characters, which are

fixed characters of the head of the pool name. Thecharacters are case-sensitive.

• Initial Number: Enter the initial number following theprefix name, which can be entered up to 9 digits.

• You can enter up to 32 characters including the initialnumber.

Initial Pool ID The smallest available number is entered in the text box asa default. No number appears in the text box if no availablepool ID exists.If you specify the pool ID which is used already, theminimum pool ID after that the specified pool ID isautomatically set.

Subscription Limit Set the subscription limit of the pool from 0 to 65534 (%).If this is blank, the subscription is set to unlimited.When creating a Thin Image pool, this setting is notnecessary.

Warning Threshold Set the threshold between 1 and 100%. The default value is70%.For Thin Image: Set the threshold between 20% and 95%.The default value is 80%.

Depletion Threshold Set the threshold between 1% and 100%. The default valueis 80%.When creating a Thin Image pool, this setting is notnecessary.


This item can be set if following are satisfied:• Dynamic Provisioning is selected in Pool Type.• Open is selected in System Type.• Data Retention Utility must be installed.Select Yes or No in the protect function for DP-VOL. If thisfunction is enabled, when the pool-VOL is blocked, DP-VOLis protected from reading and writing requests. And at thesame instant, the access attribute of the DP-VOL is changedto the Protect attribute.


Item Description


This item can be set if following are satisfied:• Dynamic Provisioning is selected in Pool Type.• Open is selected in System Type.• Data Retention Utility must be installed.Select Yes or No in the protect function for DP-VOL. If thisfunction is enabled, when the pool usage reaches the fullsize, DP-VOL is protected from reading and writingrequests. And at the same instant, the access attribute ofthe DP-VOL is changed to the Protect attribute.

Tier Management Select Auto or Manual of performance monitoring and tierrelocation.• Cycle Time

Select the cycle of performance monitoring and tierrelocation.

• Monitoring PeriodWhen 24 Hours is selected in the Cycle Time list,specify the time zone from 00:00 to 23:59 (defaultvalue), in which performance monitoring is to beperformed. Take one or more hours between thestarting time and the ending time. If you specify thestarting time later than the ending time, theperformance monitoring continues until the time whenyou specify as the ending time on the next day.

This function can be set when the Multi-Tier Pool is enabled.

Monitoring Mode Specifies the monitoring mode, If you perform the tierrelocation weighted to the past period monitoring result,select Continuous Mode. If you perform the tier relocationon the specified cycle, select Period Mode. You can specifythis function when the Multi-Tier Pool is enabled.

Relocation speed Specifies the page relocation speed. You can set the speedto: 1(Slowest), 2(Slower), 3(Standard), 4(Faster), or5(Fastest). The default is 3(Standard). If the speedspecified is slower than 3(Standard), the data drive load islow when tier relocation is performed.

Buffer Space for New pageassignment

You can set this function when the Multi-Tier Pool isenabled.Tier 1: Enter an integer value from 0 to 50 as thepercentage (%) to set for tier 1. A default value depends onthe data drive type of pool-VOL in tier 1. The default valueof SSD is 0%. The default value other than SSD is 8%.Tier 2: Enter an integer value from 0 to 50 as thepercentage (%) to set for tier 2. A default value depends onthe data drive type of pool-VOL in tier 2.Tier 3: Enter an integer value from 0 to 50 as thepercentage (%) to set for tier 3. A default value depends onthe data drive type of pool-VOL in tier 3.

Buffer Space for Tierrelocation

You can set this function when the Multi-Tier Pool isenabled.


Item Description

Tier 1: Enter an integer value from 2 to 40 as thepercentage (%) to set for tier 1. A default value is 2%.Tier 2: Enter an integer value from 2 to 40 as thepercentage (%) to set for tier 2. A default value is 2%.Tier 3: Enter an integer value from 2 to 40 as thepercentage (%) to set for tier 3. A default value is 2%.

*Items with asterisks require configuration.

Caution: When you create the Dynamic Provisioning or Dynamic Provisioningfor Mainframe pool, if you specify Mixable for RAID level to display theSelect Pool VOLs window, external volumes with the cache mode set todisabled are not displayed in the Available Pool Volumes table becausethey cannot coexist with volumes of the other RAID levels:When you select these volumes in the Select Pool VOLs window, specify ahyphen (-) for RAID level.

Add

When you click Add, the configured information is added to the right side ofthe Selected Pools table.

Selected Pools table


Item Description


RAID Level Displays RAID level of the pool. If multiple RAID levels existin a pool, this field indicates that RAID levels are mixed. Ifall pool-VOLs are external volumes, a hyphen (-) isdisplayed.

Capacity Displays the total capacity of the created pool in thespecified unit.For open systems, the displayed capacity is approximately4.1 GB (capacity of the management area) less than thetotal capacity of the selected pool-VOLs.For mainframe systems, the displayed capacity isapproximately 3.7 GB (capacity of the management area)less than the total capacity of the selected pool-VOLs.


Drive Type/RPM Displays the data drive type and RPM. If multiple drivetypes or RPMs exist in a pool, this field indicates Mixed.When the volume is the external volume, Drive Typedisplays External Storage and the value of the externalLDEV tier rank.


Displays the pool threshold.• Warning: Warning threshold is displayed.• Depletion: Depletion threshold is displayed.For a Thin Image pool, a hyphen (-) is displayed forDepletion.

Subscription Limit (%) Displays subscription limit of the pool.For Thin Image pool, a hyphen (-) is displayed.




Displays whether the protect function for DP-VOL is beingenabled or disabled. If the setting is enabled, when the poolusage reaches the full size, DP-VOL is protected fromreading and writing requests. And at the same instant, the


Item Description

access attribute of the DP-VOL is changed to the Protectattribute.A hyphen appears if the pool corresponds with one offollowing:• Data Retention Utility is not installed.• Pool type is the type other than DP and DT.

Number of Pool VOLs Displays the number of pool-VOLs.

Tier Management If Dynamic Tiering or Dynamic Tiering for Mainframe isenabled, Auto or Manual for performance monitoring andtier relocation is displayed. If Dynamic Tiering or DynamicTiering for Mainframe is disabled, a hyphen (-) is displayed.


Monitoring Period Displays the time zone of performance monitoring when 24Hours is selected as the Cycle Time. If Dynamic Tiering orDynamic Tiering for Mainframe is disabled, a hyphen (-) isdisplayed.

Monitoring Mode If the continuous mode is enabled, Continuous Mode isdisplayed. If the period mode is enabled, Period Mode isdisplayed.

Relocation speed Displays the page relocation speed: 1(Slowest), 2(Slower),3(Standard), 4(Faster), or 5(Fastest). If Dynamic Tiering orDynamic Tiering for Mainframe is disabled, a hyphen (-) isdisplayed.

Buffer Space for New pageassignment (%)

Displays the information of the buffer space for new pageassignment to each tier.Tier 1: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, the buffer space for newpage assignment to tier 1 is displayed. If you make theDynamic Tiering or Dynamic Tiering for Mainframe functionunavailable, a hyphen (-) is displayed.Tier 2: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, and tier 2 exists, thebuffer space for new page assignment to tier 2 is displayed.If you make the Dynamic Tiering or Dynamic Tiering forMainframe function unavailable, or tier 2 does not exist, ahyphen (-) is displayed.Tier 3: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, and tier 3 exists, thebuffer space for new page assignment to tier 3 is displayed.If you make the Dynamic Tiering or Dynamic Tiering forMainframe function unavailable, or tier 3 does not exist, ahyphen (-) is displayed.

Buffer Space for Tierrelocation (%)

Displays the information of the buffer space for tierrelocation to each tier.Tier 1: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, the buffer space for tierrelocation to tier 1 is displayed. If you make the Dynamic


Item Description

Tiering or Dynamic Tiering for Mainframe functionunavailable, a hyphen (-) is displayed.Tier 2: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, and tier 2 exists, thebuffer space for tier relocation to tier 2 is displayed. If youmake the Dynamic Tiering or Dynamic Tiering forMainframe function unavailable, or tier 2 does not exist, ahyphen (-) is displayed.Tier 3: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, and tier 3 exists, thebuffer space for tier relocation to tier 3 is displayed. If youmake the Dynamic Tiering or Dynamic Tiering forMainframe function unavailable, or tier 3 does not exist, ahyphen (-) is displayed.

Detail Displays the Pool Properties window when a row is selected,and shows the error window when a row is not selected ormultiple rows are selected.

Remove Deletes the pool selected in the Selected Pools window.Displays the error window when a row is not selected.

Next Task Option

Click Next to go to the task setting window, which is indicated in Task NextOption.

Create Pools Confirm windowConfirm proposed settings, name the task, then click Apply. The task will beadded to the execution queue.



Item Description


RAID Level Displays the RAID level. If multiple RAID levels exist in apool, this field indicates that RAID levels are mixed. If allpool-VOLs are external volumes, a hyphen (-) is displayed.

Capacity Displays the pool capacity.


Drive Type/RPM Displays the data drive type and RPM. If multiple drivetypes or RPMs exist in a pool, this field indicates that drivetypes or RPMs are mixed. When the volume is the externalvolume, Drive Type displays External Storage and thevalue of the external LDEV tier rank.




Item Description

Subscription Limit (%) Displays the subscription limit.For Thin Image pool, a hyphen (-) is displayed.










Relocation speed Displays the page relocation speed: 1(Slowest), 2(Slower),3(Standard), 4(Faster), or 5(Fastest). If Dynamic Tiering orDynamic Tiering for Mainframe is disabled, a hyphen (-) isdisplayed.


Displays the information of the buffer space for new pageassignment to each tier.Tier 1: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, the buffer space for newpage assignment to tier 1 is displayed. If you make theDynamic Tiering or Dynamic Tiering for Mainframe functionunavailable, a hyphen (-) is displayed.


Item Description

Tier 2: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, and tier 2 exists, thebuffer space for new page assignment to tier 2 is displayed.If you make the Dynamic Tiering or Dynamic Tiering forMainframe function unavailable, or tier 2 does not exist, ahyphen (-) is displayed.Tier 3: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, and tier 3 exists, thebuffer space for new page assignment to tier 3 is displayed.If you make the Dynamic Tiering or Dynamic Tiering forMainframe function unavailable, or tier 3 does not exist, ahyphen (-) is displayed.


Displays the information of the buffer space for tierrelocation to each tier.Tier 1: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, the buffer space for tierrelocation to tier 1 is displayed. If you make the DynamicTiering or Dynamic Tiering for Mainframe functionunavailable, a hyphen (-) is displayed.Tier 2: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, and tier 2 exists, thebuffer space for tier relocation to tier 2 is displayed. If youmake the Dynamic Tiering or Dynamic Tiering forMainframe function unavailable, or tier 2 does not exist, ahyphen (-) is displayed.Tier 3: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, and tier 3 exists, thebuffer space for tier relocation to tier 3 is displayed. If youmake the Dynamic Tiering or Dynamic Tiering forMainframe function unavailable, or tier 3 does not exist, ahyphen (-) is displayed.


Expand Pool wizard

Expand Pool windowUse this window to add LDEVs to a pool to expand the pool to increase poolcapacity.


Item Description

Drive Type/RPM The Drive Type/RPM of the selected pool or Mixable isdisplayed. When the volume is the external volume, DriveType displays External Storage.

RAID Level Set the RAID level of the selected pool. If the level is notset, Mixable appears. If External Storage is selected inthe Drive Type/RPM field, a hyphen (-) is displayed.

Select Pool VOLs Opens the Select Pool VOLs window.

Total Selected PoolVolumes

Total number of the pool-VOLs selected for this pool.

Total Selected Capacity Total capacity of the pool-VOLs selected for this pool.

Caution: When you create the Dynamic Provisioning or Dynamic Provisioningfor Mainframe pool, if you specify Mixable for RAID level to display theSelect Pool VOLs window, external volumes with the cache mode set todisabled are not displayed in the Available Pool Volumes table becausethey cannot coexist with volumes of the other RAID levels:When you select these volumes in the Select Pool VOLs window, specify ahyphen (-) for RAID level.

Expand Pool Confirm windowConfirm proposed settings, name the task, then click Apply. The task will beadded to the execution queue.


Selected Pool table

Item Description


Selected Pool Volumes table

Item Description

LDEV ID Displays LDEV identifier, which is the combination of LDKC,CU, and LDEV.


Capacity Displays the pool-VOL capacity.


RAID Level Displays RAID level. If a pool-VOL is an external volume, ahyphen (-) is displayed.




Edit Pools wizard

Edit Pools window

Caution: In one pool, if the setting operations are performed with two timesor more to edit many setting items, wait until the primary task applies thenperform the secondary operation. If the secondary operation is performedwhile being applying of the primary task, the primary task is canceled and thesecondary task is applied to the storage system.

Item Description

Multi-Tier Pool Select the checkbox, then Enable or Disable when using ornot using Dynamic Tiering or Dynamic Tiering forMainframe.A pool that consists of the external volumes to which thecache mode is set to Disable cannot be changed fromDisable to Enable.In Thin Image, you cannot change the setting of thisfunction.If TSE-VOL is assigned to the selected pool, the pool cannotbe changed from Disable to Enable.


Item Description

Options for Multi-Tier Pool Specifies the performance monitoring, tier relocation, editbuffer space for new page assignment, and buffer space fortier relocation if Multi-Tier Pool is set to Enable.In Thin Image, you cannot change the setting of thisfunction.Select the Tier Management checkbox, then set the tiermanagement, the cycle time, and the monitoring period.• Tier Management: Select Auto or Manual.• Cycle Time: When selecting Auto in the Tier

Management option, select the cycle of performancemonitoring and tier relocation from the Cycle Time list.

• Monitoring Period: When selecting 24 Hours in theCycle Time list, specify the time of starting and endingof performance monitoring in 00:00 to 23:59 (defaultvalue). Take one or more hours between the startingtime and the ending time. If you specify the startingtime later than the ending time, the performancemonitoring continues until the time when you specify asthe ending time on the next day.

Select the Monitoring Mode checkbox, then set themonitoring mode.Monitoring Mode: Specify the monitoring mode. If youperform the tier relocation weighted to the past periodmonitoring result, select Continuous Mode. If you performthe tier relocation on the specified cycle, select PeriodMode.Select the Relocation Speed checkbox. Then set the tierrelocation speed.Relocation Speed: Specify the page relocation speed whentier relocation is performed. You can set the speed to:1(Slowest), 2(Slower), 3(Standard), 4(Faster), or5(Fastest).Select the Buffer Space for New page assignment checkbox,then set the buffer space for new page assignment.Buffer Space for New page assignment: Enter an integervalue from 0 to 50 as the percentage (%) to set for tier 1,tier 2, and tier 3. If there is no tier, you cannot set thisitem.Select the Buffer Space for Tier relocation checkbox, thenset the buffer space for tier relocation.Buffer Space for Tier relocation: Enter an integer value from2 to 40 as the percentage (%) to set for tier 1, tier 2, andtier 3.If the checkbox is not selected, you cannot set this item.You must set all items if you change the pool setting fromDynamic Provisioning (or Dynamic Provisioning forMainframe) to Dynamic Tiering (or Dynamic Tiering forMainframe).If the checkbox is selected, you cannot collapse the Optionsfor Multi-Tier Pool field.


Item Description

Subscription Limit Select the Subscription Limit checkbox, then enter thesubscription limit (%). In Thin Image, you cannot changethe setting of this function.• If this field is blank, the subscription is set to be

unlimited.• For an open system, use blank or a value in the

following range:(Total V-VOL capacity including the controlinformation / pool capacity) * 100(%) +1 to 65534(%)

• For a mainframe system, use blank or a value in thefollowing range:(Total V-VOL capacity / pool capacity) * 100(%) +1 to65534(%)

• For the open system, when the current subscriptionsetting is unlimited and the value calculated by thefollowing formula exceeds 65534, you cannot configurethe subscription limit.((Total V-VOL capacity including the controlinformation / pool capacity) * 100)

• For the mainframe system, when the currentsubscription setting is unlimited and the valuecalculated by the following formula exceeds 65534, youcannot configure the subscription limit.((Total V-VOL capacity / pool capacity) * 100)

• If the checkbox is not selected, the subscription limit isdisabled.

Pool Name Select the Pool Name checkbox, then enter the pool name.• Prefix: Enter the alphanumeric characters, which are

fixed characters of the head of the pool name. Thecharacters are case-sensitive.

• Initial Number: Enter the initial number following theprefix name, which can be entered up to 9 digits.*

• You can enter up to the 32 characters including theinitial number. The initial number must be 9 or lessdigits.

*When a pool is selected, the pool name appears in thePrefix text box by default. When multiple pools are selected,the initial number from the set number to the maximumnumber of the digit number is automatically set.Example:• When 1 is set in the Initial Number field, number 1 to 9

is automatically given to the pool name.• When 08 is set in the Initial Number field, number 08

to 99 is automatically given to the pool name.• When 098 is set in the Initial Number field, number 098

to 999 is automatically given to the pool name.

Warning Threshold Select the checkbox, then enter a threshold. The minimumthreshold is the pool usage rate plus 1%. The maximumthreshold is 100%.


Item Description

For Thin Image, you cannot change the setting of thisfunction:Check Warning Threshold and enter a threshold.You cannot set this item if the result of the followingcalculation exceeds 95:(used-pool-capacity/pool-capacity) * 100 (%)

Depletion Threshold Select the checkbox, then enter a threshold. The minimumthreshold is the pool usage rate plus 1%. The maximumthreshold is 100%.If you change the Thin Image pool, you cannot set thisitem.


Select the checkbox, then select Yes or No in the protectfunction for DP-VOL. If this function is enabled, when thepool-VOL is blocked, DP-VOL is protected from reading andwriting requests. And at the same instant, the accessattribute of the DP-VOL is changed to the Protect attribute.However, if one of following is applicable, this checkboxgoes inactive:• Data Retention Utility is not installed.• Mainframe pools are selected.


Select the checkbox, then select Yes or No in the protectfunction for DP-VOL. If this function is enabled, when thepool usage reaches the full size, DP-VOL is protected fromreading and writing requests. And at the same instant, theaccess attribute of the DP-VOL is changed to the Protectattribute.However, if one of following is applicable, this checkboxgoes inactive:• Data Retention Utility is not installed.• Mainframe pools are selected.

Caution: If you want to change multiple parameters for a pool two or moretimes, wait until the current task finishes, then change the next settings. Ifyou attempt to change settings before the current task finishes, only thesettings in the next task will be applied, so the result might be different fromwhat you expected.

Edit Pools Confirm windowConfirm proposed settings, name the task, then click Apply. The task will beadded to the execution queue.


Item Description





Drive Type/RPM Displays the data drive type and RPMs. If multiple drivetypes or RPMs exist in a pool, this field indicates Mixed.When the volume is the external volume, Drive Typedisplays External Storage and the value of the externalLDEV tier rank. If all pool-VOLs are external volumes, ahyphen (-) is displayed.




Item Description

Subscription Limit (%) Displays the subscription limit.For Thin Image pool, a hyphen (-) is displayed.










Relocation Speed Displays the page relocation speed: 1(Slowest), 2(Slower),3(Standard), 4(Faster), or 5(Fastest). If Dynamic Tiering orDynamic Tiering for Mainframe is disabled, a hyphen (-) isdisplayed.


Displays the information of the buffer space for new pageassignment to each tier.Tier 1: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, the buffer space for newpage assignment to tier 1 is displayed. If you make theDynamic Tiering or Dynamic Tiering for Mainframe functionunavailable, a hyphen (-) is displayed.


Item Description

Tier 2: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, and tier 2 exists, thebuffer space for new page assignment to tier 2 is displayed.If you make the Dynamic Tiering or Dynamic Tiering forMainframe function unavailable, or tier 2 does not exist, ahyphen (-) is displayed.Tier 3: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, and tier 3 exists, thebuffer space for new page assignment to tier 3 is displayed.If you make the Dynamic Tiering or Dynamic Tiering forMainframe function unavailable, or tier 3 does not exist, ahyphen (-) is displayed.


Displays the information of the buffer space for tierrelocation to each tier.Tier 1: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, the buffer space for tierrelocation to tier 1 is displayed. If you make the DynamicTiering or Dynamic Tiering for Mainframe functionunavailable, a hyphen (-) is displayed.Tier 2: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, and tier 2 exists, thebuffer space for tier relocation to tier 2 is displayed. If youmake the Dynamic Tiering or Dynamic Tiering forMainframe function unavailable, or tier 2 does not exist, ahyphen (-) is displayed.Tier 3: If you make the Dynamic Tiering or Dynamic Tieringfor Mainframe function available, and tier 3 exists, thebuffer space for tier relocation to tier 3 is displayed. If youmake the Dynamic Tiering or Dynamic Tiering forMainframe function unavailable, or tier 3 does not exist, ahyphen (-) is displayed.


Delete Pools wizard

Delete Pools window

Item Description


RAID Level Displays the RAID level.If multiple RAID levels exist in a pool, this field indicatesthat RAID levels are mixed. If all pool-VOLs are externalvolumes, a hyphen (-) is displayed.



Drive Type/RPM Displays the data drive type and RPM of the pool. If multipledrive types or RPMs exist in a pool, this field indicates thatdrive types or RPMs are mixed. When the volume is theexternal volume, Drive Type displays External Storageand the value of the external LDEV tier rank.


Displays the pool threshold.• Warning: Warning threshold is displayed.• Depletion: Depletion threshold is displayed.


Item Description

For a Thin Image pool, a hyphen (-) is displayed forDepletion.



Next Task Option

Click Next to go to the task setting window, which is indicated in Task NextOption.

Delete Pools Confirm windowConfirm proposed settings, name the task, then click Apply. The task will beadded to the execution queue.


Item Description



Item Description









Expand V-VOLs wizard

Expand V-VOLs windowUse this wizard to expand the V-VOLs to the defined final capacity of thevirtual volumes.


Item Description

Specify total capacity Select this checkbox when you specify the total capacity ofV-VOL.

Specify additional capacity Select this checkbox when you specify the additionalcapacity of V-VOL.

Offset boundary Select this checkbox if you want to offset the specified LDEVcapacity by boundary.

Text Box Specify the V-VOL (LDEV) capacity within the range ofvalues indicated below the text box.

Expand V-VOLs Confirm windowConfirm proposed settings, name the task, then click Apply. The task will beadded to the execution queue.


Item Description





Capacity Displays the capacity of the LDEV.• Current: Displays the capacity before expanding the

volume.• Assigned: Displays the capacity that is derived by the

current value subtracted from the final value. The valuemay not be exact because the size is displayed withtwo decimal places.

• Final: Displays the capacity after expanding thevolume.

Provisioning Type Displays the LDEV type. In this case, DP is displayed.

Attribute Displays the attribute of the LDEV.Command Device: Command device.TSE: TSE-VOL.Hyphen (-): Volume in which the attribute is not defined.


Restore Pools window

Item Description



Capacity Displays the pool capacity. If the pool is blocked and pool-VOLs that belong to the pool cannot be identified, 0 isdisplayed.







Item Description

If the pool is blocked and pool-VOLs that belong to the poolcannot be identified, 0 is displayed.

Shrink Pool window

Prediction Result of Shrinking table

Item Description




Capacity(Used/Total) Displays the capacity before and after shrinking.• Before Shrinking: Displays the used capacity, total

capacity before shrinking and the usage rates.• After Shrinking: Displays the used capacity, total

capacity after shrinking and the usage rates.



Item Description






Stop Shrinking Pools window

Item Description




Pool Type Displays the pool type.


Item Description

For a Dynamic Provisioning pool, DP is displayed.For a Dynamic Tiering pool, DT is displayed.For a Dynamic Provisioning for Mainframe pool, MainframeDP is displayed.For a Dynamic Tiering for Mainframe pool, Mainframe DT isdisplayed.



Displays the pool threshold.• Warning: Warning threshold is displayed.• Depletion: Depletion threshold is displayed.For a Thin Image or Copy-on-Write Snapshot pool, ahyphen (-) is displayed for Depletion.



Complete SIMs window

Item Description

Task Name Confirm the settings, type a unique task name or accept thedefault, then click Apply.


Item Description

A task name is case-sensitive and can be up to 32 ASCIIletters, numbers, and symbols. The default is <date>-<window name>.

Select Pool VOLs windowUse this window to add pool-VOLs to a pool. Up to 1024 volumes can beadded including the volumes already in the pool. Only the LDEVs assigned tothe logged-on user are available.

• Up to three different drive types of pool-VOLs can be registered in thesame pool.


Available Pool Volumes table

Only the LDEVs assigned to the user are displayed.

Item Description

LDEV ID Displays the LDEV identifier, which is the combination ofLDKC, CU, and LDEV.




RAID Level Displays the RAID level. If an LDEV is an external volume, ahyphen (-) is displayed.

Drive Type/RPM Displays the data drive type and RPM. When the volume isthe external volume, Drive Type displays ExternalStorage.



Cache Mode Displays whether the cache mode is enabled. If the LDEV isnot an external volume, a hyphen (-) is displayed.

Encryption Displays the information about parity group encryption.


Item Description

Enabled: The encryption of the parity group which containsLDEV is enabled.Disabled: The encryption of the parity group which containsLDEV is disabled.If LDEV is a V-VOL for Dynamic Provisioning, externalvolume, or migration volume, a hyphen (-) is displayed.


External LDEV Tier Rank

Specify the tier rank of the external volume. If there is no external volume inthe Available Pool Volumes table or Selected Pool Volumes table, youcannot select this option.

Add

When you select a row in the Available Pool Volumes table and click Add, theselected pool-VOL is added to the Selected Pool Volumes table.

Note: Up to 1,024 volumes can be added including the volumes already inthe pool.For a pool, you can add volumes whose Drive Type/RPM settings are thesame and whose RAID Levels are different. For example, you can add thefollowing volumes to the same pool:

• Volume whose Drive Type/RPM is SAS/15K and whose RAID Level is 5(3D+1P)

• Volume whose Drive Type/RPM is SAS/15K and whose RAID Level is 5(7D+1P)

Remove

When you select a row in Selected Pool Volumes table and click Remove, theselected pool-VOL is removed from the Selected Pool Volumes table.



Item Description





RAID Level Displays the RAID level. If an LDEV is an external volume, ahyphen (-) is displayed.

Drive Type/RPM Displays the data drive type and RPM. When the volume isthe external volume, Drive Type displays ExternalStorage.

External LDEV Tier Rank Displays the tier rank of the external volume. If the volumeis not an external volume, a hyphen(-) is displayed.



Cache Mode Displays whether the cache mode is enabled. If the LDEV isnot an external volume, a hyphen (-) is displayed.

Encryption Displays the information about parity group encryption.


Item Description

Enabled: The encryption of the parity group which containsLDEV is enabled.Disabled: The encryption of the parity group which containsLDEV is disabled.If LDEV is a V-VOL for Dynamic Provisioning, externalvolume, or migration volume, a hyphen (-) is displayed.


Reclaim Zero Pages window

Item Description





Capacity Displays the capacity.


Attribute Displays the attribute of the LDEV.Command Device: Command device.Hyphen (-): Volume in which the attribute is not defined.


Stop Reclaiming Zero Pages window

Item Description





Capacity Displays the capacity.


Attribute Displays the attribute of the LDEV.Command Device: Command device.Hyphen (-): Volume in which the attribute is not defined.

Pool Property windowUse this window to view and change pool properties. Only the LDEVSassigned to the logged-on user are available.


Pool Properties table

Item Description



Capacity Displays the pool capacity in the specified unit.

User-Defined Threshold(Warning/Depletion)

Displays the user-defined threshold (Warning/Depletion).

Subscription Limit Displays the subscription limit.For a Thin Image pool, a hyphen (-) is displayed for Currentor Limit.



Item Description

Pool VOL with System Area(Name)

Displays LDEV ID and LDEV name of the pool-VOL whichincludes the system area. If you open this window from theSelected Pools table in the Create Pool window, a hyphen(-)is displayed.

Pool Volumes table

Only the LDEVs assigned to the user are displayed.

Item Description



Capacity Displays the pool volumes capacity in the specified unit. Ifyou open this window from the Selected Pools table in theCreate Pool window, the LDEV capacity selected in theSelect Pool VOLs window is displayed.


RAID Level Displays the RAID level. If a pool-VOL is an externalvolume, a hyphen (-) is displayed.

Drive Type/RPM Displays the tier ID. A hyphen (-) is displayed whenselecting the pool for Dynamic Provisioning, DynamicProvisioning for Mainframe, or Thin Image.

Tier ID Displays the tier ID. A hyphen (-) is displayed when youselect a Dynamic Provisioning, Dynamic Provisioning forMainframe or Thin Image pool.



Encryption Displays the information about parity group encryption.Enabled: The encryption of the parity group which containsLDEV is enabled.Disabled: The encryption of the parity group which containsLDEV is disabled.If LDEV is a V-VOL for Dynamic Provisioning, externalvolume, or migration volume, a hyphen (-) is displayed.


View Tier Properties windowThis window shows tier properties and a performance graph:


• For pools on page E-57• For V-VOLs on page E-61

When the pool name (pool ID) appears in the graph banner, you are lookinga pool information. When the LDEV name (LDEV ID) appears in the graphbanner, you are looking at V-VOL information.

For pools

The following tables list the View Tier Properties information.

When selecting Entire Pool or Tiering Policy

Item Description

Entire Pool or Tiering Policy Select the following resource to display the performancegraph.• Entire Pool: Displays the performance graph of the

entire pool.• Tiering Policy: Displays the performance graph of the

tiering policy.

All(0), and from Level1(1)to Level31(31)

Select the Tiering Policy.


Item Description

The performance graph that corresponds to the selectedtiering policy appears.

Tier Properties table

Item Description

Pool Name(ID) Displays the pool name and ID.

Tier name Displays the tier names: Tier1, Tier2, Tier3, and Total. Eachcolumn displays information about the tier.

Drive Type/RPM Displays the data drive type and RPM of tier.If multiple types exist in a tier, Mixed is displayed. For anexternal volume, Drive Type displays External Storage withthe value of the external LDEV tier rank.

Buffer Space Displays the following buffer spaces.• New page assignment: Buffer spaces for new page

assignment.• Tier relocation: Buffer spaces for tier relocation.

Total Capacity Displays the total capacity of each tier and total capacity ofthe pool.

Used Capacity (Used %) Displays the percentage of the used capacity for the pooland each tier. The field is updated asynchronously with theRecent Tier Utilization table and when the View TierProperties window is opened. The Used Capacity of each tiermay differ from the Total value.

Tiering Policy: tieringpolicy name

Displays the used capacity size and percentage related tothe tiering-policy of the pool and each tier. This itemdisplays when you make a Tiering Policy selection.

Recent Tier Utilization (monitoring period) table

Item Description

Header area If a error occurs, a message appears.


Performance Utilization Displays the percentage of progress in performanceutilization processing.

Average Number of I/O(per Hour)

Displays the average number of I/Os on an hourly basis.*

Tiering Policy: tieringpolicy name

Displays the average number of I/Os for the pool and eachtier that are related to the tiering-policy. This item displayswhen you make a Tiering Policy selection.*

* This field is updated when performance monitoring information is collected,asynchronously with Used Capacity (Used %). If ? is displayed, take the actionsdisplayed in the header area of the Recent Tier Utilization table. If an error message and


Item Description

countermeasure are not shown in the header area of the Recent Tier Utilization table,refresh the window. If ? continues to display, call the Hitachi Data Systems SupportCenter.

Performance Graph

Item Description

Performance graph Displays the performance graph of the entire pool or tieringpolicy.

Pool If Entire Pool and the period mode of the monitoring modeare specified, this item appears. When this checkbox isselected, the performance graph appears. The vertical scaleof the performance graph indicates the average number ofI/Os on an hourly basis. The horizontal scale of theperformance graph indicates the capacity.If there is no monitor data, this item does not appear.

Pool(Weighted average) If Entire Pool and the continuous mode of the monitoringmode are specified, this item appears. When this checkboxis selected, the performance graph appears. The verticalscale indicates the average number of I/Os on an hourlybasis. The number of I/Os is a weighted, averaged with themonitoring data from the past cycle weighted against themonitoring data from the current cycle. The horizontal scaleindicates the capacity.If there is no monitor data, this item does not appear.

Policy If Tiering Policy and the period mode of the monitoringmode are specified, this item appears. When the checkboxis selected, the performance graph appears. The verticalscale of the performance graph indicates the averagenumber of I/Os on an hourly basis. The horizontal scale ofthe performance graph indicates the capacity.If there is no monitor data, this item does not appear.

Policy(Weighted average) If Tiering Policy and the continuous mode of the monitoringmode are specified, this item appears. When the checkboxis selected, the performance graph appears. The verticalscale of the performance graph indicates the averagenumber of I/Os on an hourly basis. The horizontal scale ofthe performance graph indicates the capacity.If there is no monitor data, this item does not appear.

Tier1 Displays the performance graph of tier1. The vertical scaleindicates the average number of I/Os on an hourly basis.The horizontal scale indicates the capacity.If there is no monitor data in tier1, this item does notappear.

Tier2 Displays the performance graph of tier2. The vertical scaleindicates the average number of I/Os on an hourly basis.The horizontal scale indicates the capacity.


Item Description

If there is no monitor data in tier2, this item does notappear.


Tier1 range Displays the range in tier1.If there is no monitor data in tier1, this item does notappear.


The following describes how to read the performance graph when it containspool information.

The vertical scale of the graph indicates an average number of I/Os by eachhour and the horizontal scale indicates capacity (GB) of the area where theI/Os are performed.

The two lines in the graph indicate tier 1 range and tier 2 range. They arecalculated when the collection of performance monitoring has been completed(monitoring period is completed). They show the boundary of each tier.

A maximum of 127 dots is shown in the graph. The following informationappears over a dot in the graph depending on where the cursor is placed.

• Capacities, average I/Os, and total I/Os appear if the cursor is placed onthe dot of the Tier1, Tier2, Tier3, Pool, or the Pool(Weighted average).

• The lower value of the average I/Os appears if the cursor is placed on thedot of the Tier1 Range or the Tier2 Range.

The following table describes these items.

Item Description

Capacities The capacity (GB) of the area from the dot of the maximumvalue on the vertical scale to a specified dot. The capacity ofthe dot on the vertical scale is 0.00 GB.

Average I/Os All I/Os are sorted into 127 sections. The average I/O is therepresentative I/O number assigned to each section, basedon the definition of the storage system. By the total numberof I/Os, the number of dots may be 127 or less.

Total I/Os The total number of I/Os in the section from the dot of themaximum value on the vertical scale to a specified dot. Thetotal I/Os is calculated using the average I/Os and capacitiesin the specified section. If the specified dot is on the verticalscale, the total I/Os is zero.


When no I/Os are in the lower tier with multiple tiers, the tier range line isplaced at 0 on the vertical scale.

For example, if the dot is placed far from the lower limit of the tier range, thelower limit levels of the Tier 1 Range and Tier 2 Range are adjusted toimprove the visibility of the performance graph. In this case, the value that isobtained by Command Control Interface may not correspond with the valueof the dot displayed in a performance graph.

For V-VOLs

The following table provides the View Tier Properties table information whenLDEV information is present.

Tier Properties table when selecting a DP-VOL

Item Description

LDEV ID Displays the combination of the LDKC, CU, and LDEV.

LDEV name Displays the LDEV name.

Tiering Policy Displays the tiering policy name and ID.

New Page Assignment Tier Displays the new page assigned tier.

Tier Relocation Displays whether tier relocation is set to Enabled orDisabled.

Relocation Priority Displays the relocation priority.


Drive Type/RPM Displays the data drive type and RPM of tier.If multiple types exist in a tier, Mixed is displayed. For anexternal volume, Drive Type displays External Storage withthe value of the external LDEV tier rank.

Pool Capacity Displays the total capacity of each tier and total capacity ofthe pool.

Used Capacity (Used %) Displays the percentage of the used capacity for the pooland each tier. The field is updated asynchronously with theRecent Tier Utilization table and when the View TierProperties window is opened. The Used Capacity of each tiermay differ from the Total value.

Recent Tier Utilization (monitoring period) table

Item Description

Header area If a error occurs, a message appears.


Average Number of I/O(per Hour)

Displays the average number of I/Os on an hourly basis.*


Item Description

* This field is updated when performance monitoring information is collected,asynchronously with Used Capacity (Used %). If ? is displayed, take the actionsdisplayed in the header area of the Recent Tier Utilization table. If an error message andcountermeasure are not shown in the header area of the Recent Tier Utilization table,refresh the window. If ? continues to display, call the Hitachi Data Systems SupportCenter.

Performance Graph

Item Description

Performance graph Displays the performance graph of the entire pool or tieringpolicy.

Volume If the period mode of the monitoring mode is specified, thisitem appears. When this checkbox is selected, theperformance graph appears. The vertical scale of theperformance graph indicates the average number of I/Os onan hourly basis. The horizontal scale of the performancegraph indicates the capacity.If there is no monitor data, this item does not appear.

Volume(Weighted average) If the continuous mode of the monitoring mode is specified,this item appears. When this checkbox is selected, theperformance graph appears. The vertical scale indicates theaverage number of I/Os on an hourly basis. The number ofI/Os is a weighted, averaged with the monitoring data fromthe past cycle weighted against the monitoring data fromthe current cycle. The horizontal scale indicates thecapacity.If there is no monitor data, this item does not appear.





Tier2 range Displays the range in tier2.


Item Description

If there is no monitor data in tier2, this item does notappear.

The following describes how to read the performance graph when LDEVinformation is presented.

The vertical scale of the graph indicates an average number of I/Os by eachhour and the horizontal scale indicates a capacity, in GB, of the area wherethe I/Os are performed.

The two lines in the graph indicate tier 1 range and tier 2 range. Theseranges are calculated when the collection of performance monitoring data iscomplete (monitoring period is completed). They show the boundary of eachtier.

A maximum of 127 dots is shown in the graph. The following informationappears over a dot in the graph depending on where the cursor is placed.

• Capacities, average I/Os, and total I/Os appear if the cursor is placed onthe dot of the Tier1, Tier2, Tier3, Volume or the Volume(Weightedaverage).

• The lower value of the average I/Os appears if the cursor is placed on thedot of the Tier1 Range or the Tier2 Range.

The following table describes these items.

Item Description

Capacities The capacity (GB) of the area from the dot of the maximumvalue on the vertical scale to a specified dot. The capacity ofthe dot on the vertical scale is 0.00 GB.

Average I/Os All I/Os are sorted into 127 sections. The average I/O is therepresentative I/O number assigned to each section, basedon the definition of the storage system. By the total numberof I/Os, the number of dots may be 127 or less.

Total I/Os The total number of I/Os in the section from the dot of themaximum value on the vertical scale to a specified dot. Thetotal I/Os is calculated using the average I/Os and capacitiesin the specified section. If the specified dot is on the verticalscale, the total I/Os is zero.

When no I/Os are in the lower tier with multiple tiers, the tier range line isplaced at 0 on the vertical scale.


Monitor Pools window


Item Description


Number of Pool VOLs Displays the number of pool-VOLs in the selected pool.

Capacity Displays the information about the pool capacity.• Total: Total capacity of pool.

Using Option, you can select unit of capacity.¢ One block equals 512 bytes and one page equals

42 megabytes in a pool capacity of DynamicProvisioning, Dynamic Tiering, or Thin Image.

¢ One block equals 512 bytes and one page equals38 megabytes in a pool capacity of DynamicProvisioning for Mainframe Dynamic Tiering forMainframe.




Recent Monitor Data Displays the period of monitoring time as follows:Starting-time-Ending-timeIf the monitoring data is being obtained, only the startingtime is displayed.If the latest monitoring data does not exist, a hyphen (-) isdisplayed.


Stop Monitoring Pools window


Item Description






¢ One block equals 512 bytes and one page equals38 megabytes in a pool capacity of DynamicProvisioning for Mainframe or Dynamic Tiering forMainframe.






Start Tier Relocation window


Item Description












Item Description

Relocation Speed Displays the tier relocation speed: 1(Slowest), 2(Slower),3(Standard), 4(Faster), or 5(Fastest)

Stop Tier Relocation window


Item Description










Recent Monitor Data Displays the period of monitoring time as follows:


Item Description

Starting-time-Ending-timeIf the monitoring data is being obtained, only the startingtime is displayed.If the latest monitoring data does not exist, a hyphen (-) isdisplayed.

Relocation Progress(%) Displays the progress percentage of the tier relocation.0 to 99: The relocation is performed at the indicatedpercentage progression.100: The relocation operation is not in performed, or therelocation is complete.For details about the tier relocation, see the tier relocationlog file. For details about the table items of the tierrelocation log file, see Tier relocation log file contents onpage 4-38.

Relocation Speed Displays the tier relocation speed: 1(Slowest), 2(Slower),3(Standard), 4(Faster), or 5(Fastest)

View Pool Management Status window


Pool Management Status table

Item Description



Number of V-VOLs Displays the number of V-VOLs associated with the pool,and the maximum number of V-VOLs that can be associatedwith the pool.If you select a Dynamic Provisioning, Dynamic Tiering,Dynamic Provisioning for Mainframe, or a Dynamic Tieringfor Mainframe pool, this item appears.

Number of Primary VOLs Displays the number of primary volumes of Thin Imagepairs that are associated with the pool.If you select a Thin Image pool, this item appears.

Number of Pool VOLs Displays the number of pool-VOLs set for the pool, and themaximum number of pool-VOLs that can be set for the pool.

Tier Management If Dynamic Tiering or Dynamic Tiering for Mainframe isenabled, Auto or Manual of performance monitoring and tierrelocation is displayed. If Dynamic Tiering or DynamicTiering for Mainframe is disabled, a hyphen (-) is displayed.

Monitoring Mode Displays the monitoring mode that is set for the pool. If thecontinuous mode is enabled, Continuous Mode is displayed.If the period mode is enabled, Period Mode is displayed. IfDynamic Tiering or Dynamic Tiering for Mainframe isdisabled, a hyphen (-) is displayed.

Monitoring Status Displays the status of pool monitoring.If the monitoring is being performed, In Progress isdisplayed. A hyphen (-) is displayed other than this case.

Relocation Speed/Actual Displays the tier relocation speed: 1(Slowest), 2(Slower),3(Standard), 4(Faster), or 5(Fastest). Actual displays themeasured value of the tier relocation capacity per second.

Pool Management Task(Status/Progress)

Displays the status and progress ratio of the poolmanagement task being performed to the pool, and averageprogress ratio of the each V-VOL in the pool.Waiting for Rebalance: The rebalance process is beingwaited.Rebalancing: The rebalance process is being performed.Waiting for Relocation: The tier relocation process is beingwaited.Relocating: The tier relocation process is being performed.


Item Description

Waiting for Shrink: The pool shrinking process is beingwaited.Shrinking: The pool shrinking process is being performed.Blank:The pool management task is not being performed tothe pool.The following values that are displayed in the VirtualVolume table may not correspond with the value displayedfor this item. This is because the progress of the poolmanagement task is calculated after the progress of eachV-VOL displayed in the Virtual Volume table is calculated.• Pool Management Task - Status• Pool Management Task - Progress(%)For details about the tier relocation, see the tier relocationlog file. For details about the table items of the tierrelocation log file, see Tier relocation log file contents onpage 4-38.

Relocation Result Displays the status of the tier relocation processing.In Progress: The status of Pool Management Task isWaiting for Relocation or Relocating.Completed: The tier relocation operation is not in progress,or the tier relocation is complete.Uncompleted (n% relocated): The tier relocation issuspended at the indicated percentage progression.Hyphen (-): The pool is not a Dynamic Tiering or DynamicTiering for Mainframe pool.

Capacity • Used/Total: Displays the used and total pool capacity.If the pool consists of multiple pool-VOLs, the sum ofits capacities is displayed in the Total field.

• Free: Displays the free and formatted pool capacity. Ifthe pool consists of multiple pool-VOLs, the sum of itscapacities is displayed in the Total field.

Virtual Volume table

If you select a Dynamic Provisioning, Dynamic Tiering, Dynamic Provisioningfor Mainframe, or a Dynamic Tiering for Mainframe pool, this table displays.

Item Description



Pool Management Task • Status: Displays the pool management task beingperformed to the pool.Waiting for Rebalance: The rebalance process is beingwaited.Rebalancing: The rebalance process is being performed.


Item Description

Waiting for Relocation: The tier relocation process isbeing waited.Relocating: The tier relocation process is beingperformed.Waiting for Shrink: The pool shrinking process is beingwaited.Shrinking: The pool shrinking process is beingperformed.Blank:The pool management task is not beingperformed to the pool.

• Progress(%): Displays V-VOL progress percentage (%)of the pool management task being performed. Ahyphen (-) is displayed when the pool managementtask is not performed.

V-VOL Management Task • Status: Displays the V-VOL management task beingperformed to V-VOL.Reclaiming Zero Pages: The zero page reclaimprocessing that is being performed.Waiting for Zero Page Reclaiming: The zero pagereclaim processingBlank:The V-VOL management task is not beingperformed to V-VOL.

• Progress(%): Displays the progress percentages (%) ofthe V-VOL management task being performed. Ahyphen (-) is displayed when the V-VOL managementtask is not performed.


Capacity • Total: Displays the V-VOL capacity.• Used: Displays the V-VOL used capacity.

The displayed value of Total might be larger than thedisplayed value of Used due to following reasons:¢ Used displays the used V-VOL capacity which is

rounded up on each page.¢ If the emulation type is 3390-A, the used capacity

of V-VOL includes the capacity of control cylinders(7 Cyl is required per 1,113 Cyl).

¢ If the emulation type is 3390-A and the TSEAttribute is set to Enable, the used capacity of V-VOL includes the management area capacity.

• Used(%): Displays the V-VOL usage ratio.

Tiering Policy Displays the tiering policy name and ID.All(0): Policy in which all tiers of the pool are used.Level1(1) - Level5(5):Policy selected from levels 1 to 5 isset to the V-VOL.Level6(6) - Level31(31): Policy defined by the user and setto the V-VOL.Hyphen (-): V-VOL is not the V-VOL of Dynamic Tiering orDynamic Tiering for Mainframe V-VOL.


Item Description

New Page Assignment Tier Displays the new page assigned tier.High: High is set to V-VOL.Middle: Middle is set to V-VOL.Low: Low is set to V-VOL.Hyphen (-): V-VOL is not the Dynamic Tiering or DynamicTiering for Mainframe V-VOL.

Tier Relocation Displays whether tier relocation is set to enable or disable.If the Dynamic Tiering or Dynamic Tiering for Mainframe V-VOL is not used, a hyphen (-) is displayed.

Relocation Priority Displays the relocation priority.Prioritized: The priority is set to V-VOL.Blank: The priority is not set to V-VOL.Hyphen (-): V-VOL is not the Dynamic Tiering or DynamicTiering for Mainframe V-VOL or the tier relocation functionis disabled.

Attribute Displays the attribute of the LDEV.TSE: TSE-VOL.Hyphen (-): Volume in which the attribute is not defined.

Virtual Storage Machine Information about the virtual storage machine.• Model / Serial Number: Model name and serial number

of the virtual storage machine that has LDEV.• LDEV ID: Virtual LDEV ID. If a Virtual LDEV ID is not

assigned to LDEV, this column is blank.• Device Name: Virtual device name, which is a

combination of the virtual emulation type, virtual LUSEvolume number, and the virtual CVS attribute. Valuesof the virtual emulation type, virtual LUSE volumenumber, and virtual CVS attribute appear only for itemsthat have been set. This column is blank when thevirtual emulation type, virtual LUSE volume number,and virtual CVS attribute are not set. If the virtual CVSattribute is set, CVS is attached as the suffix to thedevice name.

• SSID: Virtual SSID. If Virtual SSID is not set for LDEV,this column is blank.

• Attribute: Virtual LDEV attribute. If the attribute is notset for LDEV, this column is blank.


Edit External LDEV Tier Rank wizard

Edit External LDEV Tier Rank window


Item Description






External LDEV Tier Rank Displays the tier rank of the external volume.

Change Changes the tier rank of the selected pool-VOL to High,Middle, or Low.


Edit External LDEV Tier Rank Confirm window

Selected Pool table

Item Description



Item Description






External LDEV Tier Rank Displays the tier rank of the external volume.


Edit Tiering Policies wizard

Edit Tiering Policies window

Tiering Policies table

Item Description

ID Displays the ID of the tiering policy.

Tiering Policy Displays the name of the tiering policy.

Tier1 Max(%) Displays the maximum percentage that is allocated to tier 1in the total capacity to which tier relocation is performed.For a policy with an ID from 0 to 5, a hyphen (-) isdisplayed.

Tier1 Min(%) Displays the minimum percentage that is allocated to tier 1in the total capacity to which tier relocation is performed.For a policy whose ID is from 0 to 5, a hyphen (-) isdisplayed.


Tier3 Min(%) Displays the minimum percentage that is allocated to tier 3in the total capacity to which tier relocation is performed.


Item Description

For a policy whose ID is from 0 to 5, a hyphen (-) isdisplayed.

Number of V-VOLs Displays the number of V-VOLs to which the tiering policy isset.

Change Displays the Change Tiering Policy window when you selectthe row and click this button.A policy with an ID is from 0 to 6 cannot be changed.

Edit Tiering Policies Confirm window

Tiering Policies table

Item Description

ID Displays the ID of the tiering policy.

Tiering Policy Displays the name of the tiering policy.


Tier1 Min(%) Displays the minimum percentage that is allocated to tier 1in the total capacity to which tier relocation is performed.


Item Description

For a policy whose ID is from 0 to 5, a hyphen (-) isdisplayed.


Tier3 Min(%) Displays the minimum percentage that is allocated to tier 3in the total capacity to which tier relocation is performed.For a policy whose ID is from 0 to 5, a hyphen (-) isdisplayed.

Number of V-VOLs Displays the number of V-VOLs to which the tiering policy isset.

Change Tiering Policy Window

Change Tiering Policy table

Item Description

Tiering Policy Displays the tiering policy name and policy ID.

Tier1 Max(%) Select the maximum percentage that is allocated to tier 1 inthe total capacity for the tier relocation from 0 (%) to 100(%). The setting value is needed to satisfy either one offollowing conditions:Equal to Tier1 MinBigger than Tier1 Min

Tier1 Min(%) Select the minimum percentage that is allocated to tier 1 inthe total capacity for the tier relocation from 0 (%) to 100


Item Description

(%). The setting value is needed to satisfy either one offollowing conditions:Equal to Tier1 MaxSmaller than Tier1 Max

Tier3 Max(%) Select the maximum percentage that is allocated to tier 3 inthe total capacity for the tier relocation from 0 (%) to 100(%). The setting value is needed to satisfy either one offollowing conditions:Equal to Tier1 MinBigger than Tier1 Min

Tier3 Min(%) Select the minimum percentage that is allocated to tier 3 inthe total capacity for the tier relocation from 0 (%) to 100(%). The setting value is needed to satisfy either one offollowing conditions:Equal to Tier1 MaxSmaller than Tier1 Max

* The total of Tier1 Min and Tier3 Min must be 100(%) or less.

Change Pool Configuration Pattern Window

For Dynamic Provisioning or Dynamic Provisioning for Mainframepools

When you create a Dynamic Provisioning or Dynamic Provisioning forMainframe pool, the following table displays.


Pool Configuration Patterns table

Item Description

Priority Displays the priority of the pool configuration.

Selected Displays whether the pool configuration is selected or not.

Total Capacity Displays the total capacity of the pool.

Drive Type/RPM Displays the data drive type and RPM of the pool.

RAID Level Displays the RAID level of the pool.

Select If the pool configuration is changed, select a row in the PoolConfiguration Patterns table. Then click this button. Theselected pool configuration is reflected to the pool setting.

For Dynamic Tiering or Dynamic Tiering for Mainframe pools

When you create a Dynamic Tiering or Dynamic Tiering for Mainframe pool,the following table displays.

Pool Configuration Patterns table

Item Description

Priority Displays the priority of the pool configuration.

Selected Displays whether the pool configuration is selected or not.

Total Capacity Displays the total capacity of the pool

Tier 1 Displays the tier 1 information.


Item Description

Drive Type/RPM: Displays the data drive type and RPM ofpool-VOLs.RAID Level: Displays the RAID level of pool-VOLs.Rate (%): Displays the percentage of the tier 1 against thetotal capacity of the pool.

Tier 2 Displays the tier 2 information.Drive Type/RPM: Displays the data drive type and RPM ofpool-VOLs.RAID Level: Displays the RAID level of pool-VOLs.Rate (%): Displays the percentage of the tier 2 against thetotal capacity of the pool.

Tier 3 Displays the tier 3 information.Drive Type/RPM: Displays the data drive type and RPM ofpool-VOLs.RAID Level: Displays the RAID level of pool-VOLs.Rate (%): Displays the percentage of the tier 3 against thetotal capacity of the pool.

Select If the pool configuration is changed, select a row in the PoolConfiguration Patterns table. Then click this button. Theselected pool configuration is reflected to the pool setting.


Glossary

This glossary defines the special terms used in this document. Click the letter links below tonavigate.

A

access attributeThe setting on a logical volume (mainframe or open-systems) that determines whetherhosts can read and/or write to the volume.

Adraddress

ALarbitrated loop

alias deviceA formatted but unused mainframe logical device (LDEV) whose address can be used asan alias for a Parallel Access Volume (PAV) base device. See also base device.

allocated volumeA logical device (LDEV) for which one or more host paths are defined.

AL-PAarbitrated-loop physical address

alternate pathA secondary path (port, target ID, LUN) to a logical volume, in addition to the primarypath, that is used as a backup in case the primary path fails.

AMSHitachi Adaptable Modular Storage

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Glossary-1Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

APIapplication program interface

APLBactive path load balancing

arrayAnother name for a RAID storage system.

array domainAll functions, paths, and drives controlled by one back-end director (BED) feature (pairof boards). An array domain can contain a mix of mainframe and open-systems volumetypes. RAID-level intermix (all RAID types) is also allowed within an array domain.

array groupSee RAID group.

ASLArray Support Library

asyncasynchronous

at-time splitOperation that allows multiple pairsplit operations to be performed at a pre-determinedtime.

audit logFiles that store a history of the operations performed from Hitachi Device Manager -Storage Navigator and the service processor (SVP), commands that the storage systemreceived from hosts, and data encryption operations.

ave, avgaverage

B

back-end director (BED)The hardware component that controls the transfer of data between the drives andcache. A BED feature consists of a pair of boards. A BED is also referred to as a diskadapter (DKA).

base deviceA formatted mainframe logical device (LDEV) that contains user data and can beaccessed via alias devices using IBM Parallel Access Volume (PAV) host software. A base



device must be defined to the host as a "B" device type (for example, 3390B-9). Seealso alias device.

base emulation typeEmulation type that is set when drives are installed. Determines the device emulationtypes that can be set in the RAID group.

BCbusiness continuity

BCMBusiness Continuity Manager

BEDSee back-end director (BED).

bind modeIn bind mode the Cache Residency Manager extents are used to hold read and writedata for specific extents on volumes. Data written to the Cache Residency Manager bindarea is not destaged to the drives. For bind mode, all targeted read and write data istransferred at host data transfer speed.

BLK, blkblock

bmpbitmap

C

C/TSee consistency time (C/T).

cacache

cache logical partition (CLPR)Consists of virtual cache memory that is set up to be allocated to different hosts incontention for cache memory.

capacityThe amount of data storage space available on a physical storage device, usuallymeasured in bytes (MB, GB, TB, etc.).

CCConcurrent Copy; channel command; cylinder-cylinder



CCIHitachi Command Control Interface software

CFWcache fast write

CGSee consistency group (CTG).

CLIcommand line interface

CLPRSee cache logical partition.

clusterMultiple-storage servers working together to respond to multiple read and writerequests.

command deviceA dedicated logical volume used only by Command Control Interface to interface withthe storage system. Can be shared by several hosts.

concatenated parity groupA configuration where the VDEVs corresponding to a pair of RAID 10 (2D+2D) or RAID5 (7D+1P) parity groups, or four RAID 5 (7D+1P) parity groups, are interleaved on aRAID stripe level on a round-robin basis. A logical RAID stripe line is created as aconcatenation of the individual RAID stripe lines. This has the effect of dispersing I/Oactivity over twice or four times the number of disks, but it does not change thenumber, names, or size of VDEVs, and hence it doesn't make it possible to assign largerLDEVs to them. Note that we often refer to RAID 10 (4D+4D), but this is actually twoRAID 10 (2D+2D) parity groups interleaved together.

configuration definition fileA text file that defines the configuration, parameters, and options of Command ControlInterface (CCI) operations. It also defines the connected hosts and the volumes andgroups known to the Command Control Interface instance.

consistency group (CG, CTG)A group of pairs on which copy operations are performed simultaneously; the pairs'status changes at the same time. See also extended consistency group (EXCTG).

consistency time (C/T)Shows a time stamp to indicate how close the target volume is to the source volume.C/T also shows the time stamp of a journal group and extended consistency group.



controller chassisThe hardware component that houses the controller components of the VSP G1000storage system, including the front-end directors, virtual storage directors, cache andshared memory, switches, and back-end directors. The VSP G1000 storage system canbe configured with one or two controller chassis.

controllerThe component in a storage system that manages all storage functions. It is analogousto a computer and contains a processors, I/O devices, RAM, power supplies, coolingfans, and other sub-components as needed to support the operation of the storagesystem.

copy pairA pair of volumes in which one volume contains original data and the other volumecontains the copy of the original. Copy operations can be synchronous or asynchronous,and the volumes of the copy pair can be located in the same storage system (localcopy) or in different storage systems (remote copy).A copy pair can also be called a volume pair, or just pair.

PAVHitachi Compatible PAV

CRMHitachi Cache Residency Manager

CT, C/TSee consistency time (C/T).

CTGSee consistency group (CTG).

CUcontrol unit

custom volume (CV)A customized (variable-sized) volume whose size is defined by the user using VirtualLVI/Virtual LUN.

CVSee custom volume (CV).

CVScustom volume size

CYL, cylcylinder



D

data driveA physical data storage device that can be a hard disk drive (HDD), flash drive (alsocalled a solid-state device), or a flash module drive (FMD).

data pathThe physical paths used by primary storage systems to communicate with secondarystorage systems in a remote replication environment.

data poolOne or more logical volumes designated to temporarily store original data. When asnapshot is taken of a primary volume, the data pool is used if a data block in theprimary volume is to be updated. The original snapshot of the volume is maintained bystoring the to-be-changed data blocks in the data pool.

DCdata center

DCRDynamic Cache Residency

DEV, devdevice

deviceA physical or logical unit with a specific function.

device emulationIndicates the type of logical volume. Mainframe device emulation types provide logicalvolumes of fixed size, called logical volume images (LVIs), which contain EBCDIC datain CKD format. Typical mainframe device emulation types include 3390-9 and 3390-M.Open-systems device emulation types provide logical volumes of variable size, calledlogical units (LUs), that contain ASCII data in FBA format. The typical open-systemsdevice emulation type is OPEN-V.

DF700The factory model name for the Hitachi TagmaStore® Adaptable Modular Storage andWorkgroup Modular Storage arrays.

DF800The factory model name for the Hitachi Adaptable Modular Storage 2000 storagesystem.

differential dataChanged data in the primary volume not yet reflected in the secondary volume of acopy pair.



disk arrayDisk array, or just array, is another name for a RAID storage system.

disk controller (DKC)The hardware component that manages front-end and back-end storage operations. Theterm DKC is also used to refer to the entire RAID storage system.

DKCdisk controller. DKC can refer to the RAID storage system or the controller components.

DKCMAINdisk controller main. Refers to the microcode for the RAID storage system.

DPHitachi Dynamic Provisioning

DP-VOLDynamic Provisioning-virtual volume. A virtual volume with no memory space used byDynamic Provisioning.

drive chassisThe hardware component of the VSP G1000 storage system that contains data drivesand no controller components. A drive chassis can also be called a disk unit (DKU).

DRUHitachi Data Retention Utility

dumpA collection of data that is saved to a file when an error or crash occurs. The data isused by support personnel to determine the cause of the error or crash.

Dump ToolDownloads Hitachi Device Manager - Storage Navigator configuration information forbackup and troubleshooting purposes.

dynamic provisioningAn approach to managing storage. Instead of "reserving" a fixed amount of storage, itremoves capacity from the available pool when data is actually written to disk. Dynamicprovisioning is also referred to as thin provisioning.

E

EBCDICextended binary-coded decimal interchange code



ECKDextended count-key data

emulationThe operation of the Hitachi RAID storage system to emulate the characteristics of adifferent storage system. For device emulation the mainframe host "sees" the logicaldevices on the RAID storage system as 3390-x devices. For controller emulation themainframe host "sees" the control units (CUs) on the RAID storage system as 2107controllers.RAID storage system operates the same as the storage system being emulated.

emulation groupA set of device emulation types that can be intermixed within a RAID group and treatedas a group.

env.environment

EXCTGSee extended consistency group (EXCTG).

EXGexternal volume group

ext.external

extended consistency group (EXCTG)A set of Universal Replicator for Mainframe journal groups in which data consistency isguaranteed. When performing copy operations between multiple primary and secondarysystems, the journal groups must be registered in an EXCTG.

external portA fibre-channel port that is configured to be connected to an external storage systemfor Universal Volume Manager operations.

external volumeA logical volume whose data resides on drives that are physically located outside theHitachi RAID storage system.

F

failbackThe process of switching operations from the secondary path or host back to theprimary path or host, after the primary path or host has recovered from failure. Seealso failover.



failoverThe process of switching operations from the primary path or host to a secondary pathor host when the primary path or host fails.

FBAfixed-block architecture

FCfibre channel; FlashCopy

FCAfibre-channel adapter

FC-ALfibre-channel arbitrated loop

flash driveA data drive that is a solid-state memory device instead of a rotating hard disk drive. Aflash drive can also be called a solid-state drive (SSD).

flash module drive (FMD)A high-speed data drive that includes several flash memory (SSD) modules on a singlePCB.

free capacityThe amount of storage space (in bytes) that is available for use by the host systems.

FVfixed-size volume

FXHitachi Cross-OS File Exchange

G

GIDgroup ID

GUIgraphical user interface



H

HAhigh availability

HBAhost bus adapter

HDDhard disk drive

HDPHitachi Dynamic Provisioning

HDSHitachi Data Systems

HDTHitachi Dynamic Tiering software

host failoverThe process of switching operations from one host to another host when the primaryhost fails.

host groupA group of hosts of the same operating system platform.

host modeOperational modes that provide enhanced compatibility with supported host platforms.Used with fibre-channel ports on RAID storage systems.

host mode optionAdditional options for fibre-channel ports on RAID storage systems. Provide enhancedfunctionality for host software and middleware.

HURHitachi Universal Replicator

I

int.interval



initial copyAn initial copy operation is performed when a copy pair is created. Data on the primaryvolume is copied to the secondary volume.

initiator portA fibre-channel port configured to send remote I/Os to an RCU target port on anotherstorage system. See also RCU target port and target port.

internal volumeA logical volume whose data resides on drives that are physically located within thestorage system. See also external volume.

IOinput/output

IOPSI/Os per second

IPv4Internet Protocol, Version 4

IPv6Internet Protocol, Version 6

J

JNLjournal

JNLGSee journal group (JNLG).

journal group (JNLG)In a Universal Replicator system, journal groups manage data consistency betweenmultiple primary volumes and secondary volumes. See also consistency group (CG,CTG).

journal volumeA volume that records and stores a log of all events that take place in another volume.In the event of a system crash, the journal volume logs are used to restore lost dataand maintain data integrity.In Universal Replicator, differential data is held in journal volumes on until it is copied tothe S-VOL.



L

LCUlogical control unit

LDEVlogical device

LDKCSee logical disk controller (LDKC).

loc.location

logical device (LDEV)An individual logical data volume (on multiple drives in a RAID configuration) in thestorage system. An LDEV may or may not contain any data and may or may not bedefined to any hosts. Each LDEV has a unique identifier or "address" within the storagesystem composed of the logical disk controller (LDKC) number, control unit (CU)number, and LDEV number. The LDEV IDs within a storage system do not change. AnLDEV formatted for use by mainframe hosts is called a logical volume image (LVI). AnLDEV formatted for use by open-system hosts is called a logical unit (LU).

logical disk controller (LDKC)A group of 255 control unit (CU) images in the RAID storage system that is controlledby a virtual (logical) storage system within the single physical storage system. Forexample, the Hitachi Universal Storage Platform V/VM storage system supports twoLDKCs, LDKC 00 and LDKC 01.

logical partition (LPAR)A subset of a system's hardware resources that is virtualized as a separate system. Fora storage system, logical partitioning can be applied to cache memory.

logical unit (LU)A logical volume that is configured for use by open-systems hosts (for example, OPEN-V).

logical unit (LU) pathThe path between an open-systems host and a logical unit.

logical volumeSee volume.

logical volume image (LVI)A logical volume that is configured for use by mainframe hosts (for example, 3390-9).



LPARlogical partition

LUlogical unit

LUNlogical unit number

LUNMHitachi LUN Manager

LVlogical volume

LVISee logical volume image (LVI).

LVMLogical Volume Manager; logical volume management

M

main control unit (MCU)A storage system at a primary or main site that contains primary volumes of TrueCopyfor Mainframe remote replication pairs. The MCU is configured to send remote I/Os toone or more storage systems at the secondary or remote site, called remote controlunits (RCUs), that contain the secondary volumes of the remote replication pairs. Seealso remote control unit (RCU).

master journal (M-JNL)Holds differential data on the primary Universal Replicator system until it is copied tothe restore journal (R-JNL) on the secondary system. See also restore journal (R-JNL).

max.maximum

MCUSee main control unit (MCU).

MF, M/Fmainframe

MIBmessage information block



mig.migration

mirrorIn Universal Replicator, each pair relationship in and between journal groups is called a"mirror". Each pair is assigned a mirror ID when it is created. The mirror ID identifiesindividual pair relationships between journal groups.

M-JNLmain journal

MUmirror unit

multi-pathingA performance and fault-tolerant technique that uses more than one physicalconnection between the storage system and host system. Also called multipath I/O.

N

no.number

NUMnumber

O

OPEN-VA logical unit (LU) of user-defined size that is formatted for use by open-systems hosts.

OPEN-xA logical unit (LU) of fixed size (for example, OPEN-3 or OPEN-9) that is used primarilyfor sharing data between mainframe and open-systems hosts using Hitachi Cross-OSFile Exchange.

P

PAphysical address



pairTwo logical volumes in a replication relationship in which one volume contains originaldata to be copied and the other volume contains the copy of the original data. The copyoperations can be synchronous or asynchronous, and the pair volumes can be located inthe same storage system (in-system replication) or in different storage systems(remote replication).

pair statusIndicates the condition of a copy pair. A pair must have a specific status for specificoperations. When an operation completes, the status of the pair changes to the newstatus.

parity groupSee RAID group.

path failoverThe ability of a host to switch from using the primary path to a logical volume to thesecondary path to the volume when the primary path fails. Path failover ensurescontinuous host access to the volume in the event the primary path fails.See also alternate path and failback.

PDEVphysical device

PDLProduct Documentation Library

PGparity group. See RAID group.

PFMHitachi Performance Monitor

physical deviceSee device.

poolA set of volumes that are reserved for storing Dynamic Provisioning write data.

pool volume (pool-VOL)A logical volume that is reserved for storing snapshot data or write data for DynamicProvisioning.

port attributeIndicates the type of fibre-channel port: target, RCU target, or initiator.

PPprogram product; physical partition



P-Ppoint-to-point

primary siteThe physical location of the storage system that contains the original data to bereplicated and that is connected to one or more storage systems at the remote orsecondary site via remote copy connections. A primary site can also be called a "mainsite" or "local site".The term "primary site" is also used for host failover operations. In that case, theprimary site is the host computer where the production applications are running, andthe secondary site is where the backup applications run when the applications at theprimary site fail, or where the primary site itself fails.

primary volume (P-VOL)The volume in a copy pair that contains the original data to be replicated. The data inthe primary volume is duplicated synchronously or asynchronously on the secondaryvolume.The following Hitachi products use the term P-VOL: ShadowImage, ShadowImage forMainframe, TrueCopy, Universal Replicator, and Universal Replicator for Mainframe.See also secondary volume.

PVphysical volume

P-VOLSee primary volume.

Q

quick formatThe quick format feature in Virtual LVI/LUN in which the formatting of the internalvolumes is done in the background. This allows system configuration (such as defining apath or creating a TrueCopy pair) before the formatting is completed. To execute quickformatting, the volumes must be in blocked status.

R

VSP G1000Hitachi Virtual Storage Platform G1000

RAID groupA redundant array of inexpensive drives (RAID) that have the same capacity and aretreated as one group for data storage and recovery. A RAID group contains both userdata and parity information, which allows the user data to be accessed in the event thatone or more of the drives within the RAID group are not available. The RAID level of a



RAID group determines the number of data drives and parity drives and how the data is"striped" across the drives. For RAID1, user data is duplicated within the RAID group, sothere is no parity data for RAID1 RAID groups.A RAID group can also be called an array group or a parity group.

RAID levelThe type of RAID implementation. RAID levels include RAID0, RAID1, RAID2, RAID3,RAID4, RAID5 and RAID6.

RCreference code (of a service information message)

RCUSee remote control unit (RCU).

RCU target portA fibre-channel port that is configured to receive remote I/Os from an initiator port onanother storage system.

remote control unit (RCU)A storage system at a secondary or remote site that is configured to receive remoteI/Os from one or more storage systems at the primary or main site.

remote copy connectionsThe physical paths that connect a storage system at the primary site to a storagesystem at the secondary site. Also called data path.

remote siteSee secondary site.

restore journal (R-JNL)Holds differential data on the secondary Universal Replicator system until it is copied tothe secondary volume.

resyncresynchronize

RIOremote I/O

R-JNLrestore journal

RMRAID Manager. Another name for Command Control Interface.



R-SIMremote service information message

R-siteremote site (used for Universal Replicator)

S

S#serial number

S/Nserial number

secondary siteThe physical location of the storage system that contains the primary volumes ofremote replication pairs at the main or primary site. The storage system at thesecondary site is connected to the storage system at the main or primary site viaremote copy connections. The secondary site can also be called the "remote site". Seealso primary site.

secondary volume (S-VOL)The volume in a copy pair that is the copy. The following Hitachi products use the term"secondary volume": ShadowImage, ShadowImage for Mainframe, TrueCopy, UniversalReplicator, and Universal Replicator for Mainframe.See also primary volume.

seq.sequential

Server Priority Manager (SPM) groupA set of host bus adapters (HBAs) managed as a group. All HBAs in an SPM group mustbe of the same priority. Prioritized WWNs (that is, high priority HBAs) and nonprioritized WWNs (that is, low priority HBAs) cannot be mixed in the same group.

service information message (SIM)SIMs are generated by a RAID storage system when it detects an error or servicerequirement. SIMs are reported to hosts and displayed on Hitachi Device Manager -Storage Navigator.

service processor (SVP)The computer inside a RAID storage system that hosts the Hitachi Device Manager -Storage Navigator software and is used by service personnel for configuration andmaintenance of the storage system.



severity levelApplies to service information messages (SIMs) and Hitachi Device Manager - StorageNavigator error codes.

shared volumeA volume that is being used by more than one replication function. For example, avolume that is the primary volume of a TrueCopy pair and the primary volume of aShadowImage pair is a shared volume.

SHREDVolume Shredder

shreddingSee volume shredding.

SIHitachi ShadowImage®

sidefileAn area of cache memory that is used to store updated data for later integration intothe copied data.

SIMservice information message

SIzHitachi ShadowImage® for Mainframe

sizeGenerally refers to the storage capacity of a memory module or cache. Not usually usedfor storage of data on disk or flash drives.

SMshared memory

SNserial number; Hitachi Device Manager - Storage Navigator

snapshotA point-in-time virtual copy of a primary volume (P-VOL). The snapshot is maintainedwhen the P-VOL is updated by storing pre-updated data (snapshot data) in a data pool.

SOMSee system option mode (SOM).

source volume (S-VOL)The volume in a Compatible FlashCopy® V2 copy pair containing the original data.



spaceGenerally refers to the data storage capacity of a disk drive or flash drive.

SPMHitachi Server Priority Manager

SSBsense byte

SSDsolid-state drive. Another name for a flash drive. In this guide, single level cell (SLC),multi level cell (MLC) and flash module drive (FMD) are called collectively as SSD.

SSIDstorage subsystem ID. SSIDs are used for reporting information from the CU to themainframe operating system. Each group of 64 or 256 volumes requires one SSID, sothere are one or four SSIDs per CU image. The user-specified SSIDs are assignedduring storage system installation and must be unique to all connected host operatingenvironments.

storage tiersSee tiered storage.

S-VOLSee secondary volume or source volume (S-VOL).

SVPSee service processor (SVP).

syncsynchronize; synchronous

syslogThe file on the SVP that contains information released to both the syslog and audit logfiles and information released only to the syslog file.

system option mode (SOM)Additional operational parameters for the RAID storage systems that enable the storagesystem to be tailored to unique customer operating requirements. SOMs are set on theservice processor.

T

target portA fibre-channel port that is configured to receive and process host I/Os.



target volume (T-VOL)The volume in a Compatible FlashCopy® V2 copy pair that is the copy of the sourcevolume (S-VOL).See also source volume (S-VOL).

TCHitachi TrueCopy®

TCzHitachi TrueCopy® for Mainframe

TGTtarget; target port

THDthreshold

TIDtarget ID

tiered storageA layered structure of performance levels, or tiers, that match data access requirementswith the appropriate performance tiers.

TLCUtarget logical control unit

total capacityThe aggregate amount of storage space in a data storage system.

TRKtrack

T-VOLSee target volume (T-VOL).

U

unallocated volumeAn LDEV for which no host paths are assigned.

URHitachi Universal Replicator

URzHitachi Universal Replicator for Mainframe



USP V/VMHitachi Universal Storage Platform V/VM

USP VMHitachi Universal Storage Platform VM

USP V/VMHitachi Universal Storage Platform V/VM

UVMHitachi Universal Volume Manager

V

VDEVSee virtual device (VDEV).

virtual device (VDEV)A group of logical devices (LDEVs) in a RAID group. A VDEV typically consists of somefixed volumes (FVs) and some free space. The number of fixed volumes is determinedby the RAID level and device emulation type.

Virtual LVI/LUN volumeA custom-size volume whose size is defined by the user using Virtual LVI/LUN. Alsocalled a custom volume (CV).

virtual volume (V-VOL)The secondary volume in a pair. When in PAIR status, the V-VOL is an up-to-date virtualcopy of the primary volume (P-VOL). When in SPLIT status, the V-VOL points to data inthe P-VOL and to replaced data in the pool, maintaining the point-in-time copy of the P-VOL at the time of the split operation.When a V-VOL is used with Dynamic Provisioning, it is called a DP-VOL.

VLLHitachi Virtual LVI/LUN

VLUNHitachi Virtual LUN

VLVIHitachi Virtual LVI

VMvolume migration; volume manager



VMAvolume management area

VOL, volvolume

volservolume serial number

volumeA logical device (LDEV). A mainframe volume is called a logical volume image (LVI), andan open-systems volume is called a logical unit (LU).

volume pairSee copy pair.

volume shreddingDeleting the user data on a volume by overwriting all data in the volume with dummydata.

VPGvirtual parity group

VPMHitachi Virtual Partition Manager

VRMHitachi Volume Retention Manager

VSNvolume serial number

VSPHitachi Virtual Storage Platform

V-VOLSee virtual volume (V-VOL).

V-VOL management areaContains the pool management block and pool association information. The V-VOLmanagement area is created automatically when additional shared memory is installed.

W

WWNworldwide name



X

XRCExtended Remote Copy

Z

zero dataThe number 0 (zero). A zero-formatting operation is one that writes zero data to theentire data drive area.

zero formattingA formatting operation that writes zero data to the entire data drive area.



Index

B

basic provisioningoverview 1-3workflow 1-5

boundary values for RAID levels 3-9

C

capacity of a slot 3-9Changing External LDEV Capacity 4-107Create LDEV function 3-10custom-sized provisioning

overview 1-4

D

DP-VOLrequirements 4-7

E

Error Detail dialog box 6-9, C-4

F

fixed-sized provisioningoverview 1-3

L

LDEVsblocking 3-16

changing settings 3-15confirming SSID 3-14creating 3-10deleting (converting to free space) 3-18editing name 3-18editing SSID 3-14formatting 3-19, 3-23formatting in a parity group 3-23removing from registering task 3-15restoring if blocked 3-17

M

management area capacitymainframe volume 3-8

meta_resource 2-7monitoring capacity 4-90

P

parity groupsconfiguring volumes 3-9

pool capacitydecreasing 4-103increasing 4-100stop decreasing 4-105

pool informationviewing 4-97

pool namechanging 4-102

pool subscription limitchanging 4-94

pool threshold

Index-1Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

changing 4-94pool-VOLs

requirements 4-5pools

creating 4-74deleting 4-106managing 4-97recovering 4-102requirements 4-4

Protect 5-3provisioning key terms 1-12

Q

Quick Format function 3-20

R

RAID levelsboundary values 3-9

Read Only 5-3Read/Write 5-3reclaiming pages in a V-VOL 4-110resource groups

adding resources to 2-10assignments 2-8changing name 2-11creating 2-9deleting 2-12example not sharing a port 2-5example sharing a port 2-3license requirements 2-8meta_resource 2-7overview 2-1removing resources from 2-11resource lock 2-7rules, restrictions, and guidelines 2-8strategies 1-11system configuration 2-3user groups 2-7

resource lock 2-7

S

shared memory requirements for provisioning 1-13SIM reference codes

listed 4-95SIMs

completing automatically 4-96completing manually 4-96overview 4-95

slot capacity 3-9SSID

confirming 3-14editing 3-14requirements 3-5

subscription limit of a poolchanging 4-94

system requirements for provisioning 1-13

T

Technical Support Center 6-9thin provisioning

advantages 1-7configuring 4-1example 1-8overview 1-5, 4-3requirements 4-3workflow 1-8, 4-14

tier capacityreserving 4-48reserving example 4-49

tier relocationrules, restrictions, and guidelines 4-25

tieringworkflow 4-62

tiering policy 4-45changing execution modes example 4-52notes on using 4-51overview 4-43relationship with graphs 4-47relationship with tiers 4-46reserving tier capacity 4-48setting on a V-VOL 4-45

troubleshooting 6-1provisioning while using CCI 6-7thin provisioning 6-2

U

Universal Replicator 4-12used pool capacity

viewing 4-98


V

V-VOLschanging name 4-108creating 4-85deleting 4-112increasing capacity 4-108managing 4-97releasing pages 4-110requirements for increasing capacity 4-7stop releasing pages 4-111

Viewing formatted pool capacity 4-99, 4-113,4-114Viewing rebalancing progress 4-100Virtual LVI size calculations 3-6Virtual LVI specifications 3-3Virtual Partition Manager 4-14

W

Write-to-control Blocks function 3-22

Z

zero formatting 3-24zero pages

reclaiming 4-109



Hitachi Virtual Storage Platform G1000 Provisioning Guide for Mainframe Systems

Hitachi Data Systems

Corporate Headquarters2845 Lafayette StreetSanta Clara, California 95050-2639U.S.A.www.hds.com

Regional Contact Information

Americas+1 408 970 [email protected]

Europe, Middle East, and Africa+44 (0)1753 [email protected]

Asia Pacific+852 3189 [email protected]

MK-92RD8013-02

Documents

Hitachi Virtual Storage Platform G1000 - Hitachi Data · PDF fileProduct Version Contents Getting Help FASTFIND LINKS Hitachi Virtual Storage Platform G1000 Provisioning Guide for