hyper-v backups are failing with status code 13 or 25 if the hyper-v virtual machines has a snapshot

Question

any ideas are welcome on the following as the case we have with veritas is almost 2 months old without any progress:&nbsp;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.2020&nbsp;18:57:27&nbsp;-&nbsp;Error&nbsp;bpbrm&nbsp;(pid=145214)&nbsp;socket&nbsp;read&nbsp;failed:&nbsp;errno&nbsp;=&nbsp;104&nbsp;-&nbsp;Connection&nbsp;reset&nbsp;by&nbsp;peer28.09.2020&nbsp;18:57:27&nbsp;-&nbsp;Error&nbsp;bptm&nbsp;(pid=147427)&nbsp;system&nbsp;call&nbsp;failed&nbsp;-&nbsp;Connection&nbsp;reset&nbsp;by&nbsp;peer&nbsp;(at&nbsp;../child.c.1289)28.09.2020&nbsp;18:57:27&nbsp;-&nbsp;Error&nbsp;bptm&nbsp;(pid=147427)&nbsp;unable&nbsp;to&nbsp;perform&nbsp;read&nbsp;from&nbsp;client&nbsp;socket,&nbsp;connection&nbsp;may&nbsp;have&nbsp;been&nbsp;broken28.09.2020&nbsp;18:57:28&nbsp;-&nbsp;Error&nbsp;bptm&nbsp;(pid=147293)&nbsp;media&nbsp;manager&nbsp;terminated&nbsp;by&nbsp;parent&nbsp;process28.09.2020&nbsp;18:57:33&nbsp;-&nbsp;Info&nbsp;xxxxx&nbsp;(pid=147293)&nbsp;StorageServer=PureDisk:xxxxxx;&nbsp;Report=PDDO&nbsp;Stats&nbsp;(multi-threaded&nbsp;stream&nbsp;used)&nbsp;for&nbsp;(xxxxx):&nbsp;scanned:&nbsp;3&nbsp;KB,&nbsp;CR&nbsp;sent:&nbsp;0&nbsp;KB,&nbsp;CR&nbsp;sent&nbsp;over&nbsp;FC:&nbsp;0&nbsp;KB,&nbsp;dedup:&nbsp;100.0%,&nbsp;cache&nbsp;disabled28.09.2020&nbsp;18:57:35&nbsp;-&nbsp;Error&nbsp;bpbrm&nbsp;(pid=145214)&nbsp;could&nbsp;not&nbsp;send&nbsp;server&nbsp;status&nbsp;message&nbsp;to&nbsp;client28.09.2020&nbsp;18:57:37&nbsp;-&nbsp;Critical&nbsp;bpbrm&nbsp;(pid=145214)&nbsp;unexpected&nbsp;termination&nbsp;of&nbsp;client&nbsp;xxxxxx28.09.2020&nbsp;18:57:38&nbsp;-&nbsp;Info&nbsp;bpbkar&nbsp;(pid=0)&nbsp;done.&nbsp;status:&nbsp;13:&nbsp;file&nbsp;read&nbsp;failed28.09.2020&nbsp;19:00:15&nbsp;-&nbsp;connecting28.09.2020&nbsp;19:00:16&nbsp;-&nbsp;connected;&nbsp;connect&nbsp;time:&nbsp;0:00:0028.09.2020&nbsp;19:00:22&nbsp;-&nbsp;begin&nbsp;writing28.09.2020&nbsp;19:00:35&nbsp;-&nbsp;end&nbsp;writing;&nbsp;write&nbsp;time:&nbsp;0:00:13file&nbsp;read&nbsp;failed&nbsp; (13)&nbsp;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&nbsp;thank you all!&nbsp;

mouse · Answer

did you try to remove that one existing snapshot and try to re-run a backup?

gabriel-a · Answer

Hi,&nbsp;thanks for the suggestion.we have production snapshots for production vms and this used to work before end of july.I expect the functionality to keep working as desired.please note that we are not talking about a netbackup snapshot.yes, i have tried removing the snapshot just for the test. the backup worked. but this is not a solution.&nbsp;cheers!

mouse · Answer

I have very sporadic experience with Hyper-V but if you believe NBU behaviour is not correct, I would open a support case.
Since I have significant experience with VMware I thought that its behaviour with snapshots may provide a clue what might have happened with Hyper-V and it looks like it had worked, basically in VMware environment, you can't have snapshots attached to a VM for the snapshot backup to work, this might be well true for Hyper-V as well.

ethanh · Answer

Are all of the VMs in the policies failing, or just a few (ones with snapshot outside of NBU)? Are the VMs being selected via Intelligent Policy (query-based), or manually added to the policy? If it's query-based, I'd try adding one of the problematic VMs to a standalone policy and attempting the backup that way.

Any special network configuration that needs to be considered? VLANs, multiple interfaces, virtual name mismatch for clusters, etc. Status 13 and status 25 are very vague error codes, but they indicate to me that the problem lies between the media server and the Hyper-V host, as I would expect to see status 156 or other snapshot errors if the problem was occurring during snapshotting.

gabriel-a · Answer

thanks for your hint. there are no limitations of backing up hyper-v vm that has a non-NBU snapshot. other difference from vmware backup is that if there is NBU-snapshot, natbackup has no option to delete it, as it has for vmware policies.&nbsp;i have a case and since end of july we have no progress with the case.&nbsp;

Forum Discussion

hyper-v backups are failing with status code 13 or 25 if the hyper-v virtual machines has a snapshot

Related Content

Hyper-V machines not listed

Hyper-V Backups

Snapshots not remove after backup on Hyper-v server

hyper v snapshot backups

snapshot failed quiesce the virtual machine

Recent Discussions

Instant Access for vmware problem

Netbackup KMS

Veritas IO filter vSphere Installation Bundle

How can I reinstall just the java/jre packages for NB 8.3.0.2?

Image Sharing Support for MSDP!