Journaling - *RMVINTENT: The preferred fork in the road for heavy journal traffic
Web Doc
Note: This is publication is now archived. For reference only.
Abstract
Shops using remote journal have often found it particularly helpful to put a “fork in the road” thereby separating the resulting journal entries into two streams: those destined for the target side and those not. Configuring your journal in this fashion can save both disk space and transmission bandwidth.
Written by Larry Youngren and Christopher Kundinger
Contents
Special Notices
The material included in this document is in DRAFT form and is provided 'as is' without warranty of any kind. IBM is not responsible for the accuracy or completeness of the material, and may update the document at any time. The final, published document may not include any, or all, of the material included herein. Client assumes all risks associated with Client's use of this document.