Coordination is only from R1 to R2. If you enable it on both sides and If there is a R1 device on your DR site which is replicating to prod site, the perf stats will be sent from R1(DR site) to R2 (Prod site).  regards, Saurabh
Does anybody know whether when using SRDF with thin provisioning the secondary sites R2 volume when added to a storage group actually needs to have the same policy defined  I am replicating a number of storage groups from one site and these as per the normal way with DR are then masked and mapped out to the DR host so are part of storage groups at the secondary site  I do not know whether to enable the same fast vp policy on the secondary sites storage group or if this make any difference as I have enabled the maintain FAST VP Coordination tick box at the source site which should maintain the same tier for the remote site as per the primary site  But do not know if this configuration is needed on the DR site when I am masking and mapping out to the DR host  The enviroment I am in has both it R2 and a seperate BCV masked to the same host in the past this has  been done usign a single storage group but recently to make it easier in a DR to just remove the BCV we have been seperating the R2 and BCV in to seperate groups each with a distinct masking view  When they were together  the group had the same policy enabled as the primary site now they are seperate not sure if adding a fast policy is needed or best pratice  Any ideas
Fast VP with SRDF