TSM Agent client in a W2K Cluster doesn't failover completly!

[ebrodeur]

Is this normal?



I have setup the BA client in an W2K cluster with two nodes according to the instrcutions in the Admin Guide App. E (Client is 5.1.5 on W2K SP2).



The Webclient works fine locally, but when it fails over and I try to login to the webclient I can only access the local (non-failed over) webclient.



In other words if I have node A and B, when node B failovers to node A I can't login to the Webclient as node B anymore. I can only login as node A. This means I can do a backup/archive of the clustergroupB disks (but I shouldn't) but I can't do restores/retrieves from the clustergroupB disks!



In other words I can't do anything through the Webclient on the failed cluster node disks!



Hopefully I srewed up somewhere during my install and this is not the way it's supposed to work.



Please HELP!!!!

 

[rpask]

I might have the same problem. I just install 5.1.5. The problem we are having is when the servers are rebooted, TSM service fails because the clusters are not active yet. Do you have a solution for this, some option in the dsm.opt file?