We have 1977 libraries omitted by one entry on our system. Acknowledging Rob's warning, it's a wonderful feature. It's one of the reasons I went to the GUI to configure BRMS; I would much prefer to stay on green screen.
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Friday, May 09, 2014 15:02
To: 'Midrange Systems Technical Discussion'
Subject: RE: BRMS system save of R&D test LPAR - adding GUI omits
I also have done the same for some IFS directories.
I did get burned already, omitted some IFS directories that caused some LPP not to restore completely.
How about on the library side, have you done any there.
The other thing I do is if there are certain libraries that MUST be saved, but the GUI omit excludes them, I created a list of libraries that must be saved.
I've been told that the specific object type omits that currently have to be done in GUI omits can now be done with green screen omits in 7.2 I prefer using green screen when managing BRMS, only reason I use OpsNav with BRMS is for the GUI omits.
Link to BRMS 7.2 enhancements.
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, May 09, 2014 11:53 AM
To: Midrange Systems Technical Discussion
Subject: Re: BRMS system save of R&D test LPAR - adding GUI omits
I think that wildcards can be dangerous. For example, if I make a library, QRYROB is that considered *IBM or *ALLUSR?
Now, if someone on your system makes a library that matches one of your wildcards...
I'm not vehemently opposed. Just something to be aware of.
From: "Steinmetz, Paul"
Date: 05/09/2014 10:22 AM
Subject: BRMS system save of R&D test LPAR - adding GUI omits
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
I'm revisiting our BRMS system save for our R&D LPAR.
This LPAR is 12tb, currently 50%.
Current system save is about 6 hours, using multiple LTO5 HH fiber drives.
40% of the 50% is all test data, which really does not need be saved.
If this LPAR had to be restored or reloaded, we would rather have the BMRS restore/recovery be done quicker without all the test data.
That data can be restored later via a separate process.
Our new thought is to omit all the test libraries in future system saves.
I'm currently reviewing the GUI omit options.
Since most of the test environment libraries begin with the same letters, we can create wildcard omits as such.
Each of the omits below will omit 22 libraries, 40%, or about 4tb of data.
This will significantly shorten both the system save and recovery, if and when needed.
Has anyone ever done a similar BRMS config?
This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.