Recovery point generation failed | errorid 152006|Recovery tag generation for has failed 3 times consecutively

Question

Recovery point generation failed | errorid 152006|Recovery tag generation for has failed 3 times consecutively

Rajesh S 36

VM was stuck at Waiting for first recovery point and event Recovery point generation failed.
could you please help to fix the issue

Event Name
Recovery point generation failed.
Event Type
VmHealth
Time
8/9/2023, 12:59:14 AM
Error ID
152006
Error Message
Recovery tag generation for  has failed 3 times consecutively.
Possible causes
Failed to issue a recovery tag.
Recommendation

      This may be a transient failure. Check back after sometime (~1 hour) to see if the latest recovery points are recent enough.
      Check the latest available recovery point in the Azure portal by navigating to 'Replicated items > virtual machine' in the recovery services vault.
      For Linux Azure virtual machines, ensure the outbound traffic on port 20004 is manually opened as per the guidance of the specific Linux version.
      If the latest available recovery point is older than 2 hours, contact support.

Rajesh S 36 Reputation points

2023-08-09T14:13:22.3766667+00:00

@SadiqhAhmed-MSFT This is Azure to Azure environment replication was already enabled on that machine due to some reasons it did not generate the recovery point and then we disabled and reenabled it back but it is stuck at waiting for the irst recovery point itself and we didnt make any changes at the network level and validated the vss writer as well it is no issue but still it is not turned into the protected state could you please confirm what are logs we need checks to know the status of replication.
SadiqhAhmed-MSFT 48,466 Reputation points Microsoft Employee

2023-08-17T14:48:28+00:00

@Rajesh S Sorry for the delayed response. These are the common issues that may cause failure - https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-troubleshoot-replication#error-id-153006---no-app-consistent-recovery-point-available-for-the-vm-in-the-past-x-minutes let us know if this helps.
SadiqhAhmed-MSFT 48,466 Reputation points Microsoft Employee

2023-08-21T10:07:22.2166667+00:00

@Rajesh S Have you had a chance to see the previous response? If the suggestions were helpful, click “Accept Answer” and Up-Vote. Feel free to reach out to us if you've additional questions in this regard.
SadiqhAhmed-MSFT 48,466 Reputation points Microsoft Employee

2023-08-22T10:40:11.39+00:00

@Rajesh S We haven't heard back from you. Please reply if you have any questions in this matter and we will gladly continue the discussion.

1 answer

Your answer

Rajesh S 36 Reputation points

2023-08-09T14:13:22.3766667+00:00

@SadiqhAhmed-MSFT This is Azure to Azure environment replication was already enabled on that machine due to some reasons it did not generate the recovery point and then we disabled and reenabled it back but it is stuck at waiting for the irst recovery point itself and we didnt make any changes at the network level and validated the vss writer as well it is no issue but still it is not turned into the protected state could you please confirm what are logs we need checks to know the status of replication.
SadiqhAhmed-MSFT 48,466 Reputation points Microsoft Employee

2023-08-17T14:48:28+00:00

@Rajesh S Sorry for the delayed response. These are the common issues that may cause failure - https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-troubleshoot-replication#error-id-153006---no-app-consistent-recovery-point-available-for-the-vm-in-the-past-x-minutes let us know if this helps.
SadiqhAhmed-MSFT 48,466 Reputation points Microsoft Employee

2023-08-21T10:07:22.2166667+00:00

@Rajesh S Have you had a chance to see the previous response? If the suggestions were helpful, click “Accept Answer” and Up-Vote. Feel free to reach out to us if you've additional questions in this regard.
SadiqhAhmed-MSFT 48,466 Reputation points Microsoft Employee

2023-08-22T10:40:11.39+00:00

@Rajesh S We haven't heard back from you. Please reply if you have any questions in this matter and we will gladly continue the discussion.

Answer 1

@Rajesh S Thank you for reaching out to us on Microsoft Q&A platform. Happy to help!

Before, we start with troubleshooting, I would like to know what kind of set up it is?

Azure to Azure

VMware to Azure

Hyper-V to Azure

Is this a new set up or an old one?

Going by the error message: As it mentioned, it could be a transient error. On the other hand, I would like to know share a generalized steps to troubleshoot.

Error ID 152006 in Azure Site Recovery indicates that the recovery point generation has failed. This can happen due to a number of reasons, such as network connectivity issues, insufficient disk space, or issues with the VSS writer.

To resolve this issue, you can try the following steps:

Check the network connectivity between the source and target machines. Ensure that there are no firewalls or other network devices blocking the communication.
Check the disk space on the source and target machines. Ensure that there is enough free space to store the recovery point.
Check the status of the VSS writer on the source machine. Ensure that it is running and that there are no errors in the event log.
Check the status of the Azure Site Recovery agent on the source machine. Ensure that it is running and that there are no errors in the event log.
Check the status of the Azure Site Recovery service in the Azure portal. Ensure that it is running and that there are no issues with the service.
If the issue persists, you can try restarting the Azure Site Recovery agent on the source machine and see if that resolves the issue.

Hope this helps. Looking forward to hearing from you!

Share via

Recovery point generation failed | errorid 152006|Recovery tag generation for has failed 3 times consecutively

1 answer

Your answer