ADSM-L

Re: TSM Agent client in a W2K Cluster doesn't failover completly???

2002-10-28 13:53:27
Subject: Re: TSM Agent client in a W2K Cluster doesn't failover completly???
From: Bill Boyer <bill.boyer AT VERIZON DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 28 Oct 2002 13:47:06 -0500
Use App. C in the Installing The Clients manual for complete instructions.
For the web client you also have to create a name and IP address resource
for the group. Then you would use this group IP address to access the
webclient on whichever node owns that resource.

Bill Boyer
DSS, Inc.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Etienne Brodeur
Sent: Monday, October 28, 2002 1:17 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TSM Agent client in a W2K Cluster doesn't failover completly???


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!!!!

<Prev in Thread] Current Thread [Next in Thread>