|
Have you examined the 192 not saved, are they log files or ??--
On Fri, May 17, 2013 at 4:16 PM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>wrote:
I've done some additional IFS save testing, with and without SWA.
IFS with SWA resulted in no improvement for number of objects saved,
same amount were excluded.
It did double the IFS same time.
Has anyone had success with IFS SWA?
At this point, I do not have an IFS save solution that will result in
a good speedy recovery.
Any thoughts from the group.
IFS full save with SWA *YES - 242902 objects saved. 192 not saved.
36 minutes IFS full save with SWA *NO - 242902 objects saved. 192 not
saved. 17 minutes IFS full save with SWA *SYNC - 242902 objects
saved. 192 not saved. 25 minutes
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Fenstermacher
Sent: Tuesday, May 14, 2013 1:44 PM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS recovery
Yes we use SWA and we use omits in the IFS. The missed IFS objects
are log files we don't care about.
Paul Fenstermacher | Sys/NW Admin,Sr | Corporate Systems - POWER
Systems Administration | Jack Henry & Associates, Inc.(r)
663 West Highway 60 | Monett, MO 65708 | Ph. 417.235.6652 | x177389 |
pfenstermacher@xxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Wednesday, May 08, 2013 2:27 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: BRMS recovery
Paul,
How do you handle the IFS (*LINK) and QLNKOMT?
Do you use Save While Active?
Paul
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Fenstermacher
Sent: Wednesday, May 08, 2013 3:20 PM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS recovery
Been doing it for years and I wouldn't think about doing it without BRMS.
It's a complete, functional product and I would suggest you keep
working with it.
Paul Fenstermacher | Sys/NW Admin,Sr | Corporate Systems - POWER
Systems Administration | Jack Henry & Associates, Inc.(r)
663 West Highway 60 | Monett, MO 65708 | Ph. 417.235.6652 | x177389 |
pfenstermacher@xxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Tuesday, May 07, 2013 11:54 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: BRMS recovery
I've completed my BRMS test recovery, with limited success. Libraries
went well, DFID did its job. IFS is another story.
Did you know, (per IBM development, not yet documented, new knowledge
base doc is being written) if you use QLNKOMT list and *LINK in your
BRMS saves, only the very last *LINK is presented for recovery. I
always assumed that my entire IFS would be restored from my last
dedicated system save. This is not the case. We use QLNKOMT due to
all IFS locked items that cannot be saved while active.
So either before step 19 in the BRMS recovery report, or immediately
after, one would have to do either
1) QSYS/WRKMEDIBRM LIB(*LINK) , position back to last dedicated
system save, and manually select all the items that were omitted.
2) Have a CL already created with all items from the QLNKOMT list.
__ STEP 019 : Recover Directories and Files
Saved Save ----- ASP ------ Save Save Not
Sequence Control Volume
Item Type Name Number Date Time Saved Saved
Number Group Identifier Encrypt
---------- ------- ---------- ----- -------- -------- -------
-------
--------- ---------- ---------------------------- -------
*LINK *FULL *SYSBAS 00001 5/06/13 0:21:45 194,424 0
14727 SAVFULL05 001008
In summary, I am really considering not using BRMS for system
recovery purposes, (too many nuances and exclusions in the recovery
report), not too also mention it is very slow.
It is great for individual application recovery, but it needs a lot
of work for total system recovery.
Last year, migrating from P5 to P7, I did a P5 Save 21 LTO3,
followed by a P7 Restore 21 LTO5. Total migration was 8 hours, 4 hour
save, 2 hour restore (SSD drives)
So, I'm asking the group, how do you all recovery your systems when
they fail? Restore 21, BRMS Recovery, or custom.
I'm leaning towards Document Number: 457133341 Restoring a System
without BRMS When the Save Was Done with BRMS
It is possible to restore a system from a save done using BRMS
without using BRMS for the restore. However, when doing this, there
are some precautions users must be aware of.
o It is suggested that QMSE, QUSRBRM, and QBRM libraries be
restored after the License Internal Code and the operating system
have being restored. This prevents errors from occurring when QUSRSYS
library is restored.
o BRMS does not do a *NONSYS save of the libraries: RSTLIB
SAVLIB(*IBM) OMITLIB(QMSE QBRM) and RSTLIB SAVLIB(*ALLUSR). QUSRBRM
is not saved in *ALLUSR; therefore, there is no need to omit it.
o GO RESTORE Option 21 can not be used.
o Example of the commands to be used are as follows:
Restore the License Internal Code and the operating system RSTLIB
SAVLIB(QBRM QMSE QUSRBRM) RSTUSRPRF RSTCFG RSTLIB SAVLIB(*IBM)
OMITLIB(QMSE
QBRM) RSTLIB SAVLIB(*ALLUSR) RSTDLO RST DEV('QSYS.LIB/media device
name.DEVD') OBJ(('/*') ('/QSYS.LIB' *OMIT) ('/QDLS' *OMIT)) ENDOPT(*LEAVE)
RSTOBJ OBJ(*ALL) SAVLIB(QUSRBRM) MBROPT(*ALL)
ALWOBJDIF(*AUTL *FILELVL *OWNER *PGP)
RSTAUT
Paul
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, April 22, 2013 10:15 AM
To: Midrange Systems Technical Discussion
Subject: Re: BRMS recovery
Paul is surely doing a thorough test. Many shops may do incrementals
but when it comes to their system test they always perform a full
system save immediately beforehand and do the restore with that.
Paul is not. He's really testing that.
He is even having me think about our systems full recovery. For
example, we do a full system save on our primary machine once a
quarter. That is the only time, ever, that tape touches that
machine. For nightly backups we do backups on our Mimix backup lpar.
Once a quarter we have reviews (before the save time rolls around).
The BRMS reports do not address this situation and we pretty much
have to wing that. Yeah, we ought to document this sometime...
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
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@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.
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply email
and delete all copies.
--
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.
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply email
and delete all copies.
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
