× 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 2015

RE: BRMS Recovery Script Questions


Paul,

I just did a comparison of our backup times and ours are not that much
different in times either.

I think for the hassle the recovery presents with having Entire, Full and
Cumulative changes involved I will do the same.

I have enough time prior to the DR test to "simplify"  it some what then
consider the other points Jim brought up.

Thanks for your input.  (Always nice to know what others are using and
doing)......

 Laura Roberts











From:	"Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To:	"'Midrange Systems Technical Discussion'"
            <midrange-l@xxxxxxxxxxxx>,
Date:	12/05/2015 07:34 AM
Subject:	RE: BRMS Recovery Script Questions
Sent by:	"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I experienced the mentioned issues when I migrated from P5 to P7.
As Jim stated, they never work 100%.
We did change our save to simplify the recovery.
Compare you weekly save time to your daily changed objects.
In our case there was not much difference, so we got rid of changed
objects, do a full save every night, 2 hours, LTO5 HH Fiber.
Simplifies the recovery.
Another thing we found was that we need to customize the BRMS recovery
report so 100% recovery is possible.
This is still work in progress.
IFS locked objects is our biggest outstanding issue, and it is only getting
worse as more of the newer apps are using the IFS.

Paul


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Oberholtzer
Sent: Tuesday, May 12, 2015 8:44 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: BRMS Recovery Script Questions

;-)  More for the Archives that you Rob.  I suspect all of your systems are
fully recoverable and properly tested.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Tuesday, May 12, 2015 7:40 AM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS Recovery Script Questions

I totally agree with you.
I even stated that it was more of a migration than a DR test.
What more can I say?  Other than to not have brought it up in the first
place?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to:  2505 Dekko Drive
          Garrett, IN 46738
Ship to:  Dock 108
          6928N 400E
          Kendallville, IN 46755
http://www.dekko.com





From:   "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
To:     "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date:   05/12/2015 08:34 AM
Subject:        RE: BRMS Recovery Script Questions
Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



That's not a real recovery test.  That just tests IBM's code for the
umpteenth time.

A real recovery test is to pick a date within the last 14 days and recover
to it with the tapes that are normally generated.  In all the recovery
tests I've done for customers (many on to Agile's equipment) I've never
seen the first one work, rarely the second one, and generally the third
one gets into the acceptable range (meaning the company could continue
business with some additional work to follow)

The only recovery tests that do work are the ones that have been done
several times with the backup routines changed to match the recovery
plan/requirements.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Tuesday, May 12, 2015 7:08 AM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS Recovery Script Questions

When I did a brms recovery it was from a brms full save immediately prior.

 More of a migration than a DR test.  However, I did do 11 migrations this
way.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to:  2505 Dekko Drive
          Garrett, IN 46738
Ship to:  Dock 108
          6928N 400E
          Kendallville, IN 46755
http://www.dekko.com





From:   "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To:     "'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx>
Date:   05/11/2015 03:47 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 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 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 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.

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