Host-based backup of Nutanix AHV VMs.
Post Reply
unsichtbarre
Service Provider
Posts: 229
Liked: 39 times
Joined: Mar 08, 2010 4:05 pm
Full Name: John Borhek
Contact:

Cannot to access Closed Stream after VBR update

Post by unsichtbarre »

Case: #07303166

Howdy,
After updating VBR, the NTNX proxy fails to update with the message "Cannot access a Closed Stream." Have rebooted Proxy Appliance, same error.

I have opened case, but thought I would post here for any possible insight?

THX,
-JB
John Borhek, Solutions Architect
https://vmsources.com
Mildur
Product Manager
Posts: 9044
Liked: 2388 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Cannot to access Closed Stream after VBR update

Post by Mildur » 1 person likes this post

Hi John

Please let's wait for our support team to investigate the logs.
We cannot investigate such issues over a forum post.

Best,
Fabian
Product Management Analyst @ Veeam Software
unsichtbarre
Service Provider
Posts: 229
Liked: 39 times
Joined: Mar 08, 2010 4:05 pm
Full Name: John Borhek
Contact:

Re: Cannot to access Closed Stream after VBR update

Post by unsichtbarre »

Veeam support provided the following fix, likely related to SD-WAN and/or network latency between the VBR Server and the AHV proxy, it worked!

Navigate to C:\Program Files\Veeam\Plugins\Nutanix AHV\Service\ on the VBR server.

2. Open appsettings.json with a text editor, find the following block of settings and make the changes below.


"ClusterRestClient": {
"RetryCount": 10,
"RetryInterval": "10 sec",
"ConnectionTimeout": "1 min",
"CustomTimeouts": [
{
"Url": "/api/nutanix/v0.8/images/[0-9a-z-]+/upload",
"ConnectionTimeout": "10 min"
}
]
},


Change the timeout to 100 and save the file and the final string value should look like the string below


"ConnectionTimeout": "100 min"


3. Restart Veeam AHV service on the VBR server.
John Borhek, Solutions Architect
https://vmsources.com
Post Reply

Who is online

Users browsing this forum: sagarkokadiya and 5 guests