Alot of traffic has been created about the expire process of 3.1.2.20.
What about ADSM 3.1.2.16 for OS/390 servers? Is the expire processing
running longer at this software level also??
Thanks in advance for your cooperation.....
(Embedded
image moved "Lambelet,Rene,VEVEY,FC-SIL/INF."
to file: <Rene.Lambelet AT NESTLE DOT COM>
pic13008.pcx) 04/21/99 04:41 AM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: Bob Barden/AAL)
Subject: FW: Expire after 3.1.2.20 Upgrade
Hello,
here the results of our first expire processing after having upgraded
OS/390
2.4 server from adsm 3.1.1.3 to 3.1.2.20:
DB size 7440 MB, max. reduction: 2136 MB,
utilization went from 71% down to 61 %
Log size 1296 MB
CPU: 112 mips dyadic
Expire elapsed time 3.1.1.3 : 30 '
Expire " " after upgrade: 10 h 08 '
Expire " " 3.1.2.20 : 2 h 40 '
Before upgrade:
04/14/1999 08:30:02 ANR0984I Process 83 for EXPIRE INVENTORY started in the
BACKGROUND at 08:30:02.
04/14/1999 08:57:39 ANR0812I Inventory file expiration process 83
completed:
examined 26'090 objects, deleting 24'960 backup objects, 339 archive
objects, and 0 DB backup volumes. 0 errors were encountered.
04/14/1999 08:57:40 ANR0987I Process 83 for EXPIRE INVENTORY running in the
BACKGROUND processed 25'299 items with a completion state of SUCCESS at
08:57:39.
04/15/1999 08:30:02 ANR0984I Process 110 for EXPIRE INVENTORY started in
the
BACKGROUND at 08:30:01.
04/15/1999 08:50:37 ANR0812I Inventory file expiration process 110
completed: examined 26'126 objects, deleting 25'105 backup objects, 227
archive objects, and 0 DB backup volumes. 0 errors were encountered.
04/15/1999 08:50:37 ANR0987I Process 110 for EXPIRE INVENTORY running in
the
BACKGROUND processed 25'332 items with a completion state of SUCCESS at
08:50:37.
04/16/1999 08:30:02 ANR0984I Process 144 for EXPIRE INVENTORY started in
the
BACKGROUND at 08:30:01.
04/16/1999 08:51:55 ANR0812I Inventory file expiration process 144
completed: examined 27'661 objects, deleting 26'737 backup objects, 122
archive objects, and 0 DB backup volumes. 0 errors were encountered.
04/16/1999 08:51:55 ANR0987I Process 144 for EXPIRE INVENTORY running in
the
BACKGROUND processed 26'859 items with a completion state of SUCCESS at
08:51:55.
After upgrade, 1st time:
04/20/1999 08:30:07 ANR0984I Process 10 for EXPIRE INVENTORY started in the
BACKGROUND at 08:30:07.
04/20/1999 18:38:09 ANR0812I Inventory file expiration process 10
completed:
examined 3'131'147 objects, deleting 1'449'272 backup objects, 471 archive
objects, 0 DB backup volumes, and 0 recovery plan files. 0 errors were
encountered.
04/20/1999 18:38:09 ANR0987I Process 10 for EXPIRE INVENTORY running in the
BACKGROUND processed 1'449'743 items with a completion state of SUCCESS at
18:38:09.
After upgrade, 2nd time:
04/21/1999 08:30:24 ANR0984I Process 44 for EXPIRE INVENTORY started in the
BACKGROUND at 08:30:24.
04/21/1999 11:10:55 ANR0812I Inventory file expiration process 44
completed:
examined 1'722'416 objects, deleting 39'702 backup objects, 213 archive
objects, 0 DB backup volumes, and 0 recovery plan files. 0 errors were
encountered.
04/21/1999 11:10:55 ANR0987I Process 44 for EXPIRE INVENTORY running in the
BACKGROUND processed 39'915 items with a completion state of SUCCESS at
11:10:55.
So everything is fine, except the expire processing now takes much time to
finish!
Regards,
Rene Lambelet
Nestec SA - 55, Av. Nestle - CH-1800 Vevey
Tel: ++41'21'924'35'43 / Fax: ++41'21'924'45'89
E-Mail: rene.lambelet AT nestle DOT com
> -----Original Message-----
> From: Lambelet,Rene,VEVEY,FC-SIL/INF. [SMTP:Rene.Lambelet AT NESTLE DOT COM]
> Sent: Tuesday, April 20, 1999 5:01 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Expire after 3.1.2.20 Upgrade
>
> Hello dears,
>
> we upgraded our adsm server yesterday from 3.1.1.3 to 3.1.2.20, OS/390
> 2.4.
>
> Expire processing still running after more than 8h30 elapsed, more than
> 2'000'000 objets inspected, more than 1'000'000 backup objects deleted! I
> hope I still get backups in my database...
>
> Will tell you tomorrow the definitive results of this first expire after
> the
> upgrade (normal expire time, db size...).
>
> IBM, please make a note in the installation readme's, about this long
> expire
> processing!
>
> Question: did we got the expire problem even if we never install 3.1.2
and
> went directly from 3.1.1.3 to 3.1.2.20? It seems that the answer is
> positive.
>
> Regards,
>
> Rene Lambelet
> Nestec SA - 55, Av. Nestle - CH-1800 Vevey
> Tel: ++41'21'924'35'43 / Fax: ++41'21'924'45'89
> E-Mail: rene.lambelet AT nestle DOT com
>
>
>
> > -----Original Message-----
> > From: Robert Bunt [SMTP:rmbunt AT NYSEG DOT COM]
> > Sent: Tuesday, April 20, 1999 3:07 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: Expire and reclaim after 3.1.2.20 Upgrade
> >
> > John:
> > I tried to answer the questions as you asked them. Please see the
> > notes
> > immediately following
> > your queries. One additional note I misquoted the person that was in
> over
> > the
> > weekend about the 36 hours clock time to
> > run the EXPIRE INVENTORY. He corrected me this morning and it should
> have
> > been
> > 6 Hours. He gave
> > me the wrong start time when we spoke. I did not want to scare you any
> > more
> > than necessary.
> >
> > The reason for my original question is that we have been amassing
> > far more
> > copies of datasets
> > without expiring the older versions. My mailbox backup in Notes is
only
> > supposed to have 20 Versions at all
> > times. I checked yesterday and found that I have 30. The EXPIRE
> > INVENTORY only
> > appears to have
> > changed the Deactivation Date for the 10 oldest Versions to the day
when
> > we ran
> > the command. I thought that
> > some process would start cleaning out all of the un-needed versions and
> > would
> > start reclaim processing in
> > my tape pool.
> >
> > Bob Bunt
> > rmbunt AT nyseg DOT com
> >
> >
> >
> >
|