Re: SAV not picking up fresh file in IFS for incremental backup

Patrik:

It appears you are relying on the last save parameter to determine if a
file should be saved or not. I think you are running into a problem 99% of
us ignore when saving objects in the IFS, that is 1) Save while active does
not really work, and 2) object history dates are not always updated as you
would expect them to be. I've yet to find a save of the IFS or QDLS that
actually honored those parameters to the extent that it worked as
advertised or expected. Generally we just save the entire thing (with the
omits you have in place obviously stopping those directories) and be done
with it. I understand the object attributes are what you expect them to
be, and on the face of it, it should work, (Even at V4R5) but alas, in my
experience they never really have. Incremental saves of the IFS also
complicate recovery efforts, although I'm not sure you are as concerned
about that aspect of the endeavor, maybe so, but a hobbyist machine does
not have the same requirements a full production server might have.

Of all parts of the system the IFS is the area where IBM i is the weakest,
hence why so many companies rely on Windows or Linux (my chosen route) to
perform most of the file serving etc. I won't debate why the IFS is the
way it is, there are architectural reasons IBM has for all of that, I just
accept it, deal with it and move on.
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Fri, Apr 15, 2022 at 6:15 AM Patrik Schindler <poc@xxxxxxxxxx> wrote:

Hello,

lately I changed my backup strategy to have included QDLS, and IFS into my
incremental dailies. (I recently have learned that there is a
CHGPERIOD(*LASTSAVE) parameter to be used with SAVDLO, and SAV.) I'm using
V4R5 on my venerable 150, if this is relevant.

On April 10 I added a file (a picture) into my web tree in /QOpenSys, and
also changed the referring html page.

The next day, both weren't listed in the spool file resulting from
OUTPUT(*PRINT). I wonder why that is. I expect new and/or changed files to
be included with the save.

Both files have a "changed" timestamp of both file attributes, and file
data resulting from the upload on April 10. The last Save 21 was on April
3. I could not see any "last saved" shown on the attributes when navigating
with WRKLNK, using option 8

I'm using the save command as follows:

SAV DEV('/QSYS.LIB/TAP01.DEVD') OBJ(('/*') ('/QDLS' *OMIT)
('/QFileSvr.400' *OMIT) ('/QIBM/UserData/HTTPSVR/reports' *OMIT) ('/QNTC'
*OMIT) ('/QOpenSys/var/log/*' *OMIT) ('/QSYS.LIB' *OMIT)) OUTPUT(*PRINT)
EXPDATE(&EXPDATE) ENDOPT(*LEAVE) CHGPERIOD(*LASTSAVE) UPDHST(*YES)

Any ideas about this — to me — unexpected behavior?

Note: &EXPDATE is a date I'm calculating in the CL code before to make the
content expire after 27 days.

Note 2: I encountered that I needed to use ('/QDLS' *OMIT) instead of
('/QDLS/*' *OMIT). I thought it to be a good idea to keep the empty folder
intact in IFS so the file system could be mounted after a restore. Sav
wasn't happy about that and rejected the entire command line. :-) Same goes
for /QFileSvr.400, /QNTC, and /QSYS.LIB.

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

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com