ADSM-L

Re: Question: Impact of changing TCPPort.

2006-07-06 09:48:08
Subject: Re: Question: Impact of changing TCPPort.
From: Michael Bartl <michael.bartl AT SPACE DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 6 Jul 2006 15:33:01 +0200
Larry,
changing the TCP-Port doesn't have any impact on the objects backed up.
As it is still the old filesystem on the old server and the old TSM
client software, you won't see any impact.

TSM sends a list of backed up objects from the TSM server to the client
node. The BAClient checks this list against the real filesystem and
sends the changes (new, updated, deleted) to the server. The TCPPort
doesn't have any influence in this mechanism (I'm glad).

Best regards,
Michael

Mcnutt, Larry E. wrote:
Hello TSM list,

TSM 5.3.3.0
AIX 5.3.0 ML4

I have a TSM instance that is using the default TCPPort (1500).  I need
to change it to use a new TCPPort.  This will require a coordinated
change on the TSM server and all the clients.  What I want to verify is
that this change will not force a new full backup on all the clients.  I
have not been able to find any documentation that explains the impact of
changing the TCPPort.  Any pointers or experience will be appreciated.

Thank you,
Larry McNutt
The Timken Company
--
Michael H. Bartl                              Mail: mbartl AT space DOT net
SpaceNet AG                                   Tel:  089 / 32356-151
Joseph-Dollinger-Bogen 14                     Fax:  089 / 32356-299
D-80807 Muenchen                              http://www.space.net/

Genug von Viren und Spam? SpaceNet_Mail hilft Ihnen - lesen Sie, wie
SpaceNet_Mail beim Muenchener Verkehrs- und Tarifverbund erfolgreich
eingesetzt wird: http://www.space.net/mvvnews/index.html

Was wir sonst noch fuer Sie tun koennen, finden Sie unter:
http://www.space.net/

<Prev in Thread] Current Thread [Next in Thread>