- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Upgrade Vcenter 5.5 to Vcsa 6.5 U2
Hi all,
I need your advise about one case :
I have upgraded a vcenter 5.5 to 6.5 U2 VCSA.
Since these steps, I meet strange issues with authentication on Veeam server, backups & replications works & randomly I get this strange error on some halft of jobs :
SOAP connection is not available. Connection ID: [srv.DOMAIN].
Failed to create NFC download stream. NFC path: [nfc://conn:srv.DOMAIN,nfchost:host-10,stg:datastore-11@SRV:srv.vmx].
Soap fault. Detail: '', endpoint: ''
I opened a case with Veeam, they said there is some issues with network, we checheck network everything is Ok.
I think it could be related on psc .
Has someone already identifiy where the issue could be located ?
I have seen this link about Vcenter limitation http://andyandthevms.com/vcenter-connection-limitation-and-backup-in-big-environments/
As backups jobs are many in same time.
Thanks for your feedback
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That error message is between the ESXi host running the VM and the server functioning as your Veeam proxy server. It doesn't have anything to do with the PSC. Make sure your ESXi hosts are up-to-date on patches, and do the same for Veeam as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Upgraded Veeam to latest version which may fixed the issue.
Reference Veeam KB article: https://www.veeam.com/kb2063
-Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Already in 9.5 update 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thks, vms and proxy are on same esxi and vm network.
I Will try To dig for esxi patches
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I solved my issue by using the sso admin account in the veeam