3.3.1 also introduced the capability to enable compression on volumes. 3PAR OS 3.3.1 depreciated the TDVV volume type and made dedupe a property of a volume that could just be turned on. The Thin Deduplicated Virtual Volume (TDVV) as the name suggested this was a volume that was both deduped and thin provioned. Today if you purchase a system you get the full licence bundle included and so this becomes less of a concern.Īnother type of Virtual Volume was introduced with the 3PAR all flash systems. With a TPVV only the space that is demanded is used, so if a 100GB VV is created and only 50GB of that space is used only 50GB of space will be demanded from the CPG.Ī thin provisioning licence is required to use TPVV and assuming this is in place TPVV are the default type of VV created. A FPVV uses all the allocated space upfront, so if a 100GB VV is created straight away 100GB of space will be used from the CPG.
Virtual volumes draw their space from CPG’s and come in two varieties Fully Provisioned Virtual Volumes (FPVV) and Thin Provisioned VV (TPVV). Virtual volumes (VV’s) are HPE’s terminology for what would most commonly be called a LUN, a LUN which has been presented or exported to a host is called a VLUN. In this 3PAR 101 series so far we have looked at 3PAR fundamentals and the systems unique approach to RAID, in Part 2 we looked into Common Provisioning Groups (CPGs) Now we get onto the stage where we can provision some storage to hosts by using virtual volumes and vluns!
0 kommentar(er)
