Vitaliy S. wrote:Since other VMs are backed up without issues then connection limits shouldn't be the case here. What did our support engineer say after reviewing the debug logs?
Hi Vitaliy, some days ago i closed the case becouse thought it was solved but i was wrong, so i have opened a new case id 00987387
To be honest not all other vms are backed up successfully and what really happen is the following:
My customer has 2 errors during every backup:
1 - ChannelError:ConnectionReset (we have this error for some backup job but often the backup job end successfully on next retry, but i'd like to know why this happen)
2 - Every night one backup job hang on 99% or 47% (the same vm is always involved, only this night for another one) -> if i look at backup server with vsphere client i can see one disk is "hot-addedd" more than one time, other times the job can't work in hot-add and it switch to newtork mode.
In any event it hangs and i can't stop it, i have to kill all veeamagent process from task manager, so disc consolidation can start automatically and after that rebot backup server.
How can i escalate my case to be handled by higher tier support? It's going on from many days and we need a solution faster