Yes it will impact all replication including the intial sync, but as I stated earlier.. it is dependent on the sum of the limits of all CG's configured.. it does not matter that no other CG is replicating.. If consistency groups with settings of ‘limited’ and ‘unlimited’run on the same RPA, the effect is that there is no limit to the outgoing throughput from the RPA. When limiting the bandwidth, ensure that groups with limited bandwidthare not configuredto run on an RPA with other consistency groups whose bandwidth is unlimited orthis feature will not work.  This can be achieved by using the ‘Preferred RPAsetting
We have just setup two new CX4 SANs in 2 sites (CLA & CRS sites). We have copied over about 1 TB of data from the old CX500 SAN (CLA site) to the CX4 SAN in the CLA site which has automatically intiated a sync b/w the RP modules in the CLA & CRS sites.  The site-to-site traffic is running at around 40 Mbs even though I have set the Bandwidth Limitation in Policy\Resource Allocation of the Consistency group to 0.5 Mb/s. Is this limitation only for the "regular" data sync only because no matter what I set the value to, the inter-site bandwidth hovers around 40 Mbps.  If I pause the transfer, the inter-site bandwidth drops to 0. Can someone pls shed some light on the subject? Thanks.
Limiting bandwidth on the initial sync b/w SANs using RP3.2