You didn't say, but I presume you are still backing it up to the same TSM server, even though you are moving it to another data center?
If so, this is no problem. You aren't changing the TSM node name, just the IP. When you first bring it up you might want to bring up the TSM client linemode and issue a 'q sched' just to make sure it connects just fine, and doesn't have problems authenticating. It might ask for your password in this case, I am not sure. The TSM activity log will produce a message one time that says that the IP address for the server is changing, but that is just informational, nothing to worry about. Best Regards, John D. Schneider Sr. System Administrator - Storage Sisters of Mercy Health System 3637 South Geyer Road St. Louis, MO. 63127 Email: [EMAIL PROTECTED] Office: 314-364-3150, Cell: 314-486-2359 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Keith Arbogast Sent: Tuesday, May 08, 2007 9:27 AM To: [email protected] Subject: [ADSM-L] New DNS domain, same host name A sys admin here is moving a Linux virtual machine (vm) to a different VMWare ESX server at another data center. The virtual machine will have a new ip number and hardware address. It will have a different domain name, but the same host name. That is, wsa350.uits.indiana.edu will become wsa350.uits.iupui.edu. The vm is registered with a TSM node name of wsa350. We prefer not to change that. Session Initiation is set to 'ClientOrServer'. The sys admin wants to keep the existing backups of the vm. Is this a non-issue? Will starting the client scheduler after the move be enough to reestablish the TCP/IP Name, TCIP/IP Address and Globally Unique ID for the node? Is any other action needed to keep the old backups useable by the node? With my thanks, Keith Arbogast Indiana University
