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



I found the differences.
Most files we restore are from Production LPAR, always a FULL, never any CUML involved.

On our R&D LPAR, we have a combination of FULL and CUML.

In regards to the R&D library mentioned below, there was both a FULL and CUML save for the same day.
So when restoring that library to a previous date, RSTLIBBRM first restored from the FULL, then a 2nd restore from the CUML.

Working as designed.
I never knew the feature existed, with one BRMS RSTLIBBRM command.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Tuesday, July 05, 2016 9:23 AM
To: Midrange Systems Technical Discussion
Subject: Re: RSTLIBBRM previous date - restore incremental defaulting to . . . . . . *YES issue

I suppose, in theory, one could do a full restore from some time back, and also restore incrementals since then.
For example, if someone ran
DLTF ROB/ARC*
and deleted all my archive data. I may want to restore back from that date, and all incrementals since then.


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 Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 07/05/2016 09:10 AM
Subject: RSTLIBBRM previous date - restore incremental defaulting
to . . . . . . *YES issue
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I ran into an issue when using RSTLIBBRM with previous date along with
restore incremental defaulting to . . . . . . *YES issue.
After the RSTLIBBRM completed, (with the previous date specified), the job
tried to do a 2nd restore from current date.
The job failed with a CPF412F because the current volume was not available
at the time.
BRMS sent a BRM1426 - Mount volumes MEDIA SET #1:001302 on devices
TAPMLB01.

I've been using RSTLIBBRM for years, mostly with Save level . . . . . . .
. . . . *CURRENT, as needed with previous dates.
I've never seen this behavior.
Is this normal or did something change with a recent PTF?
I'm wondering that when doing a RSTLIBBRM with a previous date, we must
ensure that restore incremental is set to *NO.
If requesting a previous date, you would not want the current date also
restored.

Any thoughts from the group?

Restore incremental (RSTINCR) - Help

Specifies whether or not to restore any incremental or object level
saves of the object. Currently the Restore Library BRM (RSTLIBBRM)
command will restore the full backup of the library that corresponds to
the copy requested in the Save level (SAVLVL) parameter, plus the last
incremental backup of that library preceding the next full backup of the
library, plus any object level saves that are between the two full
saves. This assures that the copy that you requested has all changes
restored prior to the next full save.

*YES
Specifies to restore all incremental and object level saves since
the last full save of the object.

*NO
Specifies not to restore any of the incremental and object level
saves since the last full save of the object.

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.