VmWare Source Machine Unable to Generate RPO

Brock Harris 0 Reputation points
2024-04-02T15:33:09.1633333+00:00

This particular server has been replicating successfully to ASR, but is now failing. We have rebooted the Appliance and the source machine and RPOs are still not being generated. Both application and crash consistent recovery points are failing. We are trying to avoid re-replicating the server if possible.User's image

Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
671 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. SadiqhAhmed-MSFT 40,291 Reputation points Microsoft Employee
    2024-04-02T20:08:30.7166667+00:00

    Hello @Brock Harris Thank you for reaching out to us on Microsoft Q&A platform. Happy to help!

    If a server that was previously replicating successfully to Azure Site Recovery (ASR) is now failing, there could be a number of reasons why this is happening. Here are some steps you can take to troubleshoot the issue:

    1. The replication logs can provide valuable information about what is causing the replication to fail. Look for any error messages or warnings that could indicate the cause of the issue from the replication logs.
    2. Make sure that the source machine is healthy and that there are no issues that could be causing the replication to fail.
    3. Check the replication settings for the source machine are configured correctly and that the machine is set up to replicate to the correct destination.

    Check the network connectivity between the replication appliance and the source machine. Make sure that there are no network issues that could be causing the replication to fail.

    1. Make sure that the replication appliance is healthy and that there are no issues that could be causing the replication to fail.

    Try to create a new recovery point. If you are still unable to generate RPOs, try creating a new recovery point. This can help identify if the issue is with the existing recovery points or with the replication process itself.

    If none of these steps resolve the issue, you may need to re-replicate the server. However, before doing so, it is recommended to try and identify the root cause of the issue to prevent it from happening again in the future.

    Please let us know if you have any other questions.

    0 comments
  2. Pabitra Kumar Sikdar 80 Reputation points Microsoft Employee
    2024-04-29T11:37:38.6333333+00:00

    Hello @Brock Harris Thank you for reaching out to us on Microsoft Q&A platform.

    Based on the error message you provided, it seems like there might be connectivity issues between the source server and the process server or between the process server and Azure. To troubleshoot this issue, I recommend following the steps mentioned in Step 2: Troubleshoot connectivity and replication issues of the document you provided. Here's a summary of the steps: 1. Check the replication status of the source machine in the Azure portal. 2. Check the replication status of the process server in the Azure portal. 3. Check the connectivity between the source machine and the process server. 4. Check the connectivity between the process server and Azure. 5. Check the replication policy settings. If you have already tried these steps and the issue persists, I suggest you check the logs for any error messages that might provide more information about the issue. If you are still unable to resolve the issue, I recommend contacting Microsoft Support for further assistance. I hope this helps! Let me know if you have any other questions.

    0 comments