I moved away from this project but I'm back at it. I attempted to get the data you requested, however, knowing that snap reclaimable is a long process and not wanting to burden my filer, I did the following...
Get-NaSnapshotReclaimable -controller $ControllerName VolName3 -Snapshots ( Get-NaSnapshot -controller $ControllerName VolName3 | sort Cumulative | select -last 1)
After a few moments, this yielded the following error...
Get-NaSnapshotReclaimable : Could not connect to 10.10.10.10 on port 80 for protocol HTTP.
At line:1 char:26
+ Get-NaSnapshotReclaimable <<<< -controller $ControllerName VolName3 -Snapshots ( Get-NaSnapshot -controller $ControllerName VolName3 | sort Cumulative | select -last 1)
+ CategoryInfo : InvalidOperation: (10.10.10.10:NaController) [Get-NaSnapshotReclaimable], NaConnectionException
+ FullyQualifiedErrorId : ApiException,DataONTAP.PowerShell.SDK.Cmdlets.Snapshot.GetNaSnapshotReclaimable
Note, that any other command issued is working fine using the same $ControllerName Connect-NaController object.
I also found that immediately after issuing this command, my filer CPU went to 99%, and CIFS operations dropped dramatically (CIFS is the only filer access protocol we are using). In fact, causing filer performance issues and triggering a couple of alerts. Filer performance returned to normal in fairly short order, but I won't be issuing that again.
I plan on contacting Netapp support to see why this is having such a negative impact on my filer. It would be helpful to be able to relay what is actually being submitted to the filer from this command. Any input?
