Discussions specific to the VMware vSphere hypervisor

ian0x0r
Veeam Vanguard
Posts: 230
Liked: 43 times
Joined: Nov xi, 2010 11:53 am
Full Proper noun: Ian Sanderson
Location: UK
Contact:

Set up for Failed to open VDDK disk

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

Error Message

Code: Select all

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

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

Panel access to VM will also neglect with

Code: Select all

                  Unable to connect to the MKS: Could non connect to pipe \\.\pipe\vmware-authdpipe within retry flow

Thank you,

Ian

Bank check out my blog at www.snurf.co.united kingdom of great britain and northern ireland :D

mcclans
Influencer
Posts: fifteen
Liked: two times
Joined: Feb 17, 2015 ii:05 pm
Full Name: Shawn McClanahan
Contact:

[MERGED] Error: Failed to open VDDK

Mail service by mcclans » this mail service

Anyone else see this error when using SAN ship mode? We've been fighting with information technology for a while and have been sort of working around it only would love to run across VMWare resolve. Working with Veeam tier 2 support now on example 01954128. Ken has been superb to piece of work with. Just looking for feedback for what others may have seen and how you've worked around or perchance resolved.

mcclans
Influencer
Posts: 15
Liked: 2 times
Joined: Feb 17, 2015 2:05 pm
Total Name: Shawn McClanahan
Contact:

Re: Fix for Failed to open VDDK disk

Post by mcclans » this post

Interesting find and it does show the same error but doesn't seem to apply to our environs. We're on 5.five build 4345813 and have not found a case where console admission was interrupted. Nosotros only come across this when attempting to apply SAN transport mode on our backups and somewhat intermittently. Hotadd and NBD work without issue.

matsholm
Influencer
Posts: 19
Liked: i fourth dimension
Joined: Jan 19, 2016 8:02 am
Full Proper noun: Mats Holm
Contact:

Re: Set for Failed to open VDDK disk

Post by matsholm » this post

hello
have a customer that experinecing the aforementioned 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 chore is retried with [nbd] the failed VM'southward work fine.
Did you detect any solution or good workaround for it?

mcclans
Influencer
Posts: 15
Liked: 2 times
Joined: February 17, 2015 2:05 pm
Full Name: Shawn McClanahan
Contact:

Re: Set up for Failed to open VDDK disk

Post by mcclans » this post

Our "fix" was to employ virtual proxies (hot add) in place of SAN style. Not ideal, but it works for now. Back up seemed to remember once we moved to vSphere vi.v nosotros wouldn't have this result. Recently installed the Cisco c3260 every bit our backup repository then actually hoping we can use SAN fashion with this.

DaveWatkins
Skilful
Posts: 368
Liked: 97 times
Joined: December 13, 2015 xi:33 pm
Contact:

Re: Fix for Failed to open VDDK disk

Mail service by DaveWatkins » this post

We just ran into this as well, nonetheless in our example it was because the job was trying to utilise a DirectSAN proxy that wasn't connected to that datastore (it was in some other 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 instance nosotros're all the same on 6U2 for vCenter and ESXi. We did upgrade some of our hosts from build 4192238 to 4600944 on our DR site to test information technology and I'm now wondering if that might be the cause, although I wasn't aware the ESX hosts themselves were office of the DirectSAN LUN detection at all

wm-it-team
Novice
Posts: 3
Liked: never
Joined: Nov 15, 2016 ix:34 pm
Contact:

Re: Gear up for Failed to open up VDDK disk

Post by wm-it-team » this post

We are having this aforementioned issue. When we rolled veeam out nosotros were on vsphere v.5 u3 and we were told all problems would go abroad one time nosotros updated to vpshere/vcenter 6 u2. Well that upgrade was performed a few months back and I just went to attempt moving the backup task that experiences this effect over to the direct access proxy. Same exact error occurred. This particular chore happens to be iii divide windows 2008 r2 file servers. The largest existence almost 2.7TB. It never works with the large file server, we e'er receive this error, and it volition piece of work sporadically with the other 2.

maguilar
Lurker
Posts: one
Liked: never
Joined: May 08, 2017 ix:47 am
Contact:

Re: Prepare for Failed to open VDDK disk

Post by maguilar » this post

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

Who is online

Users browsing this forum: Bing [Bot], Imperial-12 [Bot] and 24 guests