Good thought, already checked that. While it is possible nothing else has been running. We do shutdown all subsystems, save a few key libraries and IFS locations and then start back up and continue with save-while-active of the rest of the system. We are only offline for 30-45 minutes but the full backup takes 3 1/2 hours. And it's consistent. The same process runs Mon thru Fri and Tue thru Fri is always within 10 minutes of the same time, Mon is always about 40 minutes longer.
I'm going to try not doing an IPL this weekend as test to confirm if it is the IPL
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rhody, Steve
Sent: Wednesday, April 09, 2008 10:00 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Longer backup after an IPL
Mike,
Is your Mon-Fri save performed in a restricted state, or are you using
save-while-active? If SWA, could there be something running
concurrently with the save on the days that its duration is
extended...thus imposing some level of resource contention?
Steve
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
midrange-l-request@xxxxxxxxxxxx
Sent: Wednesday, April 09, 2008 7:28 AM
To: midrange-l@xxxxxxxxxxxx
Subject: MIDRANGE-L Digest, Vol 7, Issue 797
------------------------------
message: 7
date: Wed, 9 Apr 2008 08:31:24 -0400
from: Mike Cunningham <mcunning@xxxxxxx>
subject: RE: Longer backup after an IPL
The script does the same backup process every night Mon-Fri. Weekends
are different since we are not open for business and not here to change
tapes. The script does a save of security data, configuration, all
non-system libraries except our test libraries, all of the IFS. We IPL
every Sunday AM and savsys once a month. The only time we do a GO SAVE
21 is just before an upgrade or OS or hardware.
Wouldn't it be odd if a save of an object caused it to be decompressed?
What would be the purpose of doing compression if on every save
(which every object on the system should be saved at least once a month)
the object was decompressed.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Evan Harris
Sent: Tuesday, April 08, 2008 3:28 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Longer backup after an IPL
Hi Mike
What does the backup script do ?
Seems to me that a good place to start would be a compare of the joblogs
on
the IPL backup and another one to account for the differences.
If the differences is just in the save operations could you do the
DSPOBJD
before each of them and compare the objects and sizes being saved? This
will
tell you if for instance something is getting compressed and then the
first
save caused it to be uncompressed (this is a complete shot in the dark).
If I really had to just guess I'd look for a weekly housekeeping job
that
runs weekly the day after the IPL runs. Don't forget to check the GO
ASSIST/CLEANUP settings.
Regards
Evan Harris
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Wednesday, 9 April 2008 3:01 a.m.
To: 'Midrange Systems Technical Discussion'
Subject: RE: Longer backup after an IPL
Just a followup for the archives....
Last night was the first backup since our IPL followed by the DSPOBJD of
the
entire system. No change in the length of the backup.
First backup after an IPL takes from 3:30 until about 7:20. Rest of the
week
is 3:30 until about 6:45.
--
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
midrange.com
