10-13-2014 02:17 AM
Hi,
For all vmware policies in Netbackup I get "Error opening the snapshot disks using given transport mode: Status 23". The transport method is nbd. The backup server can telnet to the ESX hosts on port 443 and 902.
I can see the snapshot getting created in vcenter during the policy execution. After that I get the transport error above (in the nbu activity monitor job) and then
"INF - vmwareLogger: PostExtendedEventAPI: SYM_VMC_ERROR: SOAP_ERROR "
That error insidactes permission misconfiguration but AFAIK this link above shold be enough:
http://www.symantec.com/business/support/index?page=content&id=TECH130493
Permissions for the account used is set according to the above.
Versions are
Netbackup 7.6.0.3 on Windows 2008 R2
The ESX hosts are v5.0.0 b1311175
Any suggestions?
/Johan
Solved! Go to Solution.
10-13-2014 02:41 AM
i would say some time permission defined on the T/N is not enough...
and to make sure.. give Full privilages for the accout that is being used.. and test the backups.. and see how it goes..
and to get the enough evidace...
enable the Vxms log on backup host and attach the logs to the thread..
see below T/N to understand how to enable the Vxms log...
http://www.symantec.com/business/support/index?page=content&id=TECH72862
NOTE:- do make sure you turn off the log one you collected it.. else it will run out of space...
10-13-2014 02:41 AM
i would say some time permission defined on the T/N is not enough...
and to make sure.. give Full privilages for the accout that is being used.. and test the backups.. and see how it goes..
and to get the enough evidace...
enable the Vxms log on backup host and attach the logs to the thread..
see below T/N to understand how to enable the Vxms log...
http://www.symantec.com/business/support/index?page=content&id=TECH72862
NOTE:- do make sure you turn off the log one you collected it.. else it will run out of space...
10-13-2014 02:45 AM
Hello
Check in the bpfis log what it says after the SOAP error. It usually has more details about what permission or other issue its facing.
As in these notes.
http://www.symantec.com/docs/TECH214208
http://www.symantec.com/docs/TECH203881
10-13-2014 07:44 AM
Thanks,
Correct permissions on the vcenter level solved it:
http://www.symantec.com/business/support/index?page=content&id=TECH130493
/Johan