Fix for Failed to open VDDK disk

VMware specific discussions

Fix for Failed to open VDDK disk

Veeam Logoby ian0x0r » Wed Aug 10, 2016 1:04 pm

Thought I would post this as I have not come across a fix for this particular error, might help some one else in the future. Environment is vSphere 6

Error Message
Code: Select all
Processing Error: Failed to open VDDK disk [[.vmdk] ( is read-only mode - [true] )
Failed to open virtual disk [.vmdk (flags: 4)
Logon attempt with parameters [VC/ESX: [vc.domain.local];Port: 443;Login: [];VMX Spec: [moref=vm-];Snapshot mor: [snapshot-443];Transports: [nbd];Read Only: [true]] failed because of the following errors:
Failed to open disk for read.
Failed to upload disk.

Fix for this is detailed here https://kb.vmware.com/selfservice/micro ... Id=2007386 . Happens if SSL authentication to the ESXi host has been disabled.

Console access to VM will also fail with
Code: Select all
Unable to connect to the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period

Cheers,

Ian
https://www.snurf.co.uk
ian0x0r
Veeam Vanguard
 
Posts: 189
Liked: 32 times
Joined: Thu Nov 11, 2010 11:53 am
Location: UK
Full Name: Ian Sanderson

Re: Fix for Failed to open VDDK disk

Veeam Logoby Gostev » Wed Aug 10, 2016 1:16 pm

Thanks for sharing, Ian!
Gostev
Veeam Software
 
Posts: 21603
Liked: 2405 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

[MERGED] Error: Failed to open VDDK

Veeam Logoby mcclans » Fri Oct 28, 2016 4:21 pm

Anyone else see this error when using SAN transport mode? We've been fighting with it for a while and have been sort of working around it but would love to see VMWare resolve. Working with Veeam tier 2 support now on case 01954128. Ken has been superb to work with. Just looking for feedback for what others may have seen and how you've worked around or possibly resolved.
mcclans
Influencer
 
Posts: 15
Liked: 2 times
Joined: Tue Feb 17, 2015 2:05 pm
Full Name: Shawn McClanahan

Re: Fix for Failed to open VDDK disk

Veeam Logoby mcclans » Fri Oct 28, 2016 7:58 pm

Interesting find and it does show the same error but doesn't seem to apply to our environment. We're on 5.5 build 4345813 and have not found a case where console access was interrupted. We only see this when attempting to utilize SAN transport mode on our backups and somewhat intermittently. Hotadd and NBD work without issue.
mcclans
Influencer
 
Posts: 15
Liked: 2 times
Joined: Tue Feb 17, 2015 2:05 pm
Full Name: Shawn McClanahan

Re: Fix for Failed to open VDDK disk

Veeam Logoby matsholm » Wed Nov 02, 2016 2:20 pm

hi
have a customer that experinecing the same error on [san] mode and only see this when doing snapshots of virtual desktops (win7 and win10) all servers seems to work fine. The failed VM's is two or three in a job out of 40 and when the job is retried with [nbd] the failed VM's work fine.
Did you find any solution or good workaround for it?
matsholm
Influencer
 
Posts: 18
Liked: 1 time
Joined: Tue Jan 19, 2016 8:02 am
Full Name: Mats Holm

Re: Fix for Failed to open VDDK disk

Veeam Logoby mcclans » Thu Feb 09, 2017 6:45 pm

Our "fix" was to use virtual proxies (hot add) in place of SAN mode. Not ideal, but it works for now. Support seemed to think once we moved to vSphere 6.5 we wouldn't have this issue. Recently installed the Cisco c3260 as our backup repository so really hoping we can use SAN mode with this.
mcclans
Influencer
 
Posts: 15
Liked: 2 times
Joined: Tue Feb 17, 2015 2:05 pm
Full Name: Shawn McClanahan

Re: Fix for Failed to open VDDK disk

Veeam Logoby DaveWatkins » Thu Feb 09, 2017 8:36 pm

We just ran into this too, however in our case it was because the job was trying to use a DirectSAN proxy that wasn't connected to that datastore (it was in another site). Some drives were backed up fine by the correct DirectSAN proxy and some failed with this because it tried to use a DirectSAN proxy from another site.

In our case we're still on 6U2 for vCenter and ESXi. We did upgrade some of our hosts from build 4192238 to 4600944 on our DR site to test it and I'm now wondering if that might be the cause, although I wasn't aware the ESX hosts themselves were part of the DirectSAN LUN detection at all
DaveWatkins
Expert
 
Posts: 272
Liked: 68 times
Joined: Sun Dec 13, 2015 11:33 pm

Re: Fix for Failed to open VDDK disk

Veeam Logoby wm-it-team » Fri Mar 17, 2017 6:38 pm

We are having this same issue. When we rolled veeam out we were on vsphere 5.5 u3 and we were told all problems would go away once we updated to vpshere/vcenter 6 u2. Well that upgrade was performed a few months back and I just went to try moving the backup job that experiences this issue over to the direct access proxy. Same exact error occurred. This particular job happens to be 3 separate windows 2008 r2 file servers. The largest being almost 2.7TB. It never works with the large file server, we always receive this error, and it will work sporadically with the other 2.
wm-it-team
Lurker
 
Posts: 2
Liked: never
Joined: Tue Nov 15, 2016 9:34 pm

Re: Fix for Failed to open VDDK disk

Veeam Logoby foggy » Mon Mar 20, 2017 2:42 pm

Have you contacted support with this?
foggy
Veeam Software
 
Posts: 15272
Liked: 1131 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Fix for Failed to open VDDK disk

Veeam Logoby maguilar » Mon May 08, 2017 9:51 am

We are having this same issue with Vsphere 5.5u3
is there any update about this error ?
yes, support was contacted but they haven't found any solution yet
maguilar
Lurker
 
Posts: 1
Liked: never
Joined: Mon May 08, 2017 9:47 am

Re: Fix for Failed to open VDDK disk

Veeam Logoby Vitaliy S. » Mon May 08, 2017 12:10 pm

maguilar, what was your support case ID?
Vitaliy S.
Veeam Software
 
Posts: 19942
Liked: 1144 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Fix for Failed to open VDDK disk

Veeam Logoby Songykhw » Tue Aug 15, 2017 1:01 pm

I also got this error and fix by change proxy server to do restore.
Songykhw
Lurker
 
Posts: 2
Liked: never
Joined: Thu Dec 22, 2016 7:11 am

Re: Fix for Failed to open VDDK disk

Veeam Logoby germanfl » Mon Sep 04, 2017 4:45 pm

I have resolved this issue by running backup jobs using as proxy the veeam server itself.
germanfl
Lurker
 
Posts: 1
Liked: never
Joined: Mon Sep 04, 2017 4:42 pm
Full Name: GERMAN FLECHA


Return to VMware vSphere



Who is online

Users browsing this forum: No registered users and 2 guests