I would definitely go the route of renaming node, and creating node with old name, as you mention below. That's what I do when this comes up. The database will not be 'confused', as it ties the filespaces, etc. to the newly renamed node's name (for example, I use "rename node node_name old_node_name", and then "register node node_name...")
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Keith Arbogast Sent: Thursday, August 24, 2006 2: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 ----------------------------------------- Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information.
