Vmware Block level incremental backup

[Abhisheknetback]

Hi Friends,

I want to conform one thing we have configured vmware blocak level incremental backup in netbackup , there is many clients added in the same policy but

some time i experince that backup keeps on failling for single client from this policy with error code 6 .

what do i do for troubleshooting remove the block level incremental check box from policy and run the backup manually , and it success .

any idea ???

failed job details .

8/12/2014 6:02:38 PM - Info nbjm(pid=8568) starting backup job (jobid=625056) for client CO, policy VMWARE_VM_V_GROUPA_CBT_PRD, schedule DAILY-INCR  
8/12/2014 6:02:52 PM - estimated 53279775 Kbytes needed
8/12/2014 6:02:52 PM - Info nbjm(pid=8568) started backup (backupid=COS_1407852172) job for client CO, policy VMWARE_VM_V_GROUPA_CBT_PRD, schedule DAILY-INCR on storage unit med_h_stu1
8/12/2014 6:02:54 PM - started process bpbrm (9756)
8/12/2014 6:03:02 PM - Info bpbrm(pid=9756) CO is the host to backup data from     
8/12/2014 6:03:02 PM - Info bpbrm(pid=9756) reading file list from client        
8/12/2014 6:03:02 PM - connecting
8/12/2014 6:03:03 PM - Info bpbrm(pid=9756) starting bpbkar32 on client         
8/12/2014 6:03:03 PM - connected; connect time: 00:00:01
8/12/2014 6:03:05 PM - Info bpbkar32(pid=12588) Backup started           
8/12/2014 6:03:05 PM - Info bptm(pid=8460) start            
8/12/2014 6:03:05 PM - Info bptm(pid=8460) using 524288 data buffer size        
8/12/2014 6:03:05 PM - Info bptm(pid=8460) setting receive network buffer to 2098176 bytes      
8/12/2014 6:03:05 PM - Info bptm(pid=8460) using 256 data buffers         
8/12/2014 6:03:06 PM - Info bpbkar32(pid=12588) CONTINUE BACKUP received.          
8/12/2014 6:03:09 PM - Info bptm(pid=8460) start backup           
8/12/2014 6:03:11 PM - Info bptm(pid=8460) backup child process is pid 11200.4016       
8/12/2014 6:03:11 PM - Info bptm(pid=11200) start            
8/12/2014 6:03:11 PM - begin writing
8/12/2014 6:52:44 PM - Error bptm(pid=11200) socket operation failed - 10054 (at child.c.1296)      
8/12/2014 6:52:44 PM - Error bptm(pid=11200) unable to perform read from client socket, connection may have been broken
8/12/2014 6:52:52 PM - Error bpbrm(pid=9756) could not send server status message       
8/12/2014 6:52:54 PM - Critical bpbrm(pid=9756) unexpected termination of client CO     
8/12/2014 6:52:55 PM - Error bpbrm(pid=9756) cannot send mail to ,ab       
8/12/2014 6:52:56 PM - end writing; write time: 00:49:45

Thank You

[Marianne]

This looks like a timeout:

8/12/2014 6:03:11 PM - begin writing
8/12/2014 6:52:44 PM - Error bptm(pid=11200) socket operation failed - 10054 (at child.c.1296)      

No data was received in the period specified in Client Read Timeout on the media server.

As a start, create bpbkar log folder on the backup host and bpbrm and bptm log folders on the media server.

Copy logs to .txt files (e.g. bptm.txt) after the next failure and post here as File attachments.

[Abhisheknetback]

Hi Marianne,

Without Block level incremental backup sucess after that againg revert the setting back and ran the backup it failed .

find the log as you requested .

Thank You

[Dollypee]

Hi, Have you checked that you are running on supported platforms? Please see below link, page 77 http://clientui-kb.symantec.com/resources/sites/BUSINESS/content/live/DOCUMENTATION/6000/DOC6461/en_...

 - BLIB require mininmum ESX 4.x version

- Virtual machine hard ware minimum : vmx-07

Please confirm these two for a start. Thank you

[Anonymous · Accepted solution]

In addition to @Dolly reference here is the KB from VMware with further requirements and settings to check in the VM config itself for incremental backups.

Confirm the disks are set to allow change block tracking they may not be set.

Further, Virtual machine storage must not be (persistent or non-persistent) independent disk, meaning unaffected by snapshots.

VMware KB: Changed Block Tracking (CBT) on virtual machines
http://kb.vmware.com/kb/1020128

[Mark_Solutions · Accepted solution]

As Marianne says this is a timeout issue when you run the jobs with BLIB selected... this means that there is a process taking a long time to gather the required data for the BLIB part.

Look to your VMware setup for more clues .. usually thing sget logged in vCenter these days .. and you can also check the state / size of the change block tracking logs etc. in case your system is struggling to cope with having CBT enabled and used.