Re: Best Practice Question

Patrik,
If you want everything on DASD at a point in time you could try FlashCopy.
On three of our more critical LPARs we do a flashcopy 12 hours after the
saves. We also do one each quarter after we bring the system into
restricted state but before applying PTF's, etc.
We started this to have copies in case of malware attacks.
Look up Safeguarded Copy Tool Kit from IBM. I think it's now part of the
bundles. We got it from IBM Lab Services. It's kind of a special
offering. One of these years it should be certified for IBM i 7.6.
It takes mere seconds to create a copy.

On Wed, Aug 20, 2025 at 8:23 PM Patrik Schindler <poc@xxxxxxxxxx> wrote:

Hello Jim,

Am 20.08.2025 um 23:01 schrieb Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx>:

Um, maybe not “best practice “

Does any other application or LPP use /tmp? At least some of the LPPs

use it. If lost you’ll loose several flight recorder type logs etc.

Keep recovery in mind with these things. If you know nothing in there

is needed for forensic use OK, but be sure.

If any application places indispensable data in /tmp, I'd consider this a
program error.

If a user places indispensable data in /tmp, this is as plain stupid as
those users using the macOS or Windows Trashcan as "sort me later"
temporary storage.

/tmp sounds like "temp" for a reason. :-)

One could debate the expendability of flight recorder type logs. From my
PoV, those should not be created in /tmp, because they are logs and hence
belong to /var/log, with a proper automatism to expire old entries. And
we're back to a program error.

My $.02.

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