cancel
Showing results for 
Search instead for 
Did you mean: 

Using NetBackup 7 to backup VM from ESX

jeffwai
Level 2

I always get the following problem. How can I investigate the problem? Could you help me? Thank you very much!

06/05/2010 15:54:30 - connecting
06/05/2010 15:54:31 - connected; connect time: 00:00:01
06/05/2010 15:54:36 - begin writing
06/05/2010 15:54:47 - Error bpbrm(pid=6768) from client av2.xxxx.xx: ERR - Error opening the snapshot disks using given transport mode: Status 23.
06/05/2010 15:54:47 - Error bptm(pid=4768) socket operation failed - 10054 (at child.c.1294)     
06/05/2010 15:54:47 - Error bptm(pid=4768) unable to perform read from client socket, connection may have been broken
06/05/2010 15:54:48 - Error bpbrm(pid=6768) could not send server status message      
06/05/2010 15:54:51 - end writing; write time: 00:00:15
the backup failed to back up the requested files(6)

9 REPLIES 9

Andy_Welburn
Level 6
backup failures & this one is mentioned:

"...
■ If the VMware backup host cannot access the VMware datastore by means of the transfer type that was selected for the job, the backup fails.
Select a different transfer type and retry the backup.

The final status code for the failure depends on whether the backup uses VCB or vStorage, as follows.

■ For VCB backups: The backup fails with status 156 and the bpfis log on the backup host may contain messages such as the following:
12:23:29.998 [3892.3332] <2> onlfi_vfms_logf: [2008-05-07
12:23:26.279 'App' 3668 trivia] Attempting to open
LVID:46a9ed36-ca235c12-1236-00001a1a24e4/46a9ed35-aa804fd4-6b99
-00001a1a24e4/1.
12:23:29.998 [3892.3332] <2> onlfi_vfms_logf: [2008-05-07
12:23:26.279 'App' 3668 error] No path to device
LVID:46a9ed36-ca235c12-1236-00001a1a24e4/46a9ed35-aa804fd4-6b99
-00001a1a24e4/1 found.

■ For vStorage backups: The backup fails with status 6 and the job detailed status log on the backup host may contain messages such as the following:
12/4/2009 1:12:34 PM - Error bpbrm(pid=21376) from
client moneevm4_clone: ERR - Error opening the snapshot
disks using given transport mode: Status 23.

12/4/2009 1:12:39 PM - Error bpbrm(pid=21376) could not
send server status message
12/4/2009 1:12:40 PM - end writing; write time: 00:00:28
the backup failed to back up the requested files(6)
..."

So the suggestion is to try a different transfer type.

Also from the VM Admin Guide

"...
The transfer types determine how the snapshot data is sent from the VMware datastore to the VMware backup host. The appropriate option depends in part on the type of network that connects the VMware datastore to the VMware backup host.
..."

litefoot
Level 2
I have a support ticket in for this error msg will let you know the outcome.

jeffwai
Level 2
Thank you !

I'm using vCenter.  I can browe the VM host list in NBU7. Do we need to open firewall port for the ESX?

I selected "Try all type" already.

litefoot
Level 2
Don't think it would be a ESX  firewall issue as your connecting on the 443 port of vCenter, more likely the local firewall/AV on the server the is  issue. 


apa-it
Level 2

anoyone got a solution for this problem, we have exactly the same problem here. I´m having a support call in line ,but they trying to point me to vmware.

I also have a testing site running on the same server and the backup is running perfectly with the testing vsphere realm. same settings used on the production site and i´m getting the ": ERR - Error opening the snapshot
disks using given transport mode: Status 23."
error.

westy2010
Not applicable

Make sure that your media server/off-host backup server can see the datastore the VMs are on. eg. for an EMC SAN, you need to make sure that the datastore LUN that the VMs are on is in the storage group of the media server.

robin_miller
Not applicable

Did you get a resolution for this?  I am having the same issue.

J_H_Is_gone
Level 6

I don't do VMs yet but I am studing it.

I am told that you need 5% of free space for each of the servers that is being backed up.

So if you have 50 vm's but only backup 5 at a time you only need free space to the amount of 5% of the servers currently being backed up.

So check the ESX and see if you have enough free space for the snapshot.

apa-it
Level 2

hi,

the solution to this problem was an Vmware issue. The disktype modi of the VM has NOT to be set to independent.