Error codes: [39:521], [39:522], [39:523], [39:526] Cataloging or Scanning fails when using SnapDiff V3

The snapshot cataloging operation for the NDMP, CIFS or NFS agent, or file scanning for the CIFS or NFS agent fails when using SnapDiff V3.

Symptoms

After upgrading the NetApp file server to ONTAP version 9.10.1 or later, the snapshot cataloging operation for the NDMP, CIFS or NFS agent, or file scanning for the CIFS or NFS agent fails with one of the following job pending reasons:

• Error code: [39:521] Could not start SnapDiff on vserver interface [<array name>]. Please use array management to set this vserver to tunnel to the cluster.
• Error code: [39:522] Unable to start SnapDiff session. Please check if RPC is enabled and if there is a data network interface configured for NFS on vserver [<vserver>].
• Error code: [39:523] User is not authorized for REST. Please verify that array [<array name>] login [<login>] is configured on the file server for http access - check the security login for application 'http', and check the vserver services web access for service 'rest'.
• Error code: [39:526] Unable to start SnapDiff session. Array [<array name>] version [<ONTAP version>] is reporting that SnapDiff APIs are not supported. Please upgrade to ONTAP 9.10.1 P11 or later, 9.11.1 P7 or later, or a later ONTAP version.
• Error code: [39:301] Failed to index data for snapshot on volume [<file server volume name>].

Causes

For ONTAP version 9.10.1 prior to P11 and 9.11.1 prior to P7, the SnapDiff V1 and V2 APIs are not enabled on the file server. The cataloging or scanning must use the NetApp SnapDiff V3 API. The configuration requirements for V3 API are different compared to the V1 and V2 APIs requirements. Following are the reasons for snapshot cataloging failure:

• Either a vServer is used that does not tunnel to the cluster or the cluster array is not configured in the Array Management. The SnapDiff API must be initiated from a cluster interface. If a vServer array is used, then the vServer must be configured to tunnel to the cluster.
• The Remote Procedure Call (RPC) is not enabled on the vServer. The SnapDiff V2 and V3 APIs require RPC to be enabled on the vServer.
• No NFS interface is present between the vServer and the Commvault MediaAgent.
• Either the cluster array is not authorized for REST APIs or HTTP is not enabled. The SnapDiff V3 APIs are only available through the NetApp REST interface.
• The file server is running ONTAP version 9.10.1 prior to P11 or 9.11.1 prior to P7. These ONTAP versions have the SnapDiff V1 and V2 APIs disabled. SnapDiff V3 is still possible but one of the previous causes prevented SnapDiff V3 from succeeding.

Resolution

• To verify and confirm the NetApp file server commands listed in this section, see the NetApp ONTAP product documentation page.
  • If you want to perform snapshot cataloging on the vServer client, ensure that the following requirements are met:
    • Cluster array and vServer array are configured in the Array Management. The SnapDiff APIs require sending commands directly to the cluster. Therefore, when cataloging NDMP snapshots of a vServer client, the vServer must be associated to the cluster client.
    • In the Storage Virtual Machine tab of the cluster client properties, check whether the vServer client is listed.
      • If the Storage Virtual Machine tab is not available in the cluster client properties, configure the cluster client in the Array Management.
      • If the vServer client is not listed, then either navigate to the vServer client properties and select the cluster or navigate to the Storage Virtual Machine tab of the cluster client properties and add the vServer to the cluster client.
  • Verify RPC is enabled on the vServer being cataloged. Even if a cluster client is being cataloged, the vServer for the volume being cataloged must have RPC enabled. On the file server, verify RPC is enabled on the vServer using the following commands:
    • set advanced
    • vserver snapdiff-rpc-server show -vserver <vserver>
    • vserver snapdiff-rpc-server on -vserver <vserver>
  • Verify whether an NFS interface exists between the vServer and the Commvault MediaAgent. Specifically, confirm that there exists a vServer NFS interface on the file server node containing the volume being cataloged using the following commands:
    • vserver nfs show -vserver <vserver>
    • network interface show -vserver <vserver> -data-protocol nfs
  • Verify that the cluster array login is authorized for REST, HTTP, and SSL. For more information on setting up a NetApp cluster login, see Frequently Asked Questions for the NetApp Storage Array.
    • To enable REST API based authorization to the cluster array, run the following commands:
      • vserver services web access show -vserver <vserver> -name rest -role <role>
      • vserver services web access create -vserver <vserver > -name rest -role <role>
    • To enable HTTP and SSH based authorization to the cluster array, run the following commands:
      • security login show -vserver <vserver> -user-or-group-name <user> -application http
      • security login create -vserver <vserver> -user-or-group-name IntelliSnapUser -application http -authentication-method password -role <role>
      • security login show -vserver <vserver> -user-or-group-name <user> -application ssh
      • security login create -vserver <vserver> -user-or-group-name IntelliSnapUser -application ssh -authentication-method password -role <role>
    • To enable the SnapDiff and license APIs for the cluster array, run the following commands:
      • security login role show -vserver <vserver> -role <role> -cmddirname "snapdiff"
      • security login role create -vserver <vserver> -role <role> -cmddirname "snapdiff" -access all
      • security login role show -vserver <vserver> -role <role> -cmddirname "license"
      • security login role create -vserver <vserver> -role <role> -cmddirname "license" -access all
• For ONTAP versions 9.10.1 prior to P11 and 9.11.1 prior to P7, consider enabling the REST interface as described above or upgrade the ONTAP version to 9.10.1 P11 or later, 9.11.1 P7 or later, or later ONTAP version. Using the REST interface is preferable over the HTTPS interface.