Error 153051 Azure Site Recovery

ARINTASS 0

VSS writer failed for an application. App consistency recovery points cannot be generated. No app-consistent recovery point available for the VM in the last 510 minutes.

1 respuesta

Gao Chen 8,340 Puntos de reputación Microsoft External Staff

2025-03-03T23:41:15.1066667+00:00
Hello ARINTASS,

Welcome to Microsoft Q&A!

It sounds like you're encountering Error 153051 with Azure Site Recovery, which indicates that the VSS writer failed for an application, preventing the generation of app-consistent recovery points.

Here are some steps you can take to troubleshoot and resolve this issue:

Check the VSS Writer Status: Ensure that the VSS writers on the source machine are in a stable state. You can do this by running the vssadmin list writers command in the Command Prompt. If any writers are in a failed state, try restarting the associated services or the machine itself.

Change VSS Provider Service: Some users have resolved this issue by changing the Azure Site Recovery VSS Provider service from "Manual" to "Automatic"

Reinstall VSS Provider: If the VSS Provider service is not functioning correctly, you might need to reinstall it. Use the following commands to uninstall and reinstall the VSS Provider:

"C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Uninstall.cmd" "C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Install.cmd"

Check for High Data Change Rate: High data change rates on the source virtual machine can also cause this issue. Monitor the data change rate and ensure it is within the supported limits

If these steps don't resolve the issue, you may need to contact Azure support for further assistance.

I hope the information provided was useful!

Regards,

Gao

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Inicie sesión para calificar esta respuesta.
ARINTASS 0 Puntos de reputación

2025-03-04T09:32:54.7633333+00:00

Thank you for your answer. When checking the VSS Writers I found that ‘SQLServerWriter’ was giving an error. I restarted it and now it appears with status ‘OK’. I'm going to wait and see if that fixes the problem.

Gao Chen 8,340 Puntos de reputación Microsoft External Staff

2025-03-04T21:34:28.64+00:00

Hello again ARINTASS,

For sure, thank you for checking and for letting me know! Please do let me know if the problem persists and if it were to solve the problem, please remember to "Accept Answer" if the answer helped, so that others in the community facing similar issues can easily find the solution.

Have a great rest of the day! I will be pending for you response :D

Regards,

Gao

ARINTASS 0 Puntos de reputación

2025-03-05T16:22:50.2666667+00:00

Hi again,

The problem persists despite the issue having been resolved with the VSS writer.

Thank you in advance,

Gao Chen 8,340 Puntos de reputación Microsoft External Staff

2025-03-05T20:55:15.1033333+00:00

Hi ARINTASS,

I see, since the SQLServerWriter VSS writer is now showing a status of 'OK' but the problem persists, here are a few additional steps you can take to troubleshoot and resolve the issue:

Review the Azure Site Recovery logs for any specific errors or warnings that might provide more insight into why the app-consistent recovery points are not being generated. These logs can often be found in the Azure portal under the Recovery Services vault.

Verify that the source VM has sufficient resources (CPU, memory, disk space) to perform the VSS snapshot. Resource constraints can sometimes cause VSS operations to fail.

Ensure that the Azure Site Recovery agent on the source VM is up to date. Outdated agents can sometimes cause issues with VSS operations.

Check that there are no other backup or snapshot software running on the source VM that might conflict with Azure Site Recovery's VSS operations.

Since the SQLServerWriter was previously in an error state, check the SQL Server logs for any related errors or warnings that might provide more context.

As a last resort, you can try reconfiguring the protection for the VM in Azure Site Recovery. This involves disabling protection and then re-enabling it. Be cautious with this step as it may involve reinitializing the replication.

If these steps do not resolve the issue, it may be necessary to contact Azure support for further assistance as they can provide more detailed diagnostics and help identify the root cause of the problem.

Regards,

Gao
Inicie sesión para comentar

Use comentarios para pedir alguna aclaración, más información o mejoras de la pregunta.

Compartir a través de

Error 153051 Azure Site Recovery

1 respuesta

Su respuesta