Hi Thomas, I never found documentation for this situation, either. And I'm not sure it's even consistent between TSm server versions. I can only tell you about my experience moving clients from an AIX to Windows TSM server via export/import.
What I found (and this was at TSM 5.1) was that 1) The good news: TSM Windows clients had no problem maintaining passwords for 2 different TSM servers in the registry. I don't remember where to find it now, but at one time I think we started regedit and just poked around until we found that the client had the good sense to store stuff in the registry under a key that included the TSM server name (not the host name, but the name you define with SET SERVERNAME). So it can maintain as many passwords as you have TSM servers. 2) Now the bad news: Doing an export/import ACROSS platforms invalidated the password in the registry (Or rather, it no longer matched what was in the client registry). We had to go to each Windows client and REENTER the password on the client end the first time it connected to the new (Windows) TSM server it has been IMPORTED to. Now I'm not sure if that was because a) the password encryption algorithm is different between AIX and Windows TSM servers, or b) the IP address being different caused the problem. Anyway, don't assume that anybody knows for sure what will happen to the password when you EXPORT/IMPORT from OS/390 to Linux - I have no clue. You better try it and see. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Denier Sent: Friday, July 09, 2004 11:27 AM To: [EMAIL PROTECTED] Subject: Windows client passwords for multiple servers We are preparing to migrate our TSM server from OS/390 to mainframe Linux. We are planning to run complete backups to the new server and let data on the old server age off. Each of our Windows clients will need two options files for a while (one for each server). In most cases, the options file for the old server will be needed only for restores of files that became inactive before the cut-over. However, some of our clients are too big to do a complete backup in one day. Each of these will need two scheduler services as well as two options files. One service will be used to run the complete backup to the new server in managable chunks, and the other will be used to continue incremental backups to the old server. The documentation for the Windows client code indicates that passwords are stored in the registry. However, the documentation provides no information about the registry keys used, and hence no information about the conditions (if any) under which two independently maintained passwords can be stored. The procedure we have in mind for most Windows clients is as follows: 1.Use server to server export/import to copy the node name and password from old server to new server. 2.Copy dsm.opt to oldtsm.opt. 3.Update dsm.opt to address the new server. 4.Stop and start the scheduler service. Eventually, one or both of the servers will negotiate a new password (we always use 'passwordaccess generate'). Will scheduled backups to the new server work after that? Will it still be possible to run manually initiated restores from either server? A few of the bigger clients will require an additional step: 5.Define a second scheduler service using oldtsm.opt. This raises an additional question. Will scheduled backups to both servers continue working after a password change?
