Skip to main content
NetApp Knowledge Base

Is full junction path of a volume required when creating NFS datastore mounted to clustered Data ONTAP for Virtual Storage Console?

Views:
144
Visibility:
Public
Votes:
0
Category:
clustered-data-ontap-8
Specialty:
nfs
Last Updated:

Applies to

  • Clustered Data ONTAP 8
  • FlexPod

Answer

When adding an NFS datastore mounted to clustered Data ONTAP in Home -> Inventory -> Datastores on vSphere Client, full junction path of a volume in one SVM should be input in 'Folder' in the 'Add Datastore' wizard. For example, if the full junction path is '/junction_path_name', then '/junction_path_name' should be input in 'Folder'.

The reason for emphasizing this point is, vSphere Client/ESX host allows for junction path like 'junction_path_name' (without '/'). That is, even when you input 'junction_path_name' instead of '/junction_path_name' as 'Folder', the creation and mount of the datastore will still be OK for VMware.

However, if this datastore will be used in Virtual Storage Console, then the full junction path is required. Because when adding backup job through 'Backup and Recovery', whatever is input in 'Folder' will be used as a parameter to query clustered Data ONTAP whether a volume with this junction path exists in the SVM. If there is no '/' in this parameter, clustered Data ONTAP will treat it as a different junction path and respond with no volume with such junction path. Thus this datastore will not be listed in the 'Available Entities' in 'Backup and Recovery' when adding a backup job.

In such a case, the server.log will appear similar to the following:

2014-09-02 11:33:04,862 [datastoreList:90eeb5ada2cb78270e7e34cd9d858b98:] DEBUG - Executing ZAPI request volume-get-iter to 10.130.200.222:
<?xml version='1.0' encoding='UTF-8'?><!DOCTYPE netapp SYSTEM 'file:/etc/netapp_filer.dtd'><netapp xmlns="http://www.netapp.com/filer/admin" version="1.7" vfiler="nfsv"><volume-get-iter><desired-attributes><volume-attributes><volume-id-attributes><name></name></volume-id-attributes></volume-attributes></desired-attributes><query><volume-attributes><volume-id-attributes><junction-path>qianbing_test2</junction-path></volume-id-attributes></volume-attributes></query></volume-get-iter></netapp>
2014-09-02 11:33:04,872 [datastoreList:90eeb5ada2cb78270e7e34cd9d858b98:] DEBUG - Received ZAPI response for volume-get-iter from 10.130.200.222:
<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE netapp SYSTEM 'file:/etc/netapp_gx.dtd'>
<netapp version='1.21' xmlns='http://www.netapp.com/filer/admin'>
<results status="passed"><num-records>0</num-records></results></netapp>

SMVI will complain:

2014-07-23 10:43:32,529 [datastoreList:0fd85a365279e0ad2349b2c4b81ff33a:] INFO - Unable to manage datastore datastore-15: Failed to find NFS export path qianbing_test2 for datastore datastore_qianbing_test2 on storage system xxx.xxx.xxx.xxx. NFS datastores must be exported from a Data ONTAP storage system.
com.netapp.smvi.task.vmware.util.InvalidDatastoreException: Failed to find NFS export path JDLVNFS0001_vol5 for datastore NFS_VDI_Store4 on storage system 192.168.83.25. NFS datastores must be exported from a Data ONTAP storage system.
at com.netapp.smvi.task.vmware.util.DatastoreMapper.createNfsDatastore(DatastoreMapper.java:447)
at com.netapp.smvi.task.vmware.util.DatastoreMapper.createDatastore(DatastoreMapper.java:269)
at com.netapp.smvi.task.vmware.util.DatastoreMapper.createDatastore(DatastoreMapper.java:135)
at com.netapp.smvi.task.vmware.VmGetDatastoreList.execute(VmGetDatastoreList.java:112)
at com.netapp.common.flow.TaskInstanceTemplate.execute(TaskInstanceTemplate.java:325)
at com.netapp.common.flow.Operation.executeCurrentStack(Operation.java:133)
at com.netapp.common.flow.Operation.execute(Operation.java:59)
at com.netapp.common.flow.Threadpool$OperationThread.run(Threadpool.java:263)

On contrast, server.log under a normal condition appears similar to the following:

2014-09-02 11:33:05,167 [datastoreList:90eeb5ada2cb78270e7e34cd9d858b98:] DEBUG - Executing ZAPI request volume-get-iter to 10.130.200.222:
<?xml version='1.0' encoding='UTF-8'?><!DOCTYPE netapp SYSTEM 'file:/etc/netapp_filer.dtd'><netapp xmlns="http://www.netapp.com/filer/admin" version="1.7" vfiler="nfsv"><volume-get-iter><desired-attributes><volume-attributes><volume-id-attributes><name></name></volume-id-attributes></volume-attributes></desired-attributes><query><volume-attributes><volume-id-attributes><junction-path>/qianbing_test3</junction-path></volume-id-attributes></volume-attributes></query></volume-get-iter></netapp>
2014-09-02 11:33:05,274 [datastoreList:90eeb5ada2cb78270e7e34cd9d858b98:] DEBUG - Received ZAPI response for volume-get-iter from 10.130.200.222:
<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE netapp SYSTEM 'file:/etc/netapp_gx.dtd'>
<netapp version='1.21' xmlns='http://www.netapp.com/filer/admin'>
<results status="passed"><attributes-list><volume-attributes><volume-id-attributes><name>qianbing_test3</name><owning-vserver-name>nfsv</owning-vserver-name></volume-id-attributes></volume-attributes></attributes-list><num-records>1</num-records></results></netapp>

Additional Information

additionalInformation_text