hyper-v backups are failing with status code 13 or 25 if the hyper-v virtual machines has a snapshot
any ideas are welcome on the following as the case we have with veritas is almost 2 months old without any progress: if the hyper-v virtual machine has a snapshot which was created from hyper-v or failover console, the backup of the vm fails with status code 13 or 25: 28.09.202018:57:27-Errorbpbrm(pid=145214)socketreadfailed:errno=104-Connectionresetbypeer 28.09.202018:57:27-Errorbptm(pid=147427)systemcallfailed-Connectionresetbypeer(at../child.c.1289) 28.09.202018:57:27-Errorbptm(pid=147427)unabletoperformreadfromclientsocket,connectionmayhavebeenbroken 28.09.202018:57:28-Errorbptm(pid=147293)mediamanagerterminatedbyparentprocess 28.09.202018:57:33-Infoxxxxx(pid=147293)StorageServer=PureDisk:xxxxxx;Report=PDDOStats(multi-threadedstreamused)for(xxxxx):scanned:3KB,CRsent:0KB,CRsentoverFC:0KB,dedup:100.0%,cachedisabled 28.09.202018:57:35-Errorbpbrm(pid=145214)couldnotsendserverstatusmessagetoclient 28.09.202018:57:37-Criticalbpbrm(pid=145214)unexpectedterminationofclientxxxxxx 28.09.202018:57:38-Infobpbkar(pid=0)done.status:13:filereadfailed 28.09.202019:00:15-connecting 28.09.202019:00:16-connected;connecttime:0:00:00 28.09.202019:00:22-beginwriting 28.09.202019:00:35-endwriting;writetime:0:00:13 filereadfailed (13) a workaround is to disable exclude deleted block and swap and paging files but this is not appropriate for us due to negative performance impact thank you all!2.2KViews0likes6Comments