I'm looking for help on creating some powershell code that retrieves the current DACLs of a volume (or directory path) and stores it as a security descriptor.  I had come across this page on the web (http://www.craig-tolley.co.uk/2016/02/09/assigning-permissions-to-a-volume-through-the-netapp-powershell-toolkit/) and it guided me through applying new permissions using the OnTap Powershell toolkit - however I cannot devise a way to modify the code so that an ACE can be removed or added to the ACL (Security Descriptor).   I presume it's some combination of Get-NcFileDirectorySecurity and (New-NcFileDirectorySecurityNtfs or Add-NcFileDirectorySecurityNtfsDacl).  I've investigated all of the  *NcFileDirectorySecurity* cmdlets, and only Get-NCFileDirectorySecurity appears to retrieve currently applied permissions, but it cannot be pipe'd into another cmdlet 😞   My larger objective is to build a WFA command that allows a user to add/remove an AD Group from their volume.   I've found the Powershell toolkit to be much quicker and straightforward than using (Get-Acl / Set-Acl)         connect-NcController $ClusterName   $volName = "vol_test_3" $Vserver = "svm-lab-a"   Get-NcFileDirectorySecurity -Path "/$volName" -VserverContext $Vserver | New-NcFileDirectorySecurityNtfs -SecurityDescriptor $VolName     #this part doesn't work!   First cmdlet returns ACLs, but doesn't store it within SecurityDescriptor. Get-NcFileDirectorySecurityNtfsDacl -SecurityDescriptor $volName -Vserver $vserver   #my output is {Administrators,Users,CREATOR OWNER, SYSTEM}.   I'm hoping to capture the DACLs of "/$VolName" - such as displayed by (Get-NcFileDirectorySecurity -Path "/$volName" -VserverContext $Vserver).acls ... View more

Dear all,   It has been a while, here is finally some news about NetApp Harvest.   TL;DR: - We are planning Harvest 2.0 alpha-test release in around a month - Simultaneously, we will do a (probably last) legacy release, Harvest 1.7, in August.   Harvest 2.0 Things have been going a bit slower than we expected, but we made a lot of progress. As announced earlier, we've changed the whole architecture to meet two goals that are often regarded as disjoint in software engineering: high performance and high flexibility. Flexibility mainly means that it will be much easier to integrate Harvest to any system that you want to monitor (including but not limited to Ontap systems). It will be also relatively easier to feed metrics into new databases. Out of the box, we will support Prometheus. Graphite will be supported as well, but with some limitations (since Graphite only accepts numerical data).     Before we plan on the official release of Harvest 2.0, we want to do an alpha-test release for users who want to "play around" with the new software and give us feedback. Tentatively we want to do this release late July or early August (once we decide the final date, I'll post an update here).   If you are interested to get the alpha release, please send me a message with your name, email address and organization. But please note the following: - this will be a strictly test release, not intended for production - Harvest 2.0 requires Linux + Python3 and optionally pip to install dependencies, - supports only CDOT systems, 7 mode will come later - gives you approximately the same set of counters as Harvest 1.6 + extensions - for capacity counters there is no need for OCUM/ActiveIQUM anymore - collected counters can be sent to Prometheus or Graphite or both, but: - there will be limited number of Grafana dashboards ready and only for Prometheus (but of course, you can create your dashboards if wished) - Harvest 2.0 includes a self-monitoring collector, so you can see how much CPU/RAM it uses and compare to Harvest 1.6 - it will come with a developer's documentation for writing your own collectors and exporters.   If you want to test the new package, we appreciate that a lot, since feedback at this point can help us incredibly. If you want to wait for the official (stable) release, just keep tuned. We will keep you updated as soon as we have a release date on the horizon.   Harvest 1.7 This will probably be our last legacy release which we are planning to do in August. It will mainly include bug fixes and no new major features.   Lastly, again, I need to apologize for not responding to many messages here in communities. I will try to catch up, but if you don't get a response to your issue, please DM or tag me (probably again -- sorry).   Cheers,   Vachagan ... View more

I just wanted to say thank you for making the tool available.   Within a few hours of it collecting data, we already knew more about what the storage was doing than before 🙂   A minor note. The init.d script needs a #!/bin/bash on the first line (well at least under RedHat 7.1) otherwise it gets an exec error when the system starts, and doesn't start the pollers.   Looking to see futher into the capability, is there a way to collect snapmirror statistics?   Iain ... View more

I am trying to create what I assume should be an extremely simple view in ActiveIQ Unified Manager - a list of every volume with a column showing the current volume sizes. My intent is to browse through and look for volume with odd sizes, which indicates autogrow has kicked in, so I can manually inspect and possibly resize / reconfigure them.   I added the "Total Data Capacity" field. For most volumes this field shows full volume size, but for extremely tiny volumes that are 1GB (mostly root volumes) it shows Total Data Capacity of 973 MB instead of 1GB. When looking in System Manager, it shows correctly as 1GB. I spent a long time thinking the whole list was invalid until I scrolled down and saw that the rest were fine. Is this a bug/glitch in AIUM or am I missing something? ... View more