Hi, ( I guess you are in active/passive HACMP resource configuration ) Haven't Tried that before with TSM, but I Would Recommand: Use three nodes: one for each basic node excluding the shared directories. one for the resource group service address (new node name), including only the shared directories, keeping the password file ( and all other tsm client files ) in a shared directory. (that way the node will go to the same place nomatter on which host you are on). You should, probably, bring up the tsm scheduler for this node as part of you start script, and bring it down with the stop script.
In case you have more than one resource group, implement that for each one, assuming each could be brought up on a separate host. In case of failover, the dsm node wail fail over with the resource group... Good Luck. Ran. -----Original Message----- From: brian welsh [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 23, 2002 10:57 PM To: [EMAIL PROTECTED] Subject: HACMP and password-file Hello, Server AIX 4.3.3, TSM-server 4.1.1.0 and client AIX 4.3.3 and TSM 4.1.x We have some problems with two clients using HACMP. On both clients there is a TSM-client. We use Password Access Generate. When there is a fail-over, the password-file in /etc/security/adsm is deleted and the client is trying to connect the server. This results in 10 to 20 stop and start sessions in the Activity Log and it grows so fast that in a few minutes the Activity Log is unreachable. Besides the errorlog on the client is getting very big. We know why it is happened and how to stop is, but the question is: how are sites setup TSM-clients on HACMP-systems, and how do these clients react in case of fail-over. Thanks, Brian. _________________________________________________________________ Meld je aan bij de grootste e-mailservice wereldwijd met MSN Hotmail: http://www.hotmail.com/nl
