I applied the TSM 3.7.2 client with the same result, could not allocate a
handle when reading the Novell volumes.
> > JIm,
> > I am running into the EXACT same problem. This was escalated to
> > IBM/Tivoli's level 2 support. So far I have not gotten any feedback. Have
> > you recieved any additional info? If so, could you let me know?
> > Thanks,
> > Jeff Carroll
> > American General
> > Jim Kirkman <jmk AT EMAIL.AIS.UNC DOT EDU>@VM.MARIST.EDU> on 05/03/2000
> > 03:18:48
> > PM
> > Please respond to jim_kirkman AT unc DOT edu
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> > To: ADSM-L AT VM.MARIST DOT EDU
> > cc:
> > Subject: TSM vs ADSM on Novell
> > Interesting situation. Box has been fairly steady ( for a Novell client) as
> > a
> > Novell 4.11 server running, initially, ADSM 126.96.36.199 and more recently TSM
> > 3.7.1.07. A week or so ago this server was upgraded to NW5.0. Since that
> > time it
> > has had problems backing up. It will back up fine one or two nights in a
> > row and
> > then have problems. The most recent being ANS1076E:This program could not
> > allocate a directory handle. This when trying to read either of the two
> > volumes,
> > so no files get backed up.
> > Out of curiosity, and because the files were still out there, I invoked the
> > ADSM
> > client and it backed up fine!
> > Anyone able to shed any light on why the TSM client can't recognize the
> > volumes
> > after an upgrade of the OS?
> > Thx
> > --
> > Jim Kirkman
> > AIS, UNC-Chapel Hill
> Jim Kirkman
> AIS UNC-Chapel Hill
AIS UNC-Chapel Hill