2016-08-29 09:46 AM
I find this to be a rather curious entry in the published Inventory User Guide for OCI 7.2.2:
"Written Capacity JK: Need Ram's input"
Did Ram ever provide input? I'd like to better understand the difference between Written and Consumed Capacity in the Backend Volumes view.
Solved! SEE THE SOLUTION
2016-08-29 10:50 AM
I understand since (from Ketsia Pha) that in OCI Written is from the Volume perspective and Consumed is the ammount of capacity consumed in the aggr or storage pool, so any overhead would be included in Consumed and Consumed is expected to be equal or higer than Written Capacity.
2016-08-29 12:28 PM
Well, that isn't ideal. I laughed, but that was probably inappropriate. I opened a documentation bug.
We only have this data for a few storage platforms - I think some SVC, and Vmax generation 1 and maybe 2. EMC seems to have de-emphasized this, and I don't think it is available for the Vmax 3 family.
A couple platforms of array purport to know exactly how much data has been written to a volume. This theoretically would line up more closely with the hosts' perspective on how much capacity utilization is occurring.
If OCI can obtain this for block volumes, it would be populated here.
2016-08-29 12:56 PM
Thank you for the quick follow-up and the bug report!
The capacity in the Backend Volumes view is coming from several VMAX. There is a VPLEX on the front end, so we don't see consumed, written, etc in the Volume view for host.
The block capacity is only reported in Backend, and to a lesser extent in the Virtual Storage View. Written Capacity is indeed less than Consumed.
To add to this, is there a reason why the Raw Capacity is double the Capacity? I wondered if it was being duplicated because of the VPLEX, the Redundancy, something else?