You can setup a regular search in the TSM server actlog for the
following msgno (our specific data masked):

Date/Time                Message

--------------------
----------------------------------------------------------
05/05/2009 08:00:15      ANR1639I Attributes changed for node XXXXXXXX:
TCP Name   
                          from YYYYYYYY to ZZZZZZZZ, TCP Address from
10.99.99.999  
                          to 10.88.88.888, GUID from
99.99.99.99.99.99.11.dc.89.50.-
                          00.11.25.9c.28.2c to
88.88.88.88.88.88.11.dc.ab.82.00.1a-
                          .64.59.35.68. (SESSION: 1277591

Steve Schaub
Systems Engineer, Windows
BlueCross BlueShield of Tennessee


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Rhodes
Sent: Tuesday, May 05, 2009 8:12 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Cloned Win servers and multiple backups

This is a strange problem.

Once in a while, our Windows support team will clone a Windows server.
The
clone will have the exact same TSM setup as the source server.  I'm not
familiar with the Win BA client, but it seems it always has a nodename
line
for the dsm.sys file, so the clone reports to TSM server that it's the
same
node as the clone source.  They both appear to respond to the same
schedule.   This results in the new server performing good backups to
the
exact same node as the server that is the clone source.   The end result
seems to be to two different servers happily  backing up the same TSM
node.
Obviously what we get is a useless mess.  When they clone a system they
are
supposed to use a source without a TSM setup, or,  clean out the TSM
setup
right away, but sometimes this doesn't happen.  I've tried to find a way
to
detect this from the TSM server, but I'm not coming up with anything
obvious.   I'm interested if anyone else has fought this problem and
what
you've done.

Thanks!

Rick


-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.

-----------------------------------------------------
Please see the following link for the BlueCross BlueShield of Tennessee E-mail 
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm