I personally would believe your Windows Admin (after all, it's his data, not yours) and just do a delete filespace on all the data associated with that node. That way you don't have to redefine the node and all the schedule definitions are intact. Your job is done, you just need to wait for him to reload the client on his newly built machine. Steve Schaub Systems Engineer, WNI BlueCross BlueShield of Tennessee 423-535-6574 (desk) 423-785-7347 (cell)
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Keith Arbogast Sent: Thursday, August 24, 2006 3:18 PM To: [email protected] Subject: [ADSM-L] 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 Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
