Thursday, June 20, 2024
Thinware Forums
ForumsForumsThinware vBacku...Thinware vBacku...DiscussionsDiscussionsVMWARE 6.5 ESXiVMWARE 6.5 ESXi
Previous Previous
Next Next
New Post
 1/2/2017 7:14 PM
I am getting the following error when trying to run the backup after upgrading to VMWARE 6.5 ESXI, has anyone tried this?

Backup Folder: \\DNas0\Backup\Backups\143-99.3-20003-Controller-III
Backup: 170102_205432
No existing temporary snapshots found.
Temporary Snapshot: vBackup-TMP-170102_205432
VMware Virtual Disk Manager: VMware Virtual Disk Manager - build 2248791
VMware Virtual Disk Manager response for Hard disk 1: [lcnas0] 143-99.3-20003-Controller-III/143-99.3-20003-Controller-III.vmdk:
SSL: connect failed
[NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error:
VixDiskLib: NFC Error during user connect: Failed to convert disk: Cannot connect to the host (0x4650).
E Unable to complete backup. Unable to verify successful transfer of virtual machine virtual disk file \\DNas0\Backup\Backups\143-99.3-20003-Controller-III\170102_205432\143-99.3-20003-Controller-III.vmdk.
Temporary snapshot removed.
New Post
 1/18/2017 8:45 PM
 Modified By Bitstorm  on 1/18/2017 7:46:42 PM

I'm having the same issue, and the lack of activity from the support team after all this time worries me.

I've searched alot on the issue in the last weeks, but there's not much infos to be found.

There's another post here with the same error message, in an earlier version here.
The solution was to disable SSL verification using a registry key.

VMware's vsphere-vddk-65-programming-guide.pdf says:
SSL Certificates and Security

The VDDK 5.1 release and later were security hardened, with virtual machines set to check SSL certificates.

On Windows VDDK 5.1 and 5.5 required the VerifySSLCertificates and InstallPath registry keys under
HKEY_LOCAL_MACHINE\SOFTWARE to check SSL certificates. On Linux VDDK 5.1 and 5.5 required adding a line
to the VixDiskLib_InitEx configuration file to set linuxSSL.verifyCertificates = 1.

As of VDDK 6.0 both SSL certificate verification and SSL thumbprint checking are mandatory and cannot be
. The Windows registry and Linux SSL setting are no longer checked, so neither has any effect.

My guess is that vBackup just can't work with ESXi 6.5 right now, because SSL verification is probably mandatory now for ESXi 6.5 or requires VDDK 6.x which has it mandatory anyway.

I'm not 100% sure, but I think I've read something about changing the default ESXi SSL keys, but I'm not sure if it's enough to get SSL verification working or if it requires a modification inside vBackup. I'm lacking spare time to investigate further on this, and I've been running without VM backups for over a month now.

I'm debating on waiting some more for a fix (again, the lack of activity from the devs worries me) or spend my time switching to an alternative instead, like XSI Backup which they claim they have version 6.0.11 compatible with ESXi 6.5 since november.

Hopefully the devs will show some good news (at least, please confirm if vBackup is supposed to be working at all -or not- with ESXi 6.5) in the next couple days/weeks. vBackup v5.0.0 (pre-release) has been in private beta for almost a year...

New Post
 1/19/2017 1:38 AM
 Modified By vBackup Team  on 1/19/2017 12:42:22 AM
Please know that we are actively working to add support for vSphere 6.5. As with other third-party solutions utilizing VMware APIs (VDDK) all of the security changes introduced in vSphere 6.5, along with a very poorly documented VDDK 6.5 release, have made adding support for this release a very daunting task. We have tested every scenario included in VMware’s release notes (e.g. upgrading OpenSSL, including thumbprints, etc.), however, we have not yet narrowed in on a solid solution that works in every case. The alternative solution you mentioned (XSI Backup) does not utilize off-host backup processing or VMware VDDK – this is why they were able to support vSphere 6.5 right out of the gate.

As of today we have designed and proof-of-concept tested two solutions to quickly add support for vSphere 6.5. Both solutions work without VMware VDDK (which, as stated above, we have found to be the culprit in support issues with vSphere 6.5). Our current plan is to complete development and testing of these new features and release them in vBackup v5 beta 4 sometime next week. This beta release is planned to be released as public (unlike the prior 3 beta releases for v5 which were all private), however, we may delay making the download publicly available until we have verified full functionality through our v5 private beta users group.

As far as support not being responsive… We have reviewed our support queue and have been unable to find a support request that has not been responded to or resolved as of today. If you don’t mind, please send your contact information to so that we can communicate with you about your support case directly.

We will update this forum thread once we have additional information about the vBackup v5 beta 4 release.
New Post
 1/19/2017 9:17 AM

Thanks for the (quick!) reply. This is great news!

Sorry for the "lack of activity" part (I didn't mention "unresponsive support"). Admittedly I didn't open a support case myself (I felt that was a general issue so you were already aware of it), but I was referring to observations made while trying to find a statement on ESXi 6.5 compatibility (no offense):

-latest news in news section on the product page is announcement of v4.0.2 release (about 1 year ago)
-latest tweet on your twitter account is dated august 2015
-screenshots on the product page are dated v0.2.4 (5 years old)
-latest public product upgrade in the download section is almost a year old
-new ESXi 6.5 has been out for about 2 months and there's ("was", until your last post) still no public statement about product compatibility (neither to confirm it's compatible, nor to warn customers to stick with ESXi 6.0 until new compatible version is released).
-AndyP's post here about issue with ESXI 6.5 has been left unanswered for two weeks. I wish you had replied to his post two weeks ago to confirm the problem with ESXi 6.5, that'd have saved me (and most likely other customers) alot of headaches ;-)

I work for a software development company myself so I know sometimes things don't get fixed as fast as we'd like (also sometimes not as "cleanly" as we'd like).

I'm glad to see you are actively working on a solution.

New Post
 5/1/2017 7:07 AM
Hi support,

Is there maybe already an beta to test?
I am running a big R&D test envirenment and upgraded 30% to 6.5 now I have to vmove systems weekly.

Previous Previous
Next Next
ForumsForumsThinware vBacku...Thinware vBacku...DiscussionsDiscussionsVMWARE 6.5 ESXiVMWARE 6.5 ESXi

Thinware Community
Membership Membership:
Latest New User Latest: haihd4
New Today New Today: 0
New Yesterday New Yesterday: 0
User Count Overall: 41208

People Online People Online:
Visitors Visitors: 18
Members Members: 0
Total Total: 18

Privacy Statement  |  Terms Of Use
Copyright 2007-2019 Thinware, Inc.