>> You are saying I have to change the registry key on each client?
Yep! ;-)
Regards,
Karel
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Schneider, John
Sent: maandag 12 februari 2007 18:45
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Problem changing TSM server name
Thanks for your reply, Karel. You are saying I have to change the
registry key on each client? If so, I still have to go out to 50-100
clients and change them all on the same day, or their backups will fail.
That is not a cheery prospect.
And for the Unix machines, I guess I have to log in to them and
reauthenticate.
Richard Sims pointed me to his QuickFacts, which says basically the same
thing. If I change the TSM server name, I have to resave the password
on each local client. Bummer.
Best Regards,
John D. Schneider
Sr. System Administrator - Storage
Sisters of Mercy Health System
3637 South Geyer Road
St. Louis, MO. 63127
Email: schnjd AT stlo.mercy DOT net
Office: 314-364-3150, Cell: 314-486-2359
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Bos, Karel
Sent: Monday, February 12, 2007 10:59 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Problem changing TSM server name
Hi,
For windows, you can remotely change the registry key
\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Nodes\
<node_name>\<ITSM server name> folder and after restarting the ITSM
service(s) things should work.
Regards,
Karel
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Schneider, John
Sent: maandag 12 februari 2007 17:28
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Problem changing TSM server name
Greetings,
I recently inherited a few TSM servers. Their internal TSM
server name does match the DNS name. The TSM clients connect to it via
the DNS name, but we would like to change the TSM server name to match.
For example, the DNS names of our standard are ABCD-TSM1, where ABCD is
a 4 letter abreviation of the site name. But the internal TSM name of
these servers are ADSM, or TSM-SERVER1 or something.
This is easy to change with SET SERVERNAME, but when I tried to
change one of them, I hit an unforeseen consequence. The next night
when the client backups kicked off, all the clients failed to run their
schedules because of authentication errors. The message in the activity
log showed the clients getting unknown client errors, and the client
name, instead of the real client name, looked like some sort of
encrypted garbage characters. As soon as I set the TSM servername back
to the original, they all went back to working.
This leads me to believe that the TSM servername is used during
the initial password exchange-and-save when the client first
authenticated and saved it's local password. To fix this then, will we
have to go out to every TSM client one at a time and re-authenticate and
save the passwords? Does anyone one know of a way to change the
servername without touching each of the clients?
Best Regards,
John D. Schneider
Sr. System Administrator - Storage
Sisters of Mercy Health System
3637 South Geyer Road
St. Louis, MO. 63127
Email: schnjd AT stlo.mercy DOT net
Office: 314-364-3150, Cell: 314-486-2359
disclaimer.txt
Description: Text document
|
