Get-NcSnapshot | NetApp | Page 1

red steeple May 21, 2024, 9:04 AM

#

Get-NcSnapshot -Volume 'volname' times out via REST if more than 4 snapshots exists. Tested with ONTAP 9.12.1 & 9.13.1, Module version 9.11 and 9.14

ancient schooner May 21, 2024, 4:21 PM

#

Think I solved something similar by adding -ZapiCall. Unfortunately my lab is down currently so can't test it.

red steeple May 22, 2024, 5:51 AM

#

Yeah I did that as a workaround too. This API transition will run the Powershell Toolkit in the ground...

stuck birch Jul 29, 2024, 12:54 PM

#

ancient schooner Think I solved something similar by adding -ZapiCall. Unfortunately my lab is do...

Any idea if this is a problem in PSTK? Or is it an issue on the ONTAP side?

wanton crater Aug 26, 2024, 3:20 PM

#

Same for me... Adding ZapiCall was the workaround for me.

chilly fern Aug 29, 2024, 12:25 PM

#

Yeah, tell me about it... It will take thousands of customer (or consultant) man-hours to test and modify PowerShell scripts to work with newer toolkit versions and REST. Attributes are suddenly empty and some cmdlets take forever or time out.

One hint it to start using templates or attributes in order to reduce the amount of data collected. The Get-NcSnapshot cmdlet is pretty useless without it.

shy yoke Aug 30, 2024, 5:34 PM

#

FYI - latest official communique on ZAPI (excerpt) .....

This correspondence is an update to our previous announcement from February 2023, which stated the end of availability (EOA) of ONTAPI (ZAPI) in January 2024. Upon reassessment and recognizing our customers' continued reliance on ONTAPI, we have decided to prolong offering ONTAPI. Consequently, the EOA for ONTAPI is now deferred until further communication.

Post upgrade to ONTAP versions 9.14 and beyond, ONTAPI (ZAPI) will stay active for 30 days. If no ONTAPI calls are detected during this timeframe, ONTAPI will be automatically disabled. However, it can be re-enabled if necessary, using a CLI command.

#Get-NcSnapshot