BackupExec 2010 R3 Hyper-V Job Failures - Network Failures.....bizarre

[peter_stephens1]

We are experiencing problems where our scheduled Hyper-V backup jobs have started to fail with-

"Final error: 0xe0000f02 - The media server could not connect to the remote computer. The remote computer may not exist on the selected subnet. Try an alternative network interface, or allow Backup Exec to choose any available network interface. "
Final error category: Resource Errors

We are, and have been succefully until the last week backing the VM's up over a seperate backup subnet to our production LAN, but in the past week all our jobs are failing.

If we create a new job exactly the same as the ones that fail, point it at the same selection list the failed jobs use then the job runs through fine.

So, before we re-create all our jobs, any ideas as to how we can fix this issue? We can ping the servers from the Media server and they reply on the backup subnet......

Thanks
 

[VJware]

Check if the existing job has specified a network/subnet/protocol under Network & Security tab of the job properties...

[pkh]

Make sure that there is no firewall blocking port 10000 between the two subnets.

[peter_stephens1]

They are all specified to use the backup interface, subnet and IPv4 protocol.

Have tried jobs with 'use any available subnet' and 'use any available protocol' on the Backup LAN interface and jobs still fail with same issue.

Recreated jobs from the same selection list are succesfull with the subnet and protocol specified.

[peter_stephens1]

Nothing is getting blocked firewall wise and recreated jobs run without problems