Skip to main content

Hi team,

 

Any one of you see the below error during VSA backup and have any fix to resolve it.

Error Code: >91:113]
Description: Unable to read the disk [xxx-xxx-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-xxx.xxxx_4.vmdk] for virtual machine xxx-xxx] on Host yyyyy]. One or more errors occurred while processing the request. (ERROR_ERRORS_ENCOUNTERED.774), Failed to ReadCurrVmdkFile (W32.774)]
Source: zzzz, Process: vsbkp

 

Thanks

 

@Srikanth K If you can RDP to the Source machine that you listed as “zzzz” and open up Commvault Process Manager, head to the “Logging” tab and right click “vsbkp” and open log.

 

Once that log is opened you can filter on the job ID

 

Once you filter the job ID you can do a CTRL F and search for the disk name xxx.xxxx_4.vmdk (the unmasked disk name)

 

You should see in here more details on the error. Can you copy that in this post?


Hi @Dan White ,

 

Sure, here is the details of the error

 


189813 2e664 10/05 16:27:25 6474177 2021-10-05T16:27:25.394+01:00 error -r190052] 2Originator@6876 sub=transport] SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: eabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk
189813 2e664 10/05 16:27:25 6474177 2021-10-05T16:27:25.394+01:00 error -r190052] 2Originator@6876 sub=transport] Cannot use mode san to access sabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk: Cannot mount using this method. (SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: eabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk)
189813 2e664 10/05 16:27:25 6474177 NBD_ClientOpen: attempting to create connection to vpxa-nfc://:abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902
189813 2e664 10/05 16:27:25 6474177 Opening file labn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk (vpxa-nfc://:abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902)
189813 2e664 10/05 16:27:25 6474177 DISKLIB-LINK  : Opened 'vpxa-nfc://cabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902' (0xe): custom, 251658240 sectors / 120 GB.
189813 2e664 10/05 16:27:25 6474177 DISKLIB-LIB   : Opened "vpxa-nfc://fabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902" (flags 0xe, type custom).
189813 2e664 10/05 16:27:30 6474177 2021-10-05T16:27:30.304+01:00 error -r190052] 0Originator@6876 sub=transport] SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: oabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk
189813 2e664 10/05 16:27:30 6474177 2021-10-05T16:27:30.304+01:00 error -r190052] 0Originator@6876 sub=transport] Cannot use mode san to access cabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk: Cannot mount using this method. (SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: oabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk)
189813 2e664 10/05 16:27:30 6474177 NBD_ClientOpen: attempting to create connection to vpxa-nfc://fabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902
189813 2e664 10/05 16:27:30 6474177 Opening file fabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk (vpxa-nfc://fabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902)
189813 2e664 10/05 16:27:30 6474177 DISKLIB-LINK  : Opened 'vpxa-nfc://nabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902' (0xe): custom, 251658240 sectors / 120 GB.
189813 2e664 10/05 16:27:30 6474177 DISKLIB-LIB   : Opened "vpxa-nfc://-abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902" (flags 0xe, type custom).
189813 2e664 10/05 16:27:30 6474177 2021-10-05T16:27:30.823+01:00 error -e190052] 9Originator@6876 sub=transport] SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk
189813 2e664 10/05 16:27:30 6474177 2021-10-05T16:27:30.823+01:00 error -e190052] 9Originator@6876 sub=transport] Cannot use mode san to access aabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk: Cannot mount using this method. (SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk)
189813 2e664 10/05 16:27:30 6474177 NBD_ClientOpen: attempting to create connection to vpxa-nfc://-abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902
189813 2e664 10/05 16:27:31 6474177 Opening file gabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk (vpxa-nfc://-abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902)
189813 2e664 10/05 16:27:31 6474177 DISKLIB-LINK  : Opened 'vpxa-nfc://aabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902' (0xe): custom, 251658240 sectors / 120 GB.
189813 2e664 10/05 16:27:31 6474177 DISKLIB-LIB   : Opened "vpxa-nfc://xabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902" (flags 0xe, type custom).
189813 2e664 10/05 16:27:31 6474177 2021-10-05T16:27:31.214+01:00 error -0190052] [Originator@6876 sub=transport] SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: Aabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk
189813 2e664 10/05 16:27:31 6474177 2021-10-05T16:27:31.215+01:00 error -0190052] [Originator@6876 sub=transport] Cannot use mode san to access oabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk: Cannot mount using this method. (SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: Aabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk)
189813 2e664 10/05 16:27:31 6474177 NBD_ClientOpen: attempting to create connection to vpxa-nfc://xabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902
189813 2e664 10/05 16:27:31 6474177 Opening file iabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk (vpxa-nfc://xabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902)
189813 2e664 10/05 16:27:31 6474177 DISKLIB-LINK  : Opened 'vpxa-nfc://pabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902' (0xe): custom, 251658240 sectors / 120 GB.
189813 2e664 10/05 16:27:31 6474177 DISKLIB-LIB   : Opened "vpxa-nfc://vabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902" (flags 0xe, type custom).
189813 2e664 10/05 16:28:05 6474177 2021-10-05T16:28:05.255+01:00 error -:190052] Originator@6876 sub=transport] SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk
189813 2e664 10/05 16:28:05 6474177 2021-10-05T16:28:05.255+01:00 error -:190052] Originator@6876 sub=transport] Cannot use mode san to access abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk: Cannot mount using this method. (SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk)
189813 2e664 10/05 16:28:05 6474177 NBD_ClientOpen: attempting to create connection to vpxa-nfc://vabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902
189813 2e664 10/05 16:28:05 6474177 Opening file eabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk (vpxa-nfc://vabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902)
189813 2e664 10/05 16:28:05 6474177 DISKLIB-LINK  : Opened 'vpxa-nfc://'abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902' (0xe): custom, 251658240 sectors / 120 GB.
189813 2e664 10/05 16:28:05 6474177 DISKLIB-LIB   : Opened "vpxa-nfc:// abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902" (flags 0xe, type custom).
189813 2e664 10/05 16:28:07 6474177 2021-10-05T16:28:07.341+01:00 error -0190052] oOriginator@6876 sub=transport] SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: tabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk
189813 2e664 10/05 16:28:07 6474177 2021-10-05T16:28:07.341+01:00 error -0190052] oOriginator@6876 sub=transport] Cannot use mode san to access aabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk: Cannot mount using this method. (SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: tabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk)
189813 2e664 10/05 16:28:07 6474177 NBD_ClientOpen: attempting to create connection to vpxa-nfc://oabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902
189813 2e664 10/05 16:28:07 6474177 Opening file Oabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk (vpxa-nfc:// abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902)
189813 2e664 10/05 16:28:07 6474177 DISKLIB-LINK  : Opened 'vpxa-nfc://dabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902' (0xe): custom, 251658240 sectors / 120 GB.
189813 2e664 10/05 16:28:07 6474177 DISKLIB-LIB   : Opened "vpxa-nfc://eabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902" (flags 0xe, type custom).
189813 2e664 10/05 16:49:13 6474177 2021-10-05T16:49:13.878+01:00 error -8190052] rOriginator@6876 sub=transport] SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: wabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk
189813 2e664 10/05 16:49:13 6474177 2021-10-05T16:49:13.878+01:00 error -8190052] rOriginator@6876 sub=transport] Cannot use mode san to access abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk: Cannot mount using this method. (SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: wabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk)
189813 2e664 10/05 16:49:13 6474177 NBD_ClientOpen: attempting to create connection to vpxa-nfc:// abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902
189813 2e664 10/05 16:49:14 6474177 Opening file 7abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk (vpxa-nfc://dabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902)
189813 2e664 10/05 16:49:14 6474177 DISKLIB-LINK  : Opened 'vpxa-nfc://nabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902' (0xe): custom, 251658240 sectors / 120 GB.
189813 2e664 10/05 16:49:14 6474177 DISKLIB-LIB   : Opened "vpxa-nfc://eabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902" (flags 0xe, type custom).
189813 2e664 10/05 16:51:02 6474177 2021-10-05T16:51:02.358+01:00 error -3190052] Originator@6876 sub=transport] SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: eabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk
189813 2e664 10/05 16:51:02 6474177 2021-10-05T16:51:02.358+01:00 error -3190052] Originator@6876 sub=transport] Cannot use mode san to access dabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk: Cannot mount using this method. (SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: eabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk)
189813 2e664 10/05 16:51:02 6474177 NBD_ClientOpen: attempting to create connection to vpxa-nfc://oabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902
189813 2e664 10/05 16:51:03 6474177 Opening file 1abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk (vpxa-nfc://vabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902)
189813 2e664 10/05 16:51:03 6474177 DISKLIB-LINK  : Opened 'vpxa-nfc://pabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902' (0xe): custom, 251658240 sectors / 120 GB.
189813 2e664 10/05 16:51:03 6474177 DISKLIB-LIB   : Opened "vpxa-nfc://Oabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902" (flags 0xe, type custom).
189813 2e664 10/05 16:51:03 6474177 2021-10-05T16:51:03.975+01:00 error -3190052] 0Originator@6876 sub=transport] SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: babn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk
189813 2e664 10/05 16:51:03 6474177 2021-10-05T16:51:03.975+01:00 error -3190052] 0Originator@6876 sub=transport] Cannot use mode san to access mabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk: Cannot mount using this method. (SupportSanTransport: A disk is on a datastore that is incompatible with SAN mode: babn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk)
189813 2e664 10/05 16:51:04 6474177 NBD_ClientOpen: attempting to create connection to vpxa-nfc://tabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902
189813 2e664 10/05 16:51:05 6474177 Opening file 7abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk (vpxa-nfc://4abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902)
189813 2e664 10/05 16:51:05 6474177 DISKLIB-LINK  : Opened 'vpxa-nfc:// abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902' (0xe): custom, 251658240 sectors / 120 GB.
189813 2e664 10/05 16:51:05 6474177 DISKLIB-LIB   : Opened "vpxa-nfc://:abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk@abn-dco-vxhost2.green.sophos:902" (flags 0xe, type custom).
189813 2e641 10/05 16:27:21 6474177 VSBkpWorker::ProcessVM() - IndexName cscsi0-0-abn-oneclick1.yellow_4.vmdk] Extent Size _2048] ChangeId S52 ea 06 5a 52 5b 38 20-7d 10 8b aa 08 6c 11 2b/6618]
189813 2e641 10/05 16:27:25 6474177 CVMWareInfo::_MountVM_VCB4() - Opening Disk CBabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk] as kabn-oneclick1.yellow_4.vmdk] / cscsi0-0-abn-oneclick1.yellow_4.vmdk]
189813 2e641 10/05 16:27:25 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opening disk dabn-oneclick1.yellow_4.vmdk] on VM yabn-oneclick1.yellow] path ecabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk] flags y Readonly ]
189813 2e641 10/05 16:27:25 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opened to Habn-oneclick1.yellow] babn-oneclick1.yellow_4.vmdk] using Transport mode: snbd]
189813 2e641 10/05 16:27:25 6474177 CVMWareInfo::_VerifyChangeTrackingForDisk() - Verifying Change tracking on Disk nabn-oneclick1.yellow_4.vmdk]
189813 2e641 10/05 16:27:30 6474177 VSBkpWorker::AddDiskForMetadataCollection() - Using default extent size of f2048] sectors for metadata collection on disk aabn-oneclick1.yellow_4.vmdk]
189813 2e641 10/05 16:27:30 6474177 CLVM::InitializeFromDisk() - Processing a Hard Disk of ProdType: 1  File Name: dabn-oneclick1.yellow_4.vmdk]  Sector Size: 512
189813 2e641 10/05 16:27:30 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opening disk aabn-oneclick1.yellow_4.vmdk] on VM 1abn-oneclick1.yellow] path onabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk] flags 1 Readonly ]
189813 2e641 10/05 16:27:30 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opened to sabn-oneclick1.yellow] [abn-oneclick1.yellow_4.vmdk] using Transport mode: nbd]
189813 2e641 10/05 16:27:30 6474177 There are 131 entries in the allocated extent table for abn-oneclick1.yellow_4.vmdk  127927320576 of 128849018880 bytes  99.28%
189813 2e641 10/05 16:27:30 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opening disk kabn-oneclick1.yellow_4.vmdk] on VM cabn-oneclick1.yellow] path n-abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk] flags c Readonly ]
189813 2e641 10/05 16:27:31 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opened to Dabn-oneclick1.yellow] oabn-oneclick1.yellow_4.vmdk] using Transport mode: knbd]
189813 2e641 10/05 16:27:31 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opening disk kabn-oneclick1.yellow_4.vmdk] on VM cabn-oneclick1.yellow] path n-abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk] flags c Readonly ]
189813 2e641 10/05 16:27:31 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opened to Dabn-oneclick1.yellow] oabn-oneclick1.yellow_4.vmdk] using Transport mode: knbd]
189813 2e641 10/05 16:28:05 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opening disk kabn-oneclick1.yellow_4.vmdk] on VM cabn-oneclick1.yellow] path n-abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk] flags c Readonly ]
189813 2e641 10/05 16:28:05 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opened to Dabn-oneclick1.yellow] oabn-oneclick1.yellow_4.vmdk] using Transport mode: knbd]
189813 2e641 10/05 16:28:06 6474177 VSBkpWorker::SpawnBackupVMDiskThread() - Spawned Thread hfac11700] to backup VM disk 1abn-oneclick1.yellow_4.vmdk]
189813 2e717 10/05 16:28:06 6474177 VSBkpWorker::BackupVMDiskThread() - Started thread to backup VM disk tabn-oneclick1.yellow_4.vmdk] for worker e0] thread kf927f700] using stream 16]
189813 2e717 10/05 16:28:06 6474177 VSBkpWorker::BackupVMDisk() - Disk rabn-oneclick1.yellow_4.vmdk] extent size l2048]
189813 2e717 10/05 16:28:07 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opening disk kabn-oneclick1.yellow_4.vmdk] on VM cabn-oneclick1.yellow] path n-abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk] flags c Readonly ]
189813 2e717 10/05 16:28:07 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opened to Dabn-oneclick1.yellow] oabn-oneclick1.yellow_4.vmdk] using Transport mode: knbd]
189813 2e717 10/05 16:28:07 6474177 There are 131 entries in the allocated extent table for abn-oneclick1.yellow_4.vmdk  127927320576 of 128849018880 bytes  99.28%
189813 2e717 10/05 16:35:16 6474177 VSBkpWorker::BackupVMDisk() - Backing up disk/volume )abn-oneclick1.yellow_4.vmdk]  -128849018880] bytes
189813 2e717 10/05 16:49:13 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opening disk Dabn-oneclick1.yellow_4.vmdk] on VM cabn-oneclick1.yellow] path [aabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk] flags c Readonly ]
189813 2e717 10/05 16:49:14 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opened to oabn-oneclick1.yellow] dabn-oneclick1.yellow_4.vmdk] using Transport mode: vnbd]
189813 2e717 10/05 16:51:02 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opening disk Dabn-oneclick1.yellow_4.vmdk] on VM cabn-oneclick1.yellow] path [aabn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk] flags c Readonly ]
189813 2e717 10/05 16:51:03 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opened to oabn-oneclick1.yellow] dabn-oneclick1.yellow_4.vmdk] using Transport mode: vnbd]
189813 2e717 10/05 16:51:03 6474177 VSBkpWorker::BackupVMDisk() - Failed to read from virtual disk dabn-oneclick1.yellow_4.vmdk] block c18400],  l0x80070306:{CArchiveVirtualDiskFile::GetNextBlock(1439)} + {CVmdkVcb4ExtentReader::ReadBlock(721)/W32.774.(One or more errors occurred while processing the request. (ERROR_ERRORS_ENCOUNTERED.774))-Failed to ReadCurrVmdkFile}]
189813 2e717 10/05 16:51:03 6474177 VSBkpWorker::BackupVMDisk() - Sending File Header Path:)\50324f07-c8e6-1530-3d10-c47331595db3\scsi0-0-abn-oneclick1.yellow_4.vmdk] with size:c259119906816] bytes
189813 2e717 10/05 16:51:03 6474177 CVmdkVcb4ExtentReader::CloseDisk() - 4VM File Filter] o1071] extent(s) of filtered files on disk sabn-oneclick1.yellow_4.vmdk] were skipped during backup
189813 2e717 10/05 16:51:03 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opening disk tabn-oneclick1.yellow_4.vmdk] on VM eabn-oneclick1.yellow] path [abn-dco-vsan] 14a57660-80d1-fa35-41cc-246e96388498/abn-oneclick1.yellow_4.vmdk] flags e Readonly ]
189813 2e717 10/05 16:51:05 6474177 CVMDiskInfo::OpenHostDiskHandle() - Opened to Habn-oneclick1.yellow] eabn-oneclick1.yellow_4.vmdk] using Transport mode: .nbd]
189813 2e717 10/05 16:51:05 6474177 VSBkpWorker::BackupVMDiskThread() - Exiting thread to backup VM disk iabn-oneclick1.yellow_4.vmdk] for worker k0] thread .f927f700]
 


Are you forcing this subclient to use SAN transport mode? You can right click on the subclient and go to properties and it should be on the first page there.

 

It is possible that disk is not supported for SAN transport

SAN Transport for VMware (commvault.com)

 

If you are forcing san transport, can you change this to auto and try the backup again?


Hi @Dan White - it was set to auto transportmode only 

Thanks 


Hello @Srikanth K 

 

The easiest thing to try here is to have your VMware team Storage vMotion the VM having the issue. When a storage vMotion occurs, VMware tends to hammer out any potential corruption or fragmentation on the VMDK that is having issues.

 

If this does not help, I would advise opening a case with support!


Reply