Christo,

We are backing up a Netware cluster with TSM and our server is on OS/390.
I've had numerous 'issues', but I can (via the gui or web) see the file
space info.

Our server is 4.1.4_2 and the clients on the cluster nodes are 4.2.1_19.
All the netware clients have the same nodename in the opt file, which is
the cluster name. However, the filespaces are listed under the cluster ID
by physical machine name. That is, while the nodename is Superion, the
filespace name is firefight\sys:

I hope you're aware that the nlms are not truly cluster aware so that if a
volume fails over to another cluster node TSM sees it as a new filespace
and backs the whole thing up again.

As to the TSM website, Tivoli support told me on my last ETR that Netware
clusters are not 'officially' supported. I've heard with NW6 it may be.

Christo Heuer wrote:

> Hi,
>
> Has anyone tried to backup a clustered Netware environment
> with the Tsm clients?
>
> I've got a V4.2.13 Tsm client running on Netware V5 backing
> up to TSM 4.1.2 server.
> When I query the filespaces from a administrative interface
> it does not have any entries for the last backup start time etc.
> It is as if the backup has never run before.
> When checking the client schedule log and the backups table in
> the TSM database it shows that the backup completed.
>
> Has this got to do with the fact that it is a clustered Netware
> environment?
> I know in the days of SFT3 the Adsm code would have been SFT3
> certified - I don't think it was ever really done.
> On the Tivoli website I can not find any info in terms of TSM
> running on Netware in a clustered environment either - is it only
> the Intel based TSM client that has cluster aware capabilities?
>
> Thanks for any info...
>
> Regards
> Christo
>
> ______________________________________________
> "The information contained in this communication is confidential and
> may be legally privileged.  It is intended solely for the use of the
> individual or entity to whom it is addressed and others authorised to
> receive it.  If you are not the intended recipient you are hereby
> notified that any disclosure, copying, distribution or taking action
> in reliance of the contents of this information is strictly prohibited
> and may be unlawful.  Absa is neither liable for the proper, complete
> transmission of the information contained in this communication, any
> delay in its receipt or that the mail is virus-free."

--
Jim Kirkman
Jim Kirkman
AIS - Systems
UNC-Chapel Hill
966-5884