Backup dropping one resource

[Valentin_Stefan]

Hi,

I have Backup exec 9.1 for Windows Servers running on a XP sp2 machine. It backs up 2 snap servers and another XP machine perfectly. I also have a 2003 server that it will not backup.
I have been through the your forums, google, exchange experts, and Microsoft and found basically the same fixes listed everywhere. However none of them are working in this scenario. I have tried making a new single job to backup the 2003 server and generated debug logs. Following are the portions of the logs where it fails and the specific error from the job and the fixes I have already tried.
Does anyone have any other suggestions? Fyi, these machines are on a 2003 domain with AD.

Client log

Job Start - Wed Aug 31 19:57:40 2005
1014 8/31/2005 19:57:40: Entering SetupLocalShareInfo
1014 8/31/2005 19:57:40: Attach to \\HBDC\F_Drive
1014 8/31/2005 19:57:40: Detach from \\HBDC\F_Drive
1014 8/31/2005 19:57:40: Job Stop(0) - Wed Aug 31 19:57:40 2005
11f4 8/31/2005 19:57:42: Successfully impersonated administrator4hb
11f4 8/31/2005 19:57:42: WhoAmI( ) reports: DOMAIN\administrator4hb
11f4 8/31/2005 19:57:43: ndmpdDataConnect: Rant is attempting data connection on IP: 10.0.0.79
11f4 8/31/2005 19:57:43: ndmpdDataConnect: Rant is attempting data connection on Port: 33035
11f4 8/31/2005 19:58:04: ERROR: ndmpdDataConnect: connect error: 10060
11f4 8/31/2005 19:58:04: ndmpdDataConnect: Rant is attempting data connection on IP: 10.0.0.79
11f4 8/31/2005 19:58:04: ndmpdDataConnect: Rant is attempting data connection on Port: 33035
11f4 8/31/2005 19:58:25: ERROR: ndmpdDataConnect: connect error: 10060
168c 8/31/2005 20:04:49: ndmpRun: accept() returned 10004
168c 8/31/2005 20:04:49: FS_RemoveFileSys
168c 8/31/2005 20:04:49: unloading bedssms.dll
168c 8/31/2005 20:04:49: unloading bedsxchg.dll
168c 8/31/2005 20:04:49: unloading bedssmsp.dll
168c 8/31/2005 20:04:49: unloading bedsnote.dll
168c 8/31/2005 20:04:49: unloading bedsnt5.dll
168c 8/31/2005 20:04:49: unloading bedsxese.dll
168c 8/31/2005 20:04:49: unloading bedssql2.dll
168c 8/31/2005 20:04:49: unloading bedsmdoc.dll
168c 8/31/2005 20:04:49: unloading bedsshadow.dll
168c 8/31/2005 20:04:49: unloading bedsupfs.dll

Server log
Attach to Microsoft Windows Network
d18 8/31/2005 14:14:41: Detach from Microsoft Windows Network
d18 8/31/2005 14:14:42: Attach to DOMAIN
d18 8/31/2005 14:14:42: Detach from DOMAIN
af8 8/31/2005 14:15:57: ERROR: ndmpcSendRequest(): timeout waiting for reply from control connection
af8 8/31/2005 14:15:57: ERROR: ndmpSendRequest failed:
d18 8/31/2005 14:15:58: Error 997 opening cluster on \\HBDC
d18 8/31/2005 14:15:58: Error 0 on NetShareEnum of \\HBDC, level 1
d18 8/31/2005 14:15:58: NTFS_SurrogateCalling: HBDC
d18 8/31/2005 14:15:58: HBDC is not local -- exiting
d18 8/31/2005 14:16:00: Informational: NTFS_GetServerType status 1219 for null session
d18 8/31/2005 14:16:00: SQL2_SurrogateCalling - the default SQL Service is not running on HBDC.
d18 8/31/2005 14:16:00: SQL2_SurrogateCalling - Sorry, SQL 2000 Agent not autherized.
d18 8/31/2005 14:16:00: beclass::ConvertServerNameFromIP failed!!
d18 8/31/2005 14:16:00: belcass:: ConvertServerNameFromIP failed !!
d18 8/31/2005 14:16:00: Attach to \\HBDC
d18 8/31/2005 14:16:00: Detach from \\HBDC
238 8/31/2005 14:17:40: NDMP version 3 connection CONNECTED
af8 8/31/2005 14:17:52: JobEngine::LaunchJob
af8 8/31/2005 14:17:52: RunJobWithGuidAndServer( {2B293B2B-DF63-414C-A14E-5A1FD27C819C}, ) = 0
530 8/31/2005 14:17:52: Thread for job Backup 0050 ({2B293B2B-DF63-414C-A14E-5A1FD27C819C}) starting
530 8/31/2005 14:17:52: Boot drive is C:, status is 0
530 8/31/2005 14:17:52: SQL2_FindDrives - the default SQL Service is not running on BACKUP.
530 8/31/2005 14:17:52: SQL2_FindDrives - checking named instance BKUPEXEC.
530 8/31/2005 14:17:52: SQL2_FindDrives - Sorry, SQL 2000 Agent not autherized.
530 8/31/2005 14:17:52: No utility partitions found on any of the disks
530 8/31/2005 14:17:52: ENGSCRPT: ConvertDeviceName osId = 0Xe
530 8/31/2005 14:17:52: ENGSCRPT: IN - oldDeviceName = \\HBDC\F_Drive
530 8/31/2005 14:17:52: ENGSCRPT: OUT - newName = \\HBDC\F_Drive
530 8/31/2005 14:17:52: NDMP version 3 connection CONNECTED
530 8/31/2005 14:17:53:
dataStartBackup: ndmpSendRequest returned: 0x0, 0
530 8/31/2005 14:17:53: ????????????????›?4?????????????????
238 8/31/2005 14:17:53: DS_CloseSelectionService
d18 8/31/2005 14:17:53: DsWorkerThread terminating with exit code 0
530 8/31/2005 14:17:53: data halted: SUCCESSFUL
530 8/31/2005 14:17:53: NDMPEngine: Shutting down.


Job log error

0xa00084f9 - A communications failure has occurred between the Backup Exec job engine and the remote agent.


Fixes I have tried

TechNote ID: 263776
When backing up or restoring to the local media server or to a remote server with VERITAS Backup Exec (tm) 9.x, some resources are skipped, and the job fails with "A communications failure has occurred between the Backup Exec job engine and the remote agent."
http://support.veritas.com/docs/263776

TechNote ID: 256120
An error "A Communications Failure has occurred between the VERITAS Backup Exec job engine and the remote agent." message is reported in the job log while performing a backup of a remote server.
http://support.veritas.com/docs/256120

TechNote ID: 263503
The error "A communications failure has occurred between the Backup Exec job engine and the remote agent" is reported during a backup of a remote server.
http://support.veritas.com/docs/263503

TechNote ID: 262333
Backup jobs fail with the error "A communications failure has occurred between the Backup Exec job engine and the remote agent" or the jobs hang, and a debug of the Remote Agent shows "ERROR: ndmpdDataConnect: connect error: Bad file descriptor". The job log will be empty or have very little in it.
http://support.veritas.com/docs/262333

TechNote ID: 258331
When running a backup job, the backup fails with "A communications failure has occurred between the Backup Exec job engine and the remote agent."
http://support.veritas.com/docs/258331

[priya_khire]

Hello,

The remote agent is Backup exec by default uses port 10000 in order to connect to a remote server, so while backing up the remote server, you need to ensure that this port is kpet open so that beremote uses it.

As per the technote,http://support.veritas.com/docs/263776 mentioned by you, what are the ports ranges mentioned by you for backup exec as well as for the remote agent?

Download the TCPView utility from the following link and check that the port 10000 is listed as listening:
http://www.sysinternals.com/Utilities/TcpView.html

Also refer to the following technotes that might help resolve the issue:

Title: The error "Communications failure has occurred between job engine and the remote agent" is returned when backing up remote systems after applying Service Pack 2 for XP on an XP workstation hosting Backup Exec.
http://support.veritas.com/docs/273865

Hope tihs helps. If the issue persists, revert with details to the above questions.

Note : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.

Regards.

[Valentin_Stefan]

Thanks for the response. I have specified port 33000-34000 for the media server range and 36000-37000 for the remote range.
I have exceptions in the firewalls on both server and remote for port 10000 and for beremote.
I will trace using the tcp utility.

I do not believe I mentioned that I also have tried it with the Windows forewall disabled on both the server and the remote with the same results.

[Valentin_Stefan]

Ran the tcp viewer on both the server and remote machines. It lists Beremote on port 10000 as listening.

[Sharvari_Deshmu]

Hello,

1. Please check whether you can ping the remote server and vice versa?
2. Also in tools-options -network please change the network interface to use any available.


Thanks,

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.