Hi Nadeem, The lag between the production and DR site will always be twice the min cycle time, based on how the SRDF/A works. If you want to have a lag between your production and DR less than 15sec then you need to adjust your min cycle time at 15/2 sec. That will of course require from EMC to model the solution using an internal/partner only available tool called BCSD (they have to take btp files from your box and analyze them with that tool). The change of min cycle time has many impacts:- You need to adjust the network between your production and DR so the data of the transmit cycle of SRDF/A will be sent on time to DR before the cycle switch.- You need to monitor the cache for WP (f.e. based on the analysis you may need to enable Transmit Idle and create SRDF/A DSE Pools on both sites).  So I will agree with Paul Martin, do not proceed with the change unless you seekadvice from a Solutions Architect or a SPEED Guru.
Hello All,  Currently in the customer's environment, the min cycle time for  SRDF/A is set at default 15 secs. I have also checked the avg cycle time over a period of 6 months and its 15 secs. Hence, the R2 data lag is always 30 secs. Customer wants to decrease the R2 lag data time below 30 secs. Hence, we need to decrease the min cycle time for some of the RDF groups below 15 sec, maybe 10 sec.  My questions is how do I go about this approach and what will be the impact. I know write pending count would be high but I need to understand all other factors and the gradual approach towards this. If anyone has actually done it, would be glad to know their experience as well.
Customer looking to decrease the min cycle time for srdf/a below 15 sec