4 vm's from a policy of 27 vm's are failing with error code 6 and 23

[lovy1]

Hello,

4 vm's from a policy of 27 vm's are failing with error code 6 and 23. name resolution is ok. pls assist.

08/13/2018 19:47:50 - Info bptm (pid=5960) start backup
08/13/2018 19:47:50 - Info bpbkar (pid=5959) INF - Backing up vCenter server xxx, ESX host xxx, BIOS UUID xxx, Instance UUID xxx, Display Name xxx, Hostname xx.xx.xx.xx
08/13/2018 19:49:46 - Error bpbrm (pid=5955) from client xxx: ERR - Error opening the snapshot disks using given transport mode: nbd Status 23
08/13/2018 19:49:47 - Critical bpbrm (pid=5955) from client xxx: FTL - cleanup() failed, status 6
08/13/2018 19:49:49 - Error bptm (pid=5960) media manager terminated by parent process
08/13/2018 19:53:59 - Critical bpbrm (pid=5955) unexpected termination of client xxx
08/13/2018 19:53:59 - Info bpbkar (pid=0) done. status: 6: the backup failed to back up the requested files

Thanks

[RamNagalla]

have you verified the communication between the backup host and the ESXi host hosting the 4 VMs?

does TCP 902 connecting fine?

is there any other VM on same ESXi host making successfull backups?

[Lowell_Palecek]

Whenever you see this:

>Error bpbrm (pid=5955) from client xxx...

Check the relevant logs on the client for context and more information about the error.

I expect that xxx in this case is the backup host and bpbkar32 is the process. Check the bpbkar log. Also check the bpfis log for any issues with making the snapshot.

[Marianne]

You need vxms log on the backup host to troubleshoot status 23.
See: https://www.veritas.com/support/en_US/doc/123860515-126796677-0/v23649764-126796677

[Lowell_Palecek]

Good point. Status 23 is socket read failed in other parts of NetBackup. However, the message, "Error opening the snapshot disks using given transport mode," comes from VxMS. Use @Marianne's link to configure VxMS logging on the backup host.

The NetBackup version matters for VxMS. This topic is tagged 7.7. Is that true?

[Tape_Archived]

Are these 27 VM's added to backup policy using query or manually?? If you have added manually, if they are added most of the time we are not aware be VMAdmin has done any changes in the back end which may result in failure.

Please check the status of VM's in vcenter (GUI) and messages logged for each of these VMs.

It's also possible the 4 VM's are hosted on same ESX host and that host may have some issue connecting the backup/media server.

[Marianne]

@lovy1

Have you managed to make any progress here?

[lovy1]

VM's added using query. I am checking with respective team to get info. if VM's are hosting to same ESXi or different.

[lovy1]

Actually I don't have access to client and VC and we entirely depend on App owner for the troubleshooting and i have asked all the questions recommend in prev. chat and waiting on App owner's response. Will share it.

[Michal_Mikulik1 · Accepted solution]

Hello,

when you browse for new virtual machines via NetBackup Policy (Client Tab\Select Manually\New..), you can see many VM-side attributes, including ESX server. No need to wait for VMware team.

regards

Michal