× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. May 2019

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.