|
Justin, There are two main benefits to having the journal receiver on a separate ASP. 1) Performance 2) Redundancy The performance benefits come into play when you have a journal receiving very large numbers of transactions and the system disk is already relatively busy. The redundancy benefits are from the fact that losing two disks from your system ASP could cause data loss. With the journal receiver in another ASP you can recover the lost data. Though this redbook is a little dated, I feel its conclusions should still be applicable. The only real change from then to now is the processing power and thus how much you could push through w/o separated journals vs. having separated journals. http://www.redbooks.ibm.com/abstracts/sg246286.html?Open Questions to ask yourself, what does your current config look like, particularly MAX and AVG busy for disks and controllers vs. what your planned configuration will be. If this is a new system coming in, consider benchmarking it both ways. HTH, Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121 > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Haase, Justin C. > Sent: Monday, January 30, 2006 9:06 AM > To: Midrange Systems Technical Discussion > Subject: Professional opinions: JRNRCV in separate ASP > > Good morning, all. > > Curious as to the current "state of the systems," so to speak > - back in > the day it was common practice to put journal receivers in a separate > ASP as to not affect the disk of the system ASP. > > So my question is - how's everyone setting up new environments these > days? With the speedier disk is it really making that large of a > difference? Is it better just to add the disks you'dve used in the > second ASP to *SYSBAS and benefit from the additional arms and space? > Thoughts? > > > -- > Justin C. Haase - iSeries System Engineer > IBM Certified Systems Expert - eServer i5 > Kingland Systems Corporation > > > CONFIDENTIALITY NOTICE: This e-mail communication, including > attachments, is covered by the Electronic Communications > Privacy Act, 18 U.S.C. 2510-2521, is confidential, and may be > legally privileged. If you are not the intended recipient or > believe you received this communication in error, please > reply to the sender indicating that fact and delete the copy > you received. In addition, retention, dissemination, > distribution, copying, or otherwise use of the information > contained in this communication is strictly prohibited. Thank you. > > -- > 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. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.