Already updated all the passwords for this move. Next up, Production. UGH!
No we don't use the hostname as the TSM ServerName. But I didn't want to have two of the same TSM ServerNames out there, knowing I'd at some point make a mistake of running something on one that was meant to be run on the other.
The old server still backs up production. (it was backing up both dev and production). The new server is now backing up dev. And in a few weeks, it will also take production, at which time I'll be updating passwords again, but for more clients this time. Not pretty at all. Yes I lost plenty of sleep, for this and other issues unrelated. Sometimes its live and learn the hard way.
Once I realized the problem, I didn't think to just set the servername. I thought, though it would take some time, it wouldn't be TOO bad (in the grand scheme of things) to make the password changes, but it's not TOO good either.
Might have to recruit app admins and windows admins to do groups of servers at production time.