RE: BRMS Recovery Script Questions

Hi Paul,

1. Our weekly and daily backups are NOT SWA and not totally dedicated but
we do end Qhttpsvr and punt off any users in Qinter prior to BRMS backup
start. . Very seldom do we get an object not saved and they are only 1 or 2
*DTAQ.

2. Yes we OMIT some library and IFS info from our Weekly and Daily saves:

Qusrsys objects:  omit -> Lcotpjobs, Qa1psc, Qaokp01a, Qaokp04a, Qaokp08a,
Qaop09a, Qasnadsq,
Qusrdirdb object: Qgldlock
Qmpgdata:  All omitted

IFS:
/QSYS.LIB
/QDLS
/TMP/BRMS
/QIBM/ProdData
/QOpenSys/var/log and a few more logs

How did you work around your saved changed IFS obj issues ?

Thanks


Laura Roberts
System Administrator, Information Systems and Technology

306.667.5260
Saskatchewan Blue Cross
sk.bluecross.ca I push2play.ca

Please consider the environment before printing this email.










From:	"Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To:	"'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx>,
Date:	11/05/2015 01:46 PM
Subject:	RE: BRMS Recovery Script Questions
Sent by:	"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



1) Are your weekly and daily saves dedicated, SWA, or other?
2) Do you intentional omit any library objects and/or IFS objects?

I did a similar test back in May 2013.
1) Missed and locked objects from the save were was the main reason for
recovery issues.
2) Recovery of IFS from an IFS changed object save also had issues.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
LRoberts@xxxxxxxxxxxxxxx
Sent: Monday, May 11, 2015 2:46 PM
To: midrange-l@xxxxxxxxxxxx
Subject: BRMS Recovery Script Questions


Hi,

We will be performing a DR test next month on a system supplied by IBM for
our test. We will be using BRMS Recovery script for the first time. I have
a couple of questions in regards to the BRMS recovery script if anyone
would like to share their expertise it would be very much appreciated.

Background:
We are on V7.1  Cume TL14283 and TR 9  Our recovery strategy includes 3
media tapes: (as we do not perform *savsys nightly) and yes we save our
access paths with each save.

1. *savsys (monthly) entire system save  Media: SI0176
2. *savlib (weekly)                                      Media: SI0159
3. *savchgobj (daily cumulative)               Media: SI0009

Questions:

      1. Update System Name in the BRMS Media Information step:  In a DR
test and restoring from savsys would the local network and default local
location on the new test system be the same anyway or am I missing
something ?

   2.		 In the step of :Recover Required System Libraries:  (snapshot
below)
      Can I select all 6 selections below all at once even though the media
      switches back and forth weekly to daily at each library and the fact
      that daily is a *Cuml type. Is BRMS smart enough to do the savlib and
      savchgobj restore. Or does it make sense for me to only select just
      the weekly ones first then does the screen come back to be able to
      select the daily ones (speed perspective) so not to have to unload
      tape media so often ?

(Embedded image moved to file: pic27901.gif)


   3.		 Has anyone used the Recover Media sets concurrently step ?
Pros/Cons

   4.		 If I don’t use the Concurrent option, do most people Recover
All
      Remaining System and User data at this point (then jump to the
      Recover Directories and Files as the script says) Or would you
      recommend doing the more separated BRMS recovery script steps by
      “Recover IBM  Product Libraries, then Recover user Libraries, then
      Recover Documents Library Objects then get to the recover Directories
      and Files) ?

Any tips/gotchas or recommendations ?

Thanks so much

Laura Roberts



This communication, including all attachments, is for the sole use of the
intended recipient(s) and may contain confidential, personal and / or
privileged information. Any unauthorized review, use, disclosure or
distribution is strictly prohibited. If you are not the intended recipient
or a person responsible for delivering this message to an intended
recipient, please contact us immediately so we may correct our records.
Please then delete or destroy the original transmission and any subsequent
reply.
--
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.

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

This communication, including all attachments, is for the sole use of the intended recipient(s) and may contain confidential, personal and / or privileged information. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply.