I went through the below article where it clearly illustrates the below :
https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-troubleshoot-replication
Premium P20 or P30 or P40 or P50 disk 16 KB or greater 20 MB/s 1684 GB per disk
Change the tier of the disaster recovery storage disk: This option is possible only if the disk data churn is less than 20 MB/s. For example, a VM with a P10 disk has a data churn of greater than 8 MB/s but less than 10 MB/s. If the customer can use a P30 disk for target storage during protection, the problem can be solved. This solution is only possible for machines that are using Premium-Managed Disks. Follow these steps:
Go to Disks of the affected replicated machine and copy the replica disk name.
Go to this replica of the managed disk.
You might see a banner in Overview that says an SAS URL has been generated. Select this banner and cancel the export. Ignore this step if you don't see the banner.
As soon as the SAS URL is revoked, go to Configuration for the managed disk. Increase the size so that Site Recovery supports the observed churn rate on the source disk.
My question is :
If the Data disk writes bytes /sec is like 100 MB/s an average for p30 and data change rate is greater than 20 Mb/s .. What we will do in case ? Because the above solution only applies to p10 ,p20 disk with smaller size where we raise the size at the destination .
Is that i have to access the workload with the VM to find as to why such large change rate and that is only option ? How should i solve this problem .
Why i am asking this question :
I had 3 Vm's which had Recovery point generation failed and Data change rate beyond supported limits in the site recovery logs. 2 of the VM's has p10 disk and we took the call to raise the size at the destination . But the last VM has p30 disk .