RE: BRMS restore after group SF99724-26 -- MIDRANGE-L

When you import the tape to the other VTL from replication in the vault it lists it twice.
Once with at status of RW and once with a status of RD-RO.
Clue: Do not import the RW, use the RD-RO.
One might assume that using one import or the other tells the library whether to activate the write protect tab, and it well might. And RD-RO is probably what you safely want to do a restore. But it also could have been the difference between listing the items on the tape as saved from the previous night versus listing the items on the tape from a January save, thus having different sequence numbers (thank God for preventing an even more obscure wonder about why is the data so dated).
I do not think the export back to the vault and reimporting was a time difference to get the replication done from the other site, as I would have expected it to be done prior to that time in the afternoon.
But that might be something to audit. This actually makes more sense than whether or not the write protect was activated.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of DrFranken
Sent: Wednesday, March 20, 2019 12:32 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: BRMS restore after group SF99724-26

Well that sucks for you.

For the rest of us though, cool! :-)

Thanks for letting the list know.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 3/19/2019 6:26 PM, Rob Berendt wrote:

Yep, operator error

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Rob Berendt
Sent: Tuesday, March 19, 2019 6:20 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: BRMS restore after group SF99724-26

Looks like it is NOT brms, nor any other part of IBM i. It's either the VTL replication from one DC to another. Then again it may be operator error as my coworker often does the data refreshes and I'm trying one.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Rob Berendt
Sent: Tuesday, March 19, 2019 5:08 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: BRMS restore after group SF99724-26

If you test on your system, I am betting this is a SAVE issue, not a restore issue. I am basing this on the difference in sequence numbers between WRKMEDBRM and DSPTAP. Therefore make sure you do your comparison on a save after level 26. Of course, seeing them match before level 26 might be proof of the pudding.

Hmmm, let me test that...
WRKMEDBRM TYPE(*ACT) SLTCRTDATE(022519) SYSNAME(GDIHQ2) SORT(*CRT) This date was before applying that group.
Volume Creation Expiration
Serial Status Date Date
U00024 + *ACT 02/25/19 04/08/19
U00025 + *ACT 02/25/19 04/08/19
U00462 + *ACT 02/25/19 04/09/19

Saved Save Save Save Parallel Volume File
Item Date Time Type Devices Serial Sequence
ERPLXF 2/25/19 23:41:12 *FULL 3 U00024 90
ERPLXF 2/25/19 23:41:12 *FULL 3 U00025 89
ERPLXF 2/25/19 23:41:12 *FULL 3 U00462 93

DSPTAP

Cartridge ID . . . : U00024
Data file label . . . . . . . . . : ERPLXF
File sequence . . . . . . . . . . : 0000000090

Cartridge ID . . . : U00025
Data file label . . . . . . . . . : ERPLXF
File sequence . . . . . . . . . . : 0000000089

Cartridge ID . . . : U00462
Data file label . . . . . . . . . : ERPLXF
File sequence . . . . . . . . . . : 0000000093

So the sequence numbers used to match before the group PTF. Yee haw!

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Rob Berendt
Sent: Tuesday, March 19, 2019 4:53 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: BRMS restore after group SF99724-26

Has anyone done any parallel restores since putting on BRMS group SF99724-26?

I am trying to restore a library, ERPLXF.
WRKMEDBRM, etc shows it on three tapes.
U00038, sequence 90
U00059, sequence 89
U00060, sequence 93

DSPTAP of those tapes shows
U00038, sequence 88
U00059, sequence 88
U00060, sequence 87
DSPTAP shows that sequence U00060-93 is ERPLXO, not ERPLXF like WRKMEDBRM shows.

So when I run this command
RSTLIBBRM SAVLIB(ERPLXF)
DEV(KDVLVTL)
SAVLVL(*CURRENT)
ENDOPT(*UNLOAD)
MBROPT(*ALL)
ALWOBJDIF(*ALL)
FROMSYS(GDIHQ2)

BRMS tries to restore from U00060 sequence 93 and dies with
Message ID . . . . . . : CPF3717
Message . . . . : File not selected. File label or file name mismatch
for file ERPLXO.
Cause . . . . . : The file on volume U00060 sequence number 93 was not restored because of a mismatch of file names.

Luckily I am just trying to restore to a test system.

Service request number
03920,082,000

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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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: https://amazon.midrange.com