Hello Keith, You can use the TSM server "rename filespace" command to rename the data for the existing Windows 2000 server. If you rename them to patterns that will never exist on the new server the future backups will not change them. But the data will be available from the new cliet server for restores. At the end of the time period that you wish to keep the data, you can use the TSM "delete filespace" command to remove the data from the TSM server. If you are a belt and suspenders kind of person, you can create an export or backupset to save the data before deleting.
len -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Keith Arbogast Sent: Thursday, August 24, 2006 3:18 PM To: ADSM-L@VM.MARIST.EDU 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