That's what I have done in the past, rename, and start over.
 


Gary Lee
Senior System Programmer
Ball State University
 
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Keith Arbogast
Sent: Thursday, August 24, 2006 3:18 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Reuse node name

A Windows sys-admin wishes to replace an existing Windows 2000 server with a 
newly built Windows 2003 server, but using the old name for the new server.  We 
have been backing up the old server for some time.  He is adamant that he won't 
need to roll back to the old server, or restore any files from its backups.

I'm wondering what problems might occur when we start backing up files from the 
new client, for instance since the file systems on the old and new servers will 
be somewhat different.

Would the best way to avoid problems be to do a RENAME NODE of the old client?  
Then, register the new server with the old name and TSM won't have any records 
associated with that name to 'confuse' it.

If there is a simpler way, or if no intervention is required, I would be glad 
to know that.

Our TSM servers are at version 5.3.0.2.

Thank you,
Keith Arbogast

--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.5/426 - Release Date: 8/23/2006
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.5/426 - Release Date: 8/23/2006