Re: [7.3] IFS save 21 vs. sav with chgperiod (no BRMS!)

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

Trying to see how many questions you are asking.
1 - Are certain files not saved?  Yes.  To turn it on for a file it would
be CHGATR '/mydir/myfile' ALWSAV(*NO).  IBM does this for many files that
are simple logs.  Keep in mind that save while active of IFS stuff is a
sick joke.  So IBM feels the message id for 'this item was not saved
because it was flagged not to save' can be handled differently than 'this
file was not saved because it was locked'.

2 - *lastsave:  When using that, did you set the UPDHST(*YES) on the save
everything save?  The default is *NO.  I was going to suggest
IFS_OBJECT_STATISTICS to compare changed timestamp vs last saved timestamp
but that latter doesn't seem to exist so IDK where they compare that to.
GO SAVE, 21 defaults to UPDHST(*YES).

3 - Recommendations regarding the save to alternative media.  I'm going to
pass on this.

On Thu, Feb 13, 2025 at 6:57 AM Patrik Schindler <poc@xxxxxxxxxx> wrote:

> Hello,
>
> I'm still learning about establishing a meaningful save routine for a (to
> me) newer 7.3 installation to a remote NFS based optical image catalog.
>
> The backup concept is basically:
> - do a save 21 "now and then" (manually),
> - run savchgobj updhst(*no), savdlo dlo(*chg) updhst(*no), and sav
> chgperiod(*lastsave) updhst(*no) each night.
>
> That's how I'm doing that on my V4R5 box to tape and that saves only
> things which have changed since the last Save 21. I'd expect that to behave
> similarly on newer releases.
> Goal is being able to copy the last Save 21 image to the VIOS image
> catalog, IPL from that and restore LIC, system and other objects, including
> DLO and IFS. Afterwards, restore the last differential saves from the
> remote NFS device.
>
> I'm observing that a huge load of files from the IFS is being saved over
> and over again. Nearly 1.3 GB of objects duplicated needlessly, day after
> day, because they have not changed since the last Save 21 and hence should
> not be eligible for ending up in a sav chgperiod(*lastsave) updhst(*no).
> Note: I'm not actively using the IFS, yet. Nor do I use /QDLS. But I want
> to save everything because it makes restores easier. No need to think about
> further manual steps.
>
> That's my sav command line:
>
> sav dev('/qsys.lib/optbkup01.devd') obj(('/*') ('/qsys.lib' *omit)
> ('/qdls' *omit) ('/qntc' *omit) ('/qfilesvr.400' *omit)) output(*print)
> chgperiod(*lastsave) updhst(*no)
>
> Apparently, (certain?) IFS objects aren't saved, or not being flagged as
> "have been saved" through a Save 21. Haven't checked that, yet. I dimly
> remember that the topic about a "special flag" for IFS objects regarding
> saves has been discussed here in the pastime. Can't remember details, so I
> can't search for that.
>
> With my current knowledge, allowing Save 21 to save the complete IFS seems
> to be the way to go, because I don't intent to reinstall the OS from
> scratch after a catastrophic failure, but IPL and restore from backup, see
> above.
>
> Can anyone shed some light on the "correct" approach? And/or what to do
> about the apparent fact that a full system save seems to not save
> *everything* on that system?
>
> Thanks!
>
> :wq! PoC
>
> --
> 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@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.