Backup job fails when a Network Interface and Protocol or Subnet is Specified in the job setup.
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.
A Backup job will fail in Backup Exec 2010 (FIGURE 3) for Windows server when a Network Interface and Protocol or Subnet is specified (FIGURE 1 and FIGURE 2). This issue occurs when the Backup Exec Media server and Remote server are on the same subnet and windows networking is setup and working correctly.
Examples that will cause the job to fail:
JOB FAILURE when Backup Network is specified and either Protocol or Subnet is specified.
NOTE: This issue is only observed when adding user defined selection by IP address.
This issue has been Resolved in a newer version of Backup Exec. To resolve this issue and receive the new Backup Exec improvements please upgrade to the current version of Backup Exec.
This issue is resolved in Backup Exec 2014 or later versions.
A) If IP address can only be used to specify the desired Network card Protocol and or Subnet setting and place a check box in the option to "Allow use of any available network interface, subnet, or protocol for remote agents not bound to the above network interface, subnet, or protocol" (FIGURE 4).
The backup job will use the specified network as expected. To confirm the backup job is using the correct Network card and Network review the Backup Exec job log to confirm the control and data connection are on the same network/subnet (FIGURE 5).
B) Edit host file on Backup Exec media server and add host entries for the remote servers using desired network. Add the user defined selection using Net Bios or FQDN.