Jim,
You brought up some interesting points, which I will add to.
1) I do have BRMS omits, both green screen and GUI.
I can't find the doc, but if any GUI omits are present, green screen omits are ignored. (GUI allows omit of a specific file where green screen does not).
I also found a note from an old tech doc.
http://www-01.ibm.com/support/docview.wss?uid=nas8N1019103
*SYSTEM control group will ignore all omits.
2) I also remember when I did my P5 to P7 migration, a few parts of some LPP were not restored.
After a long PMR, it was discovered they were never saved (there were some *OMITS for *LINK.
3) The 3rd item I can't remember all the specifics.
If *ALLUSR is included on the system save, and also in a more recent save, are the *ALLUSR libraries restored twice?
This is important if there are large X-LIB LF access paths which cannot be saved.
This can lengthen the restore process considerably.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Tuesday, October 25, 2016 1:48 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: BRMS system save strategy
Paul,
Intriguing question but the answer has to do with what the recovery plan is.
You touched on it by suggesting you would never use the *ALLUSR libraries from that save anyway so your recovery plan would include an *ALLUSR at other points in the save routines.
Question: Do you use omit objects anywhere in the saves? (Either IFS or in the QSYS file systems?) If so then you'll need the restricted state save as a starting point. If not, then the question becomes one of recovery point.
In short, write the recovery plan with recovery point objectives and recovery time objectives and the answer will be presented to you in that plan.
I do have many customers that only use the restricted state save to get the IBM delivered directories and libraries so the control group looks kind of
like:
Security
Configuration
SAVSYS
*IBM
I add in some objects that application would need that might not get routinely backed up as well, but that's highly dependent on the application
suite. Other save operations get all the "user data".
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Tuesday, October 25, 2016 12:39 PM
To: 'Midrange Systems Technical Discussion'
Subject: BRMS system save strategy
When doing a dedicated BRMS system save, what do you include in your BRMS control group?
I've always included everything, but was questioned today on why include *ALLUSR, because in all practicality you would never restore from this.
If a restore was needed, following the restore of *SAVSYS and *IBM, you would then restore you most recent save for *ALLUSR, would never use *ALLUSR from BRMS system save.
So should *ALLUSR be removed from the BRMS system save control group?
Group . . . . . . . . . . : SAVSYS05
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Pencor05 System Save
Weekly Retain Save
SWA
Backup List ASP Activity Object While Message
Sync
Seq Items Type Device SMTWTFS Detail Active Queue ID
10 *EXIT *******
20 *SAVSYS FFFFFFF
30 *IBM *SYSBAS FFFFFFF *NO *NO
40 *ALLUSR *SYSBAS FFFFFFF *ERR *NO
50 *ALLDLO FFFFFFF *NO *NO
60 *LINK *ALLAVL FFFFFFF *YES *NO
70 *EXIT *******
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<mailto: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:
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.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
midrange.com
