cancel
Showing results for 
Search instead for 
Did you mean: 

Error opening the snapshot disks using given transport mode: Status 23

Hendrik1
Level 3

I have added a new "Virtual machine server" to my backup, I have chosen the clients, but when I run backup on them all of them is giving me this errors, I did put them also in the host file of my master server.

 

 

03/16/2016 15:05:39 - Info nbjm (pid=8428) starting backup job (jobid=340710) for client PRASAGPPPIS01, policy PRASA_VMWARE_VBlock_01, schedule MONTHLY
03/16/2016 15:05:39 - estimated 0 kbytes needed
03/16/2016 15:05:39 - Info nbjm (pid=8428) started backup (backupid=PRASAGPPPIS01_1458133539) job for client PRASAGPPPIS01, policy PRASA_VMWARE_VBlock_01, schedule MONTHLY on storage unit prasagppbck06_disk_stu
03/16/2016 15:05:40 - started process bpbrm (pid=10132)
03/16/2016 15:05:42 - Info bpbrm (pid=10132) PRASAGPPPIS01 is the host to backup data from
03/16/2016 15:05:42 - Info bpbrm (pid=10132) reading file list for client
03/16/2016 15:05:42 - Info bpbrm (pid=10132) starting bpbkar32 on client
03/16/2016 15:05:42 - connecting
03/16/2016 15:05:42 - connected; connect time: 0:00:00
03/16/2016 15:05:43 - Info bpbkar32 (pid=12280) Backup started
03/16/2016 15:05:43 - Info bpbkar32 (pid=12280) archive bit processing:<enabled>
03/16/2016 15:05:43 - Info bptm (pid=9972) start
03/16/2016 15:05:43 - Info bptm (pid=9972) using 1048576 data buffer size
03/16/2016 15:05:43 - Info bptm (pid=9972) setting receive network buffer to 4195328 bytes
03/16/2016 15:05:43 - Info bptm (pid=9972) using 512 data buffers
03/16/2016 15:05:43 - Info bptm (pid=9972) start backup
03/16/2016 15:05:50 - begin writing
03/16/2016 15:06:01 - Error bpbrm (pid=10132) from client PRASAGPPPIS01: ERR - Error opening the snapshot disks using given transport mode: Status 23
03/16/2016 15:06:02 - Info bptm (pid=9972) waited for full buffer 1 times, delayed 748 times
03/16/2016 15:06:02 - Info bpbkar32 (pid=12280) bpbkar waited 0 times for empty buffer, delayed 0 times.
03/16/2016 15:06:02 - Info bptm (pid=9972) EXITING with status 90 <----------
03/16/2016 15:06:06 - Info prasagppbck06.prasa.com (pid=9972) StorageServer=hp-StoreOnceCatalyst:prasagppd2d01.prasa.com; Report=scanned: 1024 KB, CR sent: 1024 KB, dedup: 15.92%
03/16/2016 15:06:06 - Error bpbrm (pid=10132) could not send server status message
03/16/2016 15:06:06 - Critical bpbrm (pid=10132) unexpected termination of client PRASAGPPPIS01
03/16/2016 15:06:06 - Error bpbrm (pid=10132) cannot send mail to hendrik@apx.co.za
03/16/2016 15:06:06 - end writing; write time: 0:00:16
03/16/2016 15:06:07 - Info bpbkar32 (pid=0) done. status: 6: the backup failed to back up the requested files
the backup failed to back up the requested files  (6)

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------

03/16/2016 15:05:25 - Info nbjm (pid=8428) starting backup job (jobid=340709) for client PRASAGPPPIS01, policy PRASA_VMWARE_VBlock_01, schedule MONTHLY
03/16/2016 15:05:25 - Info nbjm (pid=8428) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=340709, request id:{AB6F2FC1-5AC8-4800-A332-9CD83A2E0242})
03/16/2016 15:05:25 - requesting resource prasagppbck06_disk_stu
03/16/2016 15:05:25 - requesting resource prasagppbck01.prasa.com.NBU_CLIENT.MAXJOBS.PRASAGPPPIS01
03/16/2016 15:05:25 - requesting resource prasagppbck01.prasa.com.NBU_POLICY.MAXJOBS.PRASA_VMWARE_VBlock_01
03/16/2016 15:05:25 - granted resource  prasagppbck01.prasa.com.NBU_CLIENT.MAXJOBS.PRASAGPPPIS01
03/16/2016 15:05:25 - granted resource  prasagppbck01.prasa.com.NBU_POLICY.MAXJOBS.PRASA_VMWARE_VBlock_01
03/16/2016 15:05:25 - granted resource  MediaID=@aaaa9;DiskVolume=NBU_Store;DiskPool=prasagppbck06_hp_disk_pool;Path=NBU_Store;StorageServer=prasagppd2d01.prasa.com;MediaServer=prasagppbck06.prasa.com
03/16/2016 15:05:25 - granted resource  prasagppbck06_disk_stu
03/16/2016 15:05:25 - estimated 0 kbytes needed
03/16/2016 15:05:25 - begin Parent Job
03/16/2016 15:05:25 - begin VMware: Start Notify Script
03/16/2016 15:05:25 - Info RUNCMD (pid=7184) started
03/16/2016 15:05:25 - Info RUNCMD (pid=7184) exiting with status: 0
Operation Status: 0
03/16/2016 15:05:25 - end VMware: Start Notify Script; elapsed time 0:00:00
03/16/2016 15:05:25 - begin VMware: Step By Condition
Operation Status: 0
03/16/2016 15:05:25 - end VMware: Step By Condition; elapsed time 0:00:00
03/16/2016 15:05:25 - begin VMware: Read File List
Operation Status: 0
03/16/2016 15:05:25 - end VMware: Read File List; elapsed time 0:00:00
03/16/2016 15:05:25 - begin VMware: Create Snapshot
03/16/2016 15:05:27 - started process bpbrm (pid=10096)
03/16/2016 15:05:29 - Info bpbrm (pid=10096) PRASAGPPPIS01 is the host to backup data from
03/16/2016 15:05:29 - Info bpbrm (pid=10096) reading file list for client
03/16/2016 15:05:29 - Info bpbrm (pid=10096) start bpfis on client
03/16/2016 15:05:29 - Info bpbrm (pid=10096) Starting create snapshot processing
03/16/2016 15:05:30 - Info bpfis (pid=11812) Backup started
03/16/2016 15:05:30 - snapshot backup of client PRASAGPPPIS01 using method VMware_v2
03/16/2016 15:05:39 - end VMware: Create Snapshot; elapsed time 0:00:14
03/16/2016 15:05:39 - Info bpfis (pid=11812) done. status: 0
03/16/2016 15:05:39 - Info bpfis (pid=11812) done. status: 0: the requested operation was successfully completed
03/16/2016 15:05:39 - end writing
Operation Status: 0
03/16/2016 15:05:39 - end Parent Job; elapsed time 0:00:14
03/16/2016 15:05:39 - Info nbjm (pid=8428) snapshotid=PRASAGPPPIS01_1458133525
03/16/2016 15:05:39 - begin VMware: Policy Execution Manager Preprocessed
Operation Status: 6
03/16/2016 15:06:06 - end VMware: Policy Execution Manager Preprocessed; elapsed time 0:00:27
03/16/2016 15:06:06 - begin VMware: Stop On Error
Operation Status: 0
03/16/2016 15:06:06 - end VMware: Stop On Error; elapsed time 0:00:00
03/16/2016 15:06:06 - begin VMware: Delete Snapshot
03/16/2016 15:06:08 - started process bpbrm (pid=5988)
03/16/2016 15:06:09 - Info bpbrm (pid=5988) Starting delete snapshot processing
03/16/2016 15:06:12 - Info bpfis (pid=6444) Backup started
03/16/2016 15:06:20 - end writing
Operation Status: 0
Operation Status: 6
03/16/2016 15:06:21 - Info bpfis (pid=6444) done. status: 0
03/16/2016 15:06:21 - end VMware: Delete Snapshot; elapsed time 0:00:15
03/16/2016 15:06:21 - Info bpfis (pid=6444) done. status: 0: the requested operation was successfully completed
the backup failed to back up the requested files  (6)

 

 

 

 

 

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Mark_Solutions
Level 6
Partner Accredited Certified

This may well be a permissions issue ... make sure the account you are using has full rights as required for VMware backups: http://www.veritas.com/docs/000007351

It could also be a connection issue .. usually port 443 to the vcenter server (if that is what you added)

View solution in original post

6 REPLIES 6

vjuhola
Level 4
Partner

What transport mode are you trying to use? If you are trying use SAN, then the VMware backup host (media server) must see all the disks that the virtual machine is running on. Also have a look at snapshot limitations (this is for vSphere 5):

https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.vm_admin.doc_50%2FGUID-53F65726-A23B-4CF0-A7D5-48E584B88613.html

Hendrik1
Level 3

I am not using SAN

vjuhola
Level 4
Partner

Are you using raw disks? Snapshots are not supported for those. What size are the disks for the virtual machine and are they on VMFS3 or VMFS5 (that was upgraded from VMFS3)?

 

Feel free to share every bit of detail rather than just answering yes/no to questions.

Suchet_Siddu_J_
Level 3
Certified

Please refer below link and verify the accessibility of Datastore with VMWare host and configure the transport mode accordingly.

https://www.veritas.com/support/en_US/article.TECH183072

Michael_G_Ander
Level 6
Certified

I would check the ESX hosts can be reached from the master and media servers on port 902.

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Mark_Solutions
Level 6
Partner Accredited Certified

This may well be a permissions issue ... make sure the account you are using has full rights as required for VMware backups: http://www.veritas.com/docs/000007351

It could also be a connection issue .. usually port 443 to the vcenter server (if that is what you added)

View solution in original post