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.