Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

vmware backup failed using san transport mode

Created: 26 Aug 2013 • Updated: 09 Nov 2013 | 4 comments
This issue has been solved. See solution.

When i backup the vmware (vsphere 5.0) using san transport mode,i had get any errors,but in the same lun,other virtual machines backup successfull.

This is backup detailed status:

2013-8-27 10:11:02 - Info nbjm (pid=5726) starting backup job (jobid=8208) for client 154.7.160.69RDP, policy vm_test, schedule Full_Backup
2013-8-27 10:11:03 - Info bpbrm (pid=9850) 154.7.160.69RDP is the host to backup data from
2013-8-27 10:11:03 - Info bpbrm (pid=9850) reading file list from client
2013-8-27 10:11:03 - estimated 0 kbytes needed
2013-8-27 10:11:03 - Info nbjm (pid=5726) started backup (backupid=154.7.160.69RDP_1377569462) job for client 154.7.160.69RDP, policy vm_test, schedule Full_Backup on storage unit stu_disk_nbu5220
2013-8-27 10:11:03 - started process bpbrm (pid=9850)
2013-8-27 10:11:03 - connecting
2013-8-27 10:11:04 - Info bpbrm (pid=9850) starting bpbkar on client
2013-8-27 10:11:04 - Info bpbkar (pid=9865) Backup started
2013-8-27 10:11:04 - Info bpbrm (pid=9850) bptm pid: 9866
2013-8-27 10:11:04 - Info bptm (pid=9866) start
2013-8-27 10:11:04 - Info bptm (pid=9866) using 262144 data buffer size
2013-8-27 10:11:04 - Info bptm (pid=9866) using 30 data buffers
2013-8-27 10:11:04 - connected; connect time: 0:00:00
2013-8-27 10:11:05 - Info bptm (pid=9866) start backup
2013-8-27 10:11:05 - begin writing
2013-8-27 10:11:10 - Error bpbrm (pid=9850) from client 154.7.160.69RDP: ERR - Error opening the snapshot disks using given transport mode: Status 23
2013-8-27 10:11:13 - Error bptm (pid=9866) media manager terminated by parent process
2013-8-27 10:11:18 - Info nbu5220 (pid=9866) StorageServer=PureDisk:nbu5220; Report=PDDO Stats for (nbu5220): scanned: 2 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%
2013-8-27 10:11:18 - Info bpbkar (pid=0) done. status: 6: the backup failed to back up the requested files
2013-8-27 10:11:18 - end writing; write time: 0:00:13
the backup failed to back up the requested files (6)

This is snapshot detailed status:

2013-8-27 10:10:37 - Info nbjm (pid=5726) starting backup job (jobid=8207) for client 154.7.160.69RDP, policy vm_test, schedule Full_Backup
2013-8-27 10:10:37 - Info nbjm (pid=5726) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=8207, request id:{DD5FFB34-0EBD-11E3-9902-B4339D446385})
2013-8-27 10:10:37 - requesting resource stu_disk_nbu5220
2013-8-27 10:10:37 - requesting resource nbu5220.NBU_CLIENT.MAXJOBS.154.7.160.69RDP
2013-8-27 10:10:37 - requesting resource nbu5220.NBU_POLICY.MAXJOBS.vm_test
2013-8-27 10:10:38 - granted resource nbu5220.NBU_CLIENT.MAXJOBS.154.7.160.69RDP
2013-8-27 10:10:38 - granted resource nbu5220.NBU_POLICY.MAXJOBS.vm_test
2013-8-27 10:10:38 - granted resource MediaID=@aaaac;DiskVolume=PureDiskVolume;DiskPool=dp_disk_nbu5220;Path=PureDiskVolume;StorageServer=nbu5220;MediaServer=nbu5220
2013-8-27 10:10:38 - granted resource stu_disk_nbu5220
2013-8-27 10:10:38 - estimated 0 kbytes needed
2013-8-27 10:10:38 - begin Parent Job
2013-8-27 10:10:38 - begin VMware: Start Notify Script
2013-8-27 10:10:38 - Info RUNCMD (pid=9790) started
2013-8-27 10:10:38 - Info RUNCMD (pid=9790) exiting with status: 0
Operation Status: 0
2013-8-27 10:10:38 - end VMware: Start Notify Script; elapsed time 0:00:00
2013-8-27 10:10:38 - begin VMware: Step By Condition
Operation Status: 0
2013-8-27 10:10:38 - end VMware: Step By Condition; elapsed time 0:00:00
2013-8-27 10:10:38 - begin VMware: Read File List
Operation Status: 0
2013-8-27 10:10:38 - end VMware: Read File List; elapsed time 0:00:00
2013-8-27 10:10:38 - begin VMware: Create Snapshot
2013-8-27 10:10:38 - started process bpbrm (pid=9799)
2013-8-27 10:10:39 - Info bpbrm (pid=9799) 154.7.160.69RDP is the host to backup data from
2013-8-27 10:10:39 - Info bpbrm (pid=9799) reading file list from client
2013-8-27 10:10:39 - Info bpbrm (pid=9799) start bpfis on client
2013-8-27 10:10:39 - Info bpbrm (pid=9799) Starting create snapshot processing
2013-8-27 10:10:39 - Info bpfis (pid=9824) Backup started
2013-8-27 10:10:40 - snapshot backup of client 154.7.160.69RDP using method VMware_v2
2013-8-27 10:11:02 - Info bpfis (pid=9824) done. status: 0
2013-8-27 10:11:02 - end VMware: Create Snapshot; elapsed time 0:00:24
2013-8-27 10:11:02 - Info bpfis (pid=0) done. status: 0: the requested operation was successfully completed
2013-8-27 10:11:02 - end writing
Operation Status: 0
2013-8-27 10:11:02 - end Parent Job; elapsed time 0:00:24
2013-8-27 10:11:02 - begin VMware: Policy Execution Manager Preprocessed
2013-8-27 10:11:55 - end VMware: Policy Execution Manager Preprocessed; elapsed time 0:00:53
2013-8-27 10:11:55 - begin VMware: Stop On Error
Operation Status: 0
2013-8-27 10:11:55 - end VMware: Stop On Error; elapsed time 0:00:00
2013-8-27 10:11:55 - begin VMware: Delete Snapshot
2013-8-27 10:11:56 - Error bpbrm (pid=10004) bpcd on nbu5220 exited with status 21: socket open failed
2013-8-27 10:11:56 - Info (pid=0) done. status: 21: socket open failed
2013-8-27 10:11:56 - started process bpbrm (pid=10004)
2013-8-27 10:11:56 - end writing
Operation Status: 150
2013-8-27 10:11:56 - end VMware: Delete Snapshot; elapsed time 0:00:01
2013-8-27 10:11:56 - begin VMware: Stop On Error
Operation Status: 0
2013-8-27 10:11:56 - end VMware: Stop On Error; elapsed time 0:00:00
Operation Status: 150
2013-8-27 10:11:57 - Info bpbrm (pid=10045) Starting delete snapshot processing
2013-8-27 10:11:57 - Info bpfis (pid=0) Snapshot will not be deleted
2013-8-27 10:11:57 - Info bpfis (pid=10058) Backup started
Operation Status: 150
2013-8-27 10:12:05 - Info bpfis (pid=10058) done. status: 0
2013-8-27 10:12:05 - Info bpfis (pid=0) done. status: 0: the requested operation was successfully completed
2013-8-27 10:12:20 - Info bpbrm (pid=10182) Starting delete snapshot processing
2013-8-27 10:12:20 - Info bpfis (pid=0) Snapshot will not be deleted
2013-8-27 10:12:20 - Info bpfis (pid=10191) Backup started
2013-8-27 10:12:20 - Warning bpbrm (pid=10182) from client 154.7.160.69RDP: WRN - Stream vm_test+d9824+1 pid 10058 is not active.
2013-8-27 10:12:43 - Info bpfis (pid=10191) done. status: 0
2013-8-27 10:12:43 - Info bpfis (pid=0) done. status: 0: the requested operation was successfully completed
termination requested by administrator (150)

Operating Systems:

Comments 4 CommentsJump to latest comment

StefanosM's picture

2013-8-27 10:11:10 - Error bpbrm (pid=9850) from client 154.7.160.69RDP: ERR - Error opening the snapshot disks using given transport mode: Status 23

 

The most probable cause is that this LUN is not presented to the backup host.

The first think I would do is to check the zoning between the LUN and the backup server

zhuqingedu's picture

Thank you,but in the same lun,other virtual machines backup successfull.

StefanosM's picture

Then try to backup this VM with another method (nbd or hotadd) just to see if it is working.

Mark_Solutions's picture

Does that VM Client have all of its disks on the SAN LUNS? If any one of them are local to the ESX Server it will not work.

The vCenter credentials are the other thing that causes this but if all others work then i guess that is not the case.

I would check exactly where all vmdk's reside for the VM in question first - take a good look at it in vCenter to see what you can spot

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

SOLUTION