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


  • Subject: Re: DB recovery from journals
  • From: Pete Massiello <pmassiello@xxxxxxxxxxxxxxxx>
  • Date: Thu, 01 Apr 1999 17:37:22 -0500
  • Organization: OS Solutions International

Ken,

    I have done many restores when everything has been on the local system, and 
I
basically do it differently and it works great.

    After getting the Lic on the machine, I restore OS/400 and related stuff 
from
my SAVSYS.  Then the next thing is to restore the User Profiles (otherwise when
you restore the objects you have ownership issues).  Then I would restore my 
user
libraires, but I would make sure that the Journal RCVRs are restored first, then
the Journals, and lastly the physical files.  You must use this order, otherwise
when you restore your files they will not be journaled.

    So, using this approach, if you slipped the journals and remote journals in 
I
think you will be fine.

    HTH

        Pete Massiello

"Graap, Ken" wrote:

> Hello all...
>
> I'm planning to perform a disaster recovery test using journals. We will be
> simulating a loss of our production system between backups and would like to
> recover right up to the time of failure. I would like this test to be
> successful so I need to completely understand how to do it before I spend
> thousands of $$$'s trying... <smile>
>
> I am currently journaling all production DB files to a remote system via the
> remote journaling support in OS/400.
>
> *** The production database, along with the journal is located in library:
> SOURCEDB on our production (source) system
>
> *** The local journal receivers are located in library: SOURCERCV on the
> production (source) system.
>
> *** Remote journaling is defined using library redirection to library:
> TARGETRCV on our remote journaling (target) system.
>       As receivers are replicated to the target system they are
> automatically deleted from the source system.
>
> I  regularly back up my production database and remote journal receivers via
> SAVLIB commands on both systems.
>
> ----------------------------------------------------------------------------
> -------------------------------------
>
> Here is how I believe I'd recover my production system at a disaster
> recovery site:
>
> I arrive at the site with B/U tapes from both my production (source) system
> and my remote journaling (target) system.
>
> After restoring LIC, OS/400 and all that stuff I would then:
>
> 1.) Restore the SOURCEDB library to library SOURCEDB on the disaster
> recovery system
>
> 2.) Restore the journal receivers from library TARGETRCV to library
> SOURCERCV on the disaster recovery system.
>
> 3.) Insure that the receiver chain is correct and current using the  "Work
> with Receiver Directory" display.
>       If it isn't then I'd use the  "Associate Receivers With Journal"
> option from the WRKJRN display.
>
> 4.) Apply journal changes via the "Forward Recovery" option from the WRKJRN
> display.
>
> My questions for this distinguished group are....
> Is it really this simple?
> Has anyone done a recovery like this?
> Are there any "gotchas" I need to know about?
> Am I correct in assuming I can just restore the receivers from the target
> system and easily associate them with the restored journal from the source
> system prior to applying them to the DB files?
>
> thanx in advance for all your input, and wish me luck with my test... :)
>
> Kenneth
>
> --
> ********************************
>        Kenneth  E.  Graap
>     IBM Certified Specialist
>           AS/400   Professional
>           System  Administrator
>  NW Natural - Information Services
>            System Services
>         503 226 4211 X5537
>           FAX  503 721 2521
>       keg@nwnatural.com
> ********************************
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---

--
Pete Massiello
OS Solutions International
Phone: (203)-744-7854  Ext 11.
http://www.os-solutions.com
mailto:pmassiello@os-solutions.com


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


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.