Video Screencast Help

Add server to 'Favorite Resources'

Created: 17 Jul 2013 • Updated: 17 Jul 2013 | 19 comments

Hello!

I have Server CASO (BKP-003-SVR) & managed media server (BKP-004-SVR) Backup EXEC 2010R3

I changed the NDMP ports to 9000 Server SQL-002-SVR .

When I add the server (SQL-002-SVR) to the 'Favorite Resources' to Server CASO, server is not added.  When I add the server (SQL-002-SVR) to the 'Favorite Resources' to managed media server, server is added.

Error

BEREMOTE: [07.17.13 10:53:46] [0000]     07/17/13 10:53:46 [fsys\oracle]        - RMAN_EnumSelfDLE: AgentConfig GetOracleDBNames returned error. If Oracle Agent is installed, please run AgentConfig.
BEREMOTE: [07.17.13 10:53:46] [0000]     07/17/13 10:53:46 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: EnumSelfDLE for file system 14 returned 0(0x0) and 0 DLEs
BEREMOTE: [07.17.13 10:53:46] [0000]     07/17/13 10:53:46 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: EnumSelfDLE for file system 37 returned 0(0x0) and 0 DLEs
BEREMOTE: [07.17.13 10:53:46] [0000]     07/17/13 10:53:46 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: EnumSelfDLE for file system 39 returned 0(0x0) and 0 DLEs
BEREMOTE: [07.17.13 10:53:46] [0000]     07/17/13 10:53:46 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: EnumSelfDLE for file system 42 returned -536805816(0xE000FE48) and 0 DLEs
BEREMOTE: [07.17.13 10:53:46] [0000]     07/17/13 10:53:46 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: Security is enabled!!!
BEREMOTE: [07.17.13 10:53:46] [0000]     07/17/13 10:53:46 [ndmp\ndmpcomm]      - GetCertificateDataFolderPath: Not checking for cluster.
BEREMOTE: [07.17.13 10:53:46] [0000]     07/17/13 10:53:46 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: connect to target=BKP-003-SVR port=6101 failed
BEREMOTE: [07.17.13 10:53:46] [0000]     07/17/13 10:53:46 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: Security is enabled!!!
BEREMOTE: [07.17.13 10:53:46] [0000]     07/17/13 10:53:46 [ndmp\ndmpcomm]      - GetCertificateDataFolderPath: Not checking for cluster.
BEREMOTE: [07.17.13 10:53:46] [0000]     07/17/13 10:53:46 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: connect to target=BKP-003-SVR port=6101 failed
BEREMOTE: [07.17.13 10:53:46] [0000]     07/17/13 10:53:46 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: Security is enabled!!!
BEREMOTE: [07.17.13 10:53:46] [0000]     07/17/13 10:53:46 [ndmp\ndmpcomm]      - GetCertificateDataFolderPath: Not checking for cluster.
BEREMOTE: [07.17.13 10:53:46] [0000]     07/17/13 10:53:46 [nrds]               - ConnectToServerEndPoint: dest=BKP-004-SVR, service=6101
BEREMOTE: [07.17.13 10:53:47] [0000]     07/17/13 10:53:46                      - SSL connection using version TLSv1
BEREMOTE: [07.17.13 10:53:47] [0000]     07/17/13 10:53:46                      - SSL connection using cipher AES256-SHA
BEREMOTE: [07.17.13 10:53:47] [0000]     07/17/13 10:53:46 [nrds]               - CreateConnection type=0 on socket 1220 via BESocket OK
BEREMOTE: [07.17.13 10:53:47] [0000]     07/17/13 10:53:46 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: send of SQL-002-SVR type 7 subtype 2 to target=BKP-004-SVR port=6101 succeeded
BEREMOTE: [07.17.13 10:53:47] [0000]     07/17/13 10:53:46 [BESocket]           - @@@@@@@MyCloseSocket called with sockfd = 1220(0x4c4) retval = 0
BEREMOTE: [07.17.13 10:53:47] [0000]     07/17/13 10:53:46 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: Security is enabled!!!
BEREMOTE: [07.17.13 10:53:47] [0000]     07/17/13 10:53:46 [ndmp\ndmpcomm]      - GetCertificateDataFolderPath: Not checking for cluster.
BEREMOTE: [07.17.13 10:53:47] [0000]     07/17/13 10:53:46 [nrds]               - ConnectToServerEndPoint: dest=BKP-004-SVR, service=6101
BEREMOTE: [07.17.13 10:53:47] [0000]     07/17/13 10:53:47                      - SSL connection using version TLSv1
BEREMOTE: [07.17.13 10:53:47] [0000]     07/17/13 10:53:47                      - SSL connection using cipher AES256-SHA
BEREMOTE: [07.17.13 10:53:47] [0000]     07/17/13 10:53:47 [nrds]               - CreateConnection type=0 on socket 1280 via BESocket OK
BEREMOTE: [07.17.13 10:53:47] [0000]     07/17/13 10:53:47 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: send of SQL-002-SVR type 7 subtype 2 to target=DHO-BKP-004-SVR.fuib.com port=6101 succeeded
BEREMOTE: [07.17.13 10:53:47] [0000]     07/17/13 10:53:47 [BESocket]           - @@@@@@@MyCloseSocket called with sockfd = 1280(0x500) retval = 0
BEREMOTE: [07.17.13 10:53:47] [0000]     07/17/13 10:53:47 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: Retrying in 60 seconds
BEREMOTE: [07.17.13 10:54:47] [0000]     07/17/13 10:54:47 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: Security is enabled!!!
BEREMOTE: [07.17.13 10:54:47] [0000]     07/17/13 10:54:47 [ndmp\ndmpcomm]      - GetCertificateDataFolderPath: Not checking for cluster.
BEREMOTE: [07.17.13 10:54:47] [0000]     07/17/13 10:54:47 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: connect to target=BKP-003-SVR port=6101 failed
BEREMOTE: [07.17.13 10:54:47] [0000]     07/17/13 10:54:47 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: Security is enabled!!!
BEREMOTE: [07.17.13 10:54:47] [0000]     07/17/13 10:54:47 [ndmp\ndmpcomm]      - GetCertificateDataFolderPath: Not checking for cluster.
BEREMOTE: [07.17.13 10:54:47] [0000]     07/17/13 10:54:47 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: connect to target=BKP-003-SVR port=6101 failed
BEREMOTE: [07.17.13 10:54:47] [0000]     07/17/13 10:54:47 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: Retrying in 60 seconds
MONITORI: [07.17.13 10:54:54] [0000]     Script 'MOM Backward Compatibility Service State Monitoring Script' completed with the following output: (empty)
 

Updates in CASO and managed media server identical.

Operating Systems:

Comments 19 CommentsJump to latest comment

Jaydeep S's picture

Have you tried to add that server with ipaddress on the CASO? See if that works. Also, are you able to browse to that server using a selection list on CASO.

EvgeniyL's picture

SBE write "The windows system 'sql-002-svr' was added successfully......" but server not added to favorite resource

Sush...'s picture

Hello EvegenyL,

This issue seems to be as addressed in following technote:

http://www.symantec.com/docs/TECH168154 : Remote Servers do not show up under 'Favorite Resources' in the backup selection list after upgrade to Backup Exec 2010 R3

As per the resolution given in he technote please install Hotfix 180429 of Backup Exec 2010 R3 Revision 5204 which can be downloaded from following technote:

http://www.symantec.com/docs/TECH180429 :  Backup Exec 2010 R3 Revision 5204 Hotfix 180429

Also please note that this hotfix is dependent on Backup Exec 2010 R3 revision 5204 Service Pack 2. So you will have to install SP2 first.

Regards,
-Sush...

Hope this piece of Information Helps you... and if it does then mark this response as Solution....!!!

Sush...'s picture

Hello EvegenyL,
Installing HF 161270 will give errors as it was released before SP2 and you have aleady have SP2 installed on the server with other HFs released after SP2. All HFs released before SP2 are included in SP2.

Coming back to this issue... Are you able to access the resources of that remote server from other nodes in the selection list?? Like Windows network, Domains....??

If not then do you get any errors about Trust Relationship not enabled? If there are trust relationship errors then please Enable Trust by right clicking on the remote server and choosing the option Enable Trust.

Regards,
-Sush...

Hope this piece of Information Helps you... and if it does then mark this response as Solution....!!!

EvgeniyL's picture

I see this server, but server seen as not install agent for this server

 

Colin Weaver's picture

This needs to be fixed

BEREMOTE: [07.17.13 10:54:47] [0000]     07/17/13 10:54:47 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: connect to target=BKP-003-SVR port=6101 failed
 

Port 6101 will be listening on both media servers, you should be able to telnet from the rmote setrver to port 6101 on both media servers.

The remote agent needs to be able to talk tot this port, it if cannot then you either have a firewall affecting things or you have not configured the TLS trust relationships between both media servers and the remote server correctly.

You may have to use Vxmon (Remote Agent Utility) on the remote server to get rid of the current certificates against the server that does not work and the publishing entry for the same server and then add it back in

 

 

 

EvgeniyL's picture

Managed media server (BKP-004-SVR) sees this server and allows me to run jobs  associated with server SQL-002-SVR.

Colin Weaver's picture

Exactly - and the port 6101 failed to connect sesms to be against teh CASO where you have the problem

 

Port 6101 access needs to work to all media servers where you want to see that object in Favorite Resources.

 

You will also need the SQL Agent license on both servers in order to create job against SQL on the CASO server even if the Managed server will be the server running the job.

EvgeniyL's picture

I  have access telnet from remote server to CASO

Vxmon i  do not see trust relationships with CASO? i sees only trust relationships with managed media server. 

Colin Weaver's picture

OK so in the Publishing tab of vxmon on the remote server, remoev anty reference to the CASO ssrevr (or the IP address of the CASO server) and then add it backin - this process should also cerate a certificate for the CASO server

Once you have done this then restart the remote agent (with the logging enabled that you added to your earlier posts) and see if this failure to connect to port 6101 is still happening.

 

EvgeniyL's picture

After delete in vxmon referents to managed server and CASO i restart all the remote agent.

now I can not add the server is not on the CASO and managmet server.

Sush...'s picture

Hello EvgeniyL,
   From both the servers (CASO and MMS) go to the selection list and then right click on the remote server which needs to be backed up and select "Enable Trust". By doing this it will create certificate files on the remote server from both CASO and MMS.

Regards,
-Sush...

Hope this piece of Information Helps you... and if it does then mark this response as Solution....!!!

EvgeniyL's picture

On server CASO

BENETNS:  [07.17.13 15:51:52] [0000]     07/17/13 15:51:52 [ndmp\ndmpcomm]      - Could not resolve the "bews-ndmp" or the "ndmp" service, error code: 10109, using port 10000
 

Sush...'s picture

Hello EvgeniyL,
   This is generic error when it fails to connect in initial attempts but later connects in attempts after that. To confirm that it gets connected you can search for the line "Control connection establised" with those 2 IP address provided.

Regards,
-Sush...

Hope this piece of Information Helps you... and if it does then mark this response as Solution....!!!

EvgeniyL's picture

 Select "Enable Trust" this Establish trust relationship?  i selected Establish trust relationship and my console freezen.

Colin Weaver's picture

I think this has probably gone as far as it can on the forums, please log a formal support case.

EvgeniyL's picture

I'm waiting for reboot server. After changing the port ndmp from 10000 to 9000 I did not reboot the server.

Maybe this will solve the problem.