Configure your system so that primary system activity does not exceed the capacity of the recovery site logical subsystem. You might require performance at the secondary site that is equivalent to your primary application’s performance. This could be performance when migrating work loads, or performance during a disaster recovery. If so, it is recommended that the secondary site logical subsystems have at least the same cache and NVS capacity as the primary site logical subsystems.
PPRC supports configurations where several primary site logical subsystems can funnel their updated data to a single logical subsystem on the recovery system. The number of copied primary volumes and the rate of write activity to these volumes can affect performance.
Ensure that you have a sufficient number of ESCON® or FCP paths established between the primary and secondary site logical subsystems. This is especially important in configurations where the same logical subsystems manage both primary and secondary volumes.