× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



You can do RCVJRNE (receive journal entry) on one system, send it to the
other system, and apply it to the other system in a nearly real-time basis;
that's the easy part.  It's getting everything back to the production system
that's nasty; when you're on the backup (now primary) box, you have to
change directions and SNDJRNE on iBox #2 back to iBox #1.  The benefit of
doing it real-time is you limit your exposure to lost transactions (if you
CHGJRN every 4 hours and the system crashes at 3:59, you're out 4 hours'
work).

The 3rd-party products handle all of this (and I have no vested interest in
any appropriate product); the last thing you want to worry about in a
disaster is tinkering with your code.  You'll probably be busy filling
sandbags or fighting off the rebels...but I can't get too political here,
lest the moderator...well, you know.

Remember that journal recovery is a database-intensive operation.  There's
no application logic and the database processing is by RRN; disk performance
and logical file structure is a contributing factor in recovery time.  It's
not like restoring a file from tape...even fast tape!

In my applications, I journal all master and transactions files but don't
journal any work files or access paths.  I define a work file as one that
can be recreated simply by rerunning the job.  I used to have a couple of
data areas but eliminated them for several reasons (not journalable being
one, but I think that's changed); don't forget about them, or
configurations, or user profiles...the list goes on!

-----Original Message-----
From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]On
Behalf Of Chuck Morehead
Sent: Wednesday, October 24, 2001 10:16 AM
To: MIDRANGE-L@midrange.com
Subject: Journals across machines

The hypothetical scenario:
I have two AS/400's with identical databases.  I.e. A save is done on AS/400
1 and restored to AS/400 2.
As soon as the save is done on AS/400 1, journalling of the database is
started.
At regular intervals the journal receivers are saved on AS/400 1, restored
on AS/400 2, and applied on AS/400 2.

1.  This is possible, isn't it?  That is, to apply journals on a different
machine in this manner?
2.  Has anyone implemented something like this as part of a disaster
recovery plan?  If so, how well did it work?

TIA!

Chuck Morehead
Nokuse Consulting - Providing high value Information Technology Services.
Native Bear Software - Providing affordable Industry Specific Software.
http://www.nokuse.com


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.