Frank

Here 
the files requested  ....

Smsstart.ncf
LOAD SMSUT.NLM
LOAD SMDR.NLM
LOAD TSAFS.NLM

Tsa.cfg
Read Buffer Size:
65536
Read Threads Per Job:
4
Read Thread Allocation:
100
Read Ahead Throttle:
2
Cache Memory Threshold:
25
Disable Cluster:
no
Enable GroupWise:
0

Thanks for your help.

Robert

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Troy Frank
Sent: Wednesday, December 14, 2005 4:22 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Version 5.3.2 problem on Novell

Could you post what your smsstart.ncf file & tsa.cfg file look like?  In case 
you're not familiar with it, the tsa.cfg is in sys:\etc\sms.


>>> rouzen AT UNIV.HAIFA.AC DOT IL 12/14/2005 3:39:33 AM >>>
Hello

I upgrade today a Novell 6.5 with Tsm client 5.3.012 to a a Tsm client
5.3.2 for testing. I update too my nlm's with the tsa5up18.exe from Novell.

But when running an incremental backup from the command line: I -su=yes

I got this following errors:

12/14/2005 11:20:32 (SMDR-6.54.2) The server is unable to allocate sufficient 
memory.
12/14/2005 11:20:32 ANS1076E The specified directory path could not be found.
12/14/2005 11:20:32 (SMDR-6.54.2) The server is unable to allocate sufficient 
memory.
12/14/2005 11:20:32 ANS1076E The specified directory path could not be found.
12/14/2005 11:20:32 (SMDR-6.54.2) The server is unable to allocate sufficient 
memory.
12/14/2005 11:20:32 ANS1076E The specified directory path could not be found.

I made no changes in my Novell server option parameters and no changes too in 
my dsm.opt.

I go back to Tsm version 5.3.012 and everything work fine ......

I read the readme attach to 5.3.2 and maybe belong to this ????

*Memory Requirements (This is a variable):

*Minimum memory is 125 bytes per file; Maximum memory is 362 bytes per file.
Multiply bytes per file by the number of files and directories being backed up.
Memory usage can vary because the directory name size and file name size can 
vary.
*When performing incremental backups memory requirements can double in size 
because we must compare meta data stored on the TSM Server with local 
file/directory information.
*To decrease memory requirements see client option 'memoryefficientbackup'.

Help will be appreciate .... My TSM server version is 5.2.4.2

Regards
Robert Ouzen


Confidentiality Notice follows:

The information in this message (and the documents attached to it, if any) is 
confidential and may be legally privileged. It is intended solely for the 
addressee. Access to this message by anyone else is unauthorized. If you are 
not the intended recipient, any disclosure, copying, distribution or any action 
taken, or omitted to be taken in reliance on it is prohibited and may be 
unlawful. If you have received this message in error, please delete all 
electronic copies of this message (and the documents attached to it, if any), 
destroy any hard copies you may have created and notify me immediately by 
replying to this email. Thank you.