Re: comfort level in not performing TAPE backups...

You are correct that the SAVCHGOBJ is cumulative, unless you are specifying
a literal in REFDATE and use the default of UPDHST(*YES)...

Also, if you've add a new library since the full system save and are using
REFDATE(*SAVLIB); then neither the new library or any of the objects in it
are saved :/

Lastly, if you leave the default OBJJRN(*NO) then none of your journaled
objects are saved! Just the journal receivers. So you'd need all to
APYJRNCHG against all journal recivers (possibly on multi SAVCHGOBJ tapes)
since the last full system backup.

If you _have_ to use SAVCHGOBJ to meet your backup window...then by all
means do so. But make sure you understand the pitfalls.

Otherwise, stick with a simpler method.

Charles


On Fri, Apr 25, 2014 at 1:07 PM, Briggs, Trevor (TBriggs2) <
TBriggs2@xxxxxxxxxxx> wrote:

<SNIP> This is how SAVCHGOBJ is designed to work. You do a full save on
tape BR0291. You do a SAVCHGOBJ on the next day and the only objects
that changed were A, B, C on BR0484 On the day after the SAVCHGOBJ gets
C, X, Y on BR0119. So now, to do a full save of all the objects you will
need all three tapes.<SNIP>

That's not how I understand it, nor how I've done backups since we got
our first System/38. (I know...SAVCHGOBJ probably doesn't go back that
far, but still). The default for the REFDATE parameter on SAVCHGOBJ is
*SAVLIB, which means AFAIK, that unless you change this value to
yesterday's date on every daily save, it will save every object that has
changed since you last did a SAVLIB on that object's library. Therefore,
in your example, objects A, B, C, X and Y would all get saved on the
second day. Therefore to do a full restore (I assume that is what you
meant), you would need only tapes BR0291 and BR0119. Now, one caveat of
all the preceding is that I know nothing about BRMS and am only taking
about what happens when using the raw IBM commands.

Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, April 24, 2014 5:27 PM
To: Midrange Systems Technical Discussion
Subject: Re: comfort level in not performing TAPE backups...


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko

--
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 message originates from Lincare Holdings Inc. It contains information
which may be confidential or privileged and is intended only for the
individual or entity named above.
It is prohibited for anyone else to disclose, copy, distribute or use the
contents of this message.
All personal messages express views solely of the sender, which are not to
be attributed to Lincare Holdings Inc., and may not be copied or
distributed without this disclaimer.
If you received this message in error, please notify us immediately at
MailAdmin@xxxxxxxxxxx or (800) 284-2006.

************************************************************************************************************************************************************************************************************

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