It’s very much a customer specific decision often based on business use or requirements, SLA’s or the basic requirement of failover whereby the original Prod site remains operational and has to be used as a Remote target.  Rich Forshaw Consultant Corporate Systems Engineer - RecoverPoint & VPLEX (EMEA) Data Protection and Availability Solutions EMC Europe Limited Mobile: +44 (0) 7730 781169 E-mail: richard.forshaw[NAME].com Twitter: [NAME] EMC Europe Limited Registered in England with Company No. 00990752 Registered office address: Level 1, Exchange House, Primrose Street, London C2A 2EG The information contained in this e-mail message and any files transmitted with it are confidential. It is intended only for the addressee and others authorised to receive it. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are advised that you have received the e-mail in error; please delete it and notify the sender immediately. You should not retain the message or disclose its contents to anyone. Any disclosure, copying, distribution or action taken in reliance on the contents of the e-mail and its attachments is strictly prohibited.
I've read thru the previous discussions and didn't see one similar to my question.  When you look at the Consistency Group, that shows the path of the writes, it doesn’t show any writes to the Production journal. I always assumed Writes get copied to the Prod Journal, and from there are sent to the Remote Journal but the flow diagram doesn’t depict that. So, given that, I've always configured the Prod Journal and Remote Journals to be the same size and number of journal luns but if we don't utilize a Local copy, do we really need the same size and number of journal volumes on the Prod side?
RP Journal Sizing Prod vs Remote