HP XP P9000 Provisioning for Mainframe Systems User Guide
Table Of Contents
- HP XP P9000 Provisioning for Mainframe Systems User Guide
- Contents
- 1 Introduction to provisioning
- 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
- Thin Provisioning Overview
- Thin Provisioning Z
- Thin Provisioning Z concepts
- When to use Thin Provisioning Z
- Thin Provisioning Z advantages
- Thin Provisioning Z advantage example
- Thin Provisioning Z work flow
- Smart Tiers Z
- Tiers concept
- When to use Smart Tiers Z
- Resource groups strategies
- Complimentary strategies
- Key terms
- Before you begin
- About pool volumes
- 2 Configuring resource groups
- 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
- Using Resource Partition and other P9500 products
- 3 Configuring custom-sized provisioning
- Virtual LVI/Virtual LUN functions
- VLL requirements
- VLL specifications
- SSID requirements
- VLL size calculations
- Create LDEV function
- Blocking an LDEV
- Restoring a blocked LDEV
- Editing an LDEV name
- Deleting an LDEV (converting to free space)
- Formatting LDEVs
- Making external mainframe system volumes usable
- Assigning a processor blade
- Using a system disk
- 4 Configuring thin provisioning
- Thin Provisioning Z overview
- Smart Tiers Z overview
- Thin provisioning requirements
- Using Thin Provisioning Z or Smart Tiers Z with other P9500 products
- Thin Provisioning Z workflow
- Smart Tiers Z
- About tiered storage
- Tier monitoring and data relocation
- Smart Pool
- Tier monitoring and relocation cycles
- Tier relocation flow
- Tier relocation rules, restrictions, and guidelines
- Buffer area of a tier
- Smart Tiers Z cache specifications and requirements
- Execution modes for tier relocation
- Monitoring modes
- Notes on performing monitoring
- Downloading the tier relocation log file
- Tiering policy
- Tiering policy expansion
- Tiering policy examples
- Setting tiering policy on a THP V-VOL
- Tiering policy levels
- Viewing the tiering policy in the performance graph
- Reserving tier capacity when setting a tiering policy
- Example of reserving tier capacity
- Notes on tiering policy settings
- New page assignment tier
- Relocation priority
- Assignment tier when pool-VOLs are deleted
- Formatted pool capacity
- Rebalancing the usage level among pool-VOLs
- Execution mode settings and tiering policy
- Changing the tiering policy level on a THP V-VOL
- Changing new page assignment tier of a V-VOL
- Opening the Edit Tiering Policies window
- Changing a tiering policy
- Changing relocation priority setting of a V-VOL
- Smart Tiers Z workflow
- Smart Tiers Z tasks and parameters
- Managing Smart Tiers Z
- Changing a pool for Smart Tiers Z to a pool for Thin Provisioning Z
- Working with pools
- Working with THP V-VOLs
- Thresholds
- Working with SIMs
- Managing pools and THP V-VOLs
- Viewing pool information
- Viewing formatted pool capacity
- Viewing the progress of rebalancing the usage level among pool-VOLs
- Increasing pool capacity
- Changing a pool name
- Recovering a blocked pool
- Decrease pool capacity
- Deleting a tier in a pool
- Deleting a pool
- Changing external LDEV tier rank
- Increasing THP V-VOL capacity
- Changing the name of a THP V-VOL
- About releasing pages in a THP V-VOL
- Enabling/disabling tier relocation of a THP V-VOL
- Deleting a THP V-VOL
- 5 Configuring access attributes
- 6 Protecting volumes from I/O operations
- Overview of Volume Security for Mainframe
- Volume Security for Mainframe Requirements
- Volume Security for Mainframe Functions
- Protecting Volumes from I/O Operations at Mainframe Hosts
- Warnings Regarding Volume Security for Mainframe
- Supported Volume Emulation Types
- Maximum Number of Groups
- Maximum Number of Hosts and Volumes
- Launching Volume Security for Mainframe
- Viewing Security Settings
- Locating Volumes in a Specified Security Group
- Locating Security Groups that Contain a Specified Host
- Locating Volumes in a Security Group that Contains a Specified Host
- Locating Ports through Which Hosts Can Access Volumes
- Locating Security Groups that Contain a Specified Volume
- Locating Hosts in a Security Group that Contains a Specified Volume
- Locating Security Groups that Contain a Specified Host Group
- Locating Security Groups that Contain a Specified LDEV Group
- Limiting Host Access
- Prohibiting Host Access
- Protecting Volumes from Copy Operations
- Disabling Volume Security for Mainframe
- Editing Security Groups
- Editing Host Groups
- Editing LDEV Groups
- 7 Troubleshooting
- 8 Support and other resources
- A RAID Manager command reference
- B Resource Partition GUI reference
- C LDEV GUI reference
- Parity Groups window
- Parity Groups window after selecting Internal (or External) under Parity Groups
- Window after selecting a parity group under Internal (or External) of Parity Groups
- Window after selecting Logical Devices
- 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
- Format LDEVs wizard
- Restore LDEVs window
- Block LDEVs window
- Delete LDEVs window
- LDEV Properties window
- Top window when selecting Components
- Top window when selecting controller chassis under Components
- Edit Processor Blades wizard
- Assign Processor Blade wizard
- View Management Resource Usage window
- D Thin Provisioning Z and Smart Tiers Z GUI reference
- Pools window after selecting pool (Pools window)
- Top window when selecting a pool under Pools
- 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
- 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
- E Volume Retention GUI reference
- F Volume Security for Mainframe GUI reference
- Volume Security for Mainframe window
- Add/Change Security Group Dialog Box
- Add/Change Host Group Dialog Box
- Add/Change LDEV Group Dialog Box
- Select LDEV Dialog Box
- Select Port Dialog Box
- Specify Security Group Dialog Box
- Host to Security Group Dialog Box
- Host to LDEV Dialog Box
- Host Group to Security Group Dialog Box
- Host Group to Port Dialog Box
- LDEV to Security Group Dialog Box
- LDEV to Host Dialog Box
- LDEV Group to Security Group Dialog Box
- Error Detail Dialog Box
- Glossary
- Index
When to use fixed-sized provisioning
Fixed-sized provisioning is a best fit in the following scenarios:
• Use fixed-size provisioning in cases where standard IBM 3390 volume sizes (3390-3, 3390-9,
etc.) are required.
Custom-sized provisioning
Custom-sized (or variable-sized) provisioning has more flexibility than fixed-sized provisioning and
is the traditional storage-based volume management strategy typically used to organize storage
space.
To create custom-sized volumes on a storage system, an administrator creates volumes of the
desired size from individual array groups. These volumes are then individually mapped to an
address composed of a control unit and logical device within the control unit.
Following are three scenarios where custom-sized provisioning is an advantage:
• In fixed-sized provisioning, when several frequently accessed data sets are located on the
same volume, users accessing other data sets on the same volume may encounter increased
response time because of logical device contention. If the custom-sized feature is used to divide
the volume into several smaller volumes and I/O workload is balanced (each data set is
allocated to a different volume), then access contention is reduced and performance is
improved.
• In fixed-sized provisioning, not all of the capacity may be used. Unused capacity on the volume
will remain inaccessible to other users. If the custom-sized feature is used, smaller volumes
can be created that do not waste capacity.
• Applications that require the capacity of many fixed-sized volumes can instead be given fewer
large volumes to relieve device addressing constraints.
To change the size of a volume already in use, you first create a new volume larger than the old
one, and then move the contents of the old volume to the new one. The new volume must be
configured in the IOGEN on the server. Depending on how the data was copied (for example
using software such as TDMF, or internal capability such as FlashCopy) the old device may need
to be varied offline and the new device varied online. This assumes that the source and target
devices are already gen'ed into the mainframe IO configuration.
A disadvantage is that this manual intervention can become costly and tedious and this provisioning
strategy is appropriate only in certain scenarios.
When to use custom-sized provisioning
Use custom-sized provisioning when you want to manually control and monitor your storage
resources and usage scenarios.
Basic provisioning workflow
The following illustrates the basic provisioning workflow:
12 Introduction to provisioning