ADSM-L

Re: Novell client still running long

2000-03-06 13:00:49
Subject: Re: Novell client still running long
From: Jeff Keen <JKeen AT CI.FLINT.MI DOT US>
Date: Mon, 6 Mar 2000 13:00:49 -0500
The copy mode and serialization were not changed, I just threw those in so 
people would know what they were set at. Just made client changes.

>>> S W Branch <SWBRANC AT PPCO DOT COM> 03/06/00 12:05PM >>>
Did you also reactivate the policy set on the ADSM server after the changes?

Steve Branch
Phillips Petroleum
e-mail: swbranc AT ppco DOT com 





Jeff Keen <JKeen AT CI.FLINT.MI DOT US> on 03/06/2000 10:25:32 AM

Any replies will be addressed to: "ADSM: Dist Stor Manager"
      <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU 

cc:
(bcc: S W Branch/PPCO)







 Subject: Re: Novell client still running long







Sorry for leaving that out, but YES, the scheduler was bounced afterwards.

>>> S W Branch <SWBRANC AT PPCO DOT COM> 03/06/00 11:01AM >>>
Did you stop and restart the client scheduler after making these changes?

Steve Branch
Phillips Petroleum
e-mail: swbranc AT ppco DOT com 





Jeff Keen <JKeen AT CI.FLINT.MI DOT US> on 03/06/2000 09:35:24 AM

Any replies will be addressed to: "ADSM: Dist Stor Manager"
      <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU 

cc:
(bcc: S W Branch/PPCO)







 Subject: Novell client still running long







ADSM Server 3.1.2.40 on AIX
ADSM Client 3.1.0.8 on Netware 4.11 SP7a

I have been trying to figure out why a Novell client doesn't seem to be doing an
incremental when it is associated with the same schedule as the rest of our
Novell clients, yet they don't have this problem. I seem to have 7 copies of all
the files, even if they haven't changed. In the last week I have upgraded client
from .7 to .8, set NWIGNORECOMPRESSBIT YES, and have changed my COMPRESSALWAYS
to NO.  COPY MODE MODIFIED, COPY SERIALIZATION SHARED DYNAMIC. Any ideas??

Thanks in advance,

Jeff