Then you could set the date to just before the last full save and move from
there. Just don't pick out the objects you don't want.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Steinmetz,
Paul
Sent: Tuesday, December 18, 2018 1:49 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: STRRCYBRM - Start Recovery using BRM - Time period for recovery
question
Jim,
Our "business rules" require that we keep some saves (tapes) indefinitely,
our Month End processes, never expire, *PERM retention..
Daily expires in 45 days.
Weekly expires in 13 months.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Oberholtzer
Sent: Tuesday, December 18, 2018 2:30 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: STRRCYBRM - Start Recovery using BRM - Time period for recovery
question
Paul:
Clearly BRMS thinks (correctly no not is your call) that some objects have
not been backed up since the old save and are still needed. The first
question I have is why is the BRMS database that big? You should be purging
it so when tapes are expired the data is removed from BRMS, therefore
cleaning up the problem you are referring to. The settings for this are
in the BRMS maintenance commands.
The second thought is; normally I do a recovery from the recovery report
BRMS sets up. If I see objects from old saves, I ignore them and move on.
Only you will know if that's a smart call or not since you might need those
objects but for whatever reason they are not on a more recent tape.
My get tells me to just ignore those objects in the recovery and move on.
We do not usually mess with the dates in the command.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Steinmetz,
Paul
Sent: Tuesday, December 18, 2018 1:07 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: STRRCYBRM - Start Recovery using BRM - Time period for recovery
question
When doing a STRRCYBRM - Start Recovery using BRM, do you normally let the
time period for recovery default, as below.
Or do you select a more recent begin date for the recovery?
Time period for recovery:
Start time and date:
Beginning time . . . . . . . . *AVAIL Time, *DAYS, *AVAIL
Beginning date . . . . . . . . *BEGIN Date, *CURRENT, *BEGIN
End time and date:
Ending time . . . . . . . . . *AVAIL Time, *AVAIL
Ending date . . . . . . . . . *END Date, *CURRENT, *END
The reason I ask, when letting default to *Begin, my BRMS recovery is
including 2 sequences from 2012.
So according to BRMS, these two sequences contain "something" and 2012 is
the most recent save.
How does one determine what that "something" might be, and if it is even
needed?
Saved Save Save Save Parallel Volume File Expire
Item Date Time Type Devices Serial Sequence Date
*NONSYS 6/03/12 12:24:59 *FILE 001060 681 *PERM
QDOC 6/03/12 12:41:40 *FILE 001060 1015 *PERM
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
--
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:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
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:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
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:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
