Hi everyone, We're currently investigating some significant differences in the reported physical used capacity between NetApp versions 9.13 and 9.14 and would appreciate your insights. In version 9.13, when querying the physical used capacity using the CLI command volume show -volume Apr* -fields size,available,total,used,physical-used, we received the following results: vserver               volume               size                   available           total            used       physical-used --------             -----------                     -------            ---------                 -------            -----       ------------- NetApp_2       Apr_ss_15gb       17.89GB          17.89GB        17.89GB       340KB       340KB NetApp_2        Apr_ss_70gb       78.86GB          78.86GB       78.86GB       308KB      308KB However, when querying the same information in version 9.14 with the same CLI command, volume show -volume Apr* -fields size,available,total,used,physical-used,we observed a notable increase in the reported physical used capacity: vserver           volume                          size          available        total        used      physical-used --------             -----------                     -------             ---------          -------         -----          ------------- NetApp_2     Apr_ss_15gb       17.89GB       17.89GB       17.89GB    468KB   17.99GB NetApp_2    Apr_ss_70gb         78.86GB       78.86GB      78.86GB    456KB    79.30GB We're trying to understand the reasons behind this discrepancy: What constitutes physical used capacity in NetApp? What changes were made between versions 9.13 and 9.14 that could account for the differences in physical used capacity? What additional data is included in the calculation of physical used capacity in version 9.14 compared to version 9.13? Where can we find documentation or resources detailing these changes to better understand how to interpret the physical used metric in our storage environment? Any insights or guidance you can provide would be greatly appreciated.  Thank You.! ... View more

Hello,   I  connected LUN Netapp on windows server. It works prefectly but, i found that antiransomware is not enable on LUN Netapp. 😞    Also, it seems, it is not possible to restore file, just somes files on LUN volume from snapshot, that is true ? It is possible restore all the volume but not somes files   Also, tiering policy not work on LUN volume ?   thanks a lot ... View more

I'm about to upgrade our SnapCenter infrastructure from 5.0P2 to 6.1P1, with the exception of five SQL Servers running Windows Server 2008R2 and 2012R2 [and yes we are pushing them to migrate to new servers]. Those Windows versions can't run SC 6.x [or for that matter some of the new prerequisites like the new PowerShell version requirement].   The problem: I just discovered that the IMT indicates that both 6.0.1 and 6.1 running on the SC server is not compatible with 5.x Windows or SQL plug-ins. I could upgrade only to 6.0 I suppose, which can run the Windows 5.x plug-in and possibly the SQL one [I say possibly because the online documentation and IMT for the plug-in say the SQL 5.x plug-in is compatible, but the IMT for the server says it is not].   Any suggestions? Is 6.0 sufficiently stable without going to 6.0.1 or 6.1? Is 6.0 in fact compatible with the SQL 5.x plug-in? ... View more

Hi,   trying to use ansible to create fc target for a vserver but no luck,  playbook below , the error is fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error: the python NetApp-Lib module is required. Import error: No module named 'netapp_lib'"}   not sure what is missing, any idea?   playbook -- - hosts: localhost vars: netapp_hostname: cluster01 netapp_username: svmadmin vars_prompt: - name: netapp_password prompt: "Please enter Netapp password (hidden from output)" private: yes tasks: - name: Create FCP interface netapp.ontap.na_ontap_interface: vserver: svmfcp31 state: present interface_name: svmtest_0g_tgt interface_type: fc data_protocol: fcp current_node: node-01 current_port: 0g role: data failover_policy: disabled force_subnet_association: false admin_status: up hostname: "{{ netapp_hostname }}" username: "{{ netapp_username }}" password: "{{ netapp_password }}" ... View more

I am not sure if this is the correct forum, but I did see other posts about NetApp volumes here. Please advise of the correct forum if needed. On the Google Cloud Platform, I deployed  a STANDARD service level 2048gb NetApp storagepool in uscentral1. Then I created a 100gb volume also in uscentral1.   I have a question about this volume's performance. When I use the FIND command to traverse through a directory, the performance is noticeably slower on the Netapp volume versus the same data on the local drive. At first I was thinking I needed to increase my throughput performance by increasing my service level or making the volume bigger(which increases throughput performance). But after thinking about it, my FIND command is not moving data, it's just traversing through the directory. So it seems this is not a throughput issue?   Does anyone have insight as to the performance issue here:   root@server1:~# time find /data_local/cache/4c71-4cb6-bd50-d80aa7/ -type f | wc -l 4995 real 0m0.119s user 0m0.058s sys 0m0.059s root@server1:~# time find /data_NetappVol/cache/4c71-4cb6-bd50-d80aa7/ -type f | wc -l 4995 real 0m3.968s user 0m0.078s sys 0m0.219s ... View more