A RecoverPoint administrator wants to use the compression setting to save bandwidth in their environment. What will be the impact of changing the link compression setting on a Consistency Group?

Changing the link compression setting on an active Consistency Group (CG) requires the system to apply the new policy to the data replication stream. This action initiates a short synchronization process to flush any data currently in transit and ensure consistency between the source and target sites. The act of synchronization, combined with the added CPU cycles required by the RecoverPoint Appliances (RPAs) to handle the new compression or decompression tasks, results in a temporary increase in system load. This period of high load subsides once the policy change is fully applied and replication stabilizes.

A. Short initialization: Initialization is the process of creating the first full copy. Changing a link setting on an already protected Consistency Group does not trigger a new initialization.
C. Journal history will be lost: Link policies affect how data is transmitted between sites. This change does not impact the point-in-time data already stored in the journals, so history is preserved.
D. Long resynchronization: A long resynchronization, which involves a full block-by-block comparison of the volumes, is not required. The system performs a much faster "short synchronization" to apply the policy change.

1. Dell RecoverPoint Administrator's Guide 5.3, Page 168, Section: "Modifying group link policies". The guide states, "When you modify the link policies of a running group, a short synchronization is initiated on the group." This synchronization event causes the temporary load.

2. Dell RecoverPoint CL 5.3 Performance Guide, Page 13, Section: "Compression". This document explains, "Compression reduces the amount of bandwidth required for data transfer, but it increases the load on the RPAs." Enabling or changing this setting directly impacts RPA load.