Re: Question on BRMS *SYSTEM Backup Control Group....

Andrew:

There is nothing in BRMS that looks like a *NONSYS. Your partner needs to
spend 20 minutes with the internet to discover how to recover the box.
Paul and others gave you good links into BRMS although I have to admit I
rarely do it quite that way when I do the restore manually, ordinarily
driven by application needs.

This year I've done so many recoveries like the one your suggesting I've
lost count of them, and did a 10TB system just this last weekend. This
should be routine, and there is a specific section on the test business
partners had to take (before this year) to get IBM to let them sell POWER
that included questions on this topic. I'm shocked they don't understand
it.

If you have BRMS, you have the media definition so you could use multiple
drives in your save/restore using the IBM save/restore commands, but that
requires advanced knowledge of BRMS. Note: BRMS creates the media
definition as part of the INZSYS *DEVICE command so transporting it from
one box to another most likely would not work unless the devices were
identical on both boxes.


Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Thu, Oct 25, 2018 at 6:44 AM Andrew Lopez (SXS US) <
Andrew.Lopez@xxxxxxxxxxxxxxxxxx> wrote:

The only caveat is if BRMS used multiple devices on the save, then BRMS

must be present to run the restore, since the media definition would be
needed to

drive the multiple devices on the restore. If you knew where to find

the media definition then the IBM supplied restore commands can be used.
It could

be done without the media definition but it would be very ugly.

I wish we had parallel tape drives, I would love to cut the backup
window. Unfortunately our DR partner, who specializes in JD Edwards
installations, doesn't support LTO 7 on the iSeries, or tape libraries with
multiple drives. It is what it is. While I recognize it isn't good, I
don't make the call. Under normal circumstances, we MImix replicate to
them.

That said, instead of restoring a SAVSYS and then a NONSYS as a "21"

save or restore would do, you would restore SAVSYS, followed by *IBM, then
*ALLUSR, ALLDLO, and

finally the IFS. That's all the BRMS *SYSTEM control group is doing.

All the standard OS commands can be used, and I do it that way frequently.

I suspect that's where things went south. Our IBM partner's tech had the
steps documented and didn't know how to handle it when he couldn't use the
NONSYS label expected. I still don't know how he loaded a V7R1 system on a
V7R3 box, but I suspect he overwrote most of the V7R3 install with V7R1,
then performed an upgrade after IPL'ing from the D source that had V7R3.
If I understand it correctly, he could never have brought up a 41A system
on V7R1. One way or the other, he managed to pull it off.

Which still leaves me with partners who don't know how to use a BRMS
*SYSTEM save to restore an entire system. It would be easier for me if
*SYSTEM created a tape that was indistinguishable from a manually created
Go Save-->21. I might go through the CL for the manual process and see if
I can create a Backup Control Group that replicates it exactly.





--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD