A reading from the book of Backup Clients (6.6.26 softcopy version):

"The length of time that ADSM will control the CPU, in hundredths of a
second, before yielding the CPU to another application.  For example, if
number is 1000, ADSM will control the CPU for 10 seconds."

Ron Clendenny <rdclendenny AT cal.ue DOT com>
Callaway Nuclear Power Plant
Fulton, Missouri


>-----Original Message-----
>From:  rmf [SMTP:finnell AT EROLS DOT COM]
>Sent:  Friday, February 28, 1997 5:44 AM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Re: Cap on processor utilization for Netware client
>
>From what I remember the number isn't a percentage but a metric between 0 -
>unlimited, the higher the number the greater processor utilization given to
>ADSM. We have found that, when compression is turned on, the processor
>utilization is run to 90 - 100% anyway and modifying the
>processorutilization number really doesn't change things greatly. Perhaps
>it makes more of a difference if you have many active NLMs (like an NLM
>based application server or something like that) running while your backup
>is going. Why you would do that is also beyond me though (backing up open
>files wise that is.)
>-Bob
>
>----------
>> From: Christo Heuer <christoh AT ABSA.CO DOT ZA>
>> To: ADSM-L AT VM.MARIST DOT EDU
>> Subject: Re: Cap on processor utilization for Netware client
>> Date: Friday, February 28, 1997 2:38 AM
>>
>> Hi Melinda,
>>
>> The option that you are looking for is PROCESSORutilization n (where n is
>> the number of cpu utilization you want ADSM to occupy). The default is 1.
>>
>> Regards
>>
>> Christo Heukr
>> christoh AT absa.co DOT za