ADSM-L

Re: Session limitation

2002-03-11 07:19:08
Subject: Re: Session limitation
From: Christo Heuer <christoh AT ABSA.CO DOT ZA>
Date: Sat, 11 Mar 2000 11:32:59 +0200
Hi William,

Apart from the normal - memory/Cpu constraints that you must stay
aware of - remember that your Tsm client makes use of a netware
userid to do the backups - make sure this ID can open enough
sessions to support what you want from the client - so yes there
IS a session limitation linked to the userid being used - but
this can be set by the netware administrators.
Cheers
Christo
----------------------------------------------------------------------------
I recently tried to backup up a Netware box straight to disk.  I did this
I recently tried to backup up a Netware box straight to disk.  I did this
manually and opened 12 sessions (6 seperate backups).  We had MacAfee
running and are thinking that the combination of the two caused the Netware
Client to reboot.  It has a 100 MB card and I was trying to backup as fast
as possible for a restore to a different box.  The total of 88 GB was need
to be backed up so that it could restore.  I thought I could open as many
sessions as I wanted since I was going straight to disk and then I would
have done the same on the restore.  Is there a known limitation on the
client for open sessions according to the size of the box or otherwise?
Would the backup have caused even remotely the Netware client to reboot?
And for future use is there anyway of telling how many sessions to open on
any box?  Some guidelines or other?
     Thank you in advance.

______________________________________________
"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."
<Prev in Thread] Current Thread [Next in Thread>