Backup job fails when a Network Interface and Protocol or Subnet is Specified in the job setup.

Article:TECH129142  |  Created: 2010-01-23  |  Updated: 2014-09-11  |  Article URL http://www.symantec.com/docs/TECH129142
Article Type
Technical Solution

Product(s)

Issue



Backup job fails when a Network Interface and Protocol or Subnet is Specified in the job setup.


Error



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.


Cause



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:

(FIGURE 1)


(FIGURE 2)


JOB FAILURE when Backup Network is specified and either Protocol or Subnet is specified.

(FIGURE 3)
 

NOTE: This issue is only observed when adding user defined selection by IP address.


Solution



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. 

 

 

 

WORKAROUND:

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).

(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).

(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.

 


Supplemental Materials

SourceUMI
ValueV-79-57344-3842
Description

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.


SourceError Code
Value0xe0000f02
Description

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.


SourceETrack
Value2029424
Description

Backups fail when specifying a network card and protocol or subnet in Backup Exec 2010.


SourceETrack
Value1824148
Description

Backups of a 2008 clustered resource will backup over a secondary NIC when multiple NICS are present.


SourceError Code
Value0xe0000f02
Description

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.


SourceUMI
ValueV-79-57344-3842
Description

 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



Legacy ID



351371


Article URL http://www.symantec.com/docs/TECH129142


Terms of use for this information are found in Legal Notices