Basic Problem Description : creating tamperproof snapshot polices on cluster - created a powershell script to identify the expired snapshots for the volumes now that the snapshot policy on the volume has been changed to a tamperproof policy. script works great on 9.13.1PX DR cluster but PROD cluster 9.10.1PX is getting the error below.   Get-NcSnapshot : Object reference not set to an instance of an object. At C:\Users\gwennculbertson\Documents\PROD-vol-snap-list-366days.ps1:62 char:10 + $list = Get-NcSnapshot -volume $thisVol | where-object {$_.Created - ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Get-NcSnapshot], ArgumentException + FullyQualifiedErrorId : Object reference not set to an instance of an object.,DataONTAP.C.PowerShell.SDK.Cmdlets.Snapshot.GetNcSnapshot Volume=vol_SATA_CIFS_Research_nicoleoreilly_01 Get-NcSnapshot : Object reference not set to an instance of an object. At C:\Users\gwennculbertson\Documents\PROD-vol-snap-list-366days.ps1:62 char:10 + $list = Get-NcSnapshot -volume $thisVol | where-object {$_.Created - ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Get-NcSnapshot], ArgumentException + FullyQualifiedErrorId : Object reference not set to an instance of an object.,DataONTAP.C.PowerShell.SDK.Cmdlets.Snapshot.GetNcSnapshot ... View more

Get-NCSnapMirror (Netapp.ONTAP 9.13.1.2306) doesn't correctly return the status of SnapMirrors from an Ontap 9.11.1P11 appliance. The returned status for all SnapMirrors, regardless of state, is just "snapmirrored".   On another workstation with DataONTAP 9.8.0 installed, the status returned is either "idle", "transferring", or "finalizing".   Any ideas? ... View more

Recently, I have performed testing to get our current set of Powershell scripts working with REST API.   I would like to share some of my results, in the spirit of trying to improve the product and ease our transition from ONTAPI to REST API   I tested a number of existing Powershell scripts which my team has developed over the years.  I tested with PSTK v9.13.1.2306 and OnTAP v9.10.1p12   On the positive side, the very basic functionality is there.  You can "drop in" the new PSTK package into Windows, use the same cmdlets with REST and ONTAPI, and they work at a basic level.  PSTK hides the complexity of the underlying calls and provides a consistent set of cmdlets.   On the not-so-great side, many common cmdlets (get-ncvol, get-ncvserver, et-ncsnapshot to name a few) do not return all of the properties with REST which they do with ONTAPI.  Since my scripts require these properties to be returned, I am unable to use the REST API and have to specify -ONTAPI for many of my calls.   There are other issues with REST, among them: REST calls in some cases are much slower than the same call with ONTAPI, The help pages for the cmdlets in many cases have not been fully updated to match the cmdlet (example the -ONTAPI option is not even mentioned), Some cmdlets behave differently with REST than with ONTAPI.  I have seen the REST flavor return a Warning message that the ONTAPI flavor does not.  While this is not a functional issue, it requires me to change my code to suppress or handle the warning message. I would be happy to share specific cmdlets which I have tested and which are inconsistent between REST and ONTAPI   I call on the PSTK maintainers to continue to improve and evolve the toolkit to provide consistent functionality, behavior, and performance between REST and ONTAPI flavors of their cmdlets.   I would encourage other users to post their replies here, regarding their experience in migrating to REST with PSTK. ... View more

I am trying to set the "snaplock-expiry-time" of a bunch of snapshots using the ONTAP Powershell toolkit... Ontap 9.13.1P2, Powershell Toolkit 9.13.1.2306 I get the snapshot created value with the Get-NcSnapshot, then add 30 days with the $snapexpdate = $snapshot.Created.adddays(30) I verify that the variables have been set correctly. I then use the Set-NcSnapshotSnaplockExpTime with the -ExpiryTime $snapexpdate and the command executes OK. Only thing is that this sets the "expiry-time" of the snapshot and not the "snaplock-expiry-time" which is not the same thing... How do I set the "snaplock-expiry-time" of my snapshots? Of cause I have the correct license (ONTAP One), snaplock compliance clock has been set, and snaplock has been set on the volume... and I am able to set the snaplock-expiry-time from both the commandline and GUI...  not apparently not via Powershell... ? Is this a bug?  And is there other ways to set this? ... View more