Hi Mario, Looks like some detailed double-checking of the config is required - here goes!
O - As Marcel points out, first you'll need to have an administrative user registered with the same password upon the source and target TSM Server instances. O - Next, the High Level Address (HLA) of the target server needs (visible in Q SERVER) to be resolvable/pingable from your shell/OS prompt on the source server. O - Finally, the Low Level Address (LLA) of the target server (visible in Q SERVER) needs to be set to the TCPPort upon which the target server is listening (e.g. visible from Q OPT output on target server). >>> What about the TCP Port (lladdress)? I´ve configured different tcp ports in each server....is that correct? Your source and target TSM Server instances can run on the same TCPPORT if they're running on different physical servers. If all of these are in place and there aren't any other factors getting in the way, PING SERVER commands should work and you'll have a platform for TSM Server to Server operations. HTH - let us know how you get on. //DMc London, UK - going to bed. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Mario Behring Sent: 17 July 2010 00:59 To: [email protected] Subject: Re: [ADSM-L] Export server error Hi David, No...it is not successful...check the output below...I am calling the servers TSM_SOURCE and TSM_TARGET to make this easier: tsm: TSM_SOURCE>ping server tsm_target ANR1705W Ping for server 'TSM_TARGET' was not able to establish a connection. ANS8001I Return code 4. The same happens the other way around. What about the TCP Port (lladdress)? I´ve configured different tcp ports in each server....is that correct? tsm: TSM_SOURCE>q server Server Comm. High-level Low-level Days Server Name Method Address Address Since Password -------- ------ ------------- --------- ------ -------- TSM_TARGET TCPIP xx.xx.xx.xx 1919 <1 Yes tsm: TSM_TARGET>q server Server Comm. High-level Low-level Days Server Name Method Address Address Since Password -------- ------ ------------- --------- ------ -------- TSM_SOURCE TCPIP xx.xx.xx.xx 1500 <1 Yes Regards, Mario ________________________________ From: David McClelland <[email protected]> To: [email protected] Sent: Fri, July 16, 2010 7:56:06 PM Subject: Re: Export server error Hi Mario, What does a `PING SERVER TSM_DEDALUS` from the source TSM Server admin CLI give you - is this successful? Cheers, //David Mc London, UK -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Mario Behring Sent: 16 July 2010 22:44 To: [email protected] Subject: [ADSM-L] Export server error Hi list, I am trying to export all data from a TSM Server to a new one. Both servers are TSM 5.5.0.0 servers. I have defined the TARGET server on the SOURCE and vice versa, specifying a password and TCP Port (lladdress) for both servers. When I issue the EXPORT SERVER command with the PREVIEWIMPORT set to YES I get the following error on the SOURCE server: 07/17/2010 18:29:44 ANR2017I Administrator ADMIN issued command: EXPORT SERVER filed=all previewi=y tos=tsm_dedalus (SESSION: 18790) 07/17/2010 18:29:44 ANR0984I Process 254 for EXPORT SERVER started in the BACKGROUND at 18:29:44. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:44 ANR0609I EXPORT SERVER started as process 254. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:44 ANR0402I Session 18873 started for administrator ADMIN (Server) (Memory IPC). (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:45 ANR8214E Session open with 200.143.2.89 failed due to connection refusal. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:45 ANR0561E EXPORT SERVER: Process aborted - sign on to server, TSM_SERVER, failed. (SESSION: 18790, PROCESS: 254) The problem is that the TARGET server is refusing the connection....but why?? NO messages appear in the ACTLOG at the TARGET server. What could be wrong? What am I missing? Regards, Mario
