Re: Journaling and Disaster Recovery

Mike,

Some years ago I worked for a BP providing support for a data replication
product. We used to put our *JRNRCV objects in a library called @JOURNALS.
Although this is not very imaginative, either, it has the advantage of
placing this lib ahead alphabetically, so it would be restored before the
rest.

HTH,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries


On Tue, Nov 17, 2009 at 9:23 AM, Mike Cunningham <mike.cunningham@xxxxxxx>wrote:

We recently did a full backup from one system and restored to a new one
(same serial number) and discovered after the restore that none of our files
where being journaled. (SQL insert errors alerted us to this problem). Our
journals are in a library named JOURNALS and our files are in FILES (aren't
we creative in our naming). FILES was restored prior to JOURNALS.

Is the best way to prevent this from reoccurring to rename JOURNALS as
SSJOURNALS or move the journals into FILES? We put them in their own library
in case someday we put them in their own ASP and so we could easily backup
just journals if needed. Or we just know that this will occur, document it
and be prepared to restart journaling after a full restore. Any words of
wisdom for best practice?

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