ADSM-L

Re: Netware 4.11 backup taking extremely long

1997-04-18 11:15:34
Subject: Re: Netware 4.11 backup taking extremely long
From: "Clendenny, Ronald D." <rdclendenny AT CAL.UE DOT COM>
Date: Fri, 18 Apr 1997 10:15:34 -0500
Jerry,
You bring up a good point about compression triggering another backup of
the file.  ADSM client 2.1.07 supports the "nwignorecomp yes" parameter
in the opt file.  This will prevent ADSM from backing up the file if the
only change to it is Netware compression.

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

"Chewy, get us outta here!" - Han Solo

> -----Original Message-----
> From: Jerry Lawson [SMTP:jlawson AT THEHARTFORD DOT COM]
> Sent: Friday, April 18, 1997 9:09 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Netware 4.11 backup taking extremely long
>
> ---------------------------- Forwarded with Changes
> ---------------------------
> From: INTERNET.OWNERAD at SNADGATE
> Date: 4/18/97 12:10AM
> To: Jerry Lawson at ASUPO
> *To: *ADSM-L at SNADGATE
> Subject: Re: Netware 4.11 backup taking extremely long
> ----------------------------------------------------------------------
> ---------
> Ron -
>
> Yes - your logic makes very good sense to me.  If your server is like
> ours
> are, then this is indeed a low activity time.  Probably the only
> competition
> might be the compression of the files that are 2 days old.  I assume
> that the
> compression does not effect the things that ADSM looks at to determine
> if a
> file has changed, and you therefore don't back files up again when
> compression occurs.
>
> Our primary concern here is with NetWork capacity, and therefore we
> force all
> clients, regardless of type, to compress. With NetWare, the only issue
> I have
> seen is when someone has a sizeable restore to do, and it is done
> during the
> day.  ADSM then becomes a bit of a pig on the NetWare machine, often
> causing
> slow response.  Of course, the situation of a server having to do
> large
> restores and carry a full user load is not common - if the server has
> been
> severly impacted, then there are no users, or if the amount to be
> restored is
> not large, then the impact is momentary.  We use the
> processorutilization
> limit, and it does help some, but not a huge amount.
>
> Jerry Lawson
> jlawson AT thehartford DOT com
>
>
> ______________________________ Forward Header
> __________________________________
> Subject: Re: Netware 4.11 backup taking extremely long
> Author:  INTERNET.OWNERAD at SNADGATE
> Date:    4/18/97 12:10 AM
>
>
> Jerry,
>
> Netware has a parameter (thru servman) that sets:
>
>  "The number of days to wait after
>   a file was last accessed before
>    automatically compressing it
>   (also settable in STARTUP.NCF)
>             Setting: 2
>         Limits: 0 to 100000"
>
> We have this set to 2 days.  My thinking was:
>
> (1) Since we do an incremental backup each night, the changed files
> would necessarily be uncompressed at that time and benefit from
> compression.
>
> (2) Since the bottleneck in the process is probably the network speed,
> compression would be good.
>
> (3) The delay caused by the server cpu performing compression would
> not
> hurt us because we back up multiple servers simultaneously and
> together
> they would pump enough data to the adsm server to keep him busy.
>
> Does this make sense?  I'm open to suggestions. I should point out
> that
> during the nightly backups the netware servers do not have high user
> demand, so the cpu compression is not an issue in that respect.
>
> Ron Clendenny  <rdclendenny AT cal.ue DOT com>
> Callaway Nuclear Power Plant
>  Fulton, Missouri
>
> "The difference between the surrealists and me is that I am a
> surrealist" - Salvador Dali
>
> > -----Original Message-----
> > From: Jerry Lawson [SMTP:jlawson AT THEHARTFORD DOT COM]
> > Sent: Thursday, April 17, 1997 10:47 AM
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      Netware 4.11 backup taking extremely long
> >
> > ---------------------------- Forwarded with Changes
> > ---------------------------
> > From: INTERNET.OWNERAD at SNADGATE
> > Date: 4/16/97 3:19PM
> > To: Jerry Lawson at ASUPO
> > *To: *ADSM-L at SNADGATE
> > Subject: Netware 4.11 backup taking extremely long
> >
> ----------------------------------------------------------------------
> > ---------
> > There have been a couple of posts about compression and NetWare -
> > perhaps
> > someone who really knows NetWare 4.x can help provide the rest of
> the
> > information on what I am about to say......  :-)>
> >
> > As has been mentioned - compression can and does add a lot of
> overhead
> > to a
> > NetWare server.  NetWare 4.x will store data on it's volumes in a
> > compressed
> > format, and the data is uncompressed when a user needs to see it.
> > Thus
> > without special handling, NetWare will uncompress a file, hand it to
> > ADSM,
> > and then ADSM will compress it again.  Not a good idea!
> >
> > I BELIEVE there was a way that you could tell NetWare that the data
> is
> > to be
> > presented to the requester still compressed.  If ADSM was then set
> up
> > to not
> > attempt compression you should have the best of all worlds -
> > compressed data
> > being processed and transmited without having any additional
> overhead
> > on the
> > server, and of course minimal impact on the network.
> >
> > Can a NetWare 4.x guru out there confirm my theory, and tell us what
> > needs to
> > be done to NetWare to get it to do this for us?
> >
> > Jerry Lawson
> > jlawson AT thehartford DOT com
> >
> >
> > ______________________________ Forward Header
> > __________________________________
> > Subject: Netware 4.11 backup taking extremely long
> > Author:  INTERNET.OWNERAD at SNADGATE
> > Date:    4/16/97 3:19 PM
> >
> >
>
>
>
>
>
> > Hi there,
>  >
> > We started to backup our Pentium 100MHz with 192MB memory Netware
> 4.11
> > server to ADSM last night at 8:00 P.M.  The estimated data on the
> > server is
> > about 40GB and so far only 15GB of data has been backed up in 19
> > hours.
> > The ADSM server is at version 2.1.0.12 and is running on an AIX
> 3.2.5
> > machine.
> >
> > Any suggestion as to what parameters need to be fixed on either the
> > server
> > or netware's dsm.opt file?
> >
> > Thanks for any suggestion and comments,
> > Naveed.