The error message "0xe0000f04 - The media server could not connect to the remote computer. The remote computer may not be running the Backup Exec Remote Agent for Windows/Linux. Make sure that the correct version of the Remote Agent is installed and running on the target computer.
Final error category: Resource Errors. V-79-57344-3844
Debug Log Error (Backup Exec Job Engine Debug)
Backup Exec will generate a Always On Debug Log after the job failure.
(C:\Program Files\Veritas\Backup Exec\Logs\BEServerHostName-bengine_AlwaysOnLog_XXXX-XX-XX_XX-XX4-XX.log)
[server] - Enter RestoreMessageHandler::SetTargetDeviceName
[server] - Queried Device: \\192.168.1.200\[ROOT]
[loops] - NDMPAgentConnector:SetupConnection(): Data Server = 192.168.1.200\
[ndmp\ndmpcomm] - ndmpConnectEx: Querying the neighbour advertisement cache to discover information on '192.168.1.200\' ...
[ndmp\ndmpcomm] - ndmpQueryAgentAdvertisementCache: Could not resolve '192.168.1.200\': 11001
[ndmp\ndmpcomm] - ndmpConnectEx: All attempts to connect to '192.168.1.200\' failed
[ndmp\ndmpcomm] - ndmpConnectEx: Connect via DNS style host name failed, Attempting to connect to NETBIOS hostname 192
[ndmp\ndmpcomm] - ndmpConnectEx: Querying the neighbour advertisement cache to discover information on '192' ...
[ndmp\ndmpcomm] - ndmpEstablishConnectionUsingGivenSubnet: '192.168.1.100' and '0.0.0.192' were not found to be on the same subnet
[ndmp\ndmpcomm] - Could not connect to any of the remote addresses using subnet: '192.168.1.100' and mask: '255.255.240.0'
[ndmp\ndmpcomm] - ndmpEstablishConnectionUsingNetworkOptions: Could not connect to the remote host through NIC: 'LAN'
[ndmp\ndmpcomm] - ndmpEstablishConnectionUsingNetworkOptions: Attempting to use any available route to connect to the remote host...
[ndmp\ndmpcomm] - ndmpEstablishConnectionUsingNoSpecificAdapter: Could not connect to remote address 0.0.0.192 and port 10000 Errorno : 10051
[ndmp\ndmpcomm] - ndmpConnectEx: unable to connect using NetworkOptions to 192
[ndmp\ndmpcomm] - ndmpConnectEx: All attempts to connect to '192' failed
[ndmp\ndmpcomm] - ndmpConnectEx: failed to connect to '192'
[loops] - NDMPAgentConnector::Connect: ndmpConnectEx() failed on server 192.168.1.200\, port: 0.
[loops] - NDMPAgentConnector::HandleConnectionError: ndmpConnect failed: Could not connect to the Remote Agent on the target machine 192.168.1.200\. Probably Remote Agent is not installed on the target system or is not up and running.
[loops] - IsLocalAgent:beclass::BEConvertServerNamePlus returned error: 87
[loops] - NDMPAgentConnector::Connect: Returning. Result = e0000f04
[loops] - NDMPRAHostRestoreEngine::ConnectToDataServer() failed. Error = 0xE0000F04.
Under Investigation.
This issue is resolved in Backup Exec 24
Workaround:
1. Add the RALUS Agent Linux server by Hostname (NetBIOS or FQDN) to the Backup/Restore tab using the Add Server wizard.
Note: If Name Resolution is not available for the remote server temporally edit the Windows Host file on the Backup Exec media server and add entries for the Hostname of the RALUS Agent Linux server.
2. Create a restore job using the IP address of the RALUS Agent Linux server.
When creating the restore job select "To a different location" when prompted "Where do you want to restore the data".
Select the "Browse" button and expand the "Known Servers" and expand the Linux Server known servers.
Select the RALUS Agent Linux server by Hostname and select the data to restore.
Note: The Backup of the RALUS Agent Linux server was performed by IP address. The restore selections or Backup set view are available under this selection.
3. Submit the Restore job.