Community

Subscribe
Highlighted

Snap Creator 4.0 backup vSphere5.1 failed

We deploy Snap Creator 4.0 on Windows 2008R2 , it's fresh installed, plan for backup vSphere5.1 VM, but it failed.  error as

conf and log file already attached, Please help me check this, for this error, how to resolve it.

Other information: FAS6120, 8.1.1 7-mode, VM datastore in Vfiler,

Thanks!

Re: Snap Creator 4.0 backup vSphere5.1 failed

Hi

Is the datastore exported in the vfiler? It looks like SC cant find the datastore in the vfiler. Everything must be in the vfiler, if you exported from physical contoller things wont work. Can you send the output from "exportfs" command from vfiler and also the mount path in ESX for this datastore?

Regards,

Keith

Re: Snap Creator 4.0 backup vSphere5.1 failed

Hi

yes, the datastore exported in the vfiler to ESXi 5.1 Host,

Re: Snap Creator 4.0 backup vSphere5.1 failed

The reason of failure is this error:

[vmw-00169] Did not find export path for NFS Datastore tscdbm01!

This error is thrown when VIBE is unable to match any path from Controller nfs exportfs results to the datastore path in vCenter.

Kapil

Re: Snap Creator 4.0 backup vSphere5.1 failed

Hi Kapil

So? How to resolve it?   Why have the error?

Previous, I install Snap Creator 3.6 in the this server, it's backup is successful, why 3.6 not report this error?

Re: Snap Creator 4.0 backup vSphere5.1 failed

The only piece of code that changed in the path was a move from nfs-exportfs-list-rules to nfs-export-list-rules-2.  I suspect that this has something to do with it, but I'd like to confirm.

appcomcnsh, can you run the following on your controller and provide the output to both?  I'd like to see if there are differences for the export rules returned associated to your NFS Datastore path:

priv set advanced

ontapi execute "<nfs-exportfs-list-rules></nfs-exportfs-list-rules>"

ontapi execute "<nfs-exportfs-list-rules-2></nfs-exportfs-list-rules-2>"

priv set

Thanks,

--Matt

Re: Snap Creator 4.0 backup vSphere5.1 failed

Result as below, please have a look.

tscbjanp01> priv set advanced

Warning: These advanced commands are potentially dangerous; use

         them only when directed to do so by NetApp

         personnel.

tscbjanp01*> ontapi execute "<nfs-exportfs-list-rules></nfs-exportfs-list-rules>"

<?xml version='1.0' encoding='UTF-8' ?>

<!DOCTYPE netapp SYSTEM '/na_admin/netapp_filer.dtd'>

<netapp version='1.1' xmlns='http://www.netapp.com/filer/admin'>

<results status="passed"><rules><exports-rule-info><pathname>/vol/ROOT/home</pathname><nosuid>true</nosuid><read-write><exports-hostname-info><all-hosts>true</all-hosts></exports-hostname-info></read-write><sec-flavor><sec-flavor-info><flavor>sys</flavor></sec-flavor-info></sec-flavor></exports-rule-info><exports-rule-info><pathname>/vol/tklndmp</pathname><nosuid>true</nosuid><read-write><exports-hostname-info><all-hosts>true</all-hosts></exports-hostname-info></read-write><sec-flavor><sec-flavor-info><flavor>sys</flavor></sec-flavor-info></sec-flavor></exports-rule-info><exports-rule-info><pathname>/vol/ROOT</pathname><anon>0</anon><nosuid>true</nosuid><read-write><exports-hostname-info><all-hosts>true</all-hosts></exports-hostname-info></read-write><sec-flavor><sec-flavor-info><flavor>sys</flavor></sec-flavor-info></sec-flavor></exports-rule-info><exports-rule-info><pathname>/vol/htidboprd04</pathname><nosuid>true</nosuid><read-write><exports-hostname-info><all-hosts>true</all-hosts></exports-hostname-info></read-write><sec-flavor><sec-flavor-info><flavor>sys</flavor></sec-flavor-info></sec-flavor></exports-rule-info><exports-rule-info><pathname>/vol/htidboprd03</pathname><nosuid>true</nosuid><read-write><exports-hostname-info><all-hosts>true</all-hosts></exports-hostname-info></read-write><sec-flavor><sec-flavor-info><flavor>sys</flavor></sec-flavor-info></sec-flavor></exports-rule-info><exports-rule-info><pathname>/vol/htidboprd02</pathname><nosuid>true</nosuid><read-write><exports-hostname-info><all-hosts>true</all-hosts></exports-hostname-info></read-write><sec-flavor><sec-flavor-info><flavor>sys</flavor></sec-flavor-info></sec-flavor></exports-rule-info><exports-rule-info><pathname>/vol/htidboprd01</pathname><read-write><exports-hostname-info><all-hosts>true</all-hosts></exports-hostname-info></read-write><sec-flavor><sec-flavor-info><flavor>sys</flavor></sec-flavor-info></sec-flavor></exports-rule-info></rules></results></netapp>

tscbjanp01*> ontapi execute "<nfs-exportfs-list-rules-2></nfs-exportfs-list-rules-2>"

<?xml version='1.0' encoding='UTF-8' ?>

<!DOCTYPE netapp SYSTEM '/na_admin/netapp_filer.dtd'>

<netapp version='1.1' xmlns='http://www.netapp.com/filer/admin'>

<results status="passed"><rules><exports-rule-info-2><pathname>/vol/ROOT/home</pathname><security-rules><security-rule-info><nosuid>true</nosuid><read-write><exports-hostname-info><all-hosts>true</all-hosts></exports-hostname-info></read-write><sec-flavor><sec-flavor-info><flavor>sys</flavor></sec-flavor-info></sec-flavor></security-rule-info></security-rules></exports-rule-info-2><exports-rule-info-2><pathname>/vol/tklndmp</pathname><security-rules><security-rule-info><nosuid>true</nosuid><read-write><exports-hostname-info><all-hosts>true</all-hosts></exports-hostname-info></read-write><sec-flavor><sec-flavor-info><flavor>sys</flavor></sec-flavor-info></sec-flavor></security-rule-info></security-rules></exports-rule-info-2><exports-rule-info-2><pathname>/vol/ROOT</pathname><security-rules><security-rule-info><anon>0</anon><nosuid>true</nosuid><read-write><exports-hostname-info><all-hosts>true</all-hosts></exports-hostname-info></read-write><sec-flavor><sec-flavor-info><flavor>sys</flavor></sec-flavor-info></sec-flavor></security-rule-info></security-rules></exports-rule-info-2><exports-rule-info-2><pathname>/vol/htidboprd04</pathname><security-rules><security-rule-info><nosuid>true</nosuid><read-write><exports-hostname-info><all-hosts>true</all-hosts></exports-hostname-info></read-write><sec-flavor><sec-flavor-info><flavor>sys</flavor></sec-flavor-info></sec-flavor></security-rule-info></security-rules></exports-rule-info-2><exports-rule-info-2><pathname>/vol/htidboprd03</pathname><security-rules><security-rule-info><nosuid>true</nosuid><read-write><exports-hostname-info><all-hosts>true</all-hosts></exports-hostname-info></read-write><sec-flavor><sec-flavor-info><flavor>sys</flavor></sec-flavor-info></sec-flavor></security-rule-info></security-rules></exports-rule-info-2><exports-rule-info-2><pathname>/vol/htidboprd02</pathname><security-rules><security-rule-info><nosuid>true</nosuid><read-write><exports-hostname-info><all-hosts>true</all-hosts></exports-hostname-info></read-write><sec-flavor><sec-flavor-info><flavor>sys</flavor></sec-flavor-info></sec-flavor></security-rule-info></security-rules></exports-rule-info-2><exports-rule-info-2><pathname>/vol/htidboprd01</pathname><security-rules><security-rule-info><read-write><exports-hostname-info><all-hosts>true</all-hosts></exports-hostname-info></read-write><sec-flavor><sec-flavor-info><flavor>sys</flavor></sec-flavor-info></sec-flavor></security-rule-info></security-rules></exports-rule-info-2></rules></results></netapp>

tscbjanp01*> priv set

Re: Snap Creator 4.0 backup vSphere5.1 failed

When I looked at the log, I didn't see /vol/tscdbm01.  Did you run this against the same export point?  If the change was against the vfiler, we would expect to see /vol/tscdbm01 in the ONTAP call but I didn't see it.  You might want to run the same command against the vfiler, but use ZEDI:

https://communities.netapp.com/community/interfaces_and_tools/developer/zedi

I'm looking for differences in the output for those ONTAP calls (nfs-exportfs-list-rules, nfs-exportfs-list-rules-2) to see whether /vol/tscdbm01 is or isn't showing up in the --2 version but does show up in the original.

If you want connect to the vfiler and run the API call with ZEDI, that might be a better approach.  You can send the results directly to 'rmatt@netapp.com' that might help expedite the debugging process.  Thanks,

--Matt

Re: Snap Creator 4.0 backup vSphere5.1 failed

I export it in vfiler,and also mount the datastore  from vfiler in VMware5.1,  so I think why it did't display in filer command.

tscbjanp01> vfiler run tscbjanv01 exportfs

===== tscbjanv01

/vol/tscbjanv01_root    -sec=sys,rw,anon=0

/vol/tscdbm01   -sec=sys,rw=172.16.5.0/24,root=172.16.5.0/24

/vol/tscdbm02   -sec=sys,rw=172.16.5.0/24,root=172.16.5.0/24

/vol/CDSRV      -sec=sys,rw=172.16.5.0/24,root=172.16.5.0/24

Re: Snap Creator 4.0 backup vSphere5.1 failed

The issue is we need to see the output differences for the ZAPI call to the vfiler.  Can you return those results with ZEDI against the vfiler?  That might give us a clue why it isn’t being found.  Thanks!

--Matt