Today I encountered two error messages from Veeam after setting up a new VMware vCenter and changing the Veeam Backup & Replication jobs to the new vCenter/Cluster. The errors did not appear until the actual backup job was started though.
First error
“Failed to retrieve updated or changed rows from the table ReportSessionView. USN: 0
A transport-level error has occurred when recieving results from the server. (provider: Session Provider, error: 18 – Connection has been closed by peer)”
Second error (almost the same)
“Failed to retrieve updated or changed rows from the table ReportSessionView. USN: 0
Unexpected end of file has occurred.”
In our case the problem was we had added the VMware vCenter using only the NETBIOS name – for example “VCENTER01” instead of using the fully qualified domain name – for example “VCENTER01.domain.local”.
After removing the “VCENTER01” entry from managed servers in Veeam and adding it again using the fully qualified domain name we no longer saw this error message.
I followed up on this with Veeam support and (of course) it is best practice to always use FQDN instead of NETBIOS when adding everything from repositories over proxies to managed servers.
Incoming search terms:
- failed to retrieve updated or changed rows from the table veeam