MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » May 2014

RE: BRMS system save of R&D test LPAR - adding GUI omits



fixed

Sean,

The BRMS system save with wildcard GUI omits just finished, down from 6 hours to 2.5, using 2 LTO5 HH fiber in parallel.
Also included is an object list for specific libraries omitted from the GUI omits.
Omitting all the large test data was the main change.
In the near future, I will be testing a full recovery/restore from this save.
And by the way, this system save was scheduled via AJS, runs in CTLSBS.
Totally automated, unattended BRMS system saves, with append and AUTODUP.
.
STRBKUBRM CTLGRP(SAVSYS06) SBMJOB(*CTLSBS) APPEND(*YES) OMITS(*PROC.

I'm interested in why you had to use the GUI to create the control groups. I've done everything in green screen, only the omits in GUI.

Paul



-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Porterfield, Sean
Sent: Friday, May 09, 2014 6:39 PM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS system save of R&D test LPAR - adding GUI omits

Our omit list has 32 entries with the others being individual libraries to avoid omitting too much (and because that's how our old CLP had them). A few of the libraries only change monthly, so they're backed up explicitly on another job.

Looks like that system has 2354 libraries as of last RTVDSKINF on Saturday. The other one should be similar; that list of 1977 libraries I mentioned is not mirrored, so each system has its own list of those that get omitted. They all match the same name pattern, though, so the BRMS configuration is identical on both systems.

We save "most" of the system but not the libraries and a few folders we don't absolutely need in a disaster. We don't save our TEST environments other than source code.

It's interesting that Navigator tells me the BRMS configuration isn't set for GUI, since I had to use the GUI to create it. I haven't had any problems maintaining the other settings from the green screen after the omits and parallel settings were configured. When I first set it up, the parallel settings were a bit wonky, but that might have been before the 7.1 upgrade. Or maybe my client was older. Or maybe there was a full moon...
--
Sean Porterfield


-----Original Message-----
From: Steinmetz, Paul
Sent: Friday, May 09, 2014 16:29
Subject: RE: BRMS system save of R&D test LPAR - adding GUI omits

Sean,

What does your omit entry look like?
How may total libraries on your LPAR?
What actually do you save?
You should be able to go back to green screen with V7R2.

Paul

-----Original Message-----
From: Porterfield, Sean
Sent: Friday, May 09, 2014 4:26 PM
Subject: RE: BRMS system save of R&D test LPAR - adding GUI omits

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.
--
Sean Porterfield

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Friday, May 09, 2014 15:02
Subject: RE: BRMS system save of R&D test LPAR - adding GUI omits

Rob,

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.
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Backup%2C%20Recovery%20and%20Media%20Services%20(BRMS)%20for%20i/page/7.2%20Overview

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, May 09, 2014 11:53 AM
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.


Rob Berendt
--

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?
Pros/Cons.

D1*
P1*
SP*
Etc.

Thank You
_____
Paul Steinmetz


________________________________

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.
--
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.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact