Re: NFS Backed image catalogs Was: [7.3] IFS save 21 vs. sav with chgperiod (no BRMS!)

Some of this I'll take on faith and just get started in the attempt to try.

On Mon, Feb 17, 2025 at 2:57 AM Patrik Schindler <poc@xxxxxxxxxx> wrote:

Hello Rob,

Am 17.02.2025 um 02:45 schrieb Rob Berendt <robertowenberendt@xxxxxxxxx>:

That special connection is a bit familiar.

I assume you're referring to the service tools adapter?

I've done similar things when playing with image catalogs over virtual

optical across the backplane from one lpar to another. I stopped using
that when I had conflicting lpars trying to use the same image catalog and
getting the current mounted volume conflicting.

I see. I wonder how that could have happened altogether, but then, a lot
of details are unclear. :-)

https://www.ibm.com/docs/en/i/7.5?topic=storage-virtual-optical-using-network-file-system

Part of me is concerned about the remark that it uses TFTP. TFTP is not

supported past 7.5. But I'll be happy to get that client upgraded from 7.2
to 7.4, then maybe to 7.5 after that ages.

As far as I understand the IPL mechanism works, TFTP is only needed if you
want to IPL the resulting backup image remotely. Hence I want to make it
available to VIOS, so no tftp necessary.

I will do the time trial and I'll take your caution about not expecting

great time with that.

I'm curious about your actual findings.

ne part in your instructions which concern me is the remark: Note: You

cannot create or modify remote (NFS based) image catalogs with the IBM i
provided commands. Those only work on local QSYS.LIB based objects. I fail
to see how anything with IBM i image catalog commands has anything to do
with the /qsys.lib file system. For example, what does

ADDIMGCLGE IMGCLG(CUME750) FROMFILE('/fixes/cume750/volume1.bin')

TOFILE(*FROMFILE) have to do with /qsys.lib ?

The object you create with crtimgclg, and modify with addimgclge resides
in QSYS.LIB. See the imgclg() parameter in your example.

NFS based remote image catalogs are different. They're entirely defined by
the VOLUME_LIST command, and get their final properties (being a tape or
optical catalog) solely through the association with a device file.

Does that help in understanding?

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