All,

The TSM Backup-Archive client has support for MSCS (Windows), HACMP (AIX)
and NCS (NetWare) clustering solutions.  If you are using a clustering
solution on one of the Intel platforms other then these listed, you will
have these naming issues after a fail-over.

We are looking into something similiar to what Peter is suggesting, and
that is a way to logically manage a set of data on the TSM server which is
sent from different client nodes.  This would be beneficial for clustering
as well as have other applications.  We are also pursuing adding support
for some of these other clustering solutions.

It doesn't hurt to open requirements to Tivoli if you have a particular
cluster solution that you would like to see supported.

Thanks,
Jim Smith
TSM client development

In response to:

>You know, there seems to be a similar issue with filespace naming with
the
new Netware cluster aware client.
>We're awaiting a server upgrade to pursue it further. Seems as it the
'getservername' API call is at the heart of this.


Yes, it seems TSM is not savey of any cluster soloutions except
Microsoft's.

If they (TSM) would only introduce a new option in the .opt file so one
could override the servername
if for some reason or another one should wish to do so.
It would probably solve the naming problem in most cluster sitiations.

Regards

Peter

J.P. (Jim) Smith
TSM Client Development
smithjp AT us.ibm DOT com