The replication group were connected to a single RDF link across Atlantic As the invalid tracks built on R1 was over 14 millions a single srdf did not help the replication across and that did created bottleneck on the link. Adding an additional srdf link to this storage group made it reach an acceptable transfer rate   (acceptable as customer seems to have bandwidth issue)
Hello,  We have had a suspended RDFG group (SRDF/A, 1TB SharePoint, concatenated devs ) that was working fine until it went to suspended state. Replication has been resumed but since the replication is taking way too long to make the R1 and R2 devices consistence. 1. Each time the replication resume it then went to suspended state. and the transfer rate was very poor. 2. when the switch to a faster link, we had a very little improvement on the speed.  - What can be the cause of such of behaviour. - where can I direct the investigation. - Is there any other way to resume a replication so that it can sync quickly.  Message was edited by: Ericvmax
1 TB sharepoint device group is taking very long to resume after been suspended