I don't know if the possible solution would apply to Hyper-V, but, I would first bring up the Task Manager on the Hyper-V server "mbhyperv4", get a list fo running processes, and see if you have any 'ob2bar' processes hanging. If so, then kill the process
Another thing you could try is to implement KeepAlive (see attachment) for a Full explanation, but the short version is to stop teh Data Perotector INET service on "mbhyperv4", and edit the file
Program Files -> Omniback -> omnirc Windows 2003
or
Program Data -> Omniback -> omnirc Windows 2008
This file does not exist by default. If you don't have it, it can be created using Notepad.
Add these lines to the file
OB2IPCKEEPALIVE=1
OB2IPCKEEPALIVETIME=900
OB2IPCKEEPALIVEINTERVAL=60
Save the file as
Program Files -> Omniback -> omnirc Windows 2003
or
Program Data -> Omniback -> omnirc Windows 2008
Make sure that the filename has no extension, like ‘txt’ or ‘tmpl’
Restart the Data Protector INET service.
As I said, I don't know if this is the same issue, but, I haved found adding KeepAlive fixes many different problems