Forum Discussion

Baleka_VG's avatar
Baleka_VG
Level 3
11 years ago

VMWare backup failing- Error code 6

Morning all,

 

I need some assistance with an issue I found this mornign on one of my VM's.

 

The backup is failing with the error code 6. backup server is 2008 R2 Standard 64bit.

 

Below is the error message on the backup:

2014/03/17 09:57:36 - Info nbjm(pid=6336) starting backup job (jobid=418958) for client clientname, policy VM_Weekly_Client, schedule Weekly_Full  
2014/03/17 09:57:36 - estimated 0 Kbytes needed
2014/03/17 09:57:36 - Info nbjm(pid=6336) started backup (backupid=clientname_1395043056) job for client clientname, policy VM_Weekly_Client, schedule Weekly_Full on storage unit MSL6000_
2014/03/17 09:57:37 - Info bpbrm(pid=9292) clientname is the host to backup data from     
2014/03/17 09:57:37 - Info bpbrm(pid=9292) reading file list from client        
2014/03/17 09:57:37 - Info bpbrm(pid=9292) starting bpbkar32 on client         
2014/03/17 09:57:37 - started process bpbrm (9292)
2014/03/17 09:57:37 - connecting
2014/03/17 09:57:37 - connected; connect time: 00:00:00
2014/03/17 09:57:39 - Info bpbkar32(pid=12344) Backup started           
2014/03/17 09:57:39 - Info bptm(pid=11548) start            
2014/03/17 09:57:39 - Info bptm(pid=11548) using 262144 data buffer size        
2014/03/17 09:57:39 - Info bptm(pid=11548) setting receive network buffer to 1049600 bytes      
2014/03/17 09:57:39 - Info bptm(pid=11548) using 64 data buffers         
2014/03/17 09:57:39 - Info bptm(pid=11548) start backup           
2014/03/17 09:57:39 - Info bptm(pid=11548) Waiting for mount of media id 1618L4 (copy 1) on server backupserver. 
2014/03/17 09:57:39 - mounting 1618L4
2014/03/17 09:57:46 - Error bpbrm(pid=9292) from client clientname: ERR - Error opening the snapshot disks using given transport mode: Status 23
2014/03/17 09:57:47 - Info bpbkar32(pid=12344) bpbkar waited 0 times for empty buffer, delayed 0 times.   
2014/03/17 09:57:51 - Error bpbrm(pid=9292) could not send server status message       
2014/03/17 09:57:51 - Critical bpbrm(pid=9292) unexpected termination of client clientname        
2014/03/17 09:57:52 - Info bpbkar32(pid=0) done. status: 6: the backup failed to back up the requested files 
2014/03/17 09:57:52 - end writing
the backup failed to back up the requested files(6)
 
I've had the VMWare tools updated and the issue is still there, there are 6 more VM's on the policy with are backing up succesfully. this issue only started happening this weekend. The VM is scheduled to be rebooted later today and further more testing will be conducted.
 
Any light to the matter?

 

  • Hi All,

     

    Thank you for the prompt feedback. It seems the issue was that LUN's were not presented on the server. I've got the Storage Team currently looking into this. I actually saw this on one of the previous posts.

    It seems like LUN’s are not presented on server clientname or user “backupuser\_svc_vcenter” does not have access to LUN

     

    I've got the teams lokoing into this currently.

  • Hi

     

    Please answer the following questions and try the following points for analysis:

    • IS this your first vmware policy?
    • What transport method are you trying hotaddSAN/http/https?
    • Try to force the poliry to backup using nbsl, tell us what happens.
    • Send us the bpvmutil log to look at[on the media server].
    • Does the 'hostname'[not display name] in ESX match the dns name you use to back it up?
    • You should also use the VMWARE policy type in 7.5.0.6 and not Windows-Flashback anymore.
    • What is the VMware hardware version of the host should be 7 or above?
  • Hi All,

     

    Thank you for the prompt feedback. It seems the issue was that LUN's were not presented on the server. I've got the Storage Team currently looking into this. I actually saw this on one of the previous posts.

    It seems like LUN’s are not presented on server clientname or user “backupuser\_svc_vcenter” does not have access to LUN

     

    I've got the teams lokoing into this currently.

  • HI Baleka

    This is mostlikely the case if you're using SAN as a backup transfer method. In the mean while you should be able to back it up using nbsl while they sort out the san. This will take a lot longer and will use the vKernel port for the transfer.

    Please remember to mark a solution once you found the problem.