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



If you're looking for the best performance, then a separate ASP for
receivers can still be useful...however the key thing is that that
separate ASP needs more than just a couple of disks.

Unless you can dedicate (10+ ?)arms to a journal receiver ASP, you're
better off just leaving the receivers in your system ASP.

http://publib-b.boulder.ibm.com/abstracts/tips0602.html?Open

Charles

On Tue, Jan 25, 2011 at 12:48 PM, Kirk Goins <kirkgoins@xxxxxxxxx> wrote:
Chris,

I remember either talking with an IBMer or reading that with putting journal
receivers into a separate ASP for 'performance' reasons is not really needed
today. Today's disks and controllers are much faster and handle the extra
I/O much better than thier grandkids...

Now there are other reasons for doing it around data recovery. I always have
to add that if yo are using additional ASPs for data recovery, make sure
they are in different raid sets from the System ASP and as well as ASPs they
are protecting.

On Tue, Jan 25, 2011 at 9:23 AM, Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>wrote:

The Journal and Journaled Objects need to be in the same ASP but for
performance it is best to put the Journal Receivers in a different ASP.
I like to keep the journal in the same library as the objects, but now
with Mimix, we have multiple libraries being journaled with one journal
so that practice broke.  The journal receivers are in a different
library.  We only have one ASP but if I ever get enough disk arms to
create a second ASP, I will move the journal receiver library to the new
ASP.

Nightly we detach the current journal receivers and then backup the
receiver library.  This allows us to delete the detached and saved
journal receivers.  (Running at 87% storage utilization.  But alas we
have a new system in house with almost 3x the storage space.)

--
Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, January 25, 2011 9:00 AM
To: Midrange Systems Technical Discussion
Subject: Re: Moving Journal Receivers to a separate library, any
tips,tricks or pitfalls?

Would be nice if IBM put some "best practices" at
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/rzaki/rzak
ijrnrcvlib.htm

If you have multiple disk pools (I don't) then this may apply "the
journal
and the journaled objects must be in the same disk pool".

The one sample they gave at Infocenter had their journals and receivers
in
a library beginning with a dollar sign.

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




--
Kirk
--
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 thread ...

Follow-Ups:
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.