On Jun 15, 2010, at 1:13 PM, Avy Wong wrote:

> Just curious Richard, what are the side effects? It is a one time thing and
> at the time I was working with and IBM with a PMR number, she did give me a
> document to follow it, but also suggests a quick way to do it is put the
> nodename to point to the target node on the dsm.opt, of course whatever it
> was, make sure changing it back.

A TSM Support representative should not suggest doing things like that.  The 
effects are summarized in ADSM QuickFacts.
Remember that the TSM server tracks the network address used by a client, which 
at a minimum can obliterate prior record of where on the network a client was.  
The nodename is also used for storing the access password on the client.  Given 
that all systems these days are multi-user, it's all too easy for some other 
person on the system to perform a backup while the other nodename is in place, 
with all the obvious ramifications.  Someone trying to retrieve or restore data 
while the other nodename is in place is going to run into problems.  A 
happenstance backup from a node-appropriated client whose software happened to 
at a higher level that the original nodename can render storage pool data no 
longer accessible to the original nodename.
This is why VIRTUALNodename is provided.

    Richard Sims    http://people.bu.edu/rbs/