Sure, it is easy and stable...
We've moved 8 servers in the past.

Once all done use
Syntax

>>-Set SERVername--server_name---------------------------------><

to change the name of your running TSM server...

Actually we just had new equipment at the new location and transported a
copy of the DB.
Backed it up at the old location, drove it to the new location, did a
restore db at the new location, pointed all the tsm clients to the new tsm
server and bounced their schedulers.
We basically moved each environment in less than 90 minutes (that was db
backup, drive, & db restore time).

Dwight
-----Original Message-----
From: Ochs, Duane [mailto:Duane.Ochs AT QG DOT COM]
Sent: Tuesday, October 08, 2002 10:35 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Renaming a TSM server.


Good Morning everyone,
 Due to some reallocating of resources it has become necessary to relocated
one of my TSM servers and Jukebox. Our company has historically prefixed
system names with the  geographical location of the installation.

I would like to change the name of the TSM server to comply with this naming
structure.

My plan:

Change the TSM server name and IP address to comply with the corporate
standard in the new plant.

Update my DNS to reflect the new system.

Change every client's server identification to point to the new IP.

Restart all schedulers and remote web services on all clients using this new
IP.


Questions:

Is this possible without damaging the DB ?

What other steps should be added ?

Has anyone done this before ?


Duane Ochs
Systems Administration
Quad/Graphics Inc.
414.566.2375