Rob,
I just want to make sure I'm understanding this. The IFS journals and journal receivers will be in a library, not in the IFS.
So they will also be saved with that library.
Also, I'm still looking for input if journaling would impact/change an IFS save, either with or without BRMS.
I'm not finding that documentation.
The last manual that gave detailed info on locking and/or SWA was Backup and Recovery, Version 4, SC41-5304-03
Lots of good stuff in that old manual, too much list, I wish I could include it all.
Why doesn't IBM carry this detail forward to the newer manuals and/or info center?
Integrated File System Considerations: Consider the following when using the
save-while-active function with the SAV or SAVRST commands.
v The wait time option is not available.
v When saving objects in libraries or document library objects, the considerations
stated previously for those objects also apply.
v When saving objects from QLANSrv or QNetWare, full synchronization is not
available.
Also, journaling could/would change your recovery process, correct.
Paul
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, November 14, 2013 11:34 AM
To: Midrange Systems Technical Discussion
Subject: RE: Back ups with High Availability Web Server
We keep our journals in a library which begins with #, like #MXJRN. Yes there are other ways to ensure your journals get restored first, but just in case someone guns through the restore like it was an AS/400 or something it helps to put that library towards the top of the list.
We use one library for all journals. Each 'group' of libraries has their own journals. If you have cross library transactions, like when you update VENDORFILE/ITEMAST you also update CUSTOMFILE/ITMHIST you probably want to journal those to the same journal.
We use one journal for all of the IFS outside of QSYS.LIB and other directories saved with other techniques.
Stream file directories that are Domino based we do not journal, we let Domino clustering take care of those. Granted, that doesn't get notes.ini modifications and that genre.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 11/14/2013 10:46 AM
Subject: RE: Back ups with High Availability Web Server
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Jim,
Would journaling certain IFS directories reduce any IFS save issues (with
or without SWA)?
Or would it just add more overhead and more to save.
When I currently journal PF, (Reorg While Active or troubleshooting an
app) I normally keep the journal in the same library as the PF.
Where would you create a Jrn for the IFS?
Would there be one Jrn for the entire IFS?
I was reviewing the STRJRN help text, examples, etc.
Paul
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Wednesday, November 13, 2013 5:24 PM
To: Midrange Systems Technical Discussion
Subject: Re: Back ups with High Availability Web Server
I agree you only want to journal IFS objects you really need to journal.
Don't just journal the root, that would be bad.....
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
On 11/13/13 4:14 PM, Sue Baker wrote:
"Steinmetz, Paul"<PSteinmetz@xxxxxxxxxx> wrote on Wed, 13 Nov
2013 21:34:55 GMT:
you can't journal the IFS.
I see that Jim O answered you on this.
Most of our IFS locked objects are system objects, log files, or
temporary files.
I would suggest
= System objects - use OMIT parameter to exclude from daily saves.
Requires trial and error to capture everything. Saving concurrent
with SAVSYS & IBM libs is probably an advised approach.
= Log files - IBM generated or user application generated?
How are the log files used? I'd likely omit as many of the log files
as possible because they are likely to be used for problem
determination and would be of little value when restoring an entire
system nor likely need to be restored due to an "oops"
event.
= Temporary files - My response is similar to log files for these.
Probably not an answer you want, but easy isn't conducive to minimal
downtime.
-- Sue IBM Americas Advanced Technical Skills (ATS) Power Systems
Rochester, MN
--
--
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.
midrange.com
