VMware backups failing with error 6

[Kisad]

Hello All,

I have several vmware backups failing in a policy with error code 6. They were working till yesterday. As far as i'm aware nothing has changed since yesterday that might have caused the backups to fail. Please could someone suggest what are the things i should be looking at (ex logs etc) for troublehooting this.

The Master & Media server which is also the vmware backup host are on windows 2008 R2 system running on netbackup 7.5

Attached is the detailed job logs from one of the failed server.

Thanks

[RamNagalla]

you would need to post the details of the child job...

and few more detais please

1) what is the transport method that you are using?

2) what is the Vcenter version?

[sri_vani]

Kisad,

Can u plz share us more details

1)What is the transport method configured to this policy?

2)If it is a SAN Transport, does all Storage LUNs that are mapped to ESXi hosts are mapped to Backup host?

3)bpfis,bpbkar and VXMS logs may give us more clues

[Kisad]

Hi Nagalla,

Thanks for responding. I have attached a screenshot of the details of ethe child job. All transport methods are checked in the backup policy in the following order san,hotadd,nbd & nbdssl. The VMware vCenter Server version is 5.1.0 

[RamNagalla]

Please attach the bpbrm log from the Media server

"critical bpbrm unexpected termination"

see the below 2 related posts.

http://www.symantec.com/business/support/index?page=content&id=TECH191198

https://www-secure.symantec.com/connect/forums/netbackup-75-vm-backup-unexpected-termination-client-system-call-failed-11

[neptor]

We had an issue with this with a box that is over 3TB.

Check on media server -  bpbkar logs,  error was VM_SET_CREDENTIAL returned stat = 2062

Fix was to bump the idle session time out value in the vpxd.cfg log on the vcenter server, the default is 15 minutes which was nowhere near enough time for a 3+ Tb server.

Lines added to vpxd.cfg

Add the following <soap> elements within the <vmacore> </vmacore> tags:
<soap>
<!-- Minutes before idle sessions time out -->
<sessionTimeout>180</sessionTimeout>
</soap>