01-07-2014 02:48 AM
**** Moved to new discussion from https://www-secure.symantec.com/connect/forums/socket-read-failed-existing-connection-was-forcibly-c... ****
Hi,
No updates about this? It's a pity.
We are seeing the same errors, though not often. When they appear, usually NBU does the backup successfully on the second try. It's a hotadd backup performed by NBU. The backup host, which is also the media server, runs NBU 7.5.0.7. Master Server is still 7.5.0.5, but this is a supported combination of versions as per Symantec's documentation. I believe this issue has been active since before we upgraded the backup host from 7.5.0.5 to 7.5.0.7.
01-07-2014 05:51 AM
In hotadd transfer type; backup / restore fails if ESX/ESXi version is 4.1, you can try deploying a backup host in ESX/ESXi 4.0 and try backup / restore.
01-07-2014 06:08 AM
Thanks for your comment. I'm afraid we're not using ESX 4.1, but 5.1.0.
We do have a backup host, which is working fine. In fact, this issue usually disappears on NBU's second try. Our VMware administrators are reviewing the VMware Tools installation on the affected VMs.
01-07-2014 06:18 AM
we are seeing this more & more :(
When using the new version of VMware Tools in ESXi/ESX 4.1 Update 1 or Update 2 or ESXi 5.x, you may experience these symptoms
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2006849