Skip to main content
Solved

VM restore with SAN transport failed with VDDK 7.0.0


Forum|alt.badge.img+9

Errors: 
24440 5afc 08/11 07:49:30 3944438 2021-08-11T07:49:30.915+02:00 error -[23292] [Originator@6876 sub=transport] Cannot use mode san to access [ESX_Restore] XYZXYZ-RestoreTest/XYZXYZ-RestoreTest.vmdk: Cannot mount using this method. (VixDiskLibCommon::Controller::DiskSpecImpl::SupportSanTransport: Cannot use san transport to write to the datastore (ESX_Restore) which is marked "clusteredVmdkSupported". ) 
24440 5afc 08/11 07:49:30 3944438 VixDiskLib: Unable to locate appropriate transport mode to open disk. Error 13 (You do not have access rights to this file) (VixDiskLibCommon::Controller::DiskSpecImpl::SupportSanTransport: Cannot use san transport to write to the datastore (ESX_Restore) which is marked "clusteredVmdkSupported". ) at 5613. 
24440 5afc 08/11 07:49:30 3944438 VixDiskLib: VixDiskLib_OpenEx: Cannot open disk [ESX_Restore] XYZXYZ-RestoreTest/XYZXYZ-RestoreTest.vmdk. Error 13 (You do not have access rights to this file) (VixDiskLibCommon::Controller::DiskSpecImpl::SupportSanTransport: Cannot use san transport to write to the datastore (ESX_Restore) which is marked "clusteredVmdkSupported". ) at 5769. 
24440 5afc 08/11 07:49:30 3944438 VDDK_PhoneHome: Invaild transport mode used at line 304 
24440 5afc 08/11 07:49:30 3944438 VixDiskLib: VixDiskLib_Open: Cannot open disk [ESX_Restore] XYZXYZ/XYZXYZ.vmdk. Error 13 (You do not have access rights to this file) at 5813. 
24440 5afc 08/11 07:49:30 3944438 VixDiskLib: VixDiskLib_Disconnect: Disconnect. 

Versions
- VMWare vCenter 7.0.2 
- Commvault V11.20.55. 

VDDK 7.0.0 is used for restore. On media agents in CommVault\Simpana\Base\VMWARE\VDDK directory I found version 7.0.0. 
This version has a problem with SAN transport restores. (https://kb.commvault.com/article/67381) 

In KB article VDDK 6.7.3 should be used, this is not possible becaue 7.0.0 is automatic used. 
23020 5530 08/11 07:49:43 3944438 CVMDiskInfo::GetVDDKInstallPath() - Using vStorage VDDK from [C:\Program Files\CommVault\Simpana\Base\VMware\VDDK\VDDK700] version [7.0.0 build-15832853] 

How can I force a VDDK version? 

And bug is fixed in VDDK 7.0.1. (https://vdc-download.vmware.com/vmwb-repository/dcr-public/91cc8936-cbd5-4f61-9a24-6b9b9e8cd63a/07ff0eec-8401-485e-bab3-5ca4db49905f/VDDK-701-ReleaseNotes.html) 

"SAN mode restore not supported for clustered VMDK. 
A datastore marked clusteredvmdk was no longer writable in VMFS6, due to SCSI reservations on the physical LUN, so restore did not proceed. Note that MSCS clustering works without clusteredvmdk. It is not required for backup. If users set Clustered VMDK to Enabled in vSphere Client > Configure > Datastore Capabilities, VDDK 6.7 hangs with a Windows proxy, or returns an error with a Linux proxy. VDDK 7.0 tried to fix the problem by rejecting SAN writes to that datastore, however 7.0 also rejects SAN writes with Disabled set. In 7.0.1, VDDK allows SAN writes with Disabled set." 

I would be able to download 7.0.2 manually and install (https://documentation.commvault.com/11.22/expert/32585_frequently_asked_questions_for_virtual_server_agent_with_vmware.html#b32591_how_do_i_manually_install_new_version_of_vddk_on_vsa_proxy).

Where can I find information which VDDK version is used in which service pack or hotfix pack? 

Best answer by Damian Andre

Dimitri wrote:

Solution to force other (older) VDDK version (example 6.7.3) :

add the below additional setting to the VSA proxies:

Name: nVDDKVersionPath
Category: VirtualServer
Type: Integer
Value: 673
  
Name: bLockVDDKVersionPath
Category: VirtualServer
Type: boolean
Value: true

This is the right temporary solution, but you don't want to accidently leave it in place and not receive updated VDDK versions in the future. 

 

VDDK versions typically don’t change with Maintenance releases, only with feature releases. I do not think we have a public listing but here is some guidance. the 6.x versions are obviously for vSphere 6.x, while vSphere 7.x automatically uses the 7.x versions.

Feature Release VDDK Version
FR25 (not yet released) 7.0.2
FR23 7.0.1
FR21 7.0 + 6.7.3
FR20

7.0

FR19 6.7.2

 

View original
Did this answer your question?

3 replies

Forum|alt.badge.img+4
  • Byte
  • 11 replies
  • August 12, 2021

Solution to force other (older) VDDK version (example 6.7.3) :

add the below additional setting to the VSA proxies:

Name: nVDDKVersionPath
Category: VirtualServer
Type: Integer
Value: 673
  
Name: bLockVDDKVersionPath
Category: VirtualServer
Type: boolean
Value: true


Damian Andre
Vaulter
Forum|alt.badge.img+23
  • Vaulter
  • 1235 replies
  • Answer
  • August 12, 2021
Dimitri wrote:

Solution to force other (older) VDDK version (example 6.7.3) :

add the below additional setting to the VSA proxies:

Name: nVDDKVersionPath
Category: VirtualServer
Type: Integer
Value: 673
  
Name: bLockVDDKVersionPath
Category: VirtualServer
Type: boolean
Value: true

This is the right temporary solution, but you don't want to accidently leave it in place and not receive updated VDDK versions in the future. 

 

VDDK versions typically don’t change with Maintenance releases, only with feature releases. I do not think we have a public listing but here is some guidance. the 6.x versions are obviously for vSphere 6.x, while vSphere 7.x automatically uses the 7.x versions.

Feature Release VDDK Version
FR25 (not yet released) 7.0.2
FR23 7.0.1
FR21 7.0 + 6.7.3
FR20

7.0

FR19 6.7.2

 


Forum|alt.badge.img+9
  • Author
  • Byte
  • 50 replies
  • August 16, 2021

Thank you


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings