- 3par ssmc change raid type full#
- 3par ssmc change raid type series#
- 3par ssmc change raid type free#
- 3par ssmc change raid type windows#
Usr Used is what is actually written to the volume, while Usr Rsvd is how much is allocated. Unfortunately it seems that the zero-detect/reclaim on 3PAR is designed to handle day-to-day unmap but when you bulk up 2 years of Vmware unmap it will in many cases need to some time to get thru it.
3par ssmc change raid type windows#
just like Microsoft did with Windows Server 2012. With VMFS6 they finally enabled this automatically. As 3PARs reclamation techology scans and reclaims zero blocks you would need to run unmap on each datastore in Vmware. When you delete a VM on a VMFS5 datastore today, Vmware will only delete the pointers and leave all the data on the datastore. With VMFS6 you want thin on both as Vmware has finally enabled automatic unmap again. Pre-VMFS6 you want Thin on 3PAR, Eager Zero Thick on Vmware. In case you want multiple CPGs (which is more common than uncommon) where you either have multiple tiers or different redundancy requirements on different parts of the systemĤ.
3par ssmc change raid type free#
When the CPG needs more space it will allocated from the system free space pool where you today have 2044GB free.ģ. A healthy system has 99% used space within a CPG. As others have stated, 2044 GiB of RAW capacity (pre-RAID) + whatever is available within your CPGs (I see 43GB net (post-RAID) in the CPG you've posted)Ģ. I'm an old school storage admin so over provisioning feels wrong to meġ. So long as my provisioned space is less than my normal space I'm happy, if I over provision that is me gambling no hosts go nuts and try to fully use all the space in their volumes. I know how much "normal" space I have for volumes on each physical disks (either from the GUI with that first picture you have showing "Free:" or from CLI with "showpd -c" and looking at the total of the free normal chunklets column. I personally like to work on the provisioned size of the volumes allocated to hosts (the size of how much each volume could potentially be if fully used). you basically have to guess! It's a painful thing of a the 3PAR, the second picture you have shows the 3PARs guess/estimate as to how much usable space it would get if that (only only that) CPG was used for future volumes : 1,695,000GiB. Working out how much space you really have left is awkward. a CPG isn't a container that has your volumes are in, it's not like a pool that you give disk space too, a CPG is just a template to say how you would like your volumes to be configured, so the space you see listed against the CPG is just the amount of space volumes are using that are using that CPGs template. that is just "raw" (normal) free space and doesn't account for anything like RAID levels, set size of volumes, reserved snapshot space for volumes, growth increments of CPGs etc.
We are hoping to get some consulting done later this year to evaluate our space needs, but for now, we just want to make sure we are comfortable with what we have.īut. I thank you for any efforts to understand this.
Last week I initially thought I was getting low on space, so I got rid of some old VM's, but I cannot tell that it freed up space listed under CPGs - why would that be?
3par ssmc change raid type full#
If I go into my CPGs, here is how it lists:
3par ssmc change raid type series#
We have a (I believe) 7000 series which shows 79% allocated and 21% free: Fast forward to now, I'm a little mystified and was hoping for a bit of clarification. Hello all - I had how space worked explained to me when our 3par was installed, but that was 2013 and I was a bit overwhelmed.
0 kommentar(er)
