文本課件案例1

1、Module 10thin provisioningbasicsCourse ObjectivesAt the end of this presentation the student should be able to:Understand 3PAR Thin ProvisioningExplain 3par capacity allocation methodCapacity allocationPagesUnits of 16KBSmallest unit of capacity allocationRepresent capacity that is really used when

2、writing to a Thin VolumeAlso used for SnapshotsRegionsUnits of 128MBRepresent capacity that is reserved for a given volumeInitial reservation of capacity is 512MB per controller node pairSubsequent reservation will be smaller or bigger depending on how fast this initial capacity is allocatedThe 3 le

3、vels of capacity allocationChunklets256MB/1GBRegions128MBCPG32GB *LDLDLDLDPages16KBChunklets are assembled in LDs to form the CPGMultiple VVs will share the CPGLDs are divided into regions. Regions are allocated to only one VVRegions are divided into pages* defaultThin provisioning3PAR Thin Provisio

4、ningOffers a simple solution to the problem of unused allocated capacityAllows IT departments to safely allocate to an application as much “virtual” logical capacity as conceivably needed Actual “physical” capacity is drawn from a common pool called a Common Provisioning Group (CPG)The physical capa

5、city drawn from the CPG relates directly to Application writes (dedicate on write)Traditional versus Thin ProvisioningTraditional (Fat) ProvisioningDedicate on Allocation HP 3PAR Thin ProvisioningDedicate on Write VolumeVolumeVolumeWritten DataWritten DataWritten DataCommon Buffer PoolPurchased Phys

6、ical CapacityPurchased Physical CapacityVolumeVolumeVolumeWritten DataWritten DataWritten DataCPGs and LDsCPGs will always contain multiple LDs.The CPG is a template for the LDs that will be createdThe RAID is at the LD levelFor Thin Provisioning volumes and snapshots 2 type of LDs are createdData (

7、SD)Admin (SA)The default growth increment of a CPG is 32GB per controller node pair. The minimum is 8GB per controller node pairFull volumes have their own LDsThin volumes share the same LDsLDs (Logical Disks)3 different types:User DataSnapshot Admin (SA)Snapshot Data (SD)Additional LDs:LoggingPrese

8、rvedAdmin VolumeThinly Provisioned Virtual VolumesA base volume capable of responding to host write requests by allocating space on demand in small increments Structured so that each volumes virtual size (the size that the volume presents to the host) always remains the sameThe storage behind the vo

9、lume is allocated on demandTPVV ComponentsSnapshot Data SpaceKnown as copy spaceContains the volumes user data and snapshot copy dataA TPVV can have its user data or VC data in separate CPGs (different QoS)Snapshot AdministrationKnown as admin spaceA Pointer file that “points” to VC or TPVVs Creatin

10、g a TPVV (GUI) Zero detectDisabled by defaultUsed for Thin Conversion and Thin PersistenceEditing CPG ParametersThe following CPG parameters can be edited:Growth increment Growth warningGrowth limitThe following Logical disk parameters for CPG can be edited:RAID TypeAvailabilityStepsizeRowsizeDisk F

11、ilterNOTE: You can use “CLI” or “GUI” to make the changes. Use the command to edit CPG parameters.Growth Increment ConsiderationsShould not exceed available space on your systemThe nature of the data running on the systemThe number of CPGs in the systemThe number of volumes associated with those CPG

12、sAnticipated growth rate of the volumes associated with the CPGGrowth increment only has effect on TPVV and CPVVGrowth Increment Defaults and Minimums32 GB64 GB96 GB128GBshowcpg -rDetermining Space Usage At CreationAfter TPVV CreationCPG Growth WarningWhen a CPG approaches its “growth” warning, an “

13、alert” is generatedThe Administrator should check and determine if any action is required upon receiving a “growth” warningThe InServ will suspend writes when a CPG is out of spaceAn Administrator can add physical disk space or limit the future growth of volumes that draw from the CPGCPG Growth Limi

14、tThe InServ Administrator must be very careful when setting “Growth Limits”The Administrator can set a Growth limit greater than the systems physical disk space mendation: Do not allow a volume that draws from a CPG to exceed its growth limitCAUTION: System AlertIf a volume that draws from the CPG r

15、eaches the CPGs growth limit, an “alert” is generated notifying you that all logical capacity for the CPG has been consumed.Viewing Alerts Using InForm GUIAlerts can be displayed by clicking the Alert Pane or selecting Events from InForm GUICapacity managementCreating a volumeChoose volume type (Thin of Full)Choose user data CPGFor Thin volumes, enter allocation warningThin Provisioning volumesSelect “Ca