<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic OCUM Reporting issues - Reporting actual (physical) consumed size on a volume, even a clone in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-Reporting-issues-Reporting-actual-physical-consumed-size-on-a-volume-even-a/m-p/133587#M24239</link>
    <description>&lt;P&gt;Hey all, I'm trying to get the affect of reporting the "physical used size" from the vol show-space command.&amp;nbsp; Volume.Used in the OCUM dataset incorporates space that is not in the snap reserve.&amp;nbsp; I put in a conditional for the volumes that don't have snapshot spill so I don't double count snapshots, but I run into an issue with clones.&amp;nbsp; They report used like a regular volume, but the real consumed space isn't reported. Any thoughts on what I can do to report the actual/physical/real consumed space of a clone with OCUM reporting?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Second question, this there a way to add attributes to be gathered by OCUM from the clusters like the 'vol show-space' outputs?&amp;nbsp; Logical-data size from 'vol efficiency", and user-data/physical used from 'vol show-space' are very useful outputs....&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 14:43:47 GMT</pubDate>
    <dc:creator>thywyn222</dc:creator>
    <dc:date>2025-06-04T14:43:47Z</dc:date>
    <item>
      <title>OCUM Reporting issues - Reporting actual (physical) consumed size on a volume, even a clone</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-Reporting-issues-Reporting-actual-physical-consumed-size-on-a-volume-even-a/m-p/133587#M24239</link>
      <description>&lt;P&gt;Hey all, I'm trying to get the affect of reporting the "physical used size" from the vol show-space command.&amp;nbsp; Volume.Used in the OCUM dataset incorporates space that is not in the snap reserve.&amp;nbsp; I put in a conditional for the volumes that don't have snapshot spill so I don't double count snapshots, but I run into an issue with clones.&amp;nbsp; They report used like a regular volume, but the real consumed space isn't reported. Any thoughts on what I can do to report the actual/physical/real consumed space of a clone with OCUM reporting?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Second question, this there a way to add attributes to be gathered by OCUM from the clusters like the 'vol show-space' outputs?&amp;nbsp; Logical-data size from 'vol efficiency", and user-data/physical used from 'vol show-space' are very useful outputs....&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 14:43:47 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-Reporting-issues-Reporting-actual-physical-consumed-size-on-a-volume-even-a/m-p/133587#M24239</guid>
      <dc:creator>thywyn222</dc:creator>
      <dc:date>2025-06-04T14:43:47Z</dc:date>
    </item>
    <item>
      <title>Re: OCUM Reporting issues - Reporting actual (physical) consumed size on a volume, even a clone</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-Reporting-issues-Reporting-actual-physical-consumed-size-on-a-volume-even-a/m-p/135613#M24589</link>
      <description>&lt;P&gt;When UM 7.3RC is released, a customer will have the ability to query the report databases in UM directly as access to certain tables and databases in&amp;nbsp;will be opened up.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Oct 2017 20:19:19 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-Reporting-issues-Reporting-actual-physical-consumed-size-on-a-volume-even-a/m-p/135613#M24589</guid>
      <dc:creator>Shawn</dc:creator>
      <dc:date>2017-10-26T20:19:19Z</dc:date>
    </item>
    <item>
      <title>Re: OCUM Reporting issues - Reporting actual (physical) consumed size on a volume, even a clone</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-Reporting-issues-Reporting-actual-physical-consumed-size-on-a-volume-even-a/m-p/135706#M24597</link>
      <description>&lt;P&gt;Does this mean that the vol show-space information will be available in the OCUM DB?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 31 Oct 2017 16:00:33 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-Reporting-issues-Reporting-actual-physical-consumed-size-on-a-volume-even-a/m-p/135706#M24597</guid>
      <dc:creator>thywyn222</dc:creator>
      <dc:date>2017-10-31T16:00:33Z</dc:date>
    </item>
    <item>
      <title>Re: OCUM Reporting issues - Reporting actual (physical) consumed size on a volume, even a clone</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-Reporting-issues-Reporting-actual-physical-consumed-size-on-a-volume-even-a/m-p/137624#M24963</link>
      <description>&lt;P&gt;Good news! UM 7.3RC1 has already been made available for download.&lt;BR /&gt;&lt;BR /&gt;Here is the download link which includes release and product information:&lt;BR /&gt;&lt;BR /&gt;OnCommand® Unified Manager 7.3 RC1&lt;BR /&gt;&lt;A href="https://mysupport.netapp.com/NOW/download/software/oncommand_um/7.3RC1/" target="_blank"&gt;&lt;U&gt;&lt;FONT color="#0066cc"&gt;https://mysupport.netapp.com/NOW/download/software/oncommand_um/7.3RC1/&lt;/FONT&gt;&lt;/U&gt;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jan 2018 14:08:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-Reporting-issues-Reporting-actual-physical-consumed-size-on-a-volume-even-a/m-p/137624#M24963</guid>
      <dc:creator>Shawn</dc:creator>
      <dc:date>2018-01-26T14:08:30Z</dc:date>
    </item>
  </channel>
</rss>

