I know you're going to blame the auditors, but they probably have only approved a policy someone at your company recommended. I really don't think there's any need to make all your longer term tapes *PERM. Again, there is no requirement for this on your PC backups, is there? I'm sure that if you came up with a new policy of only retaining for a set period it would be approved by your auditors.
We're a publicly held company and we have no permanent retention requirements. We have one save, of just a few libraries, that is performed at year end with a *perm retention. Our other longest retention is our quarterly full system save. That is saved with 376 days retention. There is no special monthly save. Daily saves are only retained for two weeks except for Mondays. Mondays are just 6 weeks.
The perm save is done something like
SAVLIB LIB1 SAVF(YE2018/LIB1) repeat for a few other libraries.
Then library YE2018 is saved.
I don't think this will cause any BRMS restore issues.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Monday, June 3, 2019 8:08 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: STRRCYBRM *SYSTEM *RESTORE - time period for recovery recommendations
Per IBM BRMS support (Mervyn) there are two possible reasons that these files are in the strrcybrm *restore.
1) they were saved outside of brms or
2) the save did not complete and outfile processing did not complete.
The *FILE indicates that the save was either done outside of brms or the save did not complete.
CBGPL 2/01/05 22:18:09 *FILE 001162 3 *PERM
IC0450PGMS 2/01/05 22:18:21 *FILE 001162 8 *PERM
IC0450CHGP 2/01/05 22:18:32 *FILE 001162 9 *PERM
*NONSYS 6/03/12 12:24:59 *FILE 001060 681 *PERM
In our case, this save was done prior to us using BRMS.
We started using BRMS 2nd quarter 2005.
Issue resolved.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Friday, May 31, 2019 10:22 AM
To: Midrange Systems Technical Discussion
Subject: RE: STRRCYBRM *SYSTEM *RESTORE - time period for recovery recommendations
Jim,
What, in your opinion, should happen when using this STRRCYBRM ACTION(*RESTORE) OMITLIB(*DELETE)
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jim Oberholtzer
Sent: Friday, May 31, 2019 9:50 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: STRRCYBRM *SYSTEM *RESTORE - time period for recovery recommendations
What I am suggesting is the system is faithfully reporting what objects are available on unexpired media, (operative word: unexpired) deleted objects and all. It clearly points out that objects have been deleted since the media in question was used. It's now up to the system administrator to determine if those objects are needed or not.
What seems to be discussed here is an operational issue of what to do with those objects BRMS knows about but recognizes have been deleted since the last restricted state save or the last media available. I'm not sure there is a software fault, but an issue of what to do.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Friday, May 31, 2019 8:37 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: STRRCYBRM *SYSTEM *RESTORE - time period for recovery recommendations
I think the general concept is this Jim.
Let's say I did a full system save on Saturday May 25. Every day since then I've done incremental backups. Also during that week I've deleted some ancient libraries. Now, on Friday May 31 I had a system crash. I would like to do a full system restore to a state as near as possible as of the last incremental backup.
The recovery report is aware that you've deleted some libraries and they were not part of your system at the time of your last incremental backup.
It alerts you to this, allowing you to make a decision as to whether or not to restore them.
Are you saying one is supposed to take that recovery report, find the deleted libraries, and, when you run the *RESTORE option add the deleted libraries to the omit list individually and not use the *DELETED option?
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jim Oberholtzer
Sent: Friday, May 31, 2019 9:30 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: STRRCYBRM *SYSTEM *RESTORE - time period for recovery recommendations
Paul,
I'm confused, if there is unexpired media, and the report shows object that
may have been deleted on that media, how is that bad, or a problem? It
shows you they were deleted, but available for restore. You very well might be looking for those objects to restore, hence the unexpired media.
As Rob pointed out earlier, you have an option to not show those objects,
and if doing a restore, simply ignore them. So again, where is the fault
in the system?
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Friday, May 31, 2019 8:11 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: STRRCYBRM *SYSTEM *RESTORE - time period for recovery recommendations
IBM requested a copy of BRMS recovery report.
When STRRCYBRM is run with ACTION(*REPORT), the deleted items do NOT appear in the report.
The deleted items only appear when ACTION(*RESTORE).
Paul
-----Original Message-----
From: Steinmetz, Paul
Sent: Friday, May 31, 2019 7:36 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: STRRCYBRM *SYSTEM *RESTORE - time period for recovery recommendations
I am opening a ticket with IBM BRMS support.
I think the issue is there is old, unexpired, BRMS media that contains the deleted libraries.
*OMITLIB with *DELETE should handle this, but is not.
Changing the dates to the last full system save does work, and is another option.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Friday, May 31, 2019 7:04 AM
To: Midrange Systems Technical Discussion
Subject: RE: STRRCYBRM *SYSTEM *RESTORE - time period for recovery recommendations
By "including" those libraries is BRMS just printing them out as items of interest, or is it actually restoring them?
Maybe you should open a ticket.
Would it help to change the dates to only go back to your last full system save?
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Thursday, May 30, 2019 4:18 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: STRRCYBRM *SYSTEM *RESTORE - time period for recovery recommendations
*OMITLIB set to *DELETE.
*DELETE
Exclude deleted libraries from the recovery. Please note that only
libraries deleted before the last run of Start Maintenance for BRM
(STRMNTBRM) will be omitted.
It "appears" that *DELETE is not WAD.
STRMNTBRM is run daily on all LPARS.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Thursday, May 30, 2019 3:54 PM
To: Midrange Systems Technical Discussion
Subject: RE: STRRCYBRM *SYSTEM *RESTORE - time period for recovery recommendations
Did you read the help on *OMITLIB?
If so, how often do you run STRMNTBRM?
On one of my systems:
WRKJOBSCDE BRM*
Next
-----Schedule------ Recovery Submit
Job Status Date Time Frequency Action Date
BRMMAINT SCD *ALL 06:45:00 *WEEKLY *SBMRLS 05/31/19
BRMRECOVER SCD USER DEF 06:30:00 *WEEKLY *NOSBM 05/31/19
BRMREORG SCD *MONTHSTR 00:01:00 *MONTHLY *SBMRLS 06/01/19
Command . . . . . . . . . . . : STRMNTBRM RMVMEDI(*REUSE) PRTEXPMED(*NO)
PRT
VSNRPT(*NO) PRTBKUACT(*NO) PRTRCYRPT(*RCYANL *SAVEXCP)
BRMRECOVER is a custom program which creates the BRMS recovery report and stores it as a PDF on three geographically dispersed servers.
The "weekly" entries run all 5 working days.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Thursday, May 30, 2019 2:23 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: STRRCYBRM *SYSTEM *RESTORE - time period for recovery recommendations
When doing a STRRCYBRM *SYSTEM *RESTORE, what are the recommendations for Time period for recovery?
1) Let it default as below, *BEGIN *END?
2) Or should you reference your last system save?
3) Other options?
I found in testing that when you let it default, it includes libraries that are no longer on the system, from old saves that are not expired.
Start time and date:
Beginning time . . . . . . . . *AVAIL
Beginning date . . . . . . . . *BEGIN
End time and date:
Ending time . . . . . . . . . *AVAIL
Ending date . . . . . . . . . *END
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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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
