I'm trying to get a remote agent on a Windows 2003 Std x64 machine working properly. When I enable agent advertising (to perform the backup on a dedicated network) the agent crashes upon startup. I have no problems with the agents on my 32-bit servers.
Here's the setup:
Media Server ------------------- Backup Exec 10d (10.1) Rev 5629.0
Agent ---------------------- Windows 2003 Std x64 Dell PowerEdge 2850 (Xeon w EM64T) Agent version - 10.1 Rev 5629.0
I've already applied the following patch: 10d (10.1.5629) Hotfix 1 - Extended 64-bit (x64) Remote Agent for Windows Servers (RAWS) (Adds support for remote computers running 64-bit extended chipset Windows operating systems) http://support.veritas.com/docs/280701
Verify if port 10000 is free on remote machine. Also check if RA service is running with Local system account.
Is Dr.Watson log generated on the remote machine?
Put the remote agent service on remote server in debug mode, rerun the backup and paste the relevant output here: http://seer.support.veritas.com/docs/254212.htm
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.
The RA service crashes immediately after it is started with "Error 1067: The process terminated unexpectedly". Therefore the backup log is irrelevant since it is indicative of no communications.
beremote.exe is bound to port 10000 , service is using 'Local System' acccount
I noticed in the registry that the HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Remote Agent for Windows Servers\Install\PROCESSOR_ARCHITECTURE value is set to AMD64... is that correct for an Intel machine?
Here's the RA Service Debug Log: -----------------------------------
01/18/06 09:42:49 Opening debug log C:\Program Files\VERITAS\Backup Exec\RAWS\logs\HS76887-D-beremote00.log 01/18/06 09:42:49 CleanupOrphanedSnapshots(). Lauching cleanup thread.. 01/18/06 09:42:49 CleanupOrphanedSnapshots(). Cleanup thread lauched. Exiting. 01/18/06 09:42:49 Process Windows Firewall is zero; no processing done. 01/18/06 09:42:49 FS_InitFileSys 01/18/06 09:42:49 loaded bedsnt5.dll 01/18/06 09:42:49 loaded bedssql2.dll 01/18/06 09:42:49 bedsxchg.dll could not be loaded: The specified module could not be found. 01/18/06 09:42:49 bedsxese.dll could not be loaded: The specified module could not be found. 01/18/06 09:42:49 bedsmbox.dll could not be loaded: The specified module could not be found. 01/18/06 09:42:49 loaded bedspush.dll 01/18/06 09:42:49 bedsnote.dll could not be loaded: The specified module could not be found. 01/18/06 09:42:49 bedsmdoc.dll could not be loaded: The specified module could not be found. 01/18/06 09:42:49 bedssps2.dll could not be loaded: The specified module could not be found. 01/18/06 09:42:49 loaded bedsupfs.dll 01/18/06 09:42:49 loaded bedsshadow.dll 01/18/06 09:42:49 bedsoffhost.dll could not be loaded: The specified module could not be found. 01/18/06 09:42:49 bedsdpm.dll could not be loaded: The specified module could not be found. 01/18/06 09:42:49 loaded bedscps.dll 01/18/06 09:42:49 bedsvx.dll could not be loaded: The specified module could not be found. 01/18/06 09:42:49 bedsorcl.dll could not be loaded: The specified module could not be found. 01/18/06 09:42:49 bedsagnt.dll could not be loaded: The specified module could not be found. 01/18/06 09:42:49 loaded bedssms.dll 01/18/06 09:42:49 loaded bedssmsp.dll 01/18/06 09:42:49 bedsra.dll could not be loaded: The specified module could not be found. 01/18/06 09:42:49 Initializing FSs é 01/18/06 09:42:49 Informational: BeDiskFind library 'BEDiskFind.dll' initialized in SHADOW::InitBeDiskFindHelperApis 01/18/06 09:42:49 Informational: Initializing the BeDisk library 'BeDisk.dll' in SHADOW::InitBeDiskHelperApis 01/18/06 09:42:49 Informational: BeDisk library 'BeDisk.dll' initialized in SHADOW::InitBeDiskHelperApis 01/18/06 09:42:49 Status Uknown (0x00000002) opening Cps registry key 'SOFTWARE\Wow6432Node\VERITAS\Backup Exec CPS' in CPS::InitCpsHelperApis:399 01/18/06 09:42:49 Informational: Initializing the Cps library 'C:\Program Files\VERITAS\Continuous Protection Server\Services\CPSVersion.dll' in CPS::InitCpsHelperApis:430 01/18/06 09:42:49 Status Uknown (0x0000007E) loading Cps library 'C:\Program Files\VERITAS\Continuous Protection Server\Services\CPSVersion.dll' in CPS::InitCpsHelperApis:437 01/18/06 09:42:49 Status Uknown (0x0000007E) initializing Cps library in CPS::InitFsys:103 01/18/06 09:42:49 ndmpRun 01/18/06 09:42:49 Listening on port 10000 01/18/06 09:42:49 NDMP Daemon Running 01/18/06 09:42:49 TCPSendAdvertisement: target=172.16.1.116 01/18/06 09:42:49 TCPSendAdvertisement: inet_addr(172.16.1.116) returned s_addr=172.16.1.116 01/18/06 09:42:49 TCPSendAdvertisement(HS76887-D) 172.16.1.114 01/18/06 09:42:49 TCPSendAdvertisement(HS76887-D) 192.168.1.114 01/18/06 09:42:52 Running... 'Q' to stop
It appears that you also have BECPS installed in your network, could you give us the details on this installation too.
NOTE : If we do not receive your reply within two business days, this post would be marked assumed answeredand would be moved toanswered questions pool.
I do not have BackupExec Continuous Protection running anywhere on the network. I assume that any log entries that mention it are merely because I'm using the BE 10d agent .