Until you get some admin that installs TSM and copies the DSM.OPT from a client 
that has the NODENAME specified. Once the
CAD/Scheduler starts....that nodename now points to this new box and the real 
NODENAME isn't getting backups anymore. I always pay
attention to these messages as they could be a mis-configuration issue. If it's 
a cluster, then I (probably) don't care. But
anything else is something I want to look in to.

Bill Boyer
"Experience is a comb nature gives us after we go bald." - ??


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Gill, Geoffrey L.
Sent: Thursday, May 03, 2007 10:44 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Client's attributes changing

>Is this normal behavior when a server has 2 IP addresses to switch
>attributes?  Or does this cause a delay?  And if this is an issue, is
>there a way to resolve this so that it doesn't occur?

We see this on clusters when a cluster node has moved/failed from one node to 
another. If a backup is in progress when it fails over
then sure there would be a delay in restart until the resource is back online. 
If nothing is going on then there are no worries. It
does seem like just mindless noise in the logs, since as far as I know TSM 
could care less about this really. The data still comes
from the cluster node and when restoring it makes no difference what IP the 
node has, or was for that matter, what you really need
is the password, if it asks when you connect.


Geoff Gill
TSM Administrator
PeopleSoft Sr. Systems Administrator
SAIC M/S-G1b
(858)826-4062
Email: geoffrey.l.gill AT saic DOT com