2014-05-12 11:46 PM
Trying to run a DWH report to build Netapp Filer Volume and Aggregate reports but not proving to be simple task. The Internal Volume dimension is fine for building a Volume report as long as you do some calculated fields but Aggregate is another matter.
I'm sure there's dB related reason but getting the 'used' data value for a Volume is not simple and when it comes to Aggregates I can't see anyway to get these figures.
I started down the road of trying to use Joins to pull the SQL query from say the Inventory dimension and use with Internal Volume or vice versa but that didn't go so well and I'm not even close to being knowledgable about how these Joins work.
At this point I'll just build separate Volume reports which is easy but the one that still really annoys me is the Aggregate report as there's no way I can tell to build a report say from Inventory dimension that'll have the actually consume data amount of the volume, not what's allocated to data but what's actually used. Appreciate any input or insight...
Solved! SEE THE SOLUTION
2014-05-13 04:28 AM
Summing the used capacity of either OCI volumes (LUNs in Ontap), or OCI Internal Volumes (Flexvols in Ontap) will not necessarily sum to the used capacity of a storage pool (Aggregate in Ontap) for NetApp arrays running Ontap, or any other storage platform.
In the world of Ontap, if the flexvol is thick provisioned, the delta between its "used" capacity and capacity is "trapped" in that flevol - so that space should not be considered free/unused at the storage pool level as it is truly not free for you to perform more writes to.
Likewise, some storage platforms have overhead - the CX4 and first generation VNX suffered from this - the allocation unit on their thin provisioning pools was 1 GB, and I believe every thin lun has a 1GB metadata overhead, so again, the used nor capacity values of volumes may not sum to what you would expect at the storage pool level due to this overhead.
Our general recommendation for storage pool use cases is the Storage Pool datamart - this mart additionally has history, so you can not only build point in time reports, but historical trending reports as well
2014-05-15 12:26 AM
Yeah I guess for some background we've just upgraded from v6.1.2 to v6.4.3 so a LOT of changes which don't show up until you start going into the new Datamarts and where as before Inventory could provide details on Internal Volume and Pool dimensions seems like not the case in latest versions. Understand the change just have to work around... the point about the #'s I understand and it's not so much being able to use the numbers to compare usage or figures in Volumes against Aggregate but more so to have both Aggregate and Volume data presented in a single report. I've looked at the 'join' option to pull data across data marts and think I'll need a few more years with the tool before I can do that easily... probably needs to be a separate thread as to how to best report data across datamarts in a single report.
So would the answer I'm looking for is under current datamarts presenting Volume and Aggregate data in a single report will need to utilise advance cross datamart techniques??
2014-05-16 04:33 AM
It looks like you're looking to do an overcommit report with utilization, see below. Note that this combines Storage and Storage Pool Capacity with Internal Volume Capacity:
SELECT dwh_capacity.storage_dimension.name AS 'Storage System Name',
dwh_capacity.storage_pool_dimension.name AS 'Storage Pool Name',
AND dwh_capacity.storage_dimension.manufacturer = 'NetApp'
AND dwh_capacity.storage_pool_dimension.name <> 'N/A'
AND dwh_capacity.date_dimension.latest = 1
ON dwh_capacity.storage_pool_dimension.tk = dwh_capacity.internal_volume_capacity_fact.storage
AND dwh_capacity.date_dimension.tk = dwh_capacity.internal_volume_capacity_fact.dateTk
Unfortunately, 6.4.x did not come with the capability to aggregate the flexvol capacity in the Storage and Storage Pool Capacity data mart by default. As a result, we had to use the above as a workaround. We've then added this in our 7.0 release so that you can easily drag and drop the data without having to do any SQL.
2014-05-16 09:13 AM
Thanks... you've hit the head on the nail so to speak. I'll work with your suggested SQL statements and see how things work out, you've put me a bit out of my league but I'll see if I can work through your suggestion. Or at least implement it...
2014-05-16 12:08 PM
Pulling a sql statement such as that into a Cognos report is relatively easy, but tricky to figure out how to do that.
If you review that link - I have an old video "How to use a SQL query in Report Studio " that hopefully will show you how to use the SQL statement in a report