VADP: Unable to open handle to virtual disk

Does VADP-TEST\VMWARE.LOG contain any additioinal information?

The VMWARE.LOG tells me all the actions are taken. The last x lines are:

==================================================================================

DISKUTIL: scsi0:0 : geometry=3916/255/63

Oct 31 14:58:42.371: vcpu-0| DISKUTIL: scsi0:0 : capacity=62914560

Oct 31 14:58:42.371: vcpu-0| DISKUTIL: scsi0:1 : geometry=3916/255/63

Oct 31 14:58:42.371: vcpu-0| DISKUTIL: scsi0:1 : capacity=62914560

Oct 31 14:58:42.415: vcpu-0| BIOS-UUID is 42 04 b8 d7 4a be 2a 16-82 60 30 0a d9 e2 c6 da

Oct 31 14:58:56.176: mks| MKS: Base polling period is 10000us

Oct 31 14:58:57.095: mks| VNCENCODE 2 encoding mode change: (720x400x16depth,16bpp,1440bytes/line)

Oct 31 14:58:57.129: mks| VNCENCODE 2 encoding mode change: (720x400x16depth,16bpp,1440bytes/line)

Oct 31 14:59:27.477: vmx| TOOLS received request in VMX to set option 'synctime' -> '0'

Oct 31 14:59:27.479: vmx| VMXVmdb_LoadRawConfig: Loading raw config

Oct 31 14:59:27.491: vmx| VMXVmdb_LoadRawConfig: Loading raw config

Oct 31 14:59:27.504: vmx| VMXVmdb_LoadRawConfig: Loading raw config

Oct 31 14:59:49.574: vcpu-0| Msg_Post: Warning

Oct 31 14:59:49.574: vcpu-0| [msg.Backdoor.OsNotFound] No bootable device was detected.  A bootable device might be a CD, floppy, hard disk, or network device, as when booting with PXE.

Oct 31 14:59:49.574: vcpu-0| To install an operating system, insert a bootable CD or floppy and restart the virtual machine.----------------------------------------

Oct 31 15:00:43.571: vmx| Vix: [116058 vmxCommands.c:212]: VMAutomation_InitiatePowerOff

Oct 31 15:00:43.571: vmx| Vix: [116058 vmxCommands.c:281]: VMAutomation_InitiatePowerOff. Trying hard powerOff

Oct 31 15:00:43.572: vmx| Stopping VCPU threads...

Oct 31 15:00:43.572: vmx| Finishing pending lazy checkpoint...

Oct 31 15:00:43.572: vcpu-0| VMMon_WaitForExit: vcpu-0: worldID=16063

Oct 31 15:00:43.650: mks| MKSHostOps_Exit3D: 1, 0

Oct 31 15:00:43.650: mks| Async MKS thread is exiting

Oct 31 15:00:43.650: vmx| Vix: [116058 mainDispatch.c:833]: VMAutomation_PowerOff: Powering off.

Oct 31 15:00:43.675: vmx| VMXVmdb_SetToolsVersionState: status value set to 'ok'

Oct 31 15:00:43.683: vmx| Destroying virtual dev for scsi0:0 vscsi=9060

Oct 31 15:00:43.684: vmx| VMMon_VSCSIStopVports: Invalid handle

Oct 31 15:00:43.684: vmx| VMMon_VSCSIDestroyDev: Not found

Oct 31 15:00:43.684: vmx| Destroying virtual dev for scsi0:1 vscsi=9061

Oct 31 15:00:43.684: vmx| VMMon_VSCSIStopVports: Invalid handle

Oct 31 15:00:43.685: vmx| VMMon_VSCSIDestroyDev: Not found

Oct 31 15:00:43.686: vmx| SOCKET 2 (108) close VNC socket on VNCBackendDestroy

Oct 31 15:00:43.689: vmx| MKS local poweroff

Oct 31 15:00:43.690: vmx| scsi0:1: numIOs = 0 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)

Oct 31 15:00:43.706: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4a0014f6-3db9f0b0-7471-0015173de89a/VADP-TEST/VADP-TEST_1-000001-delta.vmdk" : closed.

Oct 31 15:00:43.706: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4a0014f6-3db9f0b0-7471-0015173de89a/VADP-TEST/VADP-TEST_1-flat.vmdk" : closed.

Oct 31 15:00:43.707: vmx| scsi0:0: numIOs = 0 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)

Oct 31 15:00:43.718: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4a0014f6-3db9f0b0-7471-0015173de89a/VADP-TEST/VADP-TEST-000001-delta.vmdk" : closed.

Oct 31 15:00:43.718: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4a0014f6-3db9f0b0-7471-0015173de89a/VADP-TEST/VADP-TEST-flat.vmdk" : closed.

Oct 31 15:00:43.719: vmx| WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0

Oct 31 15:00:44.670: vmx| Vix: [116058 mainDispatch.c:3248]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1

Oct 31 15:00:44.671: vmx| Vix: [116058 mainDispatch.c:3254]: VMAutomation: Ignoring ReportPowerOpFinished because the VMX is shutting down.

Oct 31 15:00:44.717: vmx| VMXVmdb_LoadRawConfig: Loading raw config

Oct 31 15:00:44.727: vmx| Vix: [116058 mainDispatch.c:3248]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1

Oct 31 15:00:44.731: vmx| Vix: [116058 mainDispatch.c:3254]: VMAutomation: Ignoring ReportPowerOpFinished because the VMX is shutting down.

Oct 31 15:00:44.731: vmx| Transitioned vmx/execState/val to poweredOff

Oct 31 15:00:44.767: vmx| VMX idle exit

Oct 31 15:00:44.770: vmx| Vix: [116058 mainDispatch.c:599]: VMAutomation_LateShutdown()

Oct 31 15:00:44.770: vmx| Vix: [116058 mainDispatch.c:549]: VMAutomationCloseListenerSocket. Closing listener socket.

Oct 31 15:00:44.780: vmx| Flushing VMX VMDB connections

Oct 31 15:00:44.786: vmx| IPC_exit: disconnecting all threads

Oct 31 15:00:44.786: vmx| VMX exit (0).

Oct 31 15:00:44.786: vmx| AIOMGR-S : stat o=10 r=14 w=0 i=12 br=200704 bw=0

Oct 31 15:00:44.786: vmx| VMX has left the building: 0.

==================================================================================

The bold line is exectly my issue.

[added the vmware.log]

Regards.

Antoine Schokker

Hi Antoine,

A likely cause of this 'one of the parameters is invalid' error is the transport mode value is not correct or not working.  Try changing this to nbd and see if this works.

-Bobby

Hi Bobby,

The NBD option works correctly. I see that the recovery takes 3 to 4 time longer than the failing SAN-option.

What is the diverence between NBD and SAN?

And why is the SAN option not working?

regards

Antoine Schokker

Hi Antoine,

Maybe you don't have your setup done correctly to support the SAN transport mode.  The different between the modes and what you need for each is detailed in the NetWorker VMWare Integration Guide

Page 17 describes the different transport modes.

-Bobby

Hi Bobby,

I missed the text: "SAN mode requires a physical proxy with SAN access, and the virtual machines

need to be hosted on either FibreChannel or iSCSI-based storage".

My Proxy is a virtual machine, so SAN will never work.

Antoine Schokker