ANS2050E TSM needs to prompt for the password 1

[almond247]

Hello all,

We have a Windows Client who is planning to move a backup from Eligan1 which is part of a Windows Cluster to another server Eligan2. This was done recently and there was a password issue shown below.

The error happend when they moved it to Eligan2, Do they need to bring the Resource that runs the backup (Its uses the dsm.opt file to connect to the TSM server) on the second server (Eligan2) so the password issue can be fixed? If so how do I fix the issue? They want this to continue to work on Eligan1 if the resource goes back.


The following message appeared when the backup was moved to the second server Eligan2.

00:50:44 ANS2050E TSM needs to prompt for the password but cannot prompt because the process is running in the background.
00:50:44 ANS2050E TSM needs to prompt for the password but cannot prompt because the process is running in the background.
00:50:44 ANS1029E Communication with the TSM server is lost.
01:10:49 ANS2050E TSM needs to prompt for the password but cannot prompt because the process is running in the background.
ANS2050E TSM needs to prompt for the password but cannot prompt because the process is running in the background.


Thanks for any help, suggestions in advance!


TSM 5.3
Windows TSM client 5.3
AIX 5.3

 

[mbourne2006]

Hi

Is the client "Eligan2" part of the same cluster as "Eligan1"?

If not, here's what I'd do ...

1. Stop the TSM client services on Eligan2
2. Check dsm.opt on Eligan2, and make sure that I've got "passwordaccess generate" in the options file
3. Fire up the client (either GUI or command line, doesn't matter which)
4. Authenticate to the TSM server
5. Perform some action to test my connection with TSM
6. Shut down the client opened in (3), then open it again - all being well, I won't be prompted for a password this time
7. Check the TSM client services are using the options file I've just edited - use "dsmcutil list" and "dsmcutil query"
8. Hopefully, that's it.

If the scenario's more complex, may need more information

Please post success or otherwise, ta

Have Fun !
Matthew Bourne
"Find a job you love and never do a day's work in your life.

 

[almond247]

Hi mbourne2006,

Thanks again for your reply, Yes, Eligan2 is part of the same Windows Cluster as “Eligian1” The issue has been resolved by performing the steps below that I read in the “IBM Tivoli Storage Manager in a Clustered Environment” Redbook

Chp 6. Microsoft Cluster Server and the IBM Tivoli Storage Manager Client (the following are excerpts from the section
of the redbook covering this)

Password generation

The Windows registry of each server needs to be updated with the password used to register the nodenames for each resource group in the Tivoli Storage
Manager server.


Important: The steps below require that we run the following commands on both nodes while they own the resources. We recommend to move all Resources to one of the nodes, complete the tasks for this node, and then
move all resources to the other node and repeat the tasks.

Since the dsm.opt is located for each node in a different location, we need to specify the path for each, using the -optfile option of the dsmc command:

1. We run the following commands from a MS-DOS prompt in the Tivoli Storage
Manager client directory (c:\program files\tivoli\tsm\baclient):

dsmc q se -optfile=q:\tsm\dsm.opt

2. Tivoli Storage Manager prompts the nodename for the client (the specified in dsm.opt). If it is correct, press Enter.

3. Tivoli Storage Manager next asks for a password. We typed the password and press Enter.


Note: The password is kept in the Windows registry of this node and we do not need to type it any more. The client reads the password from the registry every time it opens a session with the Tivoli Storage Manager server.



4. We repeated the command for the other node cluster resource H disk

dsmc q se -optfile=H:\tsm\dsm.opt

Just to add we moved the resources (H & Q disks to Eligan2) and performed the above steps. The only thing is when they were moved back to Eligan1 we found we had to do a force password reset in TSM and repeat the process in order to get the disks to come online not sure why? I am curious to see if this procedure has to be done every time they move the Cluster resources to Eligan2 and back to Eligan1? According to the note the password is kept in the registry and we should not have to type it anymore.

Sorry, If my orginal scenario didn’t have all the information or was not clear enough.

Hope this is a little more clearer if you have any Comments, Suggestions feel free to post.

 

[mbourne2006]

Hi Almond247

Take a look in the Appendices for the Windows B/A Client IUG. There is an appendix dedicated to setting up cluster backups. What you're missing is the generic MS cluster service that replicates the registry entries containing the encrypted password.

Let me know how you get on

Have Fun !
Matthew Bourne
"Find a job you love and never do a day's work in your life.

 

[almond247]

Mbourne2006

I didn't actually set this cluster up and I am still in the learning stage of cluster backups however,I did though manage to look to at the cluster set-up documentation notes that was used. It seems they did create the service that replicates the registry entries

1.Now, install the scheduler service for both groups of disks. Do this on ELIG1 first and then fail over to ELIG2 and do the same thing.

The commands should be
dsmcutil inst sched /name:"TSM Scheduler Group Quorum"
/clientdir:"c:\program files\tivoli\tsm\baclient" /optfile:q:\tsm\dsm.opt
/node:ELIGAN1 /password:ELIGAN1 /clustername:LOGCLUSTER /clusternode:yes /autostart:no

dsmcutil inst sched /name:"TSM Scheduler Group H"
/clientdir:"c:\program files\tivoli\tsm\baclient" /optfile:h:\tsm\dsm.opt
/node:ELIGAN2 /password:ELIGAN2
/clustername:LOGCLUSTER /clusternode:yes /autostart:no

2. Now, encrypt the password(must be done on BOTH nodes) in the registry by going to c:\progra~1\Tivoli\tsm\baclient at the command prompt and typing
dsmc q sess –optfile=q:\tsm\dsm.opt
dsmc q sess –optfile=h:\tsm\dsm.opt
Supply the user ID and password and then quit.

3. Now create the Generic Cluster Resources for each disk group. To do this, open up Cluster Administrator, Right-Click on Cluster Group and Select New?Resource. Type a name for the Resource (it should be the same as the Schedule Name, ex: TSM Scheduler Group Quorum). The resource type should be “Generic Service” and the group is “Cluster Group”. Click NEXT. Make sure ELIG1 and ELIG2 are listed as possible owners and click NEXT. Add DISK Q to the Resource Dependencies, and click NEXT. Type the Service name (same as above) and click NEXT. Enter the root registry key. They should be:

Registry replication for Quorum
SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Nodes\ELIGIAN1SPF63
Registry replication for H:\ disk
SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Nodes\ELIGAN2\SPF63

4. Once both of these resources are created successfully, right click on each of them and select Bring Online.

Thanks again