Failed VMWare backups with Netbackup 7.5.0.4

[jpardus]

VMWare running VSphere 5.3 - Two ESX hosts and a Server 2008R2 box for the backups.  Every once in a while we can get back ups to work, but most of the time they fail.  Here's a log:

2/14/2014 2:00:41 PM - Info nbjm(pid=2832) starting backup job (jobid=283328) for client EPNSFS01, policy NewStantonGeneralBackup, schedule Weekly_Full 

2/14/2014 2:00:42 PM - estimated 433398997 Kbytes needed

2/14/2014 2:00:42 PM - Info nbjm(pid=2832) started backup (backupid=EPNSFS01_1392404434) job for client EPNSFS01, policy NewStantonGeneralBackup, schedule Weekly_Full on storage unit epnsbms02-hcart2-robot-tld-8

2/14/2014 2:00:49 PM - started process bpbrm (1076)

2/14/2014 2:00:51 PM - Info bpbrm(pid=1076) EPNSFS01 is the host to backup data from    

2/14/2014 2:00:51 PM - Info bpbrm(pid=1076) reading file list from client       

2/14/2014 2:00:51 PM - Info bpbrm(pid=1076) starting bpbkar32 on client        

2/14/2014 2:00:51 PM - connecting

2/14/2014 2:00:51 PM - connected; connect time: 00:00:00

2/14/2014 2:01:59 PM - Info bpbkar32(pid=5832) Backup started          

2/14/2014 2:01:59 PM - Info bptm(pid=3596) start           

2/14/2014 2:02:01 PM - Info bptm(pid=3596) using 65536 data buffer size       

2/14/2014 2:02:01 PM - Info bptm(pid=3596) setting receive network buffer to 263168 bytes     

2/14/2014 2:02:01 PM - Info bptm(pid=3596) using 30 data buffers        

2/14/2014 2:02:02 PM - Info bptm(pid=3596) start backup          

2/14/2014 2:02:02 PM - Info bptm(pid=3596) Waiting for mount of media id 225ADC (copy 1) on server epnsbms02.

2/14/2014 2:02:02 PM - mounting 225ADC

2/14/2014 2:02:48 PM - Info bptm(pid=3596) media id 225ADC mounted on drive index 0, drivepath {10,0,0,0}, drivename IBM.ULT3580-HH5.002, copy 1

2/14/2014 2:02:48 PM - mounted; mount time: 00:00:46

2/14/2014 2:02:48 PM - positioning 225ADC to file 5

2/14/2014 2:03:56 PM - positioned 225ADC; position time: 00:01:08

2/14/2014 2:03:56 PM - begin writing

2/14/2014 2:05:42 PM - Info bpbkar32(pid=5832) bpbkar waited 0 times for empty buffer, delayed 0 times.  

2/14/2014 2:05:50 PM - Error bpbrm(pid=1076) could not send server status message      

2/14/2014 2:05:50 PM - end writing; write time: 00:01:54

the backup failed to back up the requested files(6)

If I need anything more please let me know. 

[RamNagalla]

if you are referring about the Netbackup , VSphere 5.5 is not officallly supported yet..

if you are referring about Backup EXec, looks like only 

Backup Exec 2012 revision 1798 Service Pack 3 is supporting vspear 5.5

this forum is for netbackup, you may need to move this thread to backup EXce forum.

[jpardus]

Sorry, I am indeed running Netbackup 7.5.0.4

[RamNagalla]

so VSphere 5.5  is supported by netbackup yet..

Hopefully  Next release of netbackup would start VSphere 5.5  support.

[jpardus]

I misread my version, it's VSphere 5.3, not 5.5.  We were wanting to upgrade but we have  a few hosts we need to keep at 5.3 for now.

[RamNagalla]

are you sure its  VSphere 5.3?

as per my knowledge, the avaliable vertions in 5.X is 

5.0

5.1

5.5

only... 

[jpardus]

I just checked myself, so sorry for the comfusion.  It's ESXi 5.0.0, 1254542.

[RamNagalla]

Okay..

lets us know what is the policy type that is configured? Vmware?

what is the transport type that is being used? NBD or SAN?

what is the OS of backup host?

does backup host and media server is same or different?

what is the Vm hardware version for the failed VM?

[jpardus]

VMWare is the policy

Transport type is SAN.  There's a SAS connections being used.

Backup host is a separate physical Server 2008R2 server.

Backup host and media server are the same.

All VMs are VM Version 8.

[RamNagalla]

Okay..

sent the Verobse level in backup host to 5

make sure bpfis and bpbkar log directories are created in installpath\veritas\netbackup\logs

try the backup again and let it failed

attache the bpbkar and bpfis logs to this post.

if these logs does not give you much info , we also would require the vxms logs.

so take a look at below tech note to enable increaes the log level of the vxms logs and enable them before backup try

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

and attach the vxms logs to this post.

NOTE:- Do not forget the decreese the log level of VXms it will  it will create a huge files and fill up your C drive.

[Will_Restore]

NOTE:- Do not forget the decrease the log level of VXms it will create huge files and fill up your C drive.

Very important to do this after gathering logs.  Don't ask me how I know.

[jpardus]

Even before I started the logs, the drive on the backup server was almost full because of those logs... so now we're doing some testing to see if backups are working.  So far so good, I'll know here in a bit if backups were successful.

[Marianne]

What happened between initial failure and backups that seem to be running now?

We can only assume that backups are running now since you never came back... right?