We're running a TSM Schedule to prompt TDP-Exchange 6.x to start a backup. It issues the C:\EXCINCR.CMD command.
Two Exchange servers.... one will run a TSM-Server initiated backup, one will not. The node manager claims that 1502 is the port-spec in the Exch DSM.OPT file and that both are configured identically. Port 1502 isn't listening, which would explain why a prompted backup would not start. But, ONE of the servers does backup via schedule. TELNET <ip> 1502 fails on both; we've checked firewalls and that traffic is passable. Thus, trying to see what TSM THINKS it is supposed to use. Have found that Q N F=D reports null value for low-level address on several nodes, regardless of BAclient or TDP client. ------------------------------------------------ Harold Vandeventer Systems Programmer State of Kansas - Office of Information Technology Services [email protected] (785) 296-0631 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Thomas Denier Sent: Tuesday, August 28, 2012 2:21 PM To: [email protected] Subject: Re: [ADSM-L] Schedule Port on client? -----Harold Vandeventer wrote: ----- >Somewhere, on the TSM Server side, is stored the port number the client >has specified in their DSM.OPT file. > >Wherever the prompted schedule keeps the value to call the node at its >IP and then port number. > >I'm trying to find that value. > >It'll be 1501 for the BAClient.... we're confused re the value for the >TDP-Exchange client. > >Just trying to prove a condition before I open a PMR. We get messages like: ANR2716E Schedule prompter was not able to contact client JUPITER using type 1 (10.123.123.123 1501). when the server is not able to make the network connection needed to start a scheduled event using prompted mode scheduling. Are you getting this kind of message for the Exchange client events? Thomas Denier, Thomas Jefferson University Hospital [Confidentiality notice:] *********************************************************************** This e-mail message, including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential or privileged information. Any unauthorized review, use, or disclosure is prohibited. If you are not the intended recipient, please contact the sender and destroy the original message, including all copies, Thank you. ***********************************************************************
