Hello @Handian Sudianto Thank you for your post. Sorry for the inconvenience caused to you!
The Replication status is critical because the disk data change rate on the source virtual machine exceeded supported limits. Azure Site Recovery has limits on data change rate, based on the type of disk. Churn can be expected when VM is offline, unable to reach Azure or has a lot of changed data in a short period of time.
Based on your disk we have a limit of the amount of data writing speed:
To fix churn the best approach is to increase the disk tier to a better one that as more capacity.
If the disk or the higher tier disk still cannot resolve the issue, the machine cannot be replicated using Azure Site Recovery. Recommended Documents
- High data change rate on the source virtual machine In case of SQL Server the SQL tempdb shouldn't be replicated to azure. https://docs.microsoft.com/en-us/azure/site-recovery/exclude-disks-replication#typical-scenarios
Update:
- How can we see how big churn rate on the process server?
For Azure to Azure set up you can use our monitoring:
For VMware to Azure or Physical Servers (on-premise) to Azure you can use our Deployment Planner:
Hope this helps. Please write back to us if you have any further questions!
If the response helped, do "Accept Answer" and up-vote it