|
midrange.com
Sorry. That's one of those things that starts to make sense once you've
read some of the subsequent posts. My fingers were just faster than my
brain.
Dave Parnin
Nishikawa Standard Company
Topeka, IN 46571
daparnin@xxxxxxxxxxxxxx
"Walden H. Leverich"
<WaldenL@xxxxxxxxxxxxxxx> To:
"Midrange Systems Technical Discussion"
Sent by:
<midrange-l@xxxxxxxxxxxx>
midrange-l-bounces+daparnin=niscoseals.com@m cc:
idrange.com
Subject: RE: V5R3 Backup w/Checkpoint and Ragged Restore
(was: RE: Help me Justify iSeries)
05/27/2005 03:51 PM
Please respond to Midrange Systems Technical
Discussion
Dave,
Actually, we're looking at a situation where there are actual updates
running 24x7 under commitment control. There are actually some jobs that
run multiple DAYS with commitment control, and in some cases run many
minutes between commits. We've found SWA to be useless before V5R3
because of the requirement to get to a common commit point across jobs.
With V5R3 that requirement goes away. I was worried Al was saying
something else, but he wasn't.
-Walden
------------
Walden H Leverich III
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com
Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
daparnin@xxxxxxxxxxxxxx
Sent: Friday, 27 May, 2005 15:50
To: Midrange Systems Technical Discussion
Subject: Re: V5R3 Backup w/Checkpoint and Ragged Restore (was: RE: Help
me Justify iSeries)
We kill QINTER, QBATCH, etc. Anything that might have a job that could
update a data file in the backup. I think what he's saying is that if a
file gets updated after the checkpoint has been established for it the
checkpoint won't be valid and the pre-checkpoint version of the data
will
be saved to tape. Once the checkpoint has been established it's OK to
restart the subsystems and turn the users loose. That's what the
SAVACTMSGQ parameter is for.
Our backup runs in its own subsystem that doesn't get shut down when
QINTER
and QBATCH are whacked. I imagine that if you had a large or busy
machine
you could isolate your applications and do separate save-while-active's
for
each file library such as one for BPCS, one for Kronos, one for JDE,
etc.
assuming that each of them ran in their own subsystems. In most cases
that
would probably be overkill, extra administration, a potential for
disaster,
and not get you that much.
Dave Parnin
Nishikawa Standard Company
Topeka, IN 46571
daparnin@xxxxxxxxxxxxxx
"Walden H. Leverich"
<WaldenL@techsoftinc To: "Midrange
Systems Technical Discussion"
.com>
<midrange-l@xxxxxxxxxxxx>
Sent by: cc:
midrange-l-bounces@m Subject: V5R3 Backup
w/Checkpoint and Ragged Restore (was:
idrange.com RE: Help me
Justify iSeries)
05/27/2005 01:14 PM
Please respond to
Midrange Systems
Technical Discussion
>From: Al Barsa
>The checkpoint processing would complete, however your backup could be
bad!
>if your backup was bad because of updating during the checkpoint, save
>would still tell you that you have a good save!
Huh!!!?????!!!?!?
Are you telling me that the backup would say it was fine but I couldn't
restore to that point in time (including apply of journal receivers)????
-Walden
------------
Walden H Leverich III
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com
Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
--
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.
--
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.
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
