🚀 go-pugleaf

Robert Chambers <RMCCU@CUNYVM.BITNET> Writes:
>I'd like to get an idea of how long people's condense&discard processing
>takes each night. ...

It depends upon the time of the month (we only do MONTHLY and DAILY, no
WEEKLY, backups).  We have 40 3380 DASD and 10,000+ userids.  When the
CONDENSE runs, it usually finishes in less than half an hour.  Sometimes
it can take up to four hours.  It depends upon how many catalogs end up
getting CONDENSEd each night.  (We run our MONTHLYs on the first Wednesday
of each month, so the lengthy CONDENSEs occur at different times of the
month.)

The larger the catalog, the longer it takes to CONDENSE it.  We split
up our MONTHLY/DAILY jobs into three separate jobs and the CONDENSEs run
much more quickly now, even though the same amount of data is being backed
up/condensed.  This is based on observation only, not VMBACKUP internals.

>I END (FORCEd vmb and restarted it and the job took off without doing a
>condense and discard- The next night the same thing happened so I said to
>let it run until 2am, if it hasn't started by then, end force it and
>autolog it again.

Our OPs did this when this problem first showed up.  I never noticed until
VMBACKUP's Catalog disk filled up.  The next night's CONDENSE took over
eight (8) hours to complete!

There is a lot of storage being used.  I have a routine that SET RESERVE
1000 pages for VMBACKUP, priority gets set to one, etc.  This reduces the
time it takes for the backups to complete.  If your system is underused
during the midnight shift, consider doing the same thing.  Just remember
to SET RESERVE OFF, etc. at 8 am.  :-)

Ron,,,