I would suspect that your problem is with RedHat 9.
RedHat 9 is different to all the earlier RedHats, in the RedHat
implemented a different threading methodology in the kernel. (Hence
everyday Java doesnt run either.)
I would back down to at least RedHat 8 - but preferably RedHat 7.2 or
RedHat 7.3. (I've run TSM quite happily on RH 7.2 and RH 7.3)
Since you are not using any tape hardware, RedHat 7.x should run very
well. If you want to use tape hardware, then you will have to go to kernel
2.4.9-31 for the drivers to load (and be supported).
...deon
---
Have you looked at the A/NZ Tivoli User Group website?
http://www.tuganz.org
Deon George, IBM Tivoli Software Engineer, IBM Australia
Office: +61 3 9626 6058, Fax: +61 3 9626 6622, Mobile: +61 412 366 816,
IVPN +70 66058
mailto:dgeorge AT au1.ibm DOT com, http://www.ibm.com/tivoli
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 11/09/2003
11:40:15 AM:
> Us also...I haven't tried TSM on anything above RH 7.2, and my first
> instinct would be to back the OS down to that level and use the kernel
> they spec.
>
> So far, it's been pretty stable.
>
> -Lloyd
>
>
> On Wed, 10 Sep 2003 20:51:15 -0300
> Patrick Boutilier <boutilpj AT EDNET.NS DOT CA> wrote thusly:
>
> > Mark,
> >
> > We run TSM server 5.1.6.5 on RedHat 7.2 with 2.4.9-31 kernel without
any
> > problems.
> >
> >
> > Mark Farber wrote:
> > > Hi TSM'rs
> > >
> > > Being a Linux bigot, I managed to convince a new client to opt for a
> > > Linux TSM server over Windows. I am now starting to wish I had just
> > > gone for Windows. Unless you can help I might have to. Here's the
> > > problem.
> > >
> > > Server Version 5.2.0.2 on Redhat 9
> > > Client Version 5.1.6.2 on Redhat 7.3
> > >
> > > The TSM server has no tape library or drive but is totally file
based
> > > (400GB using software raid0)
> > >
> > > Client backups are done via the crontab using
> > > "/opt/tivoli/tsm/client/ba/bin/dsmc incr"
> > >
> > > The server just hangs during a client backup operation.....nothing
in
> > > the activity report. Eventually the client times out but
unfortunately
> > > the "dsmc incr" stays in the process queue. The next day, cron
> > > dutifully fires off another backup and so it goes. Eventually after
a
> > > call from a frustrated customer, I have to start the server manually
> > > and run the backup manually. (Seriously not good!!)
> > >
> > > Also, if a backup is running and you happen to do one too many "q
act"
> > > requests, the server hangs.
> > >
> > > By the way, only the TSM application hangs, not Linux itself.
> > >
> > > Has anyone experience with Linux TSM server and seen similar
problems?
> > >
> > > Regards
> > > Mark
> >
>
>
> --
> -----------------------------------------------------------------
> Lloyd Dieter - Senior Technology Consultant
> Registered Linux User 285528
> Synergy, Inc. http://www.synergyinc.cc ldieter AT snrgy DOT com
> Main:585-389-1260 fax:585-389-1267
> -----------------------------------------------------------------
|
