Azure Site Recovery Unresolved health

Handian Sudianto 4,431

Hello,

I have 3 server replicated to azure via ASR, one of them always have error 'Data upload blocked for the SERVER-1 '\.\PHYSICALDRIVE0, \.\PHYSICALDRIVE1' disk's replication on the source machine.'.

Even have this error and the replication health is critical but the RPO is up to date

User's image

Someone can confirm in this condition, the server is replicated or not? And how to resolve the health status?

SadiqhAhmed-MSFT 40,291 Reputation points Microsoft Employee

2024-04-25T11:05:02.0366667+00:00

@Handian Sudianto If the recovery points (RPs are available then it could be a portal glitch. I noticed that crash consistent RPs are available but app-consistent RPs are not.

This command will trigger manual app consistent snapshot:

cd C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\ and run vacp -systemlevel

See if this works. If problem persist, it is better to contact Azure technical support team for further assistance.

Hope this helps!
Handian Sudianto 4,431 Reputation points

2024-04-26T02:08:47.09+00:00

Hello,

in the replication policy the app consistency is disabled

Checked log cxps.err i found warning like this and hope somebody can explain what this error

2024-Apr-24 10:51:28 WARNING [at C:__w\1\s\host\cxpslib\requesthandler.cpp:RequestHandler::deletePutFile:649] (sid: 9205.293c502c8b0) delete file E:/PSCache/bd643efb-d31d-4fd8-b7e3-ff53ceb092cb/{FA36A2F1-38C6-4489-84F4-1908722FE63E}/3ef2f27c-54ae-5342-b272-eb9e7bb6cb7e/diffsync/62e630c6-eb47-4989-9b61-dbd4b0d43aee/pre_completed_ediffcompleted_diff_P133584041773772315_40939103_1_E133584041773772315_40939105_ME1.dat requested because there is a diff throttle 2024-Apr-24 10:52:28 ERROR [at C:__w\1\s\host\cxpslib\requesthandler.cpp:RequestHandler::ReadEntireDataAndSendThrottle:2009] (sid: 9207.293c502ea10) local ip: 10.103.248.88, local port: 9443, remote ip: 10.103.248.117, remote port: 61525 : Pair is diff throttled. Pending sync file size : 8590389316 bytes 2024-Apr-24 10:53:35 ERROR [at C:__w\1\s\host\cxpslib\requesthandler.cpp:RequestHandler::ReadEntireDataAndSendThrottle:2009] (sid: 9210.293c502a750) local ip: 10.103.248.88, local port: 9443, remote ip: 10.103.248.117, remote port: 61539 : Pair is diff throttled. Pending sync file size : 8590882708 bytes 2024-Apr-24 10:53:35 WARNING [at C:__w\1\s\host\cxpslib\requesthandler.cpp:RequestHandler::deletePutFile:649] (sid: 9210.293c502a750) delete file E:/PSCache/bd643efb-d31d-4fd8-b7e3-ff53ceb092cb/{FA36A2F1-38C6-4489-84F4-1908722FE63E}/3ef2f27c-54ae-5342-b272-eb9e7bb6cb7e/diffsync/62e630c6-eb47-4989-9b61-dbd4b0d43aee/pre_completed_ediffcompleted_diff_P133584044126550732_40940600_1_E133584044144108454_40940605_ME1.dat requested because there is a diff throttle 2024-Apr-24 10:54:31 ERROR [at C:__w\1\s\host\cxpslib\requesthandler.cpp:RequestHandler::ReadEntireDataAndSendThrottle:2009] (sid: 9211.293c502a1c0) local ip: 10.103.248.88, local port: 9443, remote ip: 10.103.248.117, remote port: 61555 : Pair is diff throttled. Pending sync file size : 8590472301 bytes 2024-Apr-24 10:54:31 WARNING [at C:__w\1\s\host\cxpslib\requesthandler.cpp:RequestHandler::deletePutFile:649] (sid: 9211.293c502a1c0) delete file E:/PSCache/bd643efb-d31d-4fd8-b7e3-ff53ceb092cb/{FA36A2F1-38C6-4489-84F4-1908722FE63E}/3ef2f27c-54ae-5342-b272-eb9e7bb6cb7e/diffsync/62e630c6-eb47-4989-9b61-dbd4b0d43aee/pre_completed_ediffcompleted_diff_P133584044703340868_40940900_1_E133584044703340868_40940902_ME1.dat requested because there is a diff throttle 2024-Apr-24 10:55:29 ERROR [at C:__w\1\s\host\cxpslib\requesthandler.cpp:RequestHandler::ReadEntireDataAndSendThrottle:2009] (sid: 9214.293c502bd90) local ip: 10.103.248.88, local port: 9443, remote ip: 10.103.248.117, remote port: 61572 : Pair is diff throttled. Pending sync file size : 8590866024 bytes 2024-Apr-24 10:55:29 WARNING [at C:__w\1\s\host\cxpslib\requesthandler.cpp:RequestHandler::deletePutFile:649] (sid: 9214.293c502bd90) delete file E:/PSCache/bd643efb-d31d-4fd8-b7e3-ff53ceb092cb/{FA36A2F1-38C6-4489-84F4-1908722FE63E}/3ef2f27c-54ae-5342-b272-eb9e7bb6cb7e/diffsync/62e630c6-eb47-4989-9b61-dbd4b0d43aee/pre_completed_ediffcompleted_diff_P133584045272401185_40941340_1_E133584045281163565_40941343_ME1.dat requested because there is a diff throttle
SadiqhAhmed-MSFT 40,291 Reputation points Microsoft Employee

2024-04-29T09:18:43.9033333+00:00

@Handian Sudianto From the logs I read this "Pending sync file size : 8590866024 bytes"

The process server has a limit to hold 8 GB of data and it will not accept more. Only when the older data gets progressed new one will come up . You can check if the bandwidth is good, or the Process server has free CPU and RAM to process more data for smoother replication.
mark wood 0 Reputation points

2024-04-29T09:25:40.7933333+00:00

Facing the challenge of unresolved health in Azure Site Recovery is like entering an arm wrestling match. Just as in arm wrestling, where two competitors engage in a test of strength, overcoming this issue requires strength, strategy, and determination.

First, assess your current setup, just as you would analyze your opponent's stance and strategy. Understand the root cause of the unresolved health status.

Next, develop a plan of action. Flex your mental muscles and strategize the best approach to resolve the issue. Perhaps you need to adjust configurations or troubleshoot connectivity.

Finally, execute your plan with determination, just as you would exert all your strength in an arm wrestling match. With perseverance and the right strategy, you'll conquer the challenge and achieve a resolved health status in Azure Site Recovery.

1 answer

Pabitra Kumar Sikdar 80 Reputation points Microsoft Employee

2024-04-25T06:10:35.7433333+00:00

Hello @Handian Sudianto

Based on the information provided, it seems that there might be an issue with the replication status of a server, possibly related to application consistency. The "latest recovery points" page is typically used to confirm the replication status, and from the screenshot, it appears that application consistency is not available.

One possible scenario for this error is that application consistency might not be enabled for the replication policy. This could lead to errors such as "Data upload blocked for the SERVER-1 '.\PHYSICALDRIVE0, .\PHYSICALDRIVE1' disk's replication on the source machine."

Another consideration is the possibility of high data change rate (CHURN), which can lead to intermittent generation of restore points. It's suggested to double-check the error message's timestamp and compare it with the restore point's timestamp for further investigation.

As a solution, you can explore high churn support options provided by Azure Site Recovery. This can help address issues related to high data change rates and ensure smoother replication processes. For more detailed information and guidance, you can refer to the Azure documentation on high churn support: https://video2.skills-academy.com/en-us/azure/site-recovery/concepts-azure-to-azure-high-churn-support.
Please sign in to rate this answer.
Handian Sudianto 4,431 Reputation points

2024-04-25T06:19:30.3033333+00:00

Hello,

How we can know if the application consistency is enabled or not? Also how to enable this?

Also i found this log on the source VM, are this error affecting the ASR replication?

Here details of the error messages
Sign in to comment

Share via

Azure Site Recovery Unresolved health

1 answer