HP 3PAR StoreServ 7450 4-node HP 3PAR CIM API Programming Reference (OS 3.1.2 - Page 43
Fully Provisioned Storage Volume, Concrete TPD_StoragePool.RemainingManagedSpace
View all HP 3PAR StoreServ 7450 4-node manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 43 highlights
• TPD_AllocatedFromStoragePool.SpaceConsumed between concrete "all-FC" pool and volume = TPD_StorageVolume.NumberOfRawBlocks * BlockSize = 21474836480 (raw space consumed from concrete pool in the creation of the volume). • Concrete TPD_StoragePool.RemainingManagedSpace = previous RemaningManagedSpace value - volume raw size = 813896302592 - 21474836480 = 792421466112. The TotalManagedSpace for the concrete pool remains unchanged. Fully Provisioned Storage Volume For a DynamicStoragePool, since it is a RAID-specific storage pool, logical user capacity is used in calculating its ManagedSpace as well as SpaceConsumed with its child pools/volumes. All DeltaReplicaStoragePools that are allocated from a DSP, use logical user capacity in calculating TotalManagedSpace and RemainingManagedSpace. RAID and other types of overhead are hidden in the SpaceConsumed between concrete pool and the DSP. TPD_AllocatedFromStoragePool.SpaceConsumed between the parent dynamic storage pool and the storage volume represents the actual size allocated to the volume, and is equal to TPD_StorageVolume.NumberOfBlocks multiplied by TPD_StorageVolume.BlockSize. This is also the usable size of the volume in blocks. Raw size of the volume is represented by TPD_StorageVolume.NumberOfRawBlocks. Unlike the case for legacy storage volume, SpaceConsumed between DynamicStoragePool and StorageVolume is not the raw size allocated to the volume, since RAID overhead is now accounted for in DynamicStoragePool. The capacity used for the metadata in the creation of the storage volume can be calculated by: [(TPD_StorageVolume.NumberOfRawBlocks TPD_StorageVolume.NumberOfBlocks)* TPD_StorageVolume.BlockSize]. TPD_StorageVolume.ConsumableBlocks is set to be the same as TPD_StorageVolume.NumberOfBlocks. Example: • Initial State A dynamic storage pool has a virtual capacity of 100GB (as set in the -sdgl option). This value is reflected in the TPD_DynamicStoragePool.SpaceLimit property and is what is available for volume allocation. Let us assume that there are no volumes or DeltaReplicaStoragePool allocated from this pool initially. The TotalManagedSpace property reflects the actual capacity allocated to the pool. • Before Volume Creation • TPD_DynamicStoragePool.TotalManagedSpace = actual capacity allocated to the pool. • TPD_DynamicStoragePool.SpaceLimit = 100GB • TPD_DynamicStoragePool.RemainingManagedSpace = 100GB (capacity that can be used to create volume) • After Volume Creation Suppose a RAID-10 volume of logical size 10G is created from the dynamic storage pool. This value is represented in the TPD_StorageVolume class as NumberOfBlocks (ConsumableBlocks also has the same value). Since this is a RAID-10 volume, its raw size is actually double that of the logical size, i.e., 20 GB. This value is represented in the TPD_StorageVolume class as NumberOfRawBlocks. AllocatedFromStoragePool.SpaceConsumed between StorageVolume and the parent Block Services Package 43