canuckconsulting
asked on
Backup Exec unable to connect to Remote Windows Agent
Hello,
We have Backup Exec 2010 installed on a file server running Windows 2003 server x86 connected to a tape drive. We have installed the Remote Windows Agent installed on another file server running Windows 2008 server x64. We installed it both by "pushing" it from the 2003 server and from the disk.
Regardless of how we install the remote agent when we start a new back up job Backup Exec does not detect the remote agent. We have disabled the firewall on both machines to test but still no luck. I would be very grateful for advice on how to get Backup Exec to detect the Windows Agent.
We have Backup Exec 2010 installed on a file server running Windows 2003 server x86 connected to a tape drive. We have installed the Remote Windows Agent installed on another file server running Windows 2008 server x64. We installed it both by "pushing" it from the 2003 server and from the disk.
Regardless of how we install the remote agent when we start a new back up job Backup Exec does not detect the remote agent. We have disabled the firewall on both machines to test but still no luck. I would be very grateful for advice on how to get Backup Exec to detect the Windows Agent.
Try to install from Disk by an local admin. I had this issue with using the domain admin. Maybe helps???
check it may be useful to you
http://www.symantec.com/business/support/index?page=content&id=TECH66221
http://www.symantec.com/business/support/index?page=content&id=TECH66221
hehe
this is a funny one....
on the remote system please disable the UAC. And try again I've seen this one before...
http://technet.microsoft.com/en-us/library/cc709691(WS.10).aspx
Cooledit
this is a funny one....
on the remote system please disable the UAC. And try again I've seen this one before...
http://technet.microsoft.com/en-us/library/cc709691(WS.10).aspx
Cooledit
Things to try / check:
Ensure you are installing the X64 agent on the X64 server.
Can you browse to the remote server from the other by running \\servername
Ensure the Backup Exec Remote Agent is running on the target server
Check Event Viewer on the target server for any errors on installation
Ensure the remote agent is publishing to the media (backup) server by double clicking the Remote Agent icon and check the 'Publishing' tab. You should see the name or ip of the Media Server.
Ensure you are installing the X64 agent on the X64 server.
Can you browse to the remote server from the other by running \\servername
Ensure the Backup Exec Remote Agent is running on the target server
Check Event Viewer on the target server for any errors on installation
Ensure the remote agent is publishing to the media (backup) server by double clicking the Remote Agent icon and check the 'Publishing' tab. You should see the name or ip of the Media Server.
One more thing, try enabling file and print sharing on the 2008 Server if you can browse to it using \\Servername
ASKER
Wilder_Admin:
Uninstalled agent and reinstalled from disk with local admin account. No difference.
sreedhar2u:
The agent log does not give a failure. In fact it looks like it succeeds as below:
[1276] 04/11/11 14:51:56 [nrds] - ConnectToServerEndPoint: dest=10.188.8.3, service=6101
[1276] 04/11/11 14:51:56 [nrds] - CreateConnection type=0 on socket 1216 via BESocket OK
[1276] 04/11/11 14:51:56 [ndmp\ndmpcomm] - NrdsAdvertiserThread: send of site-FS01.emea.company.com type 7 subtype 2 to target=10.188.8.3 port=6101 succeeded
[1276] 04/11/11 14:51:56 [BESocket] - @@@@@@@MyCloseSocket called with sockfd = 1216(0x4c0) retval = 0
[1276] 04/11/11 14:51:56 [ndmp\ndmpcomm] - NrdsAdvertiserThread: advertisement cycle complete. Waiting 1 minutes before advertising again.
[4296] 04/11/11 14:52:01 [ndmp\ndmpcomm] - NrdsAdvertiserThread: negative (purge) advertisement cycle started.
[4296] 04/11/11 14:52:01 [ndmp\ndmpcomm] - NrdsAdvertiserThread: no purge is pending.
[4296] 04/11/11 14:52:01 [ndmp\ndmpcomm] - NrdsAdvertiserThread: negative (purge) advertisement cycle complete. Waiting 1 minutes before advertising again.
[1276] 04/11/11 14:52:56 [ndmp\ndmpcomm] - NrdsAdvertiserThread: advertisement cycle started.
[1276] 04/11/11 14:52:56 [fsys\ntfs\mnet] - Informational: Restrict Anonymous Support is enabled
[1276] 04/11/11 14:52:56 [fsys\ntfs\mnet] - creating DLE for local machine
cooledit:
UAC was already disabled.
-Juddy-:
-x64 is definitely version installed.
-Yes can browse both ways by server name
-Backup Exec Remote Agent is running and logging
-No errors, Windows installer seemed to complete normally
-Publishing info set up properly on agent
-File and print sharing is on
Uninstalled agent and reinstalled from disk with local admin account. No difference.
sreedhar2u:
The agent log does not give a failure. In fact it looks like it succeeds as below:
[1276] 04/11/11 14:51:56 [nrds] - ConnectToServerEndPoint: dest=10.188.8.3, service=6101
[1276] 04/11/11 14:51:56 [nrds] - CreateConnection type=0 on socket 1216 via BESocket OK
[1276] 04/11/11 14:51:56 [ndmp\ndmpcomm] - NrdsAdvertiserThread: send of site-FS01.emea.company.com
[1276] 04/11/11 14:51:56 [BESocket] - @@@@@@@MyCloseSocket called with sockfd = 1216(0x4c0) retval = 0
[1276] 04/11/11 14:51:56 [ndmp\ndmpcomm] - NrdsAdvertiserThread: advertisement cycle complete. Waiting 1 minutes before advertising again.
[4296] 04/11/11 14:52:01 [ndmp\ndmpcomm] - NrdsAdvertiserThread: negative (purge) advertisement cycle started.
[4296] 04/11/11 14:52:01 [ndmp\ndmpcomm] - NrdsAdvertiserThread: no purge is pending.
[4296] 04/11/11 14:52:01 [ndmp\ndmpcomm] - NrdsAdvertiserThread: negative (purge) advertisement cycle complete. Waiting 1 minutes before advertising again.
[1276] 04/11/11 14:52:56 [ndmp\ndmpcomm] - NrdsAdvertiserThread: advertisement cycle started.
[1276] 04/11/11 14:52:56 [fsys\ntfs\mnet] - Informational: Restrict Anonymous Support is enabled
[1276] 04/11/11 14:52:56 [fsys\ntfs\mnet] - creating DLE for local machine
cooledit:
UAC was already disabled.
-Juddy-:
-x64 is definitely version installed.
-Yes can browse both ways by server name
-Backup Exec Remote Agent is running and logging
-No errors, Windows installer seemed to complete normally
-Publishing info set up properly on agent
-File and print sharing is on
And the server in question is added to your 'selection list'? If so, can you expand the + symbol next to it?
ASKER
I found that if I select the "Install Agents and Media Servers on Other Servers" option it actually detects the agent as shown in this screen shot:
I also started the Debug Monitor located under support utilities and it shows the client connecting. Does this log help:
BESERVER: [11/04/11 14:58:57] [0584] -1 Client requested key (1302530492).
BESERVER: [11/04/11 14:58:57] [5248] "Cluster" key does not appear to be present in the registry
BESERVER: [11/04/11 14:58:57] [5248] Failed to open Microsoft cluster ()
BESERVER: [11/04/11 14:58:57] [5248] VCS cluster keys do not appear to be present in the registry
BESERVER: [11/04/11 14:58:57] [5248] Failed to open VCS cluster ()
BESERVER: [11/04/11 14:58:57] [5248] 01 Server Configuration: Client added: 6
BESERVER: [11/04/11 14:58:57] [5248] -1 Client 'GBCRN03' connected('','EMEA\ukcra.d el.sgoodwi n'): 0x5e2ee88
BESERVER: [11/04/11 14:58:57] [5248] 01 Server Configuration: Client removed: 5
BESERVER: [11/04/11 14:58:57] [5248] -1 Client 'GBCRN03' Disconnected:0x5e2ee88
BESERVER: [11/04/11 14:59:57] [2216] -1 Client requested key (1302530552).
BESERVER: [11/04/11 14:59:57] [5248] 01 Server Configuration: Client added: 6
BESERVER: [11/04/11 14:59:57] [5248] -1 Client 'GBCRN03' connected('','EMEA\ukcra.d el.sgoodwi n'): 0x5eb2f90
BESERVER: [11/04/11 14:59:57] [5248] 01 Server Configuration: Client removed: 5
BESERVER: [11/04/11 14:59:57] [5248] -1 Client 'GBCRN03' Disconnected:0x5eb2f90
BESERVER: [11/04/11 15:00:57] [3496] -1 Client requested key (1302530612).
BESERVER: [11/04/11 15:00:57] [5248] "Cluster" key does not appear to be present in the registry
BESERVER: [11/04/11 15:00:57] [5248] Failed to open Microsoft cluster ()
BESERVER: [11/04/11 15:00:57] [5248] VCS cluster keys do not appear to be present in the registry
BESERVER: [11/04/11 15:00:57] [5248] Failed to open VCS cluster ()
BESERVER: [11/04/11 15:00:57] [5248] 01 Server Configuration: Client added: 6
BESERVER: [11/04/11 15:00:57] [5248] -1 Client 'GBCRN03' connected('','EMEA\ukcra.d el.sgoodwi n'): 0x5eb2f90
BESERVER: [11/04/11 15:00:57] [5248] 01 Server Configuration: Client removed: 5
BESERVER: [11/04/11 15:00:57] [5248] -1 Client 'GBCRN03' Disconnected:0x5eb2f90
BESERVER: [11/04/11 15:01:57] [0584] -1 Client requested key (1302530672).
BESERVER: [11/04/11 15:01:57] [5248] 01 Server Configuration: Client added: 6
BESERVER: [11/04/11 15:01:57] [5248] -1 Client 'GBCRN03' connected('','EMEA\ukcra.d el.sgoodwi n'): 0x5e86f90
BESERVER: [11/04/11 15:01:57] [5248] 01 Server Configuration: Client removed: 5
BESERVER: [11/04/11 15:01:57] [5248] -1 Client 'GBCRN03' Disconnected:0x5e86f90
I also started the Debug Monitor located under support utilities and it shows the client connecting. Does this log help:
BESERVER: [11/04/11 14:58:57] [0584] -1 Client requested key (1302530492).
BESERVER: [11/04/11 14:58:57] [5248] "Cluster" key does not appear to be present in the registry
BESERVER: [11/04/11 14:58:57] [5248] Failed to open Microsoft cluster ()
BESERVER: [11/04/11 14:58:57] [5248] VCS cluster keys do not appear to be present in the registry
BESERVER: [11/04/11 14:58:57] [5248] Failed to open VCS cluster ()
BESERVER: [11/04/11 14:58:57] [5248] 01 Server Configuration: Client added: 6
BESERVER: [11/04/11 14:58:57] [5248] -1 Client 'GBCRN03' connected('','EMEA\ukcra.d
BESERVER: [11/04/11 14:58:57] [5248] 01 Server Configuration: Client removed: 5
BESERVER: [11/04/11 14:58:57] [5248] -1 Client 'GBCRN03' Disconnected:0x5e2ee88
BESERVER: [11/04/11 14:59:57] [2216] -1 Client requested key (1302530552).
BESERVER: [11/04/11 14:59:57] [5248] 01 Server Configuration: Client added: 6
BESERVER: [11/04/11 14:59:57] [5248] -1 Client 'GBCRN03' connected('','EMEA\ukcra.d
BESERVER: [11/04/11 14:59:57] [5248] 01 Server Configuration: Client removed: 5
BESERVER: [11/04/11 14:59:57] [5248] -1 Client 'GBCRN03' Disconnected:0x5eb2f90
BESERVER: [11/04/11 15:00:57] [3496] -1 Client requested key (1302530612).
BESERVER: [11/04/11 15:00:57] [5248] "Cluster" key does not appear to be present in the registry
BESERVER: [11/04/11 15:00:57] [5248] Failed to open Microsoft cluster ()
BESERVER: [11/04/11 15:00:57] [5248] VCS cluster keys do not appear to be present in the registry
BESERVER: [11/04/11 15:00:57] [5248] Failed to open VCS cluster ()
BESERVER: [11/04/11 15:00:57] [5248] 01 Server Configuration: Client added: 6
BESERVER: [11/04/11 15:00:57] [5248] -1 Client 'GBCRN03' connected('','EMEA\ukcra.d
BESERVER: [11/04/11 15:00:57] [5248] 01 Server Configuration: Client removed: 5
BESERVER: [11/04/11 15:00:57] [5248] -1 Client 'GBCRN03' Disconnected:0x5eb2f90
BESERVER: [11/04/11 15:01:57] [0584] -1 Client requested key (1302530672).
BESERVER: [11/04/11 15:01:57] [5248] 01 Server Configuration: Client added: 6
BESERVER: [11/04/11 15:01:57] [5248] -1 Client 'GBCRN03' connected('','EMEA\ukcra.d
BESERVER: [11/04/11 15:01:57] [5248] 01 Server Configuration: Client removed: 5
BESERVER: [11/04/11 15:01:57] [5248] -1 Client 'GBCRN03' Disconnected:0x5e86f90
hi, there
pls verify the UAC as mentioned a few postings earlier...
Cooledit
pls verify the UAC as mentioned a few postings earlier...
Cooledit
ASKER
cooledit: did and noted that it was off in my reply above.
Cheers,
Cheers,
ok, did not see that sorry..
have you tried telnet \\ip address of remote system port 10000
as this is the default of Backup Exec.
Cooledit
have you tried telnet \\ip address of remote system port 10000
as this is the default of Backup Exec.
Cooledit
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have just tried a telnet from server to agent and it did answer though I was unable to log in (unprintable characters displayed).
The result of netstat -ona on the server showed the port to have status listening.
The result of netstat -ona on the server showed the port to have status listening.
ASKER
Ended up having Symantic do this but thank you for help